[JBoss Web Services Users] - Re: Cannot find service endpoint target
by groovie
Salut mecs,
the problem hints to an inavailable ressource on the
session bean, like a delayed of unavailable
datasource.You shold check the server.log for any
kind of ressource problems.
In our case, our web-services suddently ran
into the same problem,. throwing the same exception.
We are using an Oracle-DB for to persist our data.
Sombody changed the OracleDialect to OracleDialect
or another one finally we hat the problems with our
webservice.
Some week later i noticed error messages (only one
line) like this one:
server.log.2009-10-02:2009-10-02 11:28:36,575 INFO [org.hibernate.dialect.Dialect] Using dialect: org.hibernate.dialect.Oracle10gDialect
server.log.2009-10-02:2009-10-02 11:39:37,602 INFO [org.hibernate.dialect.Dialect] Using dialect: org.hibernate.dialect.OracleDialect
server.log.2009-10-02:2009-10-02 11:39:37,602 WARN [org.hibernate.dialect.Oracle9Dialect] The Oracle9Dialect dialect has been deprecated; use either Oracle9iDialect or Oracle10gDialect instead
Despite the fact, that this are only warnings, i guess,
i found that smoking gun.
Assumption:
The error/warning condition slowed down the
session bean, causing the WS unsuccessfully
searching for a session bean, that has not been
started.
I switched to the Oracle10gDialect and the problem
disappeared!
Voila
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259234#4259234
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259234
15 years, 2 months
[JBoss Web Services Users] - Possible bug when namespace name ends with
by VanceChristiaanse
Hello JBoss WS fans,
In the schemas in the WSDL for my web service I need to refer to the namespace URI http://www.w3.org/1999/02/22-rdf-syntax-ns# which ends with "#". Unfortunately, when I do I get an error when I start the server:
Caused by: java.lang.NullPointerException
| at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:178)
| at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:451)
| at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:466)
| at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:180)
| at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:129)
| at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:293)
|
When I remove the "#" from the namespace name in the WSDL (and regenerate classes with wsconsume and make corresponding class name changes) the web service deploys without error and clients can access it.
I have created a very simple WSDL file that demonstrates this error and tested it on a clean installation of JBossAS 5.1.0.GA (released 23 May 2009). Is it okay to submit it as a bug without building from the latest source and testing? Or is this not a bug? (I notice the value of the soapAction attribute in the generated WSDL includes the fragment notation "#" whether or not the namespace name includes the "#".)
Thank you for any feedback or advice,
Vance
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259000#4259000
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259000
15 years, 2 months
[JBoss Web Services Users] - Use JAX-RPC in 4.2.3.GA
by newmanw10
Does anyone know which system properties I need to set to use JAX-RPC in jboss 4.2.3.
I don't want to use the jboss.ws stuff that comes with JBoss I want to use teh sun libs. I have the libs in the correct path but I am not sure of all the System properties I need to set to get this to work correclty.
i.e.
-Djavax.xml.soap.MessageFactory=com.sun.xml.messaging.saaj.soap.ver1_2.SOAPMessageFactory1_2Impl
-Djavax.xml.soap.MetaFactory=com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl
-Djavax.xml.soap.SOAPFactory=com.sun.xml.messaging.saaj.soap.ver1_2.SOAPFactory1_2Impl
When I do this I get:
java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.Envelope1_1Impl
at org.jboss.ws.core.soap.SOAPEnvelopeImpl
So it is still going into the jboss stuff instead of the jax-rpc stuff. Any ideas?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258971#4258971
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258971
15 years, 2 months