August 2009 - jbossws-users - Jboss List Archives

by Automatic Email Delivery Software

Your message was undeliverable due to the following reason: Your message could not be delivered because the destination computer was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message could not be delivered within 3 days: Server 123.255.139.86 is not responding. The following recipients did not receive this message: <jbossws-users(a)lists.jboss.org> Please reply to postmaster(a)lists.jboss.org if you feel this message to be in error.

14 years, 8 months

1
0
0 / 0

[JBossWS] - Re: wsconsume and implementing interface top-down

by meetoblivion

i think you may have your implementation strategies mixed up. if you're using wsconsume, it assumes that you've already written the webservice, and wsconsume helps create the client interface. if you're using wsprovide, it assumes you've written the WSDL and need to generate the server side stubs. Why fits your scenario better? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248436#4248436 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248436

14 years, 9 months

1
0
0 / 0

[JBossWS] - Re: JBossWS 3.0.3 memory leak

by erili

I found a poller method in our code that created new instances of WS client objects in the poller method. Even though these were not retained they apparently added data to the classloader's (unifiedclassloader3) resourceBlackList. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248167#4248167 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248167

14 years, 9 months

1
0
0 / 0

[JBossWS] - wsconsume and implementing interface top-down

by delicjapatrycja

Hi (It's my first post, I was trying to find something about my problem but I couldn't ) I have some problem with deploy my Jax WS Web service. I'm trying to do this using top-down method - wsconsume. When I generate java classes from WSDL which I have written before, I get one which is the interface. How should I implement it ? How should I write the web.xml ? which class name should I write inside <servlet-class> </servlet-class> tags ? If i write the generated class name, how jax-ws knows where (in which java class) is implementing class ? If I write the class name inside, which impelements generated interface, I can't deploy the web service. (maybe I do something wrong?) part of Service class generated by Jax-WS: | // [...] | @WebService(name = "XXXService", targetNamespace = "http://xxx.com/XXX/ws") | public interface XXXService { | | | /** | * | * @param in | * @return | * returns int | * @throws Method1FaultMsg | */ | @WebMethod | @WebResult(name = "out", targetNamespace = "") | @RequestWrapper(localName = "method1", targetNamespace = "http://xxx.com/XXX/ws", className = "com.xxx.xxx.ws.Method1") | @ResponseWrapper(localName = "method1Response", targetNamespace = "http://xxx.com/xxx/ws", className = "com.xxx.xxx.ws.Method1Response") | public int method1( | @WebParam(name = "in", targetNamespace = "") | int in) | throws Method1FaultMsg | ; | // [...] | | My implementation class: | | public class XXXServiceImpl implements com.xxx.xxx.ws.XXXService { | | | @WebMethod | @WebResult(name = "out", targetNamespace = "") | @RequestWrapper(localName = "method1", targetNamespace = "http://xxx.com/xxx/ws", className = "com.xxx.xxx.ws.Method1") | @ResponseWrapper(localName = "method1Response", targetNamespace = "http://xxx.com/xxx/ws", className = "com.xxx.xxx.ws.Method1Response") | public int method1(int in) throws Method1FaultMsg | { | try | { | return in*2; | } | catch(Exception e) | { | new Method1FaultMsg("Server Exception", new ServerException(), e); | } | return in; | } | | Any tips? Anyway, sorry for my English :/ View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248099#4248099 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248099

14 years, 9 months

1
0
0 / 0

[JBossWS] - Re: Two classes have the same XML type name when deploying c

by meetoblivion

so a small update. i did confirm that the issue is only present when the client and server are the same box. even if both are deployed to both boxes, issue does not present itself as long as i ensure that the request comes from server1 and goes to server2. changing the package name did not fix anything, and i don't think it's right to try to change the namespace based on this. any ideas? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247999#4247999 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247999

14 years, 9 months

1
0
0 / 0

[JBossWS] - Two classes have the same XML type name when deploying clien

by meetoblivion

This may have more to do with how our test/dev environment is setup, but I am in the process of developing some web services to act as a facade to direct database access from our external site (mostly for writes). When I deploy both the client (war) and server (ejb jar) on the same box, I get the below errors in my stack trace: Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 3 counts of IllegalAnnotationExceptions | Two classes have the same XML type name "{http://sweeps.services.web.coat.com/}signupProperties". Use @XmlType.name and @XmlType.namespace to assign different names to them. | this problem is related to the following location: | at com.coat.web.services.sweeps.SignupProperties | at protected java.util.List com.coat.web.services.sweeps.SweepsSignup.properties | at com.coat.web.services.sweeps.SweepsSignup | this problem is related to the following location: | at com.coat.web.services.sweeps.SignupProperties | at public com.coat.web.services.sweeps.SignupProperties com.coat.web.services.sweeps.ObjectFactory.createSignupProperties() | at com.coat.web.services.sweeps.ObjectFactory | Two classes have the same XML type name "{http://sweeps.services.web.coat.com/}sweepsSignup". Use @XmlType.name and @XmlType.namespace to assign different names to them. | this problem is related to the following location: | at com.coat.web.services.sweeps.SweepsSignup | this problem is related to the following location: | at com.coat.web.services.sweeps.SweepsSignup | at public com.coat.web.services.sweeps.SweepsSignup com.coat.web.services.sweeps.ObjectFactory.createSweepsSignup() | at com.coat.web.services.sweeps.ObjectFactory | Two classes have the same XML type name "{http://sweeps.services.web.coat.com/}SweepsException". Use @XmlType.name and @XmlType.namespace to assign different names to them. | this problem is related to the following location: | at com.coat.web.services.sweeps.SweepsException | this problem is related to the following location: | at com.coat.web.services.sweeps.SweepsException | at public com.coat.web.services.sweeps.SweepsException com.coat.web.services.sweeps.ObjectFactory.createSweepsException() | at com.coat.web.services.sweeps.ObjectFactory Now, I think it's because both client and server are on the same machine. I used wsconsume to generate the WS client stubs. Is the correct work around to use a different package? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247907#4247907 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247907

14 years, 9 months

1
0
0 / 0

[JBossWS] - org.jboss.ws.WSException: Cannot obtain operation meta data

by karypid

Hi, I'm trying to create a web service client with WS-RM enabled, that will work with a WebLogic 10gR3 service. When I run the client I get: *********************** | Create Web Service Client... | Create Web Service... | Call Web Service Operation... | Exception in thread "main" org.jboss.ws.extensions.wsrm.api.RMException: Unable to create WSRM sequence | at org.jboss.ws.core.jaxws.client.ClientImpl.createSequence(ClientImpl.java:573) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:168) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) | at $Proxy14.deliver(Unknown Source) | at cmr.messaging.clientsample.ClientSample.main(ClientSample.java:23) | Caused by: org.jboss.ws.WSException: Cannot obtain operation meta data for: {http://docs.oasis-open.org/ws-rx/wsrm/200702}CreateSequence | at org.jboss.ws.core.CommonClient.getOperationMetaData(CommonClient.java:201) | at org.jboss.ws.core.CommonClient.getOperationMetaData(CommonClient.java:182) | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:295) | at org.jboss.ws.core.jaxws.client.ClientImpl.createSequence(ClientImpl.java:559) | ... 4 more Any pointers as to what is going wrong? I use the following configuration for the client: <?xml version="1.0" encoding="UTF-8"?> | <jaxws-config xmlns="urn:jboss:jaxws-config:2.0" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:javaee="http://java.sun.com/xml/ns/javaee" | xsi:schemaLocation="urn:jboss:jaxws-config:2.0 jaxws-config_2_0.xsd"> | | <client-config> | <config-name>Standard Anonymous WSRM Client</config-name> | <reliable-messaging> | <message-retransmission attempts="50" | interval="10" timeout="10" /> | </reliable-messaging> | | <post-handler-chains> | <javaee:handler-chain> | <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings> | <javaee:handler> | <javaee:handler-name>WSAddressing Handler</javaee:handler-name> | <javaee:handler-class>org.jboss.ws.extensions.addressing.jaxws.WSAddressingClientHandler</javaee:handler-class> | </javaee:handler> | | <javaee:handler> | <javaee:handler-name>WSRM Handler</javaee:handler-name> | <javaee:handler-class>org.jboss.ws.extensions.wsrm.jaxws.RMClientHandler</javaee:handler-class> | </javaee:handler> | </javaee:handler-chain> | </post-handler-chains> | </client-config> | </jaxws-config> View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247865#4247865 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247865

14 years, 9 months

1
0
0 / 0

[JBossWS] - WebMethod call problem

by iou_paul

Hi, I'm trying to make a call from a desktop client to a webservice method running on JBoss 5.1.0. It connects to the webservice, but when calling the webmethod I got the following error: On the client side: javax.xml.ws.WebServiceException: java.lang.NullPointerException at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:176) at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:86) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436) at com.sun.xml.ws.client.Stub.process(Stub.java:248) at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89) at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118) at $Proxy22.fileUp(Unknown Source) at ro.datagroup.verlinkung.upload.webservice.TestProcess.testEJBWebService(TestProcess.java:75) at ro.datagroup.verlinkung.upload.webservice.TestProcess.main(TestProcess.java:82) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) Caused by: java.lang.NullPointerException at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.getProperty(XMLStreamWriterImpl.java:426) at com.sun.xml.ws.util.xml.XMLStreamWriterFilter.getProperty(XMLStreamWriterFilter.java:139) at com.sun.xml.ws.streaming.XMLStreamWriterUtil.getOutputStream(XMLStreamWriterUtil.java:77) at com.sun.xml.ws.message.jaxb.JAXBMessage.writePayloadTo(JAXBMessage.java:313) at com.sun.xml.ws.message.AbstractMessageImpl.writeTo(AbstractMessageImpl.java:142) at com.sun.xml.ws.encoding.MtomCodec.encode(MtomCodec.java:158) at com.sun.xml.ws.encoding.SOAPBindingCodec.encode(SOAPBindingCodec.java:258) at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:142) ... 18 more On server side: ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] (http-0.0.0.0-8080-1) SOAP request exception ClientAbortException: java.net.SocketException: Connection reset at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:342) at org.apache.tomcat.util.buf.ByteChunk.substract(ByteChunk.java:420) at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:364) at org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:193) at java.io.FilterInputStream.read(FilterInputStream.java:116) at java.io.PushbackInputStream.read(PushbackInputStream.java:169) at org.jboss.ws.core.soap.attachment.BoundaryDelimitedInputStream.fullRead(BoundaryDelimitedInputStream.java:144) at org.jboss.ws.core.soap.attachment.BoundaryDelimitedInputStream.read(BoundaryDelimitedInputStream.java:191) at org.jboss.ws.core.soap.attachment.BoundaryDelimitedInputStream.read(BoundaryDelimitedInputStream.java:312) at org.jboss.ws.core.soap.attachment.BoundaryDelimitedInputStream.read(BoundaryDelimitedInputStream.java:286) at org.jboss.ws.core.soap.attachment.MultipartRelatedDecoder.decodeMultipartRelatedMessage(MultipartRelatedDecoder.java:119) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:241) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:455) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:745) at org.apache.coyote.http11.InternalInputBuffer$InputStreamInputBuffer.doRead(InternalInputBuffer.java:775) at org.apache.coyote.http11.filters.ChunkedInputFilter.readBytes(ChunkedInputFilter.java:245) at org.apache.coyote.http11.filters.ChunkedInputFilter.parseChunkHeader(ChunkedInputFilter.java:276) at org.apache.coyote.http11.filters.ChunkedInputFilter.doRead(ChunkedInputFilter.java:132) at org.apache.coyote.http11.InternalInputBuffer.doRead(InternalInputBuffer.java:704) at org.apache.coyote.Request.doRead(Request.java:428) at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:332) ... 38 more I get the same problem regardless the webmethod signature or content. The weird thing is that the same client & ws code actually works on an older application. Can anybody give me a hint about what is or might be the problem?!? Thanks, Paul. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247829#4247829 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247829

14 years, 9 months

1
0
0 / 0

[JBossWS] - ws-addressing: use of annotations @Stateful @WebService @Add

by fsciascia

Hello! it's possible to use @Addressing annotation (javax.xml.ws.soap.Addressing) (jboss4.2.3 + jbossWS 3.1). I use also security and webservices annotations(everything works). What I want to do is to build a stateful secure web service with ejb3, without working with descriptors if possible thanks francesco View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247804#4247804 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247804

14 years, 9 months

1
0
0 / 0

[JBossWS] - Caused by: java.lang.ClassCastException: com.sun.xml.bind.v2

by creaturita

Hello everyone, I have a JBoss 4.2.3 with jdk6v14. I have installed Metro on it. I can publish webservices (ejb 3 style) and webpages (jsf+facelets+richfaces) correctly, but when I call a webservice in the page I get the following exception: [2009/08/03 17:05:30] -- ERROR -- org.ajax4jsf.webapp.BaseXMLFilter -- Exception in the filter chain javax.servlet.ServletException: La ejecuciÃ³n del Servlet lanzÃ³ una excepciÃ³n at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:313) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ExceptionInInitializerError at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:107) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78) at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107) at $Proxy158.obtenerVademecum(Unknown Source) at es.indra.peissmu.presentacion.casos.version.delegate.ServicioVersionVademecumDelegate.getObtenerVademecum(ServicioVersionVademecumDelegate.java:49) at es.indra.peismu.presentacion.casos.cargaNomenclator.view.CargaNomenclatorManagedBean.ObtenerVersion(CargaNomenclatorManagedBean.java:178) at es.indra.peismu.presentacion.casos.cargaNomenclator.view.CargaNomenclatorManagedBean.(CargaNomenclatorManagedBean.java:120 at sun.reflect.NativeCons at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ewInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at java.beans.Beans.instantiate(Beans.java:204) at java.beans.Beans.instantiate(Beans.java:48) at com.sun.faces.config.ManagedBeanFactoryImpl.newInstance(ManagedBeanFactoryImpl.java:269) at com.sun.faces.application.ApplicationAssociate.createAndMaybeStoreManagedBeans(ApplicationAssociate.java:510) at com.sun.faces.el.ManagedBeanELResolver.getValue(ManagedBeanELResolver.java:82) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143) at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:62) at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:45) at org.apache.el.parser.AstValue.getValue(AstValue.java:86) at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71) at javax.faces.component.UIOutput.getValue(UIOutput.java:176) at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getValue(HtmlBasicInputRenderer.java:100) at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurrentValue(HtmlBasicRenderer.java:290) at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:216) at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:847) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:893) at javax.faces.render.Renderer.encodeChildren(Renderer.java:137) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:827) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:883) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:889) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:578) at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:108) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:243) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) ... 23 more Caused by: java.lang.ClassCastException: com.sun.xml.bind.v2.runtime.JAXBContextImpl cannot be cast to com.sun.xml.internal.bind.api.JAXBRIContext at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.(SOAPFaultBuilder.java:533) ... 65 more I suppose it is a library mix failure, but I can not find the solution . Any ideas? Thanks in advance. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247647#4247647 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247647

14 years, 9 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 August 2009