URG: jboss JAXWS webservice
by Arvinder Kaur
Hello
I am using jboss JAXWS webservice.
When i call them from my application (a .war file) running on
JBOSS.4.2.3.GA. Web-service
call executes and returns result objects.
But When i use call web-service in my main() ( standalone class) with same (
.jars as used above in application), I get following errors.
Please help. Thanks to give some direction.
Getting these errors:
================
OperationMetaData:
qname={http://endpoint.ws.eventmgt.qs.st/}updateAction
javaName={http://endpoint.ws.eventmgt.qs.st/}updateAction
style=document/literal/WRAPPED
oneWay=false
soapAction=
DEBUG (JAXWSClientMetaDataBuilder.java:274) 16:28:23,090 - START:
rebuildMetaData
DEBUG (EndpointMetaData.java:310) 16:28:23,105 - setParameterStyle: null
DEBUG (EndpointMetaData.java:864) 16:28:23,106 - Create new config
[name=Standard Client,file=META-INF/standard-jaxws-client-config.xml]
DEBUG (JBossWSConfigFactory.java:140) 16:28:23,109 - getConfig:
[name=Standard Client,url=META-INF/standard-jaxws-client-config.xml]
DEBUG (JBossWSConfigFactory.java:70) 16:28:23,110 - parse:
jar:file:/home/arvinder/jbossws-client.jar!/META-INF/standard-jaxws-client-config.xml
Exception in thread "main" java.lang.NoSuchMethodError:
org.jboss.xb.binding.Unmarshaller.setSchemaValidation(Z)V
at
org.jboss.ws.metadata.config.JBossWSConfigFactory.parse(JBossWSConfigFactory.java:78)
at
org.jboss.ws.metadata.config.JBossWSConfigFactory.getConfig(JBossWSConfigFactory.java:149)
at
org.jboss.ws.metadata.umdm.EndpointMetaData.initEndpointConfigMetaData(EndpointMetaData.java:872)
at
org.jboss.ws.metadata.umdm.EndpointMetaData.initEndpointConfig(EndpointMetaData.java:849)
at
org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:292)
at
org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:269)
at
org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:240)
at javax.xml.ws.Service.getPort(Service.java:169)
at
st.itacn.bs.fmeabatches.wsclient.ActionWSClient.getActionEndPoint(ActionWSClient.java:43)
at
st.itacn.bs.fmeabatches.datalayer.ActionDataLayer.createAction(ActionDataLayer.java:80)
at
st.itacn.bs.fmeabatches.batchRun.ActionCreation.main(ActionCreation.java:39)
15 years, 9 months
[EJB 3.0 Development] - What makes a business method asynchronous?
by jaikiran pai
jaikiran pai [http://community.jboss.org/people/jaikiran] created the discussion
"What makes a business method asynchronous?"
To view the discussion, visit: http://community.jboss.org/message/552992#552992
--------------------------------------------------------------
... other than the use of @Asynchronous annotation or it's xml equivalent. >From what I see in the EJB3.1 Spec, Section 4.5.1:
The @Asynchronous annotation is used to designate which business methods are asynchronous.
...
Asynchronous methods can also be designated via the deployment descriptor.
I do however see that in our async interceptor (which has to decide whether to spawn a new thread or continue in the current one), we additionally check for method return type to decide whether it's asynchronous:
// Determine if asynchronous (either returns Future or has @Asynchronous)
if (invocation.resolveAnnotation(Asynchronous.class) != null || actualMethod.getReturnType().equals(Future.class))
Just wondering whether this is OK. The only side-effect that I can think of, with this implicit rule for asynchronous method, is the difference in transaction semantics for that method invocation.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552992#552992]
Start a new discussion in EJB 3.0 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 9 months