-
1. Re: Create new deployer to deploy java first jms transport w
ropalka Nov 11, 2009 5:30 AM (in response to jim.ma)"jim.ma" wrote:
If this can be deployed without web.xml, it will be more quick and flexible.Can we create another deployer to do this job ?
IMHO this is not good idea :( Why complicate things? I don't see the problem web.xml have to be provided. -
2. Re: Create new deployer to deploy java first jms transport w
asoldano Nov 11, 2009 5:31 AM (in response to jim.ma)I agree on having another deployer for jms endoints, as we said on IRC last week.
-
3. Re: Create new deployer to deploy java first jms transport w
asoldano Nov 11, 2009 5:33 AM (in response to jim.ma)"richard.opalka@jboss.com" wrote:
"jim.ma" wrote:
If this can be deployed without web.xml, it will be more quick and flexible.Can we create another deployer to do this job ?
IMHO this is not good idea :( Why complicate things? I don't see the problem web.xml have to be provided.
why would you need a servlet for a jms only endpoint? -
4. Re: Create new deployer to deploy java first jms transport w
asoldano Nov 11, 2009 7:55 AM (in response to jim.ma)The point here is that we need to deploy cxf jms endpoint independently from the http endpoint, which might not even be provided. For this reason we need a mean of processing the jbossws-cxf.xml at deplyo time, instead of when initializing the CXFServletExt we have (that extends the CXF servlet). Basically we need a correct integration point for jms transport.
So, Richard is right in saying that adding a new deployer might not be a viable solution as it will break the current container integration.
A proposal for doing this might then be to add another deployment aspect for doing what Jim originally though about doing in the new deployer (parsing the jbossws-cxf.xml, installing the jms only endpoint, start the cxf bus, etc.) and leave the generated webapp there just to serve wsdl requests (in case of jms only endpoints of course). -
5. Re: Create new deployer to deploy java first jms transport w
jim.ma Nov 24, 2009 10:24 PM (in response to jim.ma)Looked at the current deployment code again , it seems adding another DA can not make this work : if there is no web.xml , the WSTypeDeployer will not generate a Deployment type for the jms endpoint . Then the WSDeploymentAspectDeployer will not trigger the DAs to process this ws deployment. So creating another DeploymentType for the jms endpoint can make this work , but it is kind of deployment type concept violation.
-
6. Re: Create new deployer to deploy java first jms transport w
ropalka Nov 25, 2009 4:10 AM (in response to jim.ma)Your investigation Jim is correct.
I'd postpone this task until we'll meet
each other and will discuss this issue
face to face. Take a look to other tasks, please.