cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: CXF on Eclipse-WS Indigo in pain
Date Fri, 29 Jul 2011 12:52:13 GMT
On Thursday, July 28, 2011 9:42:03 PM Ray Ramos wrote:
> Daniel Kulp <dkulp@...> writes:
> > Is there more to that stack trace?    There should be at least one more
> > "Caused by" at the end of that where the actual location of the NPE
> > should be found.  Right now, I have no idea.
> > 
> > In regards to removing the wsdlLocation attribute from <jaxws:endpoint>,
> > in that case, it would be picking it up from the @WebService annotation
> > and you have it defined as:
> > 
> > http://localhost:8080/Coplink_LEXS_Service/services/SRWebServiceBean?wsd
> > l
> > 
> > Thus, it's trying to load it from there, but tomcat likely hasn't even
> > started the 8080 port yet.   If it has, it's likely looping trying to
> > start the service which needs the wsdl so it starts the service,
> > etc....
> 
> I traced this all the way down to a bug in Class.getEnumConstants()
> 
> See bug 7068755.
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7068755

Wow!   That's an interesting bug.  :-)

Nice job tracking that one down.   Nothing CXF/JAXB can really do about that 
though.  :-(

Dan


> 
> Unfortunately, the perception CXF/JAXB/Java in my small world has already
> been damaged.  The opinion of some now is that CXF/JAXB/Java can't handle
> large web services.  Thanks for taking the time to look into this.
> 
> -Ray
-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com

Mime
View raw message