Package name generated by wsprovide

[zauberlehrling]

Hi,

I ran the following ant-task which executes the tool wsprovide.

<wsprovide verbose="true"
 fork="true"
 keep="true"
 destdir="${build.dir}"
 sourcedestdir="${src.dir}"
 genwsdl="true"
 resourcedestdir="${meta.dir}/beispiel_9"
 sei="beispiel_9.EjbEndpoint">
 <classpath>
 <pathelement path="${build.dir}"/>
 </classpath>
</wsprovide>

The service endpoint resides in the package

beispiel_9

The wsdl file were generated fine in the dirctory ${meta.dir}/beispiel_9.

But the generated wrapper classes SayHello.java and SayHelloResponse.java were placed in the package

beispiel_9.jaxws

and not in the package beispiel_9. Why this?

For heaven's sake from where does the 'jaxws' come?

Best regards,

Frank

[zauberlehrling]

I've forgotten the code of beispiel_9.EjbEndpoint is very simple:

package beispiel_9;

import javax.ejb.Stateless;
import javax.jws.WebMethod;
import javax.jws.WebService;


@WebService
@Stateless
public class EjbEndpoint {

 @WebMethod
 public String sayHello(String name)
 {
 return "Hallo "+name+"!";
 }

}

[jason.greene]

The spec requires that all wrappers be generated in the jaxws sub package by default (to avoid name conflicts). You can however control their destination using the RequestWrapper and ResponseWrapper annotations

@RequestWrapper(classname="beispiel_9.Hello");

Keep in mind though that you do not need to use wsprovide to deploy on jbossws, we generate all of the wrapper classes dynamically at deploy time. You only need them if you want your deployment to be portable to other containers.

-Jason

[zauberlehrling]

Oh, this helps! Thank you very much.