That worked, thanks.
I have a question about how you would recommend handling ws-security and ws-transaction information. How would you recommend this be added to the SOAP Header?
I have been working with JBoss Transaction XTS component, and have created a quickstart showing ws transactions business activity. But I had to add the transaction context to the SOAPHeader and invoke the web service through my own custom action. I would rather use SOAPClient.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160700#4160700
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160700
anonymous wrote : Yes, making the deployments in a profile available to the runtime is a separate step. Just updating a profile does not imply that the current server view is going to change.
Makes sense. Adding calls to MainDeployer after I add/remove a deployment from the profile, and then doing a MainDeployer.process() at the end of the scan gets deploy-hasingleton deployment working. At least with the basic profile service. I'll see what happens with the repository based version.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160658#4160658
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160658