I was just about to ask whether that would help, Jersey was also
interested in this...
We could also move jaxb to glassfish-common package which would make it
available in both web and full distributions...
Thanks,
Snjezana
Bhakti Mehta wrote:
> Maybe one solution is just remove jaxb from metro package and create a
> new package for jaxb and let jaxb be available for web distribution?
> Regards,
> Bhakti
>
> Ed Burns wrote:
>
>>>>>>> On Thu, 30 Apr 2009 12:57:12 -0700, Jerome Dochez
>>>>>>> <Jerome.Dochez_at_Sun.COM> said:
>>>>>>>
>>>>>>
>>
>> JD> I am not sure I understand what the initial problem is.
>> JD> first you seem to suggest we just need to modify the
>> felix.properties JD> and then you want to add a bundles (with what
>> content exactly ?) to JD> the web distribution only.
>>
>> JD> are u trying to override the JAXB APis from the JDK to run BV ?
>>
>> JD> could you clarify ?
>>
>> Of course, but this is why I wanted a voice meeting.
>>
>> The problem is that JSR-303 version 1.0 CR2 now has dependencies on
>> javax.xml.bind and javax.xml.bind.annotation. The current configuration
>> for the web distribution does not expose these packages via OSGi.
>> However you want to fix that problem is fine with me, but we need to
>> decide fast because JSR-303 version 1.0 CR2 has binary contract changes
>> that impact JSF 2.0, which also needs to be in by the 4 May deadline.
>>
>> Does that help?
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>