6:28 p.m.
create ws stack integration subprojects
---------------------------------------
Key: BPEL-249
URL: http://jira.jboss.com/jira/browse/BPEL-249
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Engine
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:11 a.m.
New subject: [JBoss JIRA] Updated: (BPEL-249) create ws stack integration subprojects
[ http://jira.jboss.com/jira/browse/BPEL-249?page=all ]
Alejandro Guizar updated BPEL-249:
----------------------------------
Description:
In order to publish document web services in addition to rpc, we need access to the WSDL
definitions deployed with the service. Neither JAX-RPC nor WSEE define a standard means to
retrieve the WSDL definitions. Luckily, This information can be retrieved from the JAX-RPC
MessageContext object in an implementation-dependent manner.
For this reason, a few subprojects will be introduced to isolate the JAX-RPC
implementation dependencies. Specifically, the current target JAX-RPC implementations
are:
JBoss WS4EE (JBoss AS 4.0.3)
JBoss WS 1.0 (JBoss AS 4.0.4 and 4.0.5)
JBoss WS 1.2 (JBoss AS 4.2.0)
Porting the project to other app servers requires two things:
1) Implementing interface org.jbpm.bpel.integration.server.EndpointMetadataLookup
2) Registering the new implementation in the map named jbpm.bpel.endpoint.metadata.lookups
in jbpm.cfg.xml
create ws stack integration subprojects
---------------------------------------
Key: BPEL-249
URL: http://jira.jboss.com/jira/browse/BPEL-249
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Engine
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 GA
In order to publish document web services in addition to rpc, we need access to the WSDL
definitions deployed with the service. Neither JAX-RPC nor WSEE define a standard means to
retrieve the WSDL definitions. Luckily, This information can be retrieved from the JAX-RPC
MessageContext object in an implementation-dependent manner.
For this reason, a few subprojects will be introduced to isolate the JAX-RPC
implementation dependencies. Specifically, the current target JAX-RPC implementations
are:
JBoss WS4EE (JBoss AS 4.0.3)
JBoss WS 1.0 (JBoss AS 4.0.4 and 4.0.5)
JBoss WS 1.2 (JBoss AS 4.2.0)
Porting the project to other app servers requires two things:
1) Implementing interface org.jbpm.bpel.integration.server.EndpointMetadataLookup
2) Registering the new implementation in the map named
jbpm.bpel.endpoint.metadata.lookups in jbpm.cfg.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:51 p.m.
New subject: [JBoss JIRA] Resolved: (BPEL-249) create ws stack integration subprojects
[ http://jira.jboss.com/jira/browse/BPEL-249?page=all ]
Alejandro Guizar resolved BPEL-249.
-----------------------------------
Resolution: Done
Created jbossws4ee, jbossws10 and jbossws12 subprojects under jbpm.3/bpel
create ws stack integration subprojects
---------------------------------------
Key: BPEL-249
URL: http://jira.jboss.com/jira/browse/BPEL-249
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Engine
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 GA
In order to publish document web services in addition to rpc, we need access to the WSDL
definitions deployed with the service. Neither JAX-RPC nor WSEE define a standard means to
retrieve the WSDL definitions. Luckily, This information can be retrieved from the JAX-RPC
MessageContext object in an implementation-dependent manner.
For this reason, a few subprojects will be introduced to isolate the JAX-RPC
implementation dependencies. Specifically, the current target JAX-RPC implementations
are:
JBoss WS4EE (JBoss AS 4.0.3)
JBoss WS 1.0 (JBoss AS 4.0.4 and 4.0.5)
JBoss WS 1.2 (JBoss AS 4.2.0)
Porting the project to other app servers requires two things:
1) Implementing interface org.jbpm.bpel.integration.server.EndpointMetadataLookup
2) Registering the new implementation in the map named
jbpm.bpel.endpoint.metadata.lookups in jbpm.cfg.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:47 a.m.
New subject: [JBoss JIRA] Closed: (BPEL-249) create ws stack integration subprojects
[ http://jira.jboss.com/jira/browse/BPEL-249?page=all ]
Alejandro Guizar closed BPEL-249.
---------------------------------
create ws stack integration subprojects
---------------------------------------
Key: BPEL-249
URL: http://jira.jboss.com/jira/browse/BPEL-249
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Engine
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 GA
In order to publish document web services in addition to rpc, we need access to the WSDL
definitions deployed with the service. Neither JAX-RPC nor WSEE define a standard means to
retrieve the WSDL definitions. Luckily, This information can be retrieved from the JAX-RPC
MessageContext object in an implementation-dependent manner.
For this reason, a few subprojects will be introduced to isolate the JAX-RPC
implementation dependencies. Specifically, the current target JAX-RPC implementations
are:
JBoss WS4EE (JBoss AS 4.0.3)
JBoss WS 1.0 (JBoss AS 4.0.4 and 4.0.5)
JBoss WS 1.2 (JBoss AS 4.2.0)
Porting the project to other app servers requires two things:
1) Implementing interface org.jbpm.bpel.integration.server.EndpointMetadataLookup
2) Registering the new implementation in the map named
jbpm.bpel.endpoint.metadata.lookups in jbpm.cfg.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6518
days inactive
6937
days old
3 comments
1 participants
participants (1)
-
Alejandro Guizar (JIRA)