Jerome,
Please read inline
Jerome Dochez wrote:
> my initial feeling is that it is too coarse grained.
I tend to agree but if different profiles start plugging in their own
versions of the subparts wouldnt that be a nightmare to debug? Hence I
brought up this question here should metro be a module or should there
be dependencies for individual technologies in metro?
Regards,
Bhakti
>
> For instance, for people who don't care about java ee compatibility
> and would want to only support say JAXB+JAXWS (which I assume would be
> doable), how would that work ?
>
> also in Java EE 6, different profiles may require different subpart of
> the metro stack, wouldn't that make things harder to decouple...
>
> Jerome
>
> On Feb 28, 2008, at 3:18 PM, Bhakti Mehta wrote:
>
>> Hi,
>> I wanted to check if there are individual modules in v3 depending on
>> various technologies from the metro stack like jaxb, jaxws, sjsxp,
>> stax-ex,saaj?
>>
>> Since all these technologies are bundled in
>> webservices-rt/webservices-tools.jar and the 1.1.2-SNAPSHOT version
>> of metro is already on maven repository
>> Imaybe we should just refer to webservices-rt,webservices-api and
>> webservices-tools in our dependencies
>>
>> The only case maybe where Kohsuke suggested sjsxp (people just
>> wanting to use the parser may not want to get the whole metro stack)
>> In that case we can let the dependency for sjsxp remain in the poms
>> but for other technologies I can just update the poms to use metro.
>>
>> Do other modules see issues with that?
>>
>> Thanks,
>> Bhakti
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>