[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4320) ESB Projects does not respect WTP module dependency rules
[
https://jira.jboss.org/jira/browse/JBIDE-4320?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4320:
------------------------------------
As I've said before, one of the goals of JBoss code is to not make anything
"magical".
We'd like to make it easy for the user to have ultimate control and to understand
whats happening because they understand their requirements better than we do. This means
that the user might change his output folder, republish, and find all his .class files not
there. Then he can go to the "Module Assembly" page and change the mapping
himself.
In the future we will add in these automatic changes, but the most important thing now is
having something easy for the user to understand that is CONTROLLABLE by the user. This is
a VERY different way of doing things than most of WTP does it which is why it doesn't
matter how WTP does it. Our goal is to do it this way.
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: Rob Stryker
Priority: Blocker
Fix For: 3.1.0.M3
Attachments: JBIDE-4320a.patch
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