[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[wtp-jst-dev] RE: Contributing new JEE project facets
|
Title: Contributing new JEE project facets
Hello,
Please take a look at bug 149007 [1]. This bug was
created to track the progress of making JEE 5 support possible in WTP 1.5.1.
For the last few weeks there are some patches submitted
as feature requests. They were reviewed by PMC members and components leads.
After short discussion it was decided that we change
the focus for these changes to the 2.0 stream and we (SAP) work closer with the
WTP team.
One suggestion was that we provided JUnit test suite to
help proving the quality of the changes.
I have had a look at some documents regarding Automated
testing and the org.eclipse.jst.j2ee.core.tests and org.eclipse.jst.j2ee.tests
plugins.
I noticed something strange. Let's take the
org.eclipse.jst.j2ee.core.tests plugin. There are ~1300 tests defined there, but
only ~300 are executed on the central test system [2]. Why is this? What about
the other ~1000 tests?
Another question is where can I see something like
method coverage of the current tests?
Can we have also some guidelines in which direction to
improve the test cases?
Execuse me for these untidy questions, but we have to
somehow get more oriented how we can work together with you in the best way
to contribute the JEE 5 support.
Any guidance by you would be
helpful.
Greetings
Kaloyan
Hello,
SAP adopts the Eclipse platform in
the SAP Netweaver platform. The next major release of the SAP Netweaver will be
based on WTP 1.5. One of the critical requirements is JEE 5 support. Since WTP
does not have JEE 5 support for the 1.5
release, we have to implement this feature ourselves.
The natural approach that we want to
follow is to extend the j2ee project facets with new versions (ejb 3.0, web 2.5,
etc.) in plugins outside WTP. The project facets framework provides enough
functionality to implement this. But we face problems with the current
implementation of the j2ee plugins. There are lots of hardcoded version checks
(project facet versions) inside WTP code. This prevents new versions of the j2ee
project facets to work correctly, because they cannot extends certain program
logic inside WTP. One possible solution for this problem is to define new
extension points in the j2ee plugins that remove the hardcoded logic and deliver
extensibility mechanisms.
So, the problem we face with
extending WTP 1.5 in the JEE 5 domain can be
separate in two main tasks:
1) Define new extension points
inside WTP code to replace hardcoded logic.
2) Define new j2ee project facet versions and
make them use the new extension points (defined in 1) to implement properly the
new program logic. This can be done in plugins outside WTP.
We can provide the necessary
development resources for implementing the two tasks along with the extensions
supporting the current functionality. We would like to contribute the changes to
WTP. We want to target the changes of Task No.1 for the 1.5.1 release. For Task
No.2 we do not have strict requirements. If there is interest we can contribute
the changes for 1.5.1 or later versions.
We are aware of the 1.5.1 change
policy. We can send the changes as independent backward-compatible patches that
can be integrated with the code after PMC approval. All patches will be
requested as hot bugs.
The main benefit of the suggested
changes is that vendors will be more indepenent from the WTP schedule when
supporting critical features regarding new J2EE specification versions.
Moreover, this will reduce WTP's effort to adopt JEE 5 and future specification
requirements.
I want to request the PMC members to
evaluate our proposal and give their opinion.
Best Regards,
Kaloyan
Raev
JEE Tools
Team
SAP
Labs
T +359 2 9157
416