Skip to main content

Things in the JAX-WS EA2 docs

2 replies [Last post]
hr_stoyanov
Offline
Joined: 2004-04-01

Doug-,
Here are a few additional findings, you might want to look into:

1) APT docs: Is the sourcePath attribute always required? It does look so, even though there can be nested

2) APT docs: Is the -Averbose=true used at all? There seems to be a verbose attribute anyway...

3) The sun-jaxws.xml has urlpattern, but there is another standard one in the web.xml descriptor for the servlet. What is the relation between the two? Do we need to specify the servlet class (and context listener) in web.xml at all?

4) Are the portable beans generated by APT and WSGEN (keep="true") the same?

5) There are a bunch of references to "JAX-RPC 2.0" in the jaxws 2.0 docs.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
kohlert
Offline
Joined: 2003-06-16

1) APT docs: Is the sourcePath attribute always required? It does look so, even though there can be nested

For very simple endpoints, no, but most of the time, yes.

2) APT docs: Is the -Averbose=true used at all? There seems to be a verbose attribute anyway...

The -A option is apt's way of passing flags to the annotation processors. The annotation processors don't have access to apt's -verbose flag. Bummer, huh.

3) The sun-jaxws.xml has urlpattern, but there is another standard one in the web.xml descriptor for the servlet. What is the relation between the two? Do we need to specify the servlet class (and context listener) in web.xml at all?

A urlpattern for an endpoint in sun-jaxws.xml should have the same url-pattern in web.xml. That associates the servlet to the endpoint.

One thing is sun-jaxws.xml has the attribute urlpattern, and web.xml has url-pattern. We could make the sun-jaxws.xml one also "url-pattern". What do you think?

4) Are the portable beans generated by APT and WSGEN (keep="true") the same?

For document/lit bare and rpc/lit yes. If your endpoint has webparam annotations with name elements for every parameter in the endpoint, yes they will be the same. Otherwise, for doc/lit wrapped, the apt generated beans will have the properties with the same names as the parameters from the source code; the wsgen beans will have parameter properties with names like arg0, arg1, etc. This is because the reflection apis do not give us the parameter names at runtime. However, if the WebParam name element is specified, both apt and wsgen will use that value. Fun, huh.

5) There are a bunch of references to "JAX-RPC 2.0" in the jaxws 2.0 docs.

Thanks, I just updated them, they should all be gone now.

hr_stoyanov
Offline
Joined: 2004-04-01

2) if the -Averbose=true is not working with APT, please, fix the APT docs, the row in the table

3) As far as I understand this is because you dropped the cooked war file. If so, yes, it is better to rename it to url-pattern. It would be nice if there is some way to make sure the two values are the same between sun-jaxws.xml and web.xml too.

One other thing worth mentioning in the docs is that APT completely replaces javac, so that folks do not try to use javac then apt (in ANT files, for example).

I am still not convinced that producing the WSDL/schema file only withing wsgen is a good idea. I'd prefer APT to be able to generate WSDL/schama1.xsd as well as wsgen. It makes for simpler ANT scripts in the 'fromjava' case, where you do not want the extra step with wsgen only to get your WSDL/schema1.xsd.