In future JAX-RPC 2.0 will be based on JAXB 2.0, and since JAX-RPC
already requires EJB bindings, your issue will have to be resolved by
JAXB or JAX-RPC working groups.
Thanks,
Gia
>
> -----Original Message-----
> From: Adam Sherman [mailto:adam_at_tritus.ca]
> Sent: Wednesday, October 29, 2003 10:49 AM
> To: users_at_jaxb.dev.java.net
>
> On 10/29/03 10:45:19 -0800 Kohsuke Kawaguchi wrote:
>
> >> I would like to use the generated classes behind forms
> being serviced
> >> by a web framework (Think Struts, Spring, WW, etc).
> >>
> >> The problem is that most, if not all, of these frameworks
> expect to
> >> be able to simply instantiate a Bean and use it.
> >>
> >> This can't be done with the generated classes, AFAIK.
> >
> > You can create implementation classes directly if you want. For
> > example, if you want a bean for abc.def.Foo, you can just do new
> > abc.def.impl.FooImpl();
> >
> > I guess this won't be portable, but as a workaround, it might be OK
> > for you.
>
> That's what I will do for now. Any thoughts on the future of
> doing this?
>
> Another related question: upon creation of Foo, foo.getBar()
> returns null.
> It would be better for me if it returned an empty Bar object.
> Thoughts?
>
> Thanks,
>
> A.
>
>
> --
> Adam Sherman
> Tritus CG Inc
> +1 (613) 797-6819
> http://www.tritus.ca/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net