[
https://jira.jboss.org/jira/browse/JBIDE-4320?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4320:
------------------------------------
No. We're still investigating the motivations of the JEE Tools behind bunches of their
code to decide exactly what is necessary here. For example, JEE Tools uses the
org.eclipse.wst.common.modulecore.componentimpl extension point to make their own virtual
component type. The question here is why.
They then make use of some of this functionality to extend VirtualArchiveComponent (?),
and then make use of both in their deployable factory.
Before writing any code we're investigating exactly what their motivations are. It
seems large portions of it have to do with setting up the classpath and getting validators
involved. While we realize this is unncessary for a first stage, we're trying to
figure out which portions of the code are dated and unnecessary, which parts are simply
done in a convulated and circuituous way, and which are the real meat and potatoes.
Also, without a fully-functioning dependency page (for a myriad of reasons) progressing
here wouldn't be the smartest idea this week. Perhaps next week.
ESB Projects does not respect WTP module dependency rules
---------------------------------------------------------
Key: JBIDE-4320
URL:
https://jira.jboss.org/jira/browse/JBIDE-4320
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.GA, 3.0.1.GA
Environment: Windows XP, Eclipse Ganymede 3.4.2 (M20090211-1700)
Reporter: Vincent Girard-Reydet
Assignee: Denny Xu
Priority: Blocker
Fix For: 3.0.2.GA, 3.1.0.M2
It is not possible to include modules as dependencies of a JBossESB module. The expected
behaviour is that ESB modules should behave as EAR modules.
For example, if I want to mimick the webservice_consumer quickstart structure using WTP
projects, I expect to end-up with 2 projects :
- an ESB project
- a Dynamic Web Module project, set as dependency of the ESB project
I expect to have the .war archive copied at the root of the ESB archive, but:
1. it is not possible to configure dependencies with graphical tools (in the project
properties)
2. Manually editing the org.eclipse.wst.common.component file to add the dependency solve
nothing to the problem.
The same applies for EJB/EJB3 projects (to mimick the helloworld_service quickstart), JPA
projects and Utility projects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira