Peter,
Now that I've skimmed chapter nine of your book, I can address your question
"Does you app include the WSDL or are you letting the server generate it?
If you include the WSDL, please post it. Also, post the source for the web service."
I am using the the bottom-up approach — as you explain in your book
I have coded the web service first and then planned to generate the
WSDL from the web service. I didn't realize that I could generate the WSDL
using a utility, such as the wsprovide utility supplied by JBossWS, so I was
package the web service and deploying it with the expectation that the web
services deployer would automatically generate the WSDL.
I sitll don't understand why when I attempt to go to
<jboss_path>\server\default\data\wsdl\<project_name>.war\<filename>.wsdl
in the data directory there is no wsdl directory. Why ???
I was able to attempt your SaleTax webservice using eclipse and jboss-5.0.0CR2 candidate release 2
and upon deploy the log shows
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException Error during deploy: vfszip:/opt/jboss_5.0.0GA/jboss-5.0.0.CR2/server/default/deploy/ch09.war
followed later by
*** CONTEXTS IN ERROR: Name -> Error
followed by a java.lang.NoSuchMethodError
When I visit localhost:8080/jbossws/services, I see no services - no
endpoints are deployed.
So I will have to wait until my downloads of JBoss5.0.1 have finished before I will know if my problems are specific to candidate release 2.
I did have to comment out ${SalesTax.import} and ${SalesTax.annotation} to allow an error free compile.
