You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by charbel el_kaed <ch...@hotmail.com> on 2010/06/01 01:58:57 UTC
RE: Error with UPnP Base driver
Hi Stefano,
Thanks for your reply.
I can't actually touch those bundles. Is there another way to do so ?
Kind Regards,
Charbel.
_________________________________________________________________
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
RE: Error with UPnP Base driver
Posted by charbel el_kaed <ch...@hotmail.com>.
Ok thanks a lot Stefano I ll try this.
Kind regards,
Charbel
> Date: Fri, 11 Jun 2010 12:09:25 +0200
> From: lenzi@apache.org
> Subject: Re: Error with UPnP Base driver
> To: dev@felix.apache.org
>
> Dear Charbel,
>
> Sorry for the late answer, I really believe that is a problem related
> from the wiring. Actually, the problem is not caused by bundle 20 and
> 22 but to others bundle on your configuration. If you want to find the
> source of the problem you should inspect the import/export tree for the
> packages org.xml.sax and org.xml.sax
>
> Nevertheless, I believe that easier for you to force the wiring of the
> org.w3c.dom and org.xml.sax packages of the "UPnP Base Driver" to the
> framework bundle.
> If you want to try this solution, you have to:
> 1 - download the UPnP bundle sources
> 2 - modify the pom.xml by replacing the content of the
> <Import-Package> tag
> org.osgi.*,
> javax.xml.parsers;bundle-symbolic-name=org.apache.felix.framework,
> org.w3c.dom;bundle-symbolic-name=org.apache.felix.framework,
> org.xml.sax;bundle-symbolic-name=org.apache.felix.framework
> 3 - package the bundle with maven, by executing mvn install
> 4 - replace the UPnP Base Driver bundle with the one just created, that
> is located inside target folder
>
> As additional note, you should be aware that "inspect" command shows
> only the actual wiring of the bundle which may be different from the
> content of the Import/Export-Pacakge headers of the bundle you are
> inspecting ( Richard would you mind to correct me if I'm wrong?)
>
> Ciao,
> Stefano "Kismet" Lenzi
>
> On 02/06/2010 11.18, charbel el_kaed wrote:
> >
> >
> > Hi Stefano,
> >
> > I inspected the packages and this is what I found. (The inspection result are below)
> >
> > Bundle 20 ONLY imports org.w3c.dom and org.xml.sax
> > while Bundle 22 imports and exports org.xml.sax
> >
> > In your previous reply you mentioned the correct configuration as:
> > I think that the correct configuration of bundle 20 and 22 are:
> > - bundle 20 and 22 import and export the packages: org.w3c.dom and
> > org.xml.sax
> > - bundle 20 and 22 ONLY import the packages: org.w3c.dom and org.xml.sax
> >
> >
> > So I am not sure if it is correct. I am really new to this.
> > I am looking at the OSGi Service Platform Release 4 core, Version 4.2 page 52
> >
> > -> inspect package c 20
> > org.soa4d.forge.osgi.xml.jdom.over.stax.sax.xquark.osgi [20] exports packages:
> > ------------------------------------------------------------------------------
> > org.jdom; version=0.0.0
> > org.jdom.adapters; version=0.0.0
> > org.jdom.filter; version=0.0.0
> > org.jdom.output; version=0.0.0
> > org.jdom.output.sax; version=0.0.0
> > org.jdom.output.stax; version=0.0.0
> > org.jdom.input.stax; version=0.0.0
> >
> > -> inspect package r 20
> > org.soa4d.forge.osgi.xml.jdom.over.stax.sax.xquark.osgi [20] imports packages:
> > ------------------------------------------------------------------------------
> > javax.xml.stream; version=1.6.0 -> org.apache.felix.framework [0]
> > org.xml.sax.ext; version=1.6.0 -> org.apache.felix.framework [0]
> > org.w3c.dom; version=2.0.0 -> org.soa4d.forge.osgi.xml.dom.l2.core.api.osgi [19]
> >
> > org.xml.sax; version=2.0.2 -> org.soa4d.forge.osgi.xml.sax2.api.osgi [21]
> > org.xml.sax.helpers; version=2.0.2 -> org.soa4d.forge.osgi.xml.sax.over.pull.bri
> > dge.osgi [22]
> > org.xquark.serialize; version=1.1.1 -> org.soa4d.forge.osgi.xml.xquare.serializi
> > ng [23]
> >
> > #########################################################################
> > -> inspect package c 22
> > org.soa4d.forge.osgi.xml.sax.over.pull.bridge.osgi [22] exports packages:
> > -------------------------------------------------------------------------
> > org.xml.sax.ext; version=2.0.2
> > org.xml.sax.helpers; version=2.0.2
> >
> > -> inspect package r 22
> > org.soa4d.forge.osgi.xml.sax.over.pull.bridge.osgi [22] imports packages:
> > -------------------------------------------------------------------------
> > org.xmlpull.v1; version=1.1.2 -> org.soa4d.forge.osgi.xml.kxml.pullparser.osgi [15]
> > org.xml.sax; version=2.0.2 -> org.soa4d.forge.osgi.xml.sax2.api.osgi [21]
> >
> >
> > Kind regards,
> > Charbel.
> >
> >
> >
> >
> >> Date: Tue, 1 Jun 2010 14:54:41 +0200
> >> From: lenzi@apache.org
> >> Subject: Re: Error with UPnP Base driver
> >> To: dev@felix.apache.org
> >>
> >> On 01/06/2010 1.58, charbel el_kaed wrote:
> >>>
> >>> Hi Stefano,
> >>>
> >>> Thanks for your reply.
> >>>
> >>> I can't actually touch those bundles. Is there another way to do so ?
> >>
> >> Have you checked if the hypothesis regarding the import/export headers
> >> of bundle 20 and 22 are correct? If they aren't then the source of the
> >> problem is somewhere else.
> >>
> >> If the hypothesis are correct then you can change the import-package
> >> header of the "UPnP Base Driver" in order to force the loading of the
> >> classes from the bundle 0 by means of the bundle-symbolic-name parameter
> >> of import-package header (see OSGi Service Platform Release 4 Version
> >> 4.2 page 52).
> >>
> >>>
> >>> Kind Regards,
> >>> Charbel.
> >>>
> >
_________________________________________________________________
Hotmail: Powerful Free email with security by Microsoft.
https://signup.live.com/signup.aspx?id=60969
Re: Error with UPnP Base driver
Posted by Stefano Lenzi <le...@apache.org>.
Dear Charbel,
Sorry for the late answer, I really believe that is a problem related
from the wiring. Actually, the problem is not caused by bundle 20 and
22 but to others bundle on your configuration. If you want to find the
source of the problem you should inspect the import/export tree for the
packages org.xml.sax and org.xml.sax
Nevertheless, I believe that easier for you to force the wiring of the
org.w3c.dom and org.xml.sax packages of the "UPnP Base Driver" to the
framework bundle.
If you want to try this solution, you have to:
1 - download the UPnP bundle sources
2 - modify the pom.xml by replacing the content of the
<Import-Package> tag
org.osgi.*,
javax.xml.parsers;bundle-symbolic-name=org.apache.felix.framework,
org.w3c.dom;bundle-symbolic-name=org.apache.felix.framework,
org.xml.sax;bundle-symbolic-name=org.apache.felix.framework
3 - package the bundle with maven, by executing mvn install
4 - replace the UPnP Base Driver bundle with the one just created, that
is located inside target folder
As additional note, you should be aware that "inspect" command shows
only the actual wiring of the bundle which may be different from the
content of the Import/Export-Pacakge headers of the bundle you are
inspecting ( Richard would you mind to correct me if I'm wrong?)
Ciao,
Stefano "Kismet" Lenzi
On 02/06/2010 11.18, charbel el_kaed wrote:
>
>
> Hi Stefano,
>
> I inspected the packages and this is what I found. (The inspection result are below)
>
> Bundle 20 ONLY imports org.w3c.dom and org.xml.sax
> while Bundle 22 imports and exports org.xml.sax
>
> In your previous reply you mentioned the correct configuration as:
> I think that the correct configuration of bundle 20 and 22 are:
> - bundle 20 and 22 import and export the packages: org.w3c.dom and
> org.xml.sax
> - bundle 20 and 22 ONLY import the packages: org.w3c.dom and org.xml.sax
>
>
> So I am not sure if it is correct. I am really new to this.
> I am looking at the OSGi Service Platform Release 4 core, Version 4.2 page 52
>
> -> inspect package c 20
> org.soa4d.forge.osgi.xml.jdom.over.stax.sax.xquark.osgi [20] exports packages:
> ------------------------------------------------------------------------------
> org.jdom; version=0.0.0
> org.jdom.adapters; version=0.0.0
> org.jdom.filter; version=0.0.0
> org.jdom.output; version=0.0.0
> org.jdom.output.sax; version=0.0.0
> org.jdom.output.stax; version=0.0.0
> org.jdom.input.stax; version=0.0.0
>
> -> inspect package r 20
> org.soa4d.forge.osgi.xml.jdom.over.stax.sax.xquark.osgi [20] imports packages:
> ------------------------------------------------------------------------------
> javax.xml.stream; version=1.6.0 -> org.apache.felix.framework [0]
> org.xml.sax.ext; version=1.6.0 -> org.apache.felix.framework [0]
> org.w3c.dom; version=2.0.0 -> org.soa4d.forge.osgi.xml.dom.l2.core.api.osgi [19]
>
> org.xml.sax; version=2.0.2 -> org.soa4d.forge.osgi.xml.sax2.api.osgi [21]
> org.xml.sax.helpers; version=2.0.2 -> org.soa4d.forge.osgi.xml.sax.over.pull.bri
> dge.osgi [22]
> org.xquark.serialize; version=1.1.1 -> org.soa4d.forge.osgi.xml.xquare.serializi
> ng [23]
>
> #########################################################################
> -> inspect package c 22
> org.soa4d.forge.osgi.xml.sax.over.pull.bridge.osgi [22] exports packages:
> -------------------------------------------------------------------------
> org.xml.sax.ext; version=2.0.2
> org.xml.sax.helpers; version=2.0.2
>
> -> inspect package r 22
> org.soa4d.forge.osgi.xml.sax.over.pull.bridge.osgi [22] imports packages:
> -------------------------------------------------------------------------
> org.xmlpull.v1; version=1.1.2 -> org.soa4d.forge.osgi.xml.kxml.pullparser.osgi [15]
> org.xml.sax; version=2.0.2 -> org.soa4d.forge.osgi.xml.sax2.api.osgi [21]
>
>
> Kind regards,
> Charbel.
>
>
>
>
>> Date: Tue, 1 Jun 2010 14:54:41 +0200
>> From: lenzi@apache.org
>> Subject: Re: Error with UPnP Base driver
>> To: dev@felix.apache.org
>>
>> On 01/06/2010 1.58, charbel el_kaed wrote:
>>>
>>> Hi Stefano,
>>>
>>> Thanks for your reply.
>>>
>>> I can't actually touch those bundles. Is there another way to do so ?
>>
>> Have you checked if the hypothesis regarding the import/export headers
>> of bundle 20 and 22 are correct? If they aren't then the source of the
>> problem is somewhere else.
>>
>> If the hypothesis are correct then you can change the import-package
>> header of the "UPnP Base Driver" in order to force the loading of the
>> classes from the bundle 0 by means of the bundle-symbolic-name parameter
>> of import-package header (see OSGi Service Platform Release 4 Version
>> 4.2 page 52).
>>
>>>
>>> Kind Regards,
>>> Charbel.
>>>
>
RE: Error with UPnP Base driver
Posted by charbel el_kaed <ch...@hotmail.com>.
Hi Stefano,
I inspected the packages and this is what I found. (The inspection result are below)
Bundle 20 ONLY imports org.w3c.dom and org.xml.sax
while Bundle 22 imports and exports org.xml.sax
In your previous reply you mentioned the correct configuration as:
I think that the correct configuration of bundle 20 and 22 are:
- bundle 20 and 22 import and export the packages: org.w3c.dom and
org.xml.sax
- bundle 20 and 22 ONLY import the packages: org.w3c.dom and org.xml.sax
So I am not sure if it is correct. I am really new to this.
I am looking at the OSGi Service Platform Release 4 core, Version 4.2 page 52
-> inspect package c 20
org.soa4d.forge.osgi.xml.jdom.over.stax.sax.xquark.osgi [20] exports packages:
------------------------------------------------------------------------------
org.jdom; version=0.0.0
org.jdom.adapters; version=0.0.0
org.jdom.filter; version=0.0.0
org.jdom.output; version=0.0.0
org.jdom.output.sax; version=0.0.0
org.jdom.output.stax; version=0.0.0
org.jdom.input.stax; version=0.0.0
-> inspect package r 20
org.soa4d.forge.osgi.xml.jdom.over.stax.sax.xquark.osgi [20] imports packages:
------------------------------------------------------------------------------
javax.xml.stream; version=1.6.0 -> org.apache.felix.framework [0]
org.xml.sax.ext; version=1.6.0 -> org.apache.felix.framework [0]
org.w3c.dom; version=2.0.0 -> org.soa4d.forge.osgi.xml.dom.l2.core.api.osgi [19]
org.xml.sax; version=2.0.2 -> org.soa4d.forge.osgi.xml.sax2.api.osgi [21]
org.xml.sax.helpers; version=2.0.2 -> org.soa4d.forge.osgi.xml.sax.over.pull.bri
dge.osgi [22]
org.xquark.serialize; version=1.1.1 -> org.soa4d.forge.osgi.xml.xquare.serializi
ng [23]
#########################################################################
-> inspect package c 22
org.soa4d.forge.osgi.xml.sax.over.pull.bridge.osgi [22] exports packages:
-------------------------------------------------------------------------
org.xml.sax.ext; version=2.0.2
org.xml.sax.helpers; version=2.0.2
-> inspect package r 22
org.soa4d.forge.osgi.xml.sax.over.pull.bridge.osgi [22] imports packages:
-------------------------------------------------------------------------
org.xmlpull.v1; version=1.1.2 -> org.soa4d.forge.osgi.xml.kxml.pullparser.osgi [15]
org.xml.sax; version=2.0.2 -> org.soa4d.forge.osgi.xml.sax2.api.osgi [21]
Kind regards,
Charbel.
> Date: Tue, 1 Jun 2010 14:54:41 +0200
> From: lenzi@apache.org
> Subject: Re: Error with UPnP Base driver
> To: dev@felix.apache.org
>
> On 01/06/2010 1.58, charbel el_kaed wrote:
> >
> > Hi Stefano,
> >
> > Thanks for your reply.
> >
> > I can't actually touch those bundles. Is there another way to do so ?
>
> Have you checked if the hypothesis regarding the import/export headers
> of bundle 20 and 22 are correct? If they aren't then the source of the
> problem is somewhere else.
>
> If the hypothesis are correct then you can change the import-package
> header of the "UPnP Base Driver" in order to force the loading of the
> classes from the bundle 0 by means of the bundle-symbolic-name parameter
> of import-package header (see OSGi Service Platform Release 4 Version
> 4.2 page 52).
>
> >
> > Kind Regards,
> > Charbel.
> >
_________________________________________________________________
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
Re: Error with UPnP Base driver
Posted by Stefano Lenzi <le...@apache.org>.
On 01/06/2010 1.58, charbel el_kaed wrote:
>
> Hi Stefano,
>
> Thanks for your reply.
>
> I can't actually touch those bundles. Is there another way to do so ?
Have you checked if the hypothesis regarding the import/export headers
of bundle 20 and 22 are correct? If they aren't then the source of the
problem is somewhere else.
If the hypothesis are correct then you can change the import-package
header of the "UPnP Base Driver" in order to force the loading of the
classes from the bundle 0 by means of the bundle-symbolic-name parameter
of import-package header (see OSGi Service Platform Release 4 Version
4.2 page 52).
>
> Kind Regards,
> Charbel.
>