JSR109 will be updated for JavaEE5 to supprt JAXWS, JSR181 specs. There
will be no need to generate artifacts at all. The reference tests I sent
should give you an idea. Checkout
glassfish/appserv-tests/devtests/webservice/{annotations|ejb_annotations}/no*
to get an idea about "artifacts-free" webservices.
Vijay
Mark Hansen wrote:
> OK - I will do that. One follow-on question, which isn't exactly
> Glassfish, but also a general Java EE 5 question.
>
> Do you know if the runtime deployment mechanism in Java EE 5 will
> still be based on JSR-109 (as in J2EE 1.4) so JSR-181 will be
> implemented by having a processor generate the webservices.xml and
> other deployment descriptors? Or will the model be changed so that a
> JSR-181 annotated class can just be "dropped in" to the container
> without having to generate artifacts?
>
> -- Mark
>
>
> Vijay Ramachandran wrote:
>
>> Yes. Checkout glassfish/appserv-tests/devtests/webservice/annotation or
>> glassfish/appserv-tests/devtests/webservice/ejb_annotation for some
>> samples
>>
>> Vijay
>>
>> On Wed, 2005-11-02 at 14:16, Mark Hansen wrote:
>>
>>> Does Glassfish currently support JSR-181 (WS-Metadata)?
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>