[
https://jira.jboss.org/jira/browse/JBIDE-4634?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4634:
------------------------------------
I'll apply the patch, but I am absolutely baffled as to how this is supposed to work.
For example, even with the the patch, if I create a BPEL project and add a text file to
it, the module does not show up in the add / remove section. The module simply isn't
created by its module factory because it lacks a BPEL file. It seems this is by design, as
the module factory specifically ignores the project if it has no BPEL file. But it seems
counter intuitive to a user who just made a BPEL project that nothing is showing up.
In addition to this, the project is a modulecore project but completely lacks a
.settings/org.eclipse.wtp.component.xml file. This means there's no mapping at all as
to what source or binary files should be exposed by the module to be published. Also
notable is that if I manually add a component.xml file, any mappings I put in it are 100%
ignored.
Additionally, I made a project with the following structure:
- BP5
- BP5/folder3
- BP5/folder3/test9.file
- BP5/MyFolder
- BP5/MyFolder/some.bpel
- BP5/MyFolder/test.file
The output of this was a jar of the following structure:
BP5.jar
BP5.jar/MyFolder
BP5.jar/MyFolder/some.bpel
Not only did it ignore the folder3 and whatever files were inside, it ALSO ignored the
MyFolder/test.file, which was in the same folder as a bpel file.
This is an *extremely* ill defined module factory. As a user of this "BPEL
Project" I honestly have no idea what files I'm supposed to include, where I
should add them, whether the files I add will be included in the resultant jar, or pretty
much anything about it at all. If *I* have no idea how to use it, I find it very very
difficult to imagine any other user will understand it either.
I simply do not understand the usecase of a user creating a "BPEL project" ,
potentially filling it with 100 files, and then when "publishing" it, asking for
only 2 of the files to be included in the zip. I *could* understand that if the user
specifically overrode the defaults to declare that as the desired publishing structure,
but as a default, to only include a .bpel file, one must wonder why the user needs a bpel
project in order to house one single bpel file and then zip it up.
I am completely baffled.
Update Jboss AS runtime type definition to support BPEL module type
-------------------------------------------------------------------
Key: JBIDE-4634
URL:
https://jira.jboss.org/jira/browse/JBIDE-4634
Project: Tools (JBoss Tools)
Issue Type: Task
Components: JBossAS
Reporter: Denny Xu
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.0.2.GA, 3.1.0.M3
Attachments: patch.txt
Rob, Gray and John agree to add the support to define a BPEL specific project type so
that BPEL project can be deployed separately instead of being deployed with ESB project
for M1, the patch only update eap5.0, JBossAS5.0 and JBossAS5.1 runtime types to support
bpel module, can you apply this patch into your AS plugins?
--
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