Re: jaxws binding issue
As an update on this if I leave my jaxb appinfo binding jaxb:typesafeEnumClass & jaxb:typesafeEnumMember in my wsdl & use the bindings file to replace the XMLGregorianCalendar using wsimport then everything works.. so this looks like a bug to me. CXF gives the error pasted at the bottom However wsimport does also seem to have a problem with having the globalBindings & typesafeEnumMember in the external bindings.. http://java.sun.com/xml/ns/jaxws"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; version="2.0"> http://www.test.com/ws/de']"> CXF error for inline jabx annotations & external bindings: [java] wsdl2java - Apache CXF (incubator) 2.0.5-incubator [java] WSDLToJava Error: Thrown by JAXB : compiler was unable to honor this globalBindings customization. It is attached to a wrong place, or its inconsistent with other bindings. [java] org.apache.cxf.tools.common.ToolException: Thrown by JAXB : compiler was unable to honor this globalBindings customization. It is attached to a wrong place, or its inconsistent with other bindings. [java] at org.apache.cxf.tools.wsdlto.databinding.jaxb.JAXBBindErrorListener.error(JAXBBindErrorListener.java:34) [java] at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.error(SchemaCompilerImpl.java:245) [java] at com.sun.tools.xjc.util.ErrorReceiverFilter.error(ErrorReceiverFilter.java:61) [java] at com.sun.tools.xjc.util.ErrorReceiverFilter.error(ErrorReceiverFilter.java:61) [java] at com.sun.tools.xjc.ErrorReceiver.error(ErrorReceiver.java:66) [java] at com.sun.tools.xjc.reader.xmlschema.ErrorReporter.error(ErrorReporter.java:63) [java] at com.sun.tools.xjc.reader.xmlschema.UnusedCustomizationChecker.check(UnusedCustomizationChecker.java:105) [java] at com.sun.tools.xjc.reader.xmlschema.UnusedCustomizationChecker.check(UnusedCustomizationChecker.java:98) [java] at com.sun.tools.xjc.reader.xmlschema.UnusedCustomizationChecker.simpleType(UnusedCustomizationChecker.java:196) [java] at com.sun.xml.xsom.impl.SimpleTypeImpl.visit(SimpleTypeImpl.java:134) [java] at com.sun.tools.xjc.reader.xmlschema.UnusedCustomizationChecker.elementDecl(UnusedCustomizationChecker.java:189) [java] at com.sun.xml.xsom.impl.ElementDecl.visit(ElementDecl.java:202) [java] at com.sun.tools.xjc.reader.xmlschema.UnusedCustomizationChecker.particle(UnusedCustomizationChecker.java:202) [java] at com.sun.xml.xsom.impl.ParticleImpl.visit(ParticleImpl.java:88) [java] at com.sun.tools.xjc.reader.xmlschema.UnusedCustomizationChecker.modelGroup(UnusedCustomizationChecker.java:183) [java] at com.sun.xml.xsom.impl.ModelGroupImpl.visit(ModelGroupImpl.java:89) [java] at com.sun.tools.xjc.reader.xmlschema.UnusedCustomizationChecker.particle(UnusedCustomizationChecker.java:202) [java] at com.sun.xml.xsom.impl.ParticleImpl.visit(ParticleImpl.java:88) [java] at com.sun.tools.xjc.reader.xmlschema.UnusedCustomizationChecker.complexType(UnusedCustomizationChecker.java:143) [java] at com.sun.xml.xsom.impl.ComplexTypeImpl.visit(ComplexTypeImpl.java:237) [java] at com.sun.tools.xjc.reader.xmlschema.UnusedCustomizationChecker.run(UnusedCustomizationChecker.java:84) [java] at com.sun.tools.xjc.reader.xmlschema.UnusedCustomizationChecker.run(UnusedCustomizationChecker.java:74) [java] at com.sun.tools.xjc.reader.xmlschema.BGMBuilder._build(BGMBuilder.java:143) [java] at com.sun.tools.xjc.reader.xmlschema.BGMBuilder.build(BGMBuilder.java:77) [java] at com.sun.tools.xjc.ModelLoader.annotateXMLSchema(ModelLoader.java:388) [java] at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:206) [java] at org.apache.cxf.tools.wsdlto.databinding.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:209) [java] at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.generateTypes(WSDLToJavaContainer.java:531) [java] at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:185) [java] at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:231) [java] at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:83) [java] at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:102) [java] at org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:171) [java] Caused by: com.sun.istack.SAXParseException2: compiler was unable to honor this globalBindings customization. It is attached to a wrong place, or its inconsistent with other bindings. [java] ... 29 more [echo] ***
jaxws binding issue
I am having some problems with jaxw binding customizations. The first problem that I am having is mixing a globalBindings definition with a bindings - the global bindings seems to be ignored. For the example below if I use it as is, I only get my typesafeEnumClass generated. My instances of XMLGregorianCalendar are not replaced with java.util.Date. However, if I remove the jaxb:bindings node then the global binding works fine. Can anyone shed any light on this? The other issue I have is if I have in-lined customizations and external customizations I cam getting an error reporting inconsistencies - anyone ever had this issue and resolved it? This has all been doing my nut in - so any help would be appreciated! http://java.sun.com/xml/ns/jaxws"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; version="2.0"> http://www.test.com/ws/de']"> Thanks -- View this message in context: http://www.nabble.com/jaxws-binding-issue-tp16823731p16823731.html Sent from the cxf-user mailing list archive at Nabble.com.
removing xsd:choice
I am trying to my my wsdl a bit more interoperable by removing xsd:choice & using polymorphism instead as per the sugestions here: http://www.ibm.com/developerworks/xml/library/ws-tip-xsdchoice.html However I am running into issues with jaxb similar to those detailed here: http://forums.java.net/jive/thread.jspa?messageID=31077&tstart=0 i.e. only the supertype appears to be marshalled & the xsi:type is missing. It seems that the only resolution is to give the jaxb marshaller/unmarshaller the classes to be used for marhsalling/unmarshalling! Anyone come across this issue, found a resolution? -- View this message in context: http://www.nabble.com/removing-xsd%3Achoice-tp14419440p14419440.html Sent from the cxf-user mailing list archive at Nabble.com.
Abstract jaxws:endpoint
Hi, Is there anyway to have an abstract endpoint so that multiple endpoints can inherit from it? I have multiple endpoints which will all have the same interceptors & features and I would like them all to inherit from the same parent. I notice that the jaxws:enpoint has supports the abstract attribute, however I parent is an unsupported attribute ... Reasoning behind this - I have 5 different services at the moment, these support 2 transports - http & local, so I now have 10 endpoint configurations. If I add support for another transport I will be up to 15... Thanks Adrian -- View this message in context: http://www.nabble.com/Abstract-jaxws%3Aendpoint-tf4834534.html#a13830933 Sent from the cxf-user mailing list archive at Nabble.com.
Re: .net ws-addressing & relationship type
Yeah that did the trick - thanks
dkulp wrote:
>
>
> Adrian,
>
> Most likely, your ~/.m2/repository has some corrupt meta-data.
> Unfortunately, it happens from time to time.
>
> I would suggest doing a "rm -rf ~/.m2/repository/org/apache/maven" to see
> if making it re-download the maven stuff will help.
>
> Dan
>
>
> On Thursday 15 November 2007, Adrian Corcoran wrote:
>> Think you may be right about dropping it if it is a reply.
>>
>> Would love to try and fix this (and a few other thing ) but am having
>> problems when trying to build trunk/2.0.3. or 2.0.2 at the moment I am
>> getting errors. Am getting:
>>
>> Project ID: null:maven-project:jar:2.0.1
>> Reason: Cannot find parent: org.apache.mvane:maven for project
>> null:maven-project:jar:2.0.1 for project null:maven-project:jar:2.0.1
>>
>> On Nov 15, 2007 3:34 PM, Sergey Beryozkin <[EMAIL PROTECTED]>
> wrote:
>> > I'm not sure but may be it should be
>> >
>> > http://www.w3.org/2005/08/addressing/reply ,
>> >
>> > "
>> > /wsa:RelatesTo/@RelationshipType
>> > This OPTIONAL attribute (of type xs:anyURI) conveys the relationship
>> > type as an IRI. When absent, the implied value of this attribute is
>> > "http://www.w3.org/2005/08/addressing/reply";.
>> >
>> > "
>> > or better yet, it should be dropped altogether ? Perhaps modifying
>> > the cxf ws-addressing code can help to find the truth...
>> >
>> >
>> > It's somewhat orthogonal but a cxf response not look good with
>> > respect to namespaces... I thought it was discussed earlier, but not
>> > sure if some work was done...
>> >
>> > Namespace declarations should really go to soap:envelope, otherwise,
>> > if a message is large, then duplicate namespace declarations will
>> > take up to 30% of the total message size. There's a number of ways
>> > to ensure that soap:envelope keeps all the ns declarations...
>> >
>> > Cheers, Sergey
>> >
>> > - Original Message -
>> > From: "Adrian C" <[EMAIL PROTECTED]>
>> > To:
>> > Sent: Thursday, November 15, 2007 3:06 PM
>> > Subject: .net ws-addressing & relationship type
>> >
>> > > if I use a .net client to consume my web service I am getting
>> > > errors when ws-addressing is used:
>> > > InnerException {"WSE205: RelationshipType attribute can only be of
>> > > reply type. The following value was found: reply."}
>> > > System.Exception
>> > > {Microsoft.Web.Services3.Addressing.AddressingFormatException}
>> > >
>> > > seems to expect the RelationshipType attribute value to be
>> > > different - i don't get it!
>> > >
>> > > The soap header generated by cxf looks fine:
>> > >
>> > > > > > xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing";>
>> > > urn:uuid:8504dd78-06aa-4c6b-b589-ad703ae19bbe
>> > >
>> > > http://schemas.xmlsoap.org/ws/2004/08/addressing";>
>> > > http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>> > >
>> > > > > > xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing";
>> > > RelationshipType="reply">
>> > > urn:uuid:b33fc856-dbae-4034-ac6f-e2d53b593722
>> > >
>> > > > > > xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing";>
>> > > http://www.daon.com/ws/de/IdentityManagement/CreateIdentity
>> > >
>> > >
>> > >
>> > > Get the feeling its expecting wsa:Reply as the attribute! Do
>> > > anyone have any ideas what is going on?
>> > > --
>> > > View this message in context:
>> > > http://www.nabble.com/.net-ws-addressing---relationship-type-tf481
>> > >2987.html#a13770286 Sent from the cxf-user mailing list archive at
>> > > Nabble.com.
>> >
>> >
>> > IONA Technologies PLC (registered in Ireland)
>> > Registered Number: 171387
>> > Registered Address: The IONA Building, Shelbourne Road, Dublin 4,
>> > Ireland
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727C: 508-380-7194
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>
>
--
View this message in context:
http://www.nabble.com/.net-ws-addressing---relationship-type-tf4812987.html#a13795365
Sent from the cxf-user mailing list archive at Nabble.com.
Re: .net ws-addressing & relationship type
Hi Sergey,
Thanks for the pointer on this. I changed the VersionTransformer to not set
the relationship type if default value and it works with .net.
Now the question is how to I submit this patch!?
Thanks,
Adrian
Sergey Beryozkin wrote:
>
> I'm not sure but may be it should be
>
> http://www.w3.org/2005/08/addressing/reply ,
>
> "
> /wsa:RelatesTo/@RelationshipType
> This OPTIONAL attribute (of type xs:anyURI) conveys the relationship type
> as an IRI. When absent, the implied value of this
> attribute is "http://www.w3.org/2005/08/addressing/reply";.
>
> "
> or better yet, it should be dropped altogether ? Perhaps modifying the cxf
> ws-addressing code can help to find the truth...
>
>
> It's somewhat orthogonal but a cxf response not look good with respect to
> namespaces... I thought it was discussed earlier, but not
> sure if some work was done...
>
> Namespace declarations should really go to soap:envelope, otherwise, if a
> message is large, then duplicate namespace declarations
> will take up to 30% of the total message size. There's a number of ways to
> ensure that soap:envelope keeps all the ns
> declarations...
>
> Cheers, Sergey
>
> - Original Message -
> From: "Adrian C" <[EMAIL PROTECTED]>
> To:
> Sent: Thursday, November 15, 2007 3:06 PM
> Subject: .net ws-addressing & relationship type
>
>
>>
>>
>> if I use a .net client to consume my web service I am getting errors when
>> ws-addressing is used:
>> InnerException {"WSE205: RelationshipType attribute can only be of reply
>> type. The following value was found: reply."} System.Exception
>> {Microsoft.Web.Services3.Addressing.AddressingFormatException}
>>
>> seems to expect the RelationshipType attribute value to be different - i
>> don't get it!
>>
>> The soap header generated by cxf looks fine:
>>
>> > xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing";>
>> urn:uuid:8504dd78-06aa-4c6b-b589-ad703ae19bbe
>>
>> http://schemas.xmlsoap.org/ws/2004/08/addressing";>
>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>>
>> > xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing";
>> RelationshipType="reply">
>> urn:uuid:b33fc856-dbae-4034-ac6f-e2d53b593722
>>
>> > xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing";>
>> http://www.daon.com/ws/de/IdentityManagement/CreateIdentity
>>
>>
>>
>> Get the feeling its expecting wsa:Reply as the attribute! Do anyone have
>> any
>> ideas what is going on?
>> --
>> View this message in context:
>> http://www.nabble.com/.net-ws-addressing---relationship-type-tf4812987.html#a13770286
>> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
> IONA Technologies PLC (registered in Ireland)
> Registered Number: 171387
> Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
>
>
--
View this message in context:
http://www.nabble.com/.net-ws-addressing---relationship-type-tf4812987.html#a13795319
Sent from the cxf-user mailing list archive at Nabble.com.
.net ws-addressing & relationship type
if I use a .net client to consume my web service I am getting errors when
ws-addressing is used:
InnerException {"WSE205: RelationshipType attribute can only be of reply
type. The following value was found: reply."} System.Exception
{Microsoft.Web.Services3.Addressing.AddressingFormatException}
seems to expect the RelationshipType attribute value to be different - i
don't get it!
The soap header generated by cxf looks fine:
http://schemas.xmlsoap.org/ws/2004/08/addressing";>
urn:uuid:8504dd78-06aa-4c6b-b589-ad703ae19bbe
http://schemas.xmlsoap.org/ws/2004/08/addressing";>
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
http://schemas.xmlsoap.org/ws/2004/08/addressing";
RelationshipType="reply">
urn:uuid:b33fc856-dbae-4034-ac6f-e2d53b593722
http://schemas.xmlsoap.org/ws/2004/08/addressing";>
http://www.daon.com/ws/de/IdentityManagement/CreateIdentity
Get the feeling its expecting wsa:Reply as the attribute! Do anyone have any
ideas what is going on?
--
View this message in context:
http://www.nabble.com/.net-ws-addressing---relationship-type-tf4812987.html#a13770286
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Error calling simple JAX-WS service from Flex/Flash
are you logging the messages in out and out of cxf - is the soap action/ws-addressing correct? BrianP wrote: > > I got my first simple JAX-WS service up and running. I got it deployed to > Tomcat, and tested it successfully from a simple client (the client from > 'a Simple JAX-WS service', but with a different address). Now I'm trying > to connect to the service from a Flex/Flash client, and am getting the > following errors (from the Tomcat log): > > Nov 9, 2007 9:51:15 AM org.apache.cxf.phase.PhaseInterceptorChain > doIntercept > INFO: Interceptor has thrown exception, unwinding now > org.apache.cxf.interceptor.Fault > at > org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:101) > at > org.apache.cxf.jaxws.JAXWSMethodInvoker.createFault(JAXWSMethodInvoker.java:76) > at > org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) > at > org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:100) > at > org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:63) > at > org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:56) > at > org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) > at > org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:92) > at > org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207) > at > org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:73) > at > org.apache.cxf.transport.servlet.ServletDestination.doMessage(ServletDestination.java:79) > at > org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:235) > at > org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:140) > at > org.apache.cxf.transport.servlet.CXFServlet.invoke(CXFServlet.java:278) > at > org.apache.cxf.transport.servlet.CXFServlet.doPost(CXFServlet.java:256) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874) > at > org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) > at > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) > at > org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.lang.IllegalArgumentException > 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 > org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:107) > at > org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:77) > ... 28 more > > I also noticed this error earlier in the log : > > Nov 9, 2007 9:38:58 AM org.apache.catalina.loader.WebappClassLoader > validateJarFile > INFO: > validateJarFile(C:\apache-tomcat-5.5.25\webapps\OrderViewWeb\WEB-INF\lib\geronimo-servlet_2.5_spec-1.1-M1.jar) > - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: > javax/servlet/Servlet.class > > Any idea what is going on? I searched this forum first and found another > post where the poster mentioned that Flex uses RPC-style, and CXF is using > doc/literal. Could that be the problem? I'm very new to developing with > both Flex and CXF, so I'm assuming I'm missing something. > > Thanks > -- View this message in context: http://www.nabble.com/Error-calling-simple-JAX-WS-service-from-Flex-Flash-tf4778205.html#a13669935 Sent from the cxf-
Re: Error calling simple JAX-WS service from Flex/Flash
are you sure its removed from the war & your expanded web-inf/lib directory? I removed it, and that produced the following error : Nov 9, 2007 10:22:38 AM org.apache.catalina.loader.WebappClassLoader modified SEVERE: Resource '/WEB-INF/lib/geronimo-servlet_2.5_spec-1.1-M1.jar' is missing And then a bit later in the log, I still have the '...geronimo-servlet... - jar not loaded' message If this problem is related, wouldn't that have caused a problem from the simple client as well? But that one worked. Adrian C wrote: > > Remove geronimo-servlet_2.5_spec-1.1-M1.jar from you war first off and see > how it goes from there > > > -- View this message in context: http://www.nabble.com/Error-calling-simple-JAX-WS-service-from-Flex-Flash-tf4778205.html#a13669191 Sent from the cxf-user mailing list archive at Nabble.com.
Re: Error calling simple JAX-WS service from Flex/Flash
Remove geronimo-servlet_2.5_spec-1.1-M1.jar from you war first off and see how it goes from there BrianP wrote: > > I got my first simple JAX-WS service up and running. I got it deployed to > Tomcat, and tested it successfully from a simple client (the client from > 'a Simple JAX-WS service', but with a different address). Now I'm trying > to connect to the service from a Flex/Flash client, and am getting the > following errors (from the Tomcat log): > > Nov 9, 2007 9:51:15 AM org.apache.cxf.phase.PhaseInterceptorChain > doIntercept > INFO: Interceptor has thrown exception, unwinding now > org.apache.cxf.interceptor.Fault > at > org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:101) > at > org.apache.cxf.jaxws.JAXWSMethodInvoker.createFault(JAXWSMethodInvoker.java:76) > at > org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) > at > org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:100) > at > org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:63) > at > org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:56) > at > org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) > at > org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:92) > at > org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207) > at > org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:73) > at > org.apache.cxf.transport.servlet.ServletDestination.doMessage(ServletDestination.java:79) > at > org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:235) > at > org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:140) > at > org.apache.cxf.transport.servlet.CXFServlet.invoke(CXFServlet.java:278) > at > org.apache.cxf.transport.servlet.CXFServlet.doPost(CXFServlet.java:256) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874) > at > org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) > at > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) > at > org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.lang.IllegalArgumentException > 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 > org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:107) > at > org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:77) > ... 28 more > > I also noticed this error earlier in the log : > > Nov 9, 2007 9:38:58 AM org.apache.catalina.loader.WebappClassLoader > validateJarFile > INFO: > validateJarFile(C:\apache-tomcat-5.5.25\webapps\OrderViewWeb\WEB-INF\lib\geronimo-servlet_2.5_spec-1.1-M1.jar) > - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: > javax/servlet/Servlet.class > > Any idea what is going on? I searched this forum first and found another > post where the poster mentioned that Flex uses RPC-style, and CXF is using > doc/literal. Could that be the problem? I'm very new to developing with > both Flex and CXF, so I'm assuming I'm missing something. > > Thanks > -- View this message in context: http://www.nabble.com/Error-calling-simple-JAX-WS-service-from-Flex-Flash-tf4778205.html#a13668997 Sent from the cx
Re: Monitoring CXF Webservices
Could you use MBeans i.e. JMX? Vespa, Anthony J wrote: > > Hello, > > I am doing some planning for production deployment of the web services I > am developing and am wondering about the best way to implement heart > beats / diagnostics for the services themselves. Is there a way to > trivially enumurate through the services, display basic info (basic > config info, name etc) and do some trivial test besides just returning > the whole WSDL or writing an additional function? Was just wondering if > there was something baked in. > > I would envison this as something that would run in the same tomcat > instance (like a another servlet) that I would access through an admin > console I write. > > Thanks for any help! > > -Tony > > -- View this message in context: http://www.nabble.com/Monitoring-CXF-Webservices-tf4777853.html#a13667699 Sent from the cxf-user mailing list archive at Nabble.com.
Re: JAXWS & WS Policy
Thanks for the reply James, maybe my understanding of this is incorrect, but I had hoped that by defining policy assertions for my endpoint ( > I've not been an expert on ws-*, but i just look at the samples in the > cxf distribution, we do have a sample of ws-policy > And we have doc on http://cwiki.apache.org/CXF20DOC/ws-support.html > > Don't know if it's sufficient > > James > >> Is there a way to configure WSPolicy in the jaxws definition of a service >> in >> the same way as WS-Reliable Messaging? >> >> i.e. is it possible to have something like this: >> >> >> >> >> >> > xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata";> >> >> >> >> >> >> >> Are there any examples of this? >> >> Thanks >> > > -- View this message in context: http://www.nabble.com/JAXWS---WS-Policy-tf4773036.html#a13666396 Sent from the cxf-user mailing list archive at Nabble.com.
Re: schema validation
Hi Dan, Thanks for your help as always - looks like upgrading to 2.0.3 & upgrading XMLSchema resolved this issue. The only issue I have with this now is with xsd:restriction - they are not annotated, not supported, so am forced to reference the wsdl, not big deal, this works I am however still having problems with the schema validation & mtom. Its faily obvious why its breaking, however I would thought that there could be some iffing about butting around the mtom (attachement in/out interceptor).. i.e. before mtom'ing perform schema validation if enabled, and them remove mark as being validated... Or is it designed to work this way? dkulp wrote: > > > Forgot to mention, 2.0.3 is being voted on now. You can download the > release candidate from: > http://people.apache.org/~dkulp/stage_cxf/2.0.3-incubator-take1/dist/ > > (That may fix your mtom validation issue as well, not really sure though) > > Dan > > > On Thursday 08 November 2007, Daniel Kulp wrote: >> On Thursday 08 November 2007, Adrian C wrote: >> > With jaxb if schema validation is turned on should validation work >> > if the wsld is not defined for the webservice? Am seeing errors when >> > I do this - I though that the schema/wsld could be generated from >> > the classes? >> >> In theory, it should. I'm not sure how well tested it is though. >> >> I'd love to see any test cases if there is an issue. Also, >> definitely try with 2.0.3.We upgraded to a newer version of >> XmlSchema to fix SOME issues where the schema was losing some needed >> information. (such as whether a base64 thing was mtom enabled or >> not). Thus, 2.0.3 may fix some of the isssues. > > > > -- > J. Daniel Kulp > Principal Engineer > IONA > P: 781-902-8727C: 508-380-7194 > [EMAIL PROTECTED] > http://www.dankulp.com/blog > > -- View this message in context: http://www.nabble.com/schema-validation-tf4770643.html#a13666392 Sent from the cxf-user mailing list archive at Nabble.com.
JAXWS & WS Policy
Is there a way to configure WSPolicy in the jaxws definition of a service in the same way as WS-Reliable Messaging? i.e. is it possible to have something like this: http://www.w3.org/2007/02/addressing/metadata";> Are there any examples of this? Thanks -- View this message in context: http://www.nabble.com/JAXWS---WS-Policy-tf4773036.html#a13653961 Sent from the cxf-user mailing list archive at Nabble.com.
schema validation & mtom
Am am getting schema validation erros when I have mtom enabled for my service. Is the default ordering of the interceptors wrong? Can I change the ordering? 08-Nov-2007 15:18:45 org.apache.cxf.ws.addressing.soap.MAPCodec encodeAsExposed INFO: To : http://www.w3.org/2005/08/addressing/anonymous 08-Nov-2007 15:18:45 org.apache.cxf.ws.addressing.soap.MAPCodec encodeAsExposed INFO: RelatesTo : urn:uuid:32472e5d-de97-41e7-9355-bc3d2febda5a 08-Nov-2007 15:18:45 org.apache.cxf.ws.addressing.soap.MAPCodec encodeAsExposed INFO: Action : http://www.xxyyzz.com/ws/de/IdentityManagement/GetIdentity 08-Nov-2007 15:18:45 org.apache.cxf.phase.PhaseInterceptorChain doIntercept INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault: Marshalling Error: cvc-type.3.1.2: Element 'Data' is a simple type, so it must have no element information item [children]. at org.apache.cxf.jaxb.JAXBEncoderDecoder.marshall(JAXBEncoderDecoder.java:179) at org.apache.cxf.jaxb.io.DataWriterImpl.write(DataWriterImpl.java:42) at org.apache.cxf.interceptor.AbstractOutDatabindingInterceptor.writeParts(AbstractOutDatabindingInterceptor.java:84) at org.apache.cxf.interceptor.BareOutInterceptor.handleMessage(BareOutInterceptor.java:68) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207) at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(OutgoingChainInterceptor.java:74) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:73) at org.apache.cxf.transport.servlet.ServletDestination.doMessage(ServletDestination.java:79) at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:235) at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:140) at org.apache.cxf.transport.servlet.CXFServlet.invoke(CXFServlet.java:278) at org.apache.cxf.transport.servlet.CXFServlet.doPost(CXFServlet.java:256) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.xxyyzz.de.ws.xfire.core.filter.AuditFilterBean.doFilter(AuditFilterBean.java:80) 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:585) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:107) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy12.doFilter(Unknown Source) at com.xxyyzz.de.ws.xfire.core.filter.AuditingFilter.doFilter(AuditingFilter.java:67) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
schema validation
With jaxb if schema validation is turned on should validation work if the wsld is not defined for the webservice? Am seeing errors when I do this - I though that the schema/wsld could be generated from the classes? -- View this message in context: http://www.nabble.com/schema-validation-tf4770643.html#a13646130 Sent from the cxf-user mailing list archive at Nabble.com.
Re: cannot resolve wsdl:tExtensibilityElement
should this not be working out of the box? I see that the schema is there - the entry is there for the pluggablespringresolver. It looks like its an issue that has been looked at before: http://www.ohloh.net/projects/4982/contributors/30202/commits/10289783 Is it possible that this issue has not been competly fixed? dkulp wrote: > > > You could add an XmlCatalog to the catalog resolver to map the > http://schemas.xmlsoap.org/schemas/wsdl/wsdl.xsd location to something > that's local. > > Dan > > > On Wednesday 07 November 2007, Adrian C wrote: >> Hate to be answering my own posts but the cause of this is the fact >> that I am behind a proxy server. Seems that the following import in >> jms-conf.xsd, http-conf.xsd causes the xsd resolver to run off to the >> internet to try and find the schema. Is there anyway around this? >> >> http://schemas.xmlsoap.org/wsdl/"; >> schemaLocation="http://schemas.xmlsoap.org/schemas/wsdl/wsdl.xsd"/> >> >> How did I know this - -well if I hack http-conf.xsd to do the >> following it works! >> >> http://schemas.xmlsoap.org/wsdl/"; >> schemaLocation="file:///c:/temp/schemas/wsdl/wsdl.xsd"/> >> >> >> Thanks >> >> Adrian C wrote: >> > Hi, >> > >> > Am doing some testing with jms & am getting the error below, has >> > anyone seen anything like this before? >> > >> > Thanks >> > >> > org.springframework.beans.factory.xml.XmlBeanDefinitionStoreExceptio >> >n: Line 175 in XML document from class path resource >> > [junit/wsclient-context.xml] is invalid; nested exception is >> > org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name >> > 'wsdl:tExtensibilityElement' to a(n) 'type definition' component. >> > >> > Caused by: org.xml.sax.SAXParseException: src-resolve: Cannot >> > resolve the name 'wsdl:tExtensibilityElement' to a(n) 'type >> > definition' component. >> > >> > at >> > com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSA >> >XParseException(ErrorHandlerWrapper.java:236) >> > >> > at >> > com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Er >> >rorHandlerWrapper.java:172) >> > >> > at >> > com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError >> >(XMLErrorReporter.java:382) >> > >> > at >> > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.rep >> >ortSchemaError(XSDHandler.java:2241) >> > >> > at >> > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.get >> >GlobalDecl(XSDHandler.java:1201) >> > >> > at >> > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexType >> >Traverser.traverseComplexContent(XSDComplexTypeTraverser.java:715) >> > >> > at >> > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexType >> >Traverser.traverseComplexTypeDecl(XSDComplexTypeTraverser.java:288) >> > >> > at >> > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexType >> >Traverser.traverseGlobal(XSDComplexTypeTraverser.java:196) >> > >> > at >> > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.get >> >GlobalDecl(XSDHandler.java:1333) >> > >> > at >> > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTrav >> >erser.traverseNamedElement(XSDElementTraverser.java:376) >> > >> > at >> > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTrav >> >erser.traverseGlobal(XSDElementTraverser.java:248) >> > >> > at >> > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.tra >> >verseSchemas(XSDHandler.java:1081) >> > >> > at >> > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.par >> >seSchema(XSDHandler.java:481) >> > >> > at >> > com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchem >> >a(XMLSchemaLoader.java:556) >> > >> > at >> > com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.findSc >> >hemaGrammar(XMLSchemaValidator.java:2459) >> > >> >
Re: cannot resolve wsdl:tExtensibilityElement
k/aop/config/spring-aop-2.0.xsd, http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd=schemas/oasis-200401-wss-wssecurity-utility-1.0.xsd, http://cxf.apache.org/schemas/configuration/soap.xsd=schemas/configuration/soap.xsd, http://www.springframework.org/schema/beans/spring-beans.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd, http://cxf.apache.org/schemas/configuration/wsrm-manager.xsd=schemas/configuration/wsrm-manager.xsd, http://cxf.apache.org/schemas/wsdl/http-conf.xsd=schemas/wsdl/http-conf.xsd, http://cxf.apache.org/schemas/jaxws.xsd=schemas/jaxws.xsd, http://www.w3.org/2006/07/ws-policy.xsd=schemas/ws-policy-200607.xsd, http://cxf.apache.org/schema/bindings/object.xsd=org/apache/cxf/binding/soap/spring/object.xsd, http://schemas.xmlsoap.org/ws/2004/09/policy/ws-policy.xsd=schemas/ws-policy-200409.xsd, http://www.springframework.org/schema/gienah/gienah.xsd=org/gienah/testing/xml/spring-gienah-0.2.xsd, http://www.springframework.org/schema/aop/spring-aop.xsd=org/springframework/aop/config/spring-aop-2.0.xsd, http://cxf.apache.org/schemas/simple.xsd=schemas/simple.xsd, http://www.springframework.org/schema/beans/spring-beans-2.0.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd, http://cxf.apache.org/schemas/configuration/wsrm-manager-types.xsd=schemas/configuration/wsrm-manager-types.xsd, http://schemas.xmlsoap.org/ws/2005/02/rm/wsrm-policy.xsd=schemas/configuration/wsrm-policy.xsd, http://www.springframework.org/schema/tx/spring-tx.xsd=org/springframework/transaction/config/spring-tx-2.0.xsd, http://www.springframework.org/schema/tool/spring-tool-2.0.xsd=org/springframework/beans/factory/xml/spring-tool-2.0.xsd, http://www.springframework.org/schema/lang/spring-lang.xsd=org/springframework/scripting/config/spring-lang-2.0.xsd, http://cxf.apache.org/schemas/configuration/cxf-beans.xsd=schemas/configuration/cxf-beans.xsd, http://cxf.apache.org/schemas/ws/addressing.xsd=schemas/ws-addr-conf.xsd, http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd=schemas/oasis-200401-wss-wssecurity-secext-1.0.xsd, http://www.springframework.org/schema/jee/spring-jee-2.0.xsd=org/springframework/ejb/config/spring-jee-2.0.xsd, http://cxf.apache.org/schemas/core.xsd=schemas/core.xsd, http://www.w3.org/2007/02/ws-policy.xsd=schemas/ws-policy-200702.xsd, http://www.springframework.org/schema/jee/spring-jee.xsd=org/springframework/ejb/config/spring-jee-2.0.xsd, http://www.w3.org/2001/xml.xsd=schemas/xml.xsd, http://cxf.apache.org/schemas/configuration/http-conf.xsd=schemas/configuration/http-conf.xsd, http://cxf.apache.org/schemas/configuration/http-jetty.xsd=schemas/configuration/http-jetty.xsd, http://cxf.apache.org/schemas/configuration/jms.xsd=schemas/configuration/jms.xsd, http://www.springframework.org/schema/tx/spring-tx-2.0.xsd=org/springframework/transaction/config/spring-tx-2.0.xsd, http://www.springframework.org/schema/tool/spring-tool.xsd=org/springframework/beans/factory/xml/spring-tool-2.0.xsd, http://www.springframework.org/schema/util/spring-util-2.0.xsd=org/springframework/beans/factory/xml/spring-util-2.0.xsd, http://www.springframework.org/schema/lang/spring-lang-2.0.xsd=org/springframework/scripting/config/spring-lang-2.0.xsd, http://schemas.xmlsoap.org/wsdl/http/=schemas/wsdl/http.xsd, http://schemas.xmlsoap.org/wsdl/=schemas/wsdl/wsdl.xsd, http://schemas.xmlsoap.org/ws/2004/08/addressing=schemas/wsdl/addressing.xsd} dkulp wrote: > > > You could add an XmlCatalog to the catalog resolver to map the > http://schemas.xmlsoap.org/schemas/wsdl/wsdl.xsd location to something > that's local. > > Dan > > > On Wednesday 07 November 2007, Adrian C wrote: >> Hate to be answering my own posts but the cause of this is the fact >> that I am behind a proxy server. Seems that the following import in >> jms-conf.xsd, http-conf.xsd causes the xsd resolver to run off to the >> internet to try and find the schema. Is there anyway around this? >> >> http://schemas.xmlsoap.org/wsdl/"; >> schemaLocation="http://schemas.xmlsoap.org/schemas/wsdl/wsdl.xsd"/> >> >> How did I know this - -well if I hack http-conf.xsd to do the >> following it works! >> >> http://schemas.xmlsoap.org/wsdl/"; >> schemaLocation="file:///c:/temp/schemas/wsdl/wsdl.xsd"/> >> >> >> Thanks >> >> Adrian C wrote: >> > Hi, >> > >> > Am doing some testing with jms & am getting the error below, has >> > anyone seen anything like this before? >> > >> > Thanks >> > >> > org.springframework.beans.factory.xml.XmlBeanDefinitionStoreExceptio >> >n: Line 175 in XML document from class path resource >> > [junit/wsclient-context.xml] is invalid; nested exception is >> > org.xml.sax.SAX
Re: cannot resolve wsdl:tExtensibilityElement
Hate to be answering my own posts but the cause of this is the fact that I am behind a proxy server. Seems that the following import in jms-conf.xsd, http-conf.xsd causes the xsd resolver to run off to the internet to try and find the schema. Is there anyway around this? http://schemas.xmlsoap.org/wsdl/"; schemaLocation="http://schemas.xmlsoap.org/schemas/wsdl/wsdl.xsd"/> How did I know this - -well if I hack http-conf.xsd to do the following it works! http://schemas.xmlsoap.org/wsdl/"; schemaLocation="file:///c:/temp/schemas/wsdl/wsdl.xsd"/> Thanks Adrian C wrote: > > Hi, > > Am doing some testing with jms & am getting the error below, has anyone > seen anything like this before? > > Thanks > > org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: > Line 175 in XML document from class path resource > [junit/wsclient-context.xml] is invalid; nested exception is > org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name > 'wsdl:tExtensibilityElement' to a(n) 'type definition' component. > > Caused by: org.xml.sax.SAXParseException: src-resolve: Cannot resolve the > name 'wsdl:tExtensibilityElement' to a(n) 'type definition' component. > > at > com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236) > > at > com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:172) > > at > com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:382) > > at > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:2241) > > at > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1201) > > at > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexContent(XSDComplexTypeTraverser.java:715) > > at > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexTypeDecl(XSDComplexTypeTraverser.java:288) > > at > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseGlobal(XSDComplexTypeTraverser.java:196) > > at > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1333) > > at > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseNamedElement(XSDElementTraverser.java:376) > > at > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseGlobal(XSDElementTraverser.java:248) > > at > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseSchemas(XSDHandler.java:1081) > > at > com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:481) > > at > com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:556) > > at > com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.findSchemaGrammar(XMLSchemaValidator.java:2459) > > at > com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:1807) > > at > com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:705) > > at > com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:330) > > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693) > > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) > > at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) > > at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) > > at > com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) > > at > com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250) > > at > com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292) > > at > org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) > >
cannot resolve wsdl:tExtensibilityElement
Hi, Am doing some testing with jms & am getting the error below, has anyone seen anything like this before? Thanks org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 175 in XML document from class path resource [junit/wsclient-context.xml] is invalid; nested exception is org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'wsdl:tExtensibilityElement' to a(n) 'type definition' component. Caused by: org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'wsdl:tExtensibilityElement' to a(n) 'type definition' component. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:172) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:382) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:2241) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1201) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexContent(XSDComplexTypeTraverser.java:715) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexTypeDecl(XSDComplexTypeTraverser.java:288) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseGlobal(XSDComplexTypeTraverser.java:196) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1333) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseNamedElement(XSDElementTraverser.java:376) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseGlobal(XSDElementTraverser.java:248) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseSchemas(XSDHandler.java:1081) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:481) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:556) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.findSchemaGrammar(XMLSchemaValidator.java:2459) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:1807) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:705) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:330) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:388) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:340) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:317) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:125) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:141) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:167) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:113) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:79) at org.springframework.context.support.AbstractRefr
class loading stax-api.jar
Not to sure if I should be posting this to the developers list or not - however I came a cross an issue with stax.jar on OAS. There was a problem with class loading because of stax-api.jar including QName. Issue was resolved by using jsr173_api-2.2.0.jar instead. I think that this should be part of jsr173_api-2.2.0.jar should be part of cxf dependencies rather that stax-api.jar -- View this message in context: http://www.nabble.com/class-loading-stax-api.jar-tf4763868.html#a13624807 Sent from the cxf-user mailing list archive at Nabble.com.
local transport & ws-addressing
I don't seem to be able to set ws-addressing for my local transport. Is there
something that I am am doing wrong?
Bus bus = BusFactory.getDefaultBus();
LocalTransportFactory localTransport = new LocalTransportFactory();
DestinationFactoryManager dfm =
bus.getExtension(DestinationFactoryManager.class);
dfm.registerDestinationFactory("http://schemas.xmlsoap.org/soap/http";,
localTransport);
dfm.registerDestinationFactory("http://schemas.xmlsoap.org/wsdl/soap/http";,
localTransport);
dfm.registerDestinationFactory("http://cxf.apache.org/bindings/xformat";,
localTransport);
dfm.registerDestinationFactory("http://cxf.apache.org/transports/local";,
localTransport);
ConduitInitiatorManager extension =
bus.getExtension(ConduitInitiatorManager.class);
extension.registerConduitInitiator("http://cxf.apache.org/transports/local";,
localTransport);
extension.registerConduitInitiator("http://schemas.xmlsoap.org/wsdl/soap/http";,
localTransport);
extension.registerConduitInitiator("http://schemas.xmlsoap.org/soap/http";,
localTransport);
extension.registerConduitInitiator("http://cxf.apache.org/bindings/xformat";,
localTransport);
ApplicationContext ctx =
WebApplicationContextUtils.getWebApplicationContext(getServletContext());
ObjectManagementV1Impl impl =
(ObjectManagementV1Impl)ctx.getBean("ObjectManagementV1Impl");
ServerFactoryBean sf = new ServerFactoryBean();
sf.setAddress("local://ObjectManagementV1");
sf.getFeatures().add(new WSAddressingFeature());
sf.setServiceBean(impl);
sf.getInInterceptors().add((AbstractSoapInterceptor)ctx.getBean("auditingin.interceptor"));
sf.getInInterceptors().add((AbstractSoapInterceptor)ctx.getBean("pa.interceptor"));
sf.getInInterceptors().add((AbstractSoapInterceptor)ctx.getBean("api.interceptor"));
sf.setServiceClass(ObjectManagementV1.class); // Optionally specify
the service interface
sf.create();
ClientProxyFactoryBean cf = new ClientProxyFactoryBean();
cf.setAddress("local://ObjectManagementV1");
cf.getOutFaultInterceptors().add(new SoapActionOutInterceptor());
cf.setServiceClass(ObjectManagementV1.class); // Optionally specify
the service interface
cf.getFeatures().add(new WSAddressingFeature());
objectManagement = (ObjectManagementV1) cf.create();
--
View this message in context:
http://www.nabble.com/local-transport---ws-addressing-tf4719686.html#a13492388
Sent from the cxf-user mailing list archive at Nabble.com.
Re: jaxws validation
sweet thanks - is there a list of all these properties/features anywhere so that we aren't bothering all you guys with questions? Willem2 wrote: > > Hi, > > You could turn on the validation by configuration like this[1] > [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/distribution/src/main/release/samples/wsdl_first/cxf.xml > > Willem. > > Adrian C wrote: >> Anyone have any ideas how to turn on validation jabx unmarshalling? My >> service is receiving a request that is invalid however it is being >> unmarshalled as normal. >> >> Thanks >> > > -- View this message in context: http://www.nabble.com/jaxws-validation-tf4689811.html#a13404133 Sent from the cxf-user mailing list archive at Nabble.com.
jaxws validation
Anyone have any ideas how to turn on validation jabx unmarshalling? My service is receiving a request that is invalid however it is being unmarshalled as normal. Thanks -- View this message in context: http://www.nabble.com/jaxws-validation-tf4689811.html#a13403665 Sent from the cxf-user mailing list archive at Nabble.com.
ResourceInjector/Jsr250BeanPostProcessor NPE
Hi, I am trying to migrate a XFire project to CXF and seem to have fallen quiet early on. I have alot of spring configuration that used to get loaded up by ContextLoaderListener before any of the xfire context were loaded up. I loaded up my XFire service contexts using the XFireConfigurableServlet. Now that I am trying to migrate, it appears I have no way to load up CXF after the all my context have loaded (if I try to do this now using the config location param for the servlet defintion I get a no bean cxf found exception). So I am forced to load my CXF services with my main spring configuration, but this doesn't work because I have a statically initialized bean - my problem seems to be with the Jsr250BeanPostProcessor & a bean which is created using a factory method at startup. i.e. ... This bean causes a NullPointerException (see below), so any suggestions as to what to do. I have a attached a source code to recreate this problem. Thanks 828 [main] ERROR org.springframework.web.context.ContextLoader - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dummy.factory ' defined in class path resource [demo/spring/bean-defs.xml]: Initialization of bean failed; nested exception is java.lang.NullPointerException Caused by: java.lang.NullPointerException at org.apache.cxf.common.injection.ResourceInjector.getAnnotatedMethods (ResourceInjector.java:333) at org.apache.cxf.common.injection.ResourceInjector.getPostConstructMethods(ResourceInjector.java:323) at org.apache.cxf.common.injection.ResourceInjector.invokePostConstruct(ResourceInjector.java :284) at org.apache.cxf.common.injection.ResourceInjector.construct(ResourceInjector.java:84) at org.apache.cxf.bus.spring.Jsr250BeanPostProcessor.postProcessBeforeInitialization(Jsr250BeanPostProcessor.java :44) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:301) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean (AbstractAutowireCapableBeanFactory.java:1167) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:425) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject (AbstractBeanFactory.java:251) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean (AbstractBeanFactory.java:248) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons (DefaultListableBeanFactory.java:287) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352) at org.springframework.web.context.ContextLoader.createWebApplicationContext (ContextLoader.java:244) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:187) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java :49) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4216) at org.apache.catalina.core.ContainerBase.addChildInternal (ContainerBase.java:760) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544) at org.apache.catalina.startup.HostConfig.deployDescriptor (HostConfig.java:626) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488) at org.apache.catalina.startup.HostConfig.start (HostConfig.java:1138) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120) at org.apache.catalina.core.ContainerBase.start (ContainerBase.java:1022) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start (StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start (Catalina.java:552) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.Delegatin
