Glen,

Thanks for having a look.  When I wrote, "..did an HTTP GET for the
WSDL...",
I was referring to just using a browser as you suggest.  The other point
I should
have mentioned was that the actual service operations work, I just can't
serve
out the WSDL and have no idea why.

  -Chris

-----Original Message-----
From: Glen Mazza [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 10, 2008 7:16 PM
To: [email protected]
Subject: Re: Cannot request WSDL with CXF-2.1 deployed to Tomcat


I don't know--I've been able to access the WSDL with my WSDL-first
sample on Tomcat, using CXF 2.1, all the time: 
http://www.jroller.com/gmazza/date/20080417#WFstep9 .  Any delta between
what you're doing and what I'm doing?

BTW--can you see "http://localhost:8080/wsstest/services/secadmin?wsdl";
from a web browser?  If you can't, nothing else will work--so I would
concentrate on being able to view it from a browser first.

HTH,
Glen


Wolf, Chris (IT) wrote:
> 
> I am not getting this exception:
> 
> javax.xml.stream.XMLStreamException: NamespaceURI cannot be null
> 
> If anyone can help, that would be great.
> 
> I recently upgraded from an April snapshot to CXF-2.1, and now I get a

> stack trace whenever I do an HTTP GET for the WSDL from my published 
> endpoint:
>  
>  
>  
> WARNING: org.apache.cxf.transport.http.WSDLQueryHandler Exception 
> caught writing response.
> org.apache.cxf.transport.http.WSDLQueryException: Exception occurred 
> while trying to process 
> http://localhost:8080/wsstest/services/secadmin?wsdl
>       at
> org.apache.cxf.transport.http.WSDLQueryHandler.writeResponse(WSDLQuery
> Ha
> ndler.java:229)
>       at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletContr
> ol
> ler.java:137)
>       at
> org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXF
> Se
> rvlet.java:170)
> [...]
> Caused by: javax.xml.stream.XMLStreamException: NamespaceURI cannot be

> null
>       at
> com.sun.xml.stream.writers.XMLStreamWriterImpl.writeAttribute(XMLStrea
> mW
> riterImpl.java:620)
>       at
> org.apache.cxf.staxutils.StaxUtils.writeElement(StaxUtils.java:520)
>       at
> org.apache.cxf.staxutils.StaxUtils.writeElement(StaxUtils.java:440)
>       at
> org.apache.cxf.staxutils.StaxUtils.writeDocument(StaxUtils.java:421)
>       at
> org.apache.cxf.staxutils.StaxUtils.writeDocument(StaxUtils.java:411)
>       at
> org.apache.cxf.staxutils.StaxUtils.writeNode(StaxUtils.java:560)
>       at
> org.apache.cxf.transport.http.WSDLQueryHandler.writeResponse(WSDLQuery
> Ha
> ndler.java:226)
> 
> 
> I traced the problem to org.apache.cxf.staxutils.StaxUtils.java, lines
> 484-488:
> 
>        } else {
> //            System.out.println("Calling writeStartElement for local
> name : " 
> //            + localName + " URI: " + ns + " Prefix :" + prefix);
>             writer.writeStartElement(prefix, localName, ns);
>         }
> 
> The values for the "writeStartElement" are:
> prefix = "wsdl"
> localname = "definitions"
> ns = "http://schemas.xmlsoap.org/wsdl/";
> 
> The start element looks like:
> 
> <wsdl:definitions name="SecAdmin"
> targetNamespace="urn:secadmin.svcscore.ibd.ms.com" 
>     xmlns="http://schemas.xmlsoap.org/wsdl/"; 
>     xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; 
>     xmlns:tns="urn:secadmin.svcscore.ibd.ms.com"
>     xmlns:x1="urn:secadmin.svcscore.ibd.ms.com/types"
>     xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; 
>     xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> --------------------------------------------------------
> 
> NOTICE: If received in error, please destroy and notify sender. Sender

> does not intend to waive confidentiality or privilege. Use of this 
> email is prohibited when received in error.
> 
> 

--
View this message in context:
http://www.nabble.com/Cannot-request-WSDL-with-CXF-2.1-deployed-to-Tomca
t-tp17766300p17766888.html
Sent from the cxf-user mailing list archive at Nabble.com.
--------------------------------------------------------

NOTICE: If received in error, please destroy and notify sender. Sender does not 
intend to waive confidentiality or privilege. Use of this email is prohibited 
when received in error.

Reply via email to