[JBoss Messaging] - Is scoped loader-repository feature unusable now
by chip_schoch
I see my thread from yesterday and the weekend has disappeared from this forum. Sorry if I breeched protocol somehow.
Anyway, my question was and continues to be, is it a feature that we can no longer scope a loader repository in an MBean that uses JBM? Having my service code in the main repository makes it difficult to do iterative development, as I prefer to leave JBossAS running and to redeploy with changes, debugging from Eclipse using the remote debugging and the IDE 3.1 deploy feature. Without the scoped loader I must restart the server each time I redeploy a service. I am having trouble particularly with a service that has a jbpm.cfg and associated hibernate.cfg file in my service classpath. It seems the second time I deploy this service it is unable to read the xml files.
This is in addition to the issue I mentioned in my last post (that was removed) that not scoping the loader repository renders the Log4j TCLFilter inoperable, so I cannot separate my service logging into constituent files. Any insight would be sincerely appreciated, as if this functionality is indeed the desired feature then I must pursue workarounds to the obstacles it has presented me with.
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051328#4051328
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051328
18Â years, 10Â months
[JBossWS] - Re: SWA / MTOM attachments
by heiko.braunï¼ jboss.com
Sreedhar, MTOM and SwA are two diffrent things. Both deal with attachments but in different manner. Actually when talking about attachments you'll encounter SwA, SwARef and MTOM/XOP.
SwA has interop issues which SwARef did solve and MTOM relieves the interposed SOAP processors from having to deal with resource consumption while processing messages in transit.
However, looking at your detailed report (thanks, that simplifies things a lot) i can see two things:
anonymous wrote :
| org.jboss.ws.binding.BindingException: Mime type text/xml not allowed for parameter mimepart allowed types are [application/xml]
|
anonymous wrote :
| URL temp = new File("resources/jaxrpc/samples/swa/attach.xml").toURL();
|
See first one states that the endpoint does only accept attachment of the type "application/octet-stream". Looking at your samples code in the second quote, you create a URL to a *.xml file. The JAF API will create a DataHandler instance with the content-type 'text/xml' from that, which then would be submitted.
If you change the client to use the right content-type everything works fine. Please consult the JAF API for further information on this topic.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051323#4051323
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051323
18Â years, 10Â months