You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Stefano Lenzi <ki...@interfree.it> on 2008/02/13 17:10:12 UTC
Creating a javax.xml bundle (FELIX-488)
Hi All,
I would like to create a bundle which contains only the javax.xml APIs
as we did for javax.servelet. In fact, at the moment, you can't install
the org.osgi.compendium bundle on a JDK 1.3 because javax.xml APIs are
missing. The creation of a javax.xml bundle which will mostly used by
JDK1.3 people will fill the gap.
As reported on JIRA, I know that under commons we have xml-apis which
exports the javax.xml APIs but it also implements the APIs thus it ends
up to be huge in size for embedded system point of view which are,
probably, the nowadays device running JDK 1.3.
WDYT?
Ciao,
Stefano "Kismet" Lenzi
Re: Creating a javax.xml bundle (FELIX-488)
Posted by Stefano Lenzi <ki...@interfree.it>.
Richard S. Hall wrote:
> Stefano Lenzi wrote:
>> Richard S. Hall wrote:
>>> I think this is not an unreasonable approach...
>>>
>>> -> richard
>>
>> Which approach were you refering to? OSGi Alliance, Our or Mine?
>
> I was agreeing with Felix...mainly because it is simpler on our end. :-)
>
> -> richard
I have made the patch and it's available on JIRA. If you agree I will
commit the patch.
>
>>
>>>
>>> Felix Meschberger wrote:
>>>> Hi Stefano,
>>>>
>>>> Comparing our compendium jar to the one downloaded from the OSGi site
>>>> shows, that we have some imports while the OSGi one only has a
>>>> "DynamicImport-Package: *".
>>>>
>>>> So I consider our compendium jar to be erroneous and we should either
>>>> tag all imports with "resolution:=optional" or have no explicit imports
>>>> at all. This is probably better than to try to mess around with XML
>>>> APIs
>>>> without a real need.
>>>>
>>>> In fact, javax.servlet.* imports of the compendium jar are also not
>>>> that
>>>> practical in a non-web oriented application ;-)
>>>>
>>>> Regards
>>>> Felix
>>>>
>>>>
>>>> Am Mittwoch, den 13.02.2008, 17:10 +0100 schrieb Stefano Lenzi:
>>>>
>>>>> Hi All,
>>>>>
>>>>> I would like to create a bundle which contains only the javax.xml
>>>>> APIs as we did for javax.servelet. In fact, at the moment, you
>>>>> can't install the org.osgi.compendium bundle on a JDK 1.3 because
>>>>> javax.xml APIs are missing. The creation of a javax.xml bundle
>>>>> which will mostly used by JDK1.3 people will fill the gap.
>>>>>
>>>>> As reported on JIRA, I know that under commons we have xml-apis
>>>>> which exports the javax.xml APIs but it also implements the APIs
>>>>> thus it ends up to be huge in size for embedded system point of
>>>>> view which are, probably, the nowadays device running JDK 1.3.
>>>>>
>>>>> WDYT?
>>>>>
>>>>> Ciao,
>>>>> Stefano "Kismet" Lenzi
>>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
Re: Creating a javax.xml bundle (FELIX-488)
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Stefano Lenzi wrote:
> Richard S. Hall wrote:
>> I think this is not an unreasonable approach...
>>
>> -> richard
>
> Which approach were you refering to? OSGi Alliance, Our or Mine?
I was agreeing with Felix...mainly because it is simpler on our end. :-)
-> richard
>
>>
>> Felix Meschberger wrote:
>>> Hi Stefano,
>>>
>>> Comparing our compendium jar to the one downloaded from the OSGi site
>>> shows, that we have some imports while the OSGi one only has a
>>> "DynamicImport-Package: *".
>>>
>>> So I consider our compendium jar to be erroneous and we should either
>>> tag all imports with "resolution:=optional" or have no explicit imports
>>> at all. This is probably better than to try to mess around with XML
>>> APIs
>>> without a real need.
>>>
>>> In fact, javax.servlet.* imports of the compendium jar are also not
>>> that
>>> practical in a non-web oriented application ;-)
>>>
>>> Regards
>>> Felix
>>>
>>>
>>> Am Mittwoch, den 13.02.2008, 17:10 +0100 schrieb Stefano Lenzi:
>>>
>>>> Hi All,
>>>>
>>>> I would like to create a bundle which contains only the javax.xml
>>>> APIs as we did for javax.servelet. In fact, at the moment, you
>>>> can't install the org.osgi.compendium bundle on a JDK 1.3 because
>>>> javax.xml APIs are missing. The creation of a javax.xml bundle
>>>> which will mostly used by JDK1.3 people will fill the gap.
>>>>
>>>> As reported on JIRA, I know that under commons we have xml-apis
>>>> which exports the javax.xml APIs but it also implements the APIs
>>>> thus it ends up to be huge in size for embedded system point of
>>>> view which are, probably, the nowadays device running JDK 1.3.
>>>>
>>>> WDYT?
>>>>
>>>> Ciao,
>>>> Stefano "Kismet" Lenzi
>>>>
>>>
>>>
>>
>>
>
Re: Creating a javax.xml bundle (FELIX-488)
Posted by Stefano Lenzi <ki...@interfree.it>.
Richard S. Hall wrote:
> I think this is not an unreasonable approach...
>
> -> richard
Which approach were you refering to? OSGi Alliance, Our or Mine?
>
> Felix Meschberger wrote:
>> Hi Stefano,
>>
>> Comparing our compendium jar to the one downloaded from the OSGi site
>> shows, that we have some imports while the OSGi one only has a
>> "DynamicImport-Package: *".
>>
>> So I consider our compendium jar to be erroneous and we should either
>> tag all imports with "resolution:=optional" or have no explicit imports
>> at all. This is probably better than to try to mess around with XML APIs
>> without a real need.
>>
>> In fact, javax.servlet.* imports of the compendium jar are also not that
>> practical in a non-web oriented application ;-)
>>
>> Regards
>> Felix
>>
>>
>> Am Mittwoch, den 13.02.2008, 17:10 +0100 schrieb Stefano Lenzi:
>>
>>> Hi All,
>>>
>>> I would like to create a bundle which contains only the javax.xml
>>> APIs as we did for javax.servelet. In fact, at the moment, you can't
>>> install the org.osgi.compendium bundle on a JDK 1.3 because javax.xml
>>> APIs are missing. The creation of a javax.xml bundle which will
>>> mostly used by JDK1.3 people will fill the gap.
>>>
>>> As reported on JIRA, I know that under commons we have xml-apis which
>>> exports the javax.xml APIs but it also implements the APIs thus it
>>> ends up to be huge in size for embedded system point of view which
>>> are, probably, the nowadays device running JDK 1.3.
>>>
>>> WDYT?
>>>
>>> Ciao,
>>> Stefano "Kismet" Lenzi
>>>
>>
>>
>
>
Re: Creating a javax.xml bundle (FELIX-488)
Posted by "Richard S. Hall" <he...@ungoverned.org>.
I think this is not an unreasonable approach...
-> richard
Felix Meschberger wrote:
> Hi Stefano,
>
> Comparing our compendium jar to the one downloaded from the OSGi site
> shows, that we have some imports while the OSGi one only has a
> "DynamicImport-Package: *".
>
> So I consider our compendium jar to be erroneous and we should either
> tag all imports with "resolution:=optional" or have no explicit imports
> at all. This is probably better than to try to mess around with XML APIs
> without a real need.
>
> In fact, javax.servlet.* imports of the compendium jar are also not that
> practical in a non-web oriented application ;-)
>
> Regards
> Felix
>
>
> Am Mittwoch, den 13.02.2008, 17:10 +0100 schrieb Stefano Lenzi:
>
>> Hi All,
>>
>> I would like to create a bundle which contains only the javax.xml APIs
>> as we did for javax.servelet. In fact, at the moment, you can't install
>> the org.osgi.compendium bundle on a JDK 1.3 because javax.xml APIs are
>> missing. The creation of a javax.xml bundle which will mostly used by
>> JDK1.3 people will fill the gap.
>>
>> As reported on JIRA, I know that under commons we have xml-apis which
>> exports the javax.xml APIs but it also implements the APIs thus it ends
>> up to be huge in size for embedded system point of view which are,
>> probably, the nowadays device running JDK 1.3.
>>
>> WDYT?
>>
>> Ciao,
>> Stefano "Kismet" Lenzi
>>
>
>
Re: Creating a javax.xml bundle (FELIX-488)
Posted by Felix Meschberger <fm...@gmail.com>.
Hi Stefano,
Comparing our compendium jar to the one downloaded from the OSGi site
shows, that we have some imports while the OSGi one only has a
"DynamicImport-Package: *".
So I consider our compendium jar to be erroneous and we should either
tag all imports with "resolution:=optional" or have no explicit imports
at all. This is probably better than to try to mess around with XML APIs
without a real need.
In fact, javax.servlet.* imports of the compendium jar are also not that
practical in a non-web oriented application ;-)
Regards
Felix
Am Mittwoch, den 13.02.2008, 17:10 +0100 schrieb Stefano Lenzi:
> Hi All,
>
> I would like to create a bundle which contains only the javax.xml APIs
> as we did for javax.servelet. In fact, at the moment, you can't install
> the org.osgi.compendium bundle on a JDK 1.3 because javax.xml APIs are
> missing. The creation of a javax.xml bundle which will mostly used by
> JDK1.3 people will fill the gap.
>
> As reported on JIRA, I know that under commons we have xml-apis which
> exports the javax.xml APIs but it also implements the APIs thus it ends
> up to be huge in size for embedded system point of view which are,
> probably, the nowadays device running JDK 1.3.
>
> WDYT?
>
> Ciao,
> Stefano "Kismet" Lenzi