[Design of JBoss ESB] - Re: Consistent handling of HTTP response header across HTTP
by dward
Okay, I have the following working in my local copy, and I can commit it to trunk ASAP if people agree. I think this is the best approach:
SOAPClient:
- response content added via payloadProxy [EXISTS - UNCHANGED]
- response headers added to message properties [MISSING - ADDED]
Wise SOAPClient:
- response content added via payloadProxy [EXISTS - UNCHANGED]
- response headers added to message properties [MISSING - UNCHANGED (reason is that there is no apparent API availabile in Wise to get out the http response headers)]
routing.HttpRouter:
(ignored since it is deprecated)
routing.http.HttpRouter:
- response content added via payloadProxy [EXISTS - UNCHANGED]
- response headers added to message properties [MISSING - ADDED]
- response headers available in body location HttpResponse.RESPONSE_KEY [EXISTS - UNCHANGED (left for backward compatibility)]
SOAPProxy:
(wraps use of routing.http.HttpRouter so it's all good)
SOAPProcessor:
- response content added via payloadProxy [EXISTS - UNCHANGED]
- response headers added to message properties [EXISTS - UNCHANGED]
HttpGatewayListener->HttpDispatchServlet->HttpMessageComposer
- payloadProxy body written to response output [EXISTS - UNCHANGED]
- message properties added to response headers [MISSING - ADDED]
- response headers available in message property HttpMessageComposer.HTTP_RESPONSE_HEADER_MAP [EXISTS - UNCHANGED (left for backward compatibility)]
JBossRemotingGatewayListener -> JBossRemotingMessageComposer
- payloadProxy body written to response output [EXISTS - UNCHANGED]
- message properties added to response headers [EXISTS - UNCHANGED]
Modified files:
product/rosetta/src/org/jboss/soa/esb/actions/routing/http/HttpRouter.java
product/rosetta/src/org/jboss/soa/esb/listeners/gateway/HttpGatewayListener.java
product/rosetta/src/org/jboss/soa/esb/listeners/gateway/HttpMessageComposer.java
product/rosetta/src/org/jboss/soa/esb/listeners/gateway/JBossRemotingGatewayListener.java
product/rosetta/src/org/jboss/soa/esb/message/ResponseHeader.java
product/services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SOAPClient.java
product/services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SOAPProcessor.java
product/services/soap/src/test/java/org/jboss/soa/esb/actions/soap/SOAPClient_Response_UnitTest.java
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241361#4241361
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241361
16 years, 5 months
[Design of JBoss jBPM] - One par file with multiple process definition ??
by chawlaashish26@gmail.com
Hi All,
I have a general question on the jbpm jpdl process definition deployment.
As I understand, a par file contains the process definition and its related java code. If I have multiple process definitions defined in a jbpm project, I can deploy each of them individually from the deployment tab, or ant task...but there will be multiple par files (as many processes I have).
But this has a drawback that anytime I need to create a new process, I have to make sure that the existing classes work with the new process. Its basically more tightly coupled with the java code.
What I am trying to find out is, if its possible to include multiple process definition.xml in the same par files. Or separate the java code from the xml definitions.
I dont want to deploy the same java code with every par file. I am trying to have some generic classes written which *will* work with all process definitions, so that deployment wise it should be easy and I just have to deploy the workflow xml ONLY.
Any thoughts? Would appreciate any feedback.
Thanks
Ashish
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241322#4241322
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241322
16 years, 5 months