February 2007 - jbossws-users - Jboss List Archives

[JBossWS] - Re: jbossws-1.2.0.CR3 generates lowercase classnames?

by dwin

You can use JAXB to specify the name of class For example, | @XmlType(name="ColorVariant") | public class ColorVariant { | ... | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019378#4019378 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019378

19 years, 1 month

1
0
0 / 0

[JBossWS] - please solve that

by mramitkrde

when i am starting jboss i am getting one message likr: 17:13:11,437 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.ws:service=DeployerInterceptorEJB3 State: CONFIGURED I Depend On: jboss.ejb3:service=EJB3Deployer --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.ejb3:service=EJB3Deployer State: NOTYETINSTALLED Depends On Me: jboss.ws:service=DeployerInterceptorEJB3 is it harmfull? how to solve that? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019296#4019296 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019296

19 years, 1 month

1
0
0 / 0

[JBossWS] - jbossws-1.2.0.CR3 generates lowercase classnames?

by fheldt

Is it intended behaviour, that jbossws-1.2.0.CR3 generates lowercase classnames? Here's a little excerpt from the log file: | [complexType={http://dhc.com/}colorVariant,javaType=com.dhc.ColorVariant] | [complexType={http://dhc.com/}colorGroup,javaType=com.dhc.ColorGroup] | As you can see, from e.g. ColorVariant it generates colorVariant in the resulting wsdl. That wasn't so in jbossws 1.0.4.GA and earlier. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019275#4019275 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019275

19 years, 1 month

1
0
0 / 0

[JBossWS] - configure jUDDI

by saschwen

Hey, Has anyone been able to configure the jboss jUDDI. I've been trying to get it going for a few days now and I can not connect and query/publish to it. I guess the first problem is authentication. I've tried the username jboss with no password and I get the following exception. I can't figure out how to authenticate with it. I'm using UDDI Browser to connect to it. | 2007-02-19 18:10:48,238 ERROR [org.apache.juddi.function.SaveBusinessFunction] E_authTokenRequired (10120) An invalid authentication token was passed to an API call that requires authentication. authToken: | 2007-02-19 18:10:48,238 ERROR [org.jboss.jaxr.juddi.JUDDIServlet] RegistryException:: | E_authTokenRequired (10120) An invalid authentication token was passed to an API call that requires authentication. authToken: | at org.apache.juddi.function.AbstractFunction.getPublisher(AbstractFunction.java:71) | at org.apache.juddi.function.SaveBusinessFunction.execute(SaveBusinessFunction.java:96) | at org.apache.juddi.registry.RegistryEngine.execute(RegistryEngine.java:194) | at org.jboss.jaxr.juddi.JUDDIServlet.doPost(JUDDIServlet.java:158) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | 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:96) | 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.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) | at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) | 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:869) | at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) | at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) | at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) | at java.lang.Thread.run(Thread.java:595) | 2007-02-19 18:10:48,278 ERROR [org.jboss.jaxr.juddi.JUDDIServlet] A serious error has occured while assembling the SOAP Fault. | java.lang.IllegalArgumentException: Invalid faultCode: Client | at org.jboss.ws.soap.SOAPFaultImpl.setFaultCode(SOAPFaultImpl.java:219) | at org.jboss.jaxr.juddi.JUDDIServlet.doPost(JUDDIServlet.java:262) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | 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:96) | 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.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) | at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) | 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:869) | at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) | at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) | at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) | at java.lang.Thread.run(Thread.java:595) | Can anyone help? Thank you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019076#4019076 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019076

19 years, 1 month

1
0
0 / 0

[JBossWS] - Re: Must a @Webservice also be a session bean?

by michea

No not necessarily, it can be any pojo. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4018993#4018993 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4018993

19 years, 1 month

1
0
0 / 0

[JBossWS] - Must a @Webservice also be a session bean?

by fbadt

Must a @Webservice also be a session bean? And why? Thank you, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4018964#4018964 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4018964

19 years, 1 month

1
0
0 / 0

[JBossWS] - Re: 1.2.0CR3 returns

by Juergen.Zimmermann

This following namespace declaration is not generated by wstools xmlns:ns1='http://jaxb.dev.java.net/array' After fixing this defect I had no problems in generating a client using JAX-WS RI !!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4018949#4018949 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4018949

19 years, 1 month

1
0
0 / 0

[JBossWS] - Re: 1.2.0CR3 returns

by Juergen.Zimmermann

Instead of the WSDL file generated by "wstools" I used the WSDL file in server\default\tmp\jbossws: Eclipse' Web Services Explorer works fine. Thus there seems to be any difference between the output of wstools and the WSDL file generated at runtime... However, using JAX-WS RI for the client still fails. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4018903#4018903 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4018903

19 years, 1 month

1
0
0 / 0

[JBossWS] - 1.2.0CR3 returns

by Juergen.Zimmermann

I tested the new JBossWS 1.2.0CR3 with a) Eclipse/WTP and the generic "Web Services Explorer" b) The reference implementation for JAX-WS on the client side. There is no problem if the web service doesn't need any input parameter and just returns a result, e.g. a string. However, if the web service's operation needs an input parameter (e.g. a long value) then I get this error message: "Cannot find child element: arg0". Eclipse's Web Services Explorer shows the following as the submitted SOAP message:<?xml version="1.0" encoding="UTF-8" ?> | <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | <soapenv:Body> | <ns0:findNachname xmlns:ns0="http://ws.hska.de"> | <long_1>1</long_1> | </ns0:findNachname> | </soapenv:Body> | </soapenv:Envelope> And the following code as the returned SOAP message:<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> | <env:Header /> | <env:Body> | <env:Fault> | <faultcode>env:Server</faultcode> | <faultstring>Cannot find child element: arg0</faultstring> | </env:Fault> | </env:Body> | </env:Envelope> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4018875#4018875 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4018875

19 years, 1 month

1
0
0 / 0

[JBossWS] - 1.2.0CR3: Default for @WebService(targetNamespace=

by Juergen.Zimmermann

I just tried 1.2.0CR3 from the repository location and was using JEMS 1.2 / JBoss 4.0.5 If I ommit the attribute "targetNamespace" within the annotation @WebService then the resulting target namespace is "http://my.package". IMHO according to the spec it should be "http://my.package/jaws" View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4018871#4018871 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4018871

19 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users February 2007