Felix Meschberger wrote
> Hi,
>
> Well, I have been experimenting with the Apache ServiceMix wrapper
> bundles and was successful. So I think, instead of actually creating
> some system bundle fragments for the XML APIs we should probably rather
> add the ServiceMix bundle(s) from the start.
>
>
On Thu, Jan 27, 2011 at 11:28 AM, Felix Meschberger wrote:
> ...See SLING-1958 [1] and the proposed patch.
>
> WDYT ?
+1
-Bertrand
Hi,
Well, I have been experimenting with the Apache ServiceMix wrapper
bundles and was successful. So I think, instead of actually creating
some system bundle fragments for the XML APIs we should probably rather
add the ServiceMix bundle(s) from the start.
See SLING-1958 [1] and the proposed patc
+1
On Wed, Jan 19, 2011 at 9:50 AM, Felix Meschberger wrote:
> Hi all,
>
> We currently add a whole bunch of Java Extension APIs in the javax.*
> arena to the export list of the system bundle by virtue of actually
> providing in the framework, what is provided in the JDK.
>
> While we (at Adobe
On 19 Jan 2011, at 14:50, Felix Meschberger wrote:
> * For more demanding applications the fragment bundle can be
>replaced with a bundle containing and exporting the full API
>packages -- thus effectively hiding what is provided by platform.
I believe this is what we have done already
Related topic: do we need to list the whole packages coming from the jre
in the sling.properties anyway? The framework comes with default values
afaik.
Regards
Carsten
Carsten Ziegeler wrote
> Felix Meschberger wrote
>> Hi all,
>>
>> We currently add a whole bunch of Java Extension APIs in the
Felix Meschberger wrote
> Hi all,
>
> We currently add a whole bunch of Java Extension APIs in the javax.*
> arena to the export list of the system bundle by virtue of actually
> providing in the framework, what is provided in the JDK.
>
> While we (at Adobe) are now confronted with real-life us
Hi all,
We currently add a whole bunch of Java Extension APIs in the javax.*
arena to the export list of the system bundle by virtue of actually
providing in the framework, what is provided in the JDK.
While we (at Adobe) are now confronted with real-life use of such API
(javax.xml, etc.) we run