July 2007 - jbossws-users - Jboss List Archives

[JBossWS] - Re: jb0ss4.2.0, JAX-WS2.0 deployment exception

by marcelvanvelzen

I encountered the same error when I had the same webmethod in two different classes with different parameters. Renaming the webmethod names solved this problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069313#4069313 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069313

17 years, 5 months

1
0
0 / 0

[JBossWS] - Problem with encoding '§' character ((char)167)

by amalkovskiy

I have a simple DTO object: public class TestDTO { private String name; public String getName() { return name; } public void setName(String name) { this.name = name; } } and q simple web-service method: public String test(TestDTO t) { String string = "Hello " + t.getName() + " special char = " + (char)167; System.out.println(string); System.out.println(string.length()); return string; } When I use this method TestDTO t = new TestDTO(); t.setName("Test §"); String str = entitySrv.test(t); System.out.println(str); I receive a string "Hello Test ?§ special char = §" instead "Hello Test § special char = §". I saw that 'B' before '§' is added by JAXB when this object is being marshalled to XML. But in a request to the server a message looks like: <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header/> <env:Body> <ns1:test xmlns:ns1="http://services.workflow.midtier.complinet.com/"> <arg0> Test ???§ </arg0> </ns1:test> </env:Body> </env:Envelope> Inside the web-service method the field name is "Test ?§" instead of "Test §". It looks like double encoding of '§' character. I use JBossWS 1.2.1.GA and JBoss 4.2.0GA. Regards, Alexey View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069307#4069307 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069307

17 years, 5 months

1
0
0 / 0

[JBossWS] - BASIC Authentication with jbossws-2.0.0.GA

by fheldt

I had some time to spend and did a short test of jbossws-2.0.0.GA (under jboss-4.2.1.GA). Most Webservices worked like under jbossws-1.2.0, but then i found a big problem. A secured SLSB that worked without a problem with a .NET 2.0 Client stopped working :-( I always get "Authentification failed" under jbosss-2.0.0.GA. | @Stateless | @WebService | @SOAPBinding( | style=SOAPBinding.Style.RPC, | use=SOAPBinding.Use.LITERAL | ) | @SecurityDomain("myRealm") | @RolesAllowed({"Admin", "Operator", "User"}) | @WebContext(authMethod="BASIC", transportGuarantee="NONE", secureWSDLAccess=false) | public class WebServiceEJB implements WebServiceIf | { | ... | } | Any hints what has changed here? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069198#4069198 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069198

17 years, 5 months

1
0
0 / 0

[JBossWS] - Transaction Not Allowed

by subramaniam.venkat

Hello All, I have exposed an SLSB as an web-service. There is no transaction on this SLSB which i have implemented. But this SLSB makes calls to Springs Beans on which transaction has been implemented. I am getting the below error and i am not able to find a reason for this. I am using Jboss-4.0.3-SP1 and JDK142. Can someone give me some pointer. Thanks in advance, Subramaniam V | java.rmi.ServerException: EJBException:; nested exception is: | javax.ejb.EJBException: Transaction not allowed | at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:352) | at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:125) | at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93) | at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:613) | at org.jboss.ejb.Container.invoke(Container.java:894) | at sun.reflect.GeneratedMethodAccessor148.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:155) | at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:104) | at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:179) | at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:165) | at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) | at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) | at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:169) | at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) | at $Proxy98.create(Unknown Source) | at sun.reflect.GeneratedMethodAccessor322.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at org.jboss.net.axis.server.EJBProvider.makeNewServiceObject(EJBProvider.java:140) | at org.jboss.axis.providers.java.JavaProvider.getNewServiceObject(JavaProvider.java:280) | at org.jboss.axis.providers.java.JavaProvider.getServiceObject(JavaProvider.java:131) | at org.jboss.axis.providers.java.JavaProvider.invoke(JavaProvider.java:335) | at org.jboss.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:73) | at org.jboss.axis.SimpleChain.doVisiting(SimpleChain.java:160) | at org.jboss.axis.SimpleChain.invoke(SimpleChain.java:123) | at org.jboss.axis.handlers.soap.SOAPService.invoke(SOAPService.java:560) | at org.jboss.axis.server.AxisServer.invoke(AxisServer.java:355) | at org.jboss.axis.transport.http.AxisServlet.doPost(AxisServlet.java:911) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | at org.jboss.axis.transport.http.AxisServletBase.service(AxisServletBase.java:370) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) | at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) | at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) | at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) | at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) | at java.lang.Thread.run(Thread.java:534) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069148#4069148 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069148

17 years, 5 months

1
0
0 / 0

[JBossWS] - Re: JBOSS-WS Client not sending COOKIE after 2 calls

by lowecg2004

Hello All, I really could use some help on this, I've exausted all my avenues of investigation and have become stuck. As I understand it, getting the client to pass on a JSESSIONID cookie to the server is the only way I can use the JBossWS clients with a Seam web service. I also believe it could offer a work around to the author's issue too. Kind Regards, Chris. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069138#4069138 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069138

17 years, 5 months

1
0
0 / 0

[JBossWS] - Re:

by chris05atm

In the end it appeared to be something unrelated to either the wsdl, or generated java code. After a clean install of JBoss the same war file worked just fine. I believe there was some kind of cache/cleanup/whatever issue that prevented things from working properly. The order of events can be followed when viewing the entirety of the thread. I tried to isolate the differences but could not easily. No further deployments have caused issues or resulted in similar problems. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068950#4068950 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068950

17 years, 5 months

1
0
0 / 0

[JBossWS] - Re: Documentation on generated WSDLs

by thomas.diesler＠jboss.com

Schema generation is delegated to jaxb, so I guess there is not. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068920#4068920 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068920

17 years, 5 months

1
0
0 / 0

[JBossWS] - Re: setting up an ssl web service & client

by thomas.diesler＠jboss.com

Our test clients use this | <sysproperty key="org.jboss.ws.wsse.keyStore" value="${tests.output.dir}/resources/jaxrpc/samples/wssecurity/wsse.keystore"/> | <sysproperty key="org.jboss.ws.wsse.trustStore" value="${tests.output.dir}/resources/jaxrpc/samples/wssecurity/wsse.truststore"/> | <sysproperty key="org.jboss.ws.wsse.keyStorePassword" value="jbossws"/> | <sysproperty key="org.jboss.ws.wsse.trustStorePassword" value="jbossws"/> | <sysproperty key="org.jboss.ws.wsse.keyStoreType" value="jks"/> | <sysproperty key="org.jboss.ws.wsse.trustStoreType" value="jks"/> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068916#4068916 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068916

17 years, 5 months

1
0
0 / 0

[JBossWS] - Re: setHeader and setServerURL, using javax.xml.ws.Service?

by eric＠attask.com

Yeah I too could do the simple "Hello World", but i don't know how to include a complex type, such as | <soapenv:Header> | <urn:SessionHeader> | <urn:sessionId>QwWsHJyTPW.1pd0_jXlNKOSU</urn:sessionId> | </urn:SessionHeader> | </soapenv:Header> as a header. Notice it wraps sessionId inside SessionHeader. I've tried a number of things including StubExt soapStub = (StubExt)soapBinding; | QName headerQ = new QName(service.getServiceName().getNamespaceURI(), "SessionHeader"); | QName sessionId = new QName(service.getServiceName().getNamespaceURI(), "SessionHeader", "sessionId"); | soapStub.addUnboundHeader(headerQ, Constants.TYPE_LITERAL_STRING, String.class, ParameterMode.IN); | soapStub.setUnboundHeaderValue(sessionId, "QwWsHJyTPW.1pd0_jXlNKOSU"); but that only managed to produce: | <ns1:SessionHeader xmlns:ns1='urn:partner.soap.sforce.com'>QwWsHJyTPW.1pd0_jXlNKOSU</ns1:SessionHeader> I've tried several other things bug I haven't had much luck. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068906#4068906 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068906

17 years, 5 months

1
0
0 / 0

[JBossWS] - Re:

by thomas.diesler＠jboss.com

Are you saying you have a wsdl that you feed into wsconsume. Then you implement an endpoint based on the generated SEI and it cannot be called. If that's the case, please create a JIRA issue and attach the wsdl to it. The issue should be linked to this forum thread View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068903#4068903 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068903

17 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 July 2007