[
https://issues.apache.org/jira/browse/FELIX-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mitesh Meswani closed FELIX-602.
Verified that issue is fixed with sources as of revision 675067
> Symbolic name system.bundle is not re
Hi,
I read the launching/embedding page, but it was a few weeks ago and I will go
back and take another look...
I went with the Sahoo's suggestion of setting the delegation property and that
is perfect for my needs...
I agree I don't want any code outside of a bundle, if at all possible...
Graig,
We've conjured up a very lightweight wrapper around log4j and made it
available
to the public...
https://opensource.luminis.net/confluence/display/SITE/OSGi+LogListener+implementation
Might be worthwhile to at least compare its classloading behavior with
that of the pax implementati
Craig,
Not sure if you read this document:
http://cwiki.apache.org/FELIX/launching-and-embedding-apache-felix.html
But this document discusses these issues and touches upon the various
solutions/approaches, such as reflection.
However, I am in agreement with the others, your life will be
Hi,
On 8 Jul 2008, at 19:19, Dieter Wimberger wrote:
I guess that 7.0 is the output from the felix classloader. When
allowing parent delegation (what Sahoo suggested), then you get the
result you were looking for.
The 7.0 is indeed the name of the classloader of bundle ID 7 (the 0 is
the
Craig:
I guess that 7.0 is the output from the felix classloader. When
allowing parent delegation (what Sahoo suggested), then you get the
result you were looking for.
Honestly, one of the reasons for switching to OSGi is the much better
classloading approach. I have had all kinds of prob
Hi,
I went to the config.properties bootdelegation line, as we did with the
pax logger stuff, and sure enough if it worked... Here's the latest
debug print:
org.osgi.framework.bootdelegation=sun.*,com.sun.*,org.craig.cache.*;
--
[
https://issues.apache.org/jira/browse/FELIX-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Lenzi closed FELIX-495.
---
> release classified version of the basedriver
>
>
>
[
https://issues.apache.org/jira/browse/FELIX-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Lenzi closed FELIX-486.
---
Yes it is right :)
> Felix release conting mixed bytecode: 1.3 and 1.4, we should compile all as
> 1.3
>
[
https://issues.apache.org/jira/browse/FELIX-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Lenzi reassigned FELIX-616:
---
Assignee: Stefano Lenzi
> upnp tester pom.xml depends on upnp base driver version 0.3.0 when i
[
https://issues.apache.org/jira/browse/FELIX-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Lenzi resolved FELIX-616.
-
Resolution: Fixed
Fixed. It depends to version 0.8.0
> upnp tester pom.xml depends on upnp base d
[
https://issues.apache.org/jira/browse/FELIX-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Lenzi resolved FELIX-495.
-
Resolution: Fixed
Fix Version/s: upnp-basedriver-0.8.0
Fixed
> release classified version
Hi,
I'm willing to give reflection a try... seems like the best approach
from a 24x7 standpoint, where I want to have the ability to change the
impl and yet my parent is wired to the interface... or, so, that's my
plan...
I was thinking about how OSGi does it (without digging in to the code,
that
Further to my previous investigations, I have now located what I believe to be
the source of the problem we are seeing when using the UPnP stack as a
ContentDirectory for the Xbox 360.
During the discovery phase, the Xbox sends out SSDP:discover messages as
expected to the well known multicast
[
https://issues.apache.org/jira/browse/FELIX-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clement Escoffier resolved FELIX-628.
-
Resolution: Fixed
Fixed in the revision 674872.
Now, the Architecture service is published
Craig Phillips wrote:
Sahoo, Dieter,
Yeah, this is what I'm suspecting and I'll try what you suggest, Deiter,
to print them out and I think I/we'll know the answer -- they were
loaded in two different class loaders... Note that they are from the
same package -- I built everything so everything i
[
https://issues.apache.org/jira/browse/FELIX-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clement Escoffier resolved FELIX-627.
-
Resolution: Fixed
Fixed in the revision 674870
Add the temporal dependency annotation. Th
Sahoo, Dieter,
Yeah, this is what I'm suspecting and I'll try what you suggest, Deiter,
to print them out and I think I/we'll know the answer -- they were
loaded in two different class loaders... Note that they are from the
same package -- I built everything so everything is on the same page
from
Craig:
Something you could try to figure out what is going wrong with
classloading is to debug print the associated classloaders. This
information could indicate what is actually going wrong.
In particular, it would be interesting to see the output of the
following:
Object o = bc.getServ
That basically means the same named class has been defined by two
different class loaders. Can you check if the bundle that's exporting
the service and the bundle that's consuming the service are not wired to
the same org.craig.cache package?
Which bundle is exporting the above package?
How ar
Architecture service should not publish the instance.name property
--
Key: FELIX-628
URL: https://issues.apache.org/jira/browse/FELIX-628
Project: Felix
Issue Type: Bug
Temporal dependency annotation
--
Key: FELIX-627
URL: https://issues.apache.org/jira/browse/FELIX-627
Project: Felix
Issue Type: Improvement
Components: iPOJO
Affects Versions: iPOJO-0.8.0
Hi,
Can't cast a class to it's own type... Huh? I just got to believe it's
some kind of class loader thing going on... I really could use a pair of
eyes from one of the class loader experts out there, I anticipate (I
brought other eyes nearby to look, they're stumped too)... Thanks,
Craig Philli
[
https://issues.apache.org/jira/browse/FELIX-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611594#action_12611594
]
Stuart McCulloch commented on FELIX-620:
No firm date yet - but at least by the end
[
https://issues.apache.org/jira/browse/FELIX-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch resolved FELIX-547.
Resolution: Fixed
This is now fixed in trunk, but not yet deployed in a snapshot.
> OBR por
[
https://issues.apache.org/jira/browse/FELIX-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clement Escoffier resolved FELIX-626.
-
Fixed in the revision 674783.
Create an empty Hashtable when parsing an empty aggregate proper
[
https://issues.apache.org/jira/browse/FELIX-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clement Escoffier updated FELIX-626:
Component/s: iPOJO
Assignee: Clement Escoffier
> Allow specifying instance configurat
Allow specifying instance configuration containing empty dictionaries
-
Key: FELIX-626
URL: https://issues.apache.org/jira/browse/FELIX-626
Project: Felix
Issue Type: Improv
28 matches
Mail list logo
