[jboss-user] [JCA] - Re: Discovery of JCA ConnectionFactory without resource-ref

Thanks for your feedback, Vicky. The trick is to define a res-ref-name not starting with ra nor jdbc in jboss-web.xml. Once I avoided using the ra JNDI context, my connection factories became accessible without declaring them in web.xml View the original post :

[jboss-user] [JNDI and Naming] - Discovery of JCA ConnectionFactory without resource-ref conf

Hi I have a JBoss 5.1 server with some JCA connectory deployes as RAR files. Each connector has its -ds.xml file holding the jndi-name declaration of the connector. Now I can load my ConnectionFactories from a web application (Servlet in a WAR), if I put a resource-ref declaration into the

[jboss-user] [JCA] - Discovery of JCA ConnectionFactory without resource-ref conf

Hi I have a JBoss 5.1 server with some JCA connectory deployes as RAR files. Each connector has its -ds.xml file holding the jndi-name declaration of the connector. Now I can load my ConnectionFactories from a web application (Servlet in a WAR), if I put a resource-ref declaration into the

[jboss-user] [JBossWS] - Re: Jar file for org.jboss.ws.core.soap.SAAJMetaFactoryImpl.

May I suggest that you log into JIRA and vote for the ticket https://jira.jboss.org/jira/browse/JBWS-2335 So maybe somebody of the JBossWS team will work on this issue reasonably soon. (the workaround I described above lead to new errors when I tried to call my web service). Cheers, Silvano

[jboss-user] [JBossWS] - Re: Jar file for org.jboss.ws.core.soap.SAAJMetaFactoryImpl.

Hi Thorsten I had the same issue after installing jbossws-metro-3.0.3 into jboss-4.2.3.GA. I then copied jbossws-client.jar from the client directory of the original jboss-4.2.3.GA distribution, and placed it into the server/default/lib directory (after applying jbossws-metro-3.0.3). Then the

[jboss-user] [JBossWS] - Re: Jar file for org.jboss.ws.core.soap.SAAJMetaFactoryImpl.

I filed a JIRA ticket: https://jira.jboss.org/jira/browse/JBWS-2335 View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4180227#4180227 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4180227

[jboss-user] [JBossWS] - SOAP calls done with native stack blocked by SmartDefense fi

Hi I would like to inform you of an issue I encountered while deploying JBoss and JBossWS (native) at a bank. The bank uses the SmartDefense intrusion detection system, and SmartDefense blocks SOAP calls done via the JBossWS native stack because of a non-compliant HTTP header. The only details

[jboss-user] [JBossWS] - Re: org.jboss.ws.WSException

Hi. I was able to work around this issue by naming all my WSDL request parameters as arg0, arg1 etc (instead of id, name in your example), and by naming by response parameter as result. Probably there is a cleaner solution using JAXB annotation, which allows you to name parameters the way you

[jboss-user] [JBossWS] - org.jboss.ws.WSException: arg0 is not a valid property on cl

I'm getting the following error in deploying a simple document/literal web service with jbossws-3.0.1-native-2.0.4.GA on jboss 4.2.2.GA. org.jboss.ws.WSException: arg0 is not a valid property on class ... Full stack trace: | 09:22:41,781 ERROR [MainDeployer] Could not start deployment:

[jboss-user] [JBossWS] - Re: org.jboss.ws.WSException: arg0 is not a valid property o

Hi Thomas I'm following the topdown model and so I've created the WSDL first ... I tried adding @WebMethod and @WebParam annotations, but that did not solve my problem. Or can you give me an example of the jaxb annotations you are suggesting? Regards, Silvano View the original post :