October 2008 - jbossws-users - Jboss List Archives

[JBossWS] - Re: Throws exception in WS (back to remote client) without g

by mjhammel

A follow up, just in case anyone else needs the info. I ignored this problem for quite some time and finally decided to return to it today. I finally figured out how to tweak log4j to hide those soap fault messages that come from my application throwing an exception. In the jboss-log4j.xml file (in my case, under server/default/conf), I added these lines at the bottom of the file: | <category name="org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS"> | <priority value="FATAL"/> | </category> | I just had to dig around to find the right category name for these messages. It just took awhile before I could find it. Hope that helps anyone with a similar concern. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186138#4186138 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186138

15 years, 5 months

1
0
0 / 0

[JBossWS] - Re: Stateless Session EJB Endpoint (JBossWS Native)

by tperrigo

Yes, that's correct; sorry, I should have mentioned that I posted to the EJB3 forum. Once the WSKernelLocator issue was resolved by the removal of one of the duplicate files, I tried removing the web service annotations from my EJB, making it just a simple stateless session bean, to see if I could then do a JNDI lookup. I'm still getting a ClassCastException, though. I left the topic open in this forum, though, just in case anyone knew of any EJB-related problems from projects created using the ant tasks provided with the JBossWS Native distribution. Thanks, Tim View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186126#4186126 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186126

15 years, 5 months

1
0
0 / 0

[JBossWS] - Re: Stateless Session EJB Endpoint (JBossWS Native)

by PeterJ

Looks like this discussion is being continued at: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186101 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186124#4186124 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186124

15 years, 5 months

1
0
0 / 0

[JBossWS] - Diff. between web.xml and web.xml.org?

by pxstein

When I deploy a web service then in the JBoss WAR directory there are suddenly 2 web.xml files: - web.xml and - web.xml.org The web.xml.org looks like my original descriptor while web.xml changed significantly. What is the difference? Peter View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186116#4186116 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186116

15 years, 5 months

1
0
0 / 0

[JBossWS] - Error "Canot get target bean instance" when calling a web se

by pxstein

When I try to call a previously successful deployed web service then I get an error: Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Canot get target bean instance at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:171) at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:94) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:240) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210) at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:103) at $Proxy24.sendObj(Unknown Source) at com.mycomp.testWsServiceClient.main(testWsServiceClient.java:29) What is the problem? Peter View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186115#4186115 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186115

15 years, 5 months

1
0
0 / 0

[JBossWS] - Re: Stateless Session EJB Endpoint (JBossWS Native)

by tperrigo

I removed the duplicate jbossws-container-jboss-beans.xml from the deploy directory of my server and the "WSKernelLocator already installed" error went away, but I am still getting the ClassCastException when I do a JNDI lookup on my EJB. I really have no idea what I'm doing wrong...everything seems to deploy without issue. If anyone has any suggestions, I would be most appreciative! Thanks, Tim View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186102#4186102 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186102

15 years, 5 months

1
0
0 / 0

[JBossWS] - Hot deployment problems using XFire or Axis2

by jluna

Hi, I'm deploying web services applications but the changes do not take effect until the JBoss is restarted. The JBoss I'm using is JBoss 4.0.4 with XFire 1.2 or Axis 2 for the services. This problem only happens to me only with web services. With others applications hot deployments are doing ok, so I know is something related to the soap stacks I'm using (XFire, Axis). Any idea how can I fix this? If I migrate my applications to EJB3 with JBoss 4.0.5 will this keep happening to me? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186087#4186087 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186087

15 years, 5 months

1
0
0 / 0

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

by alessio.soldano＠jboss.com

First of all, sorry for the late reply; btw this thread could have also be in the JBossWS-Metro forum. Anyway, I'm looking at this topic and the related issue (JBWS-2335): - the jbossws-client.jar is correctly removed by the jbossws-metro installation script because that's the native stack client artifact. You should get a jbossws-metro-client.jar artifact both in client and server/default/deploy/jbossws.sar (assuming you're using jbossws-metro 3.0.3 and the default server configuration). Restoring the jbossws-client.jar to any position in the server cannot be a solution, as you mix different implementations of the same things - the javax.xml.soap.MetaFactory implementation to be used with Metro stack is com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl . So the problem here is with the server trying to look for org.jboss.ws.core.soap.SAAJMetaFactoryImpl which of course is not available when the Metro stack is installed. You should not have the jboss-saaj.jar lib in you classpath as that pulls in the native soap MetaFactory through the META-INF/services provide system. - the jboss-saaj.jar is correctly removed from the jboss server/default/lib by the JBossWS-Metro installation. The right SAAJ library for this stack is installed instead (saaj-impl.jar) under server/default/deploy/jbossws.sar/ This said, if you didn't do this way before, I suggest starting from a vanilla jboss-4.2 distribution and then run the installation script. I'd also suggest using the default configuration or checking the jbossws-deploy.conf file in the configuration you want to use before running the installation script because of this issue https://jira.jboss.org/jira/browse/JBWS-2377 . If you still have the issue, could you please attach a small testcase to JBWS-2335 so that we can reproduce the problem? I suspect this can be related to JBWS-2377 as our Hudson instance daily runs the jbossws-framework testsuite against JBoss 4.2.3.GA after having installed the binary distribution (the one you get from the download page once the release is out) on its default configuration. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186070#4186070 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186070

15 years, 5 months

1
0
0 / 0

[JBossWS] - Re: jax-ws soap protocol handler and white space.

by mignaak

It works fine on websphere 6.1, which has axis2 jax-ws runtime. Any help would be appreciated. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186015#4186015 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186015

15 years, 5 months

1
0
0 / 0

[JBossWS] - Re: Propagate security context to second webservice call

by yousuf.raza

Again continuing this discussion with myself. One way I guess to solve this issue would be to use handlers. One picks up the credential information from the soap header and when the response is sent another handler adds the header fields. This way the second webservice will try to authenticate against the headers added by my handler. Would this be a correct solution? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185930#4185930 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185930

15 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users October 2008