[JBossWS] - Re: Where do I have to *.jws web service files in JBoss ?
by thoste
"richard.opalka(a)jboss.com" wrote : Please, read our documentation first.
| If still confused download source distribution and try to find the example that fits your needs.
| If still confused post to user forum ;)
Yes, I read the documentation and I thought this is the user forum.
Ok, lets explain the problem in more detail:
I tried out the deployment as you suggested. When I put the *.jws and web.xml (see both below)
into the deployment directory I got the error shown at the bottom.
So what wrong?
MyWebServiceClass.jws:
@WebService( name="Sum", targetNamespace = "http://sumtest.ws.ptest/", serviceName = "aaa" )
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE, style = SOAPBinding.Style.DOCUMENT)
public class MyWebServiceClass {
@WebMethod
public double myWebServiceMethod( String job, double x ) {
if ("square".equalsIgnoreCase(job) )
return x * x;
if ("root".equalsIgnoreCase(job) )
return Math.sqrt( x );
return 0.; }
}
web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
<servlet-name>MyWebServiceClass</servlet-name>
<servlet-class>MyWebServiceClass</servlet-class>
<servlet-mapping>
<servlet-name>MyWebServiceClass</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
</web-app>
Result in JBoss:
14:34:25,640 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@e95e7022 { url=file:/D:/java/JBoss/v4.2.2/server/default/deploy/MyWebServiceClass.jws }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/D:/java/JBoss/v4.2.2/server/default/deploy/MyWebServiceClass.jws
altDD: null
lastDeployed: 1209385176890
lastModified: 1209385176890
mbeans:
org.jboss.deployment.DeploymentInfo@dc36ff7c { url=file:/D:/java/JBoss/v4.2.2/server/default/deploy/web.xml }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/D:/java/JBoss/v4.2.2/server/default/deploy/web.xml
altDD: null
lastDeployed: 1209385865421
lastModified: 1209385865421
mbeans:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@e95e7022 { url=file:/D:/java/JBoss/v4.2.2/server/default/deploy/MyWebServiceClass.jws }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/D:/java/JBoss/v4.2.2/server/default/deploy/MyWebServiceClass.jws
altDD: null
lastDeployed: 1209385176890
lastModified: 1209385176890
mbeans:
org.jboss.deployment.DeploymentInfo@dc36ff7c { url=file:/D:/java/JBoss/v4.2.2/server/default/deploy/web.xml }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/D:/java/JBoss/v4.2.2/server/default/deploy/web.xml
altDD: null
lastDeployed: 1209385865421
lastModified: 1209385865421
mbeans:
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147350#4147350
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147350
18 years, 1 month
[Messaging, JMS & JBossMQ] - Re: XA Recovery of messages sent to a Topic
by mmusgrov
The remaining issue, then, is to do with how the JBossMQ XAResource handles non-durable subscriptions:
If there are durable subscriptions for a topic then published messgages are put on a peristent queue otherwise a temporary queue is used (see method JMSTopic.addMessage(...)). It appears that only messages put on a peristent queue are recoverable.
However, all messages are associated with the transaction (see SpyXAResourceManager.addMessage(...)) and the SpyXAResourceManager.prepare(...) method will only return XAResource.XA_RDONLYif there are no messages associated with the transaction (see TXState.isReadOnly()). The correct behaviour should be to check if there are any messages on any persistent queues associated with the transaction when determining whether this particular transaction branch is read only.
This is a problem for TM recovery since the XAResource a for temporary topic queue does not return XAResource.XA_RDONLY for the prepare phase. Thus when the TM calls recover on the resource no xids are returned and hence the transaction can never be recovered.
Could anyone hazzard a guess as to how much effort would be involved in resolving this issue.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147348#4147348
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147348
18 years, 1 month