Try adding @WebMethod(exclude = true) annotation to any method in
your Impl that you don't want to expose in your WSDL. (from a post yesterday
- I've not verified it)
On 7/31/07, Brett Wooldridge <[EMAIL PROTECTED]> wrote:
>
> If I am doing Java first development, and I have an SEI like so:
>
> public interface FooSEI
> {
> Bar getBar();
> }
>
> And a data class like this:
>
> public class Bar
> {
> private int x;
> private String s;
>
> public int getX()
> {
> ...
> }
>
> public String getStr()
> {
> ...
> }
> }
>
> Is there an annotation or some other mechanism by which I can exclude the
> "s" attribute of Bar from the WSDL generation? For example, bar.getStr()
> should only be available on the server-side, whereas the public API with
> respect to the client only contains the 'x' attribute (bar.getX()).
>
> Thanks,
> Brett
>
>
