[
https://jira.jboss.org/jira/browse/JBIDE-4634?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4634:
------------------------------------
I'm still not sure exactly how we should "publish" something from a generic
BPEL project. What is the structure of this project? What are we assuming about this
project structure? What does the Module Factory look like? Does it expose the resources
properly?
Does the user have any way to customize this project type? Are we expected to know which
folders to know to expose for the zipped / published version of the file? How do we know
what to call this output file? (Is it a .jar? a .bpel? A .ear?)
Without these details and a functioning module factory that exposes the proper resources,
I see no way to properly handle this module and know how to assemble it.
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