[
https://jira.jboss.org/jira/browse/JBIDE-4634?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-4634:
---------------------------------
Rob, I have defined a ModuleFactory and a publisher for bpel project in my code, so if you
apply the patch and then the bpel project deployment will work, we really know which
folder should be packaged for ODE runtime.
Burr will do a demo in webinar Jul 22, so we must provide a full function BPEL tools with
being able to deploy separately, for now, I think we should not debate the modulefactory
and generic BPEL project type, we don't have much time to for now, what the urgent
thing currently is to make sure that Burr can do the bpel demo successfully. I think we
can revert the patch if we decided not to do it this way, but for now, we need to do it by
this way, at least temporarily.
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