Hello,
I get an intermittent (very rare) exception while running tests using
declarative services under Felix.
The exception stack trace shows:
java.lang.IllegalArgumentException: Service object cannot be null.
at org.apache.felix.framework.Felix.registerService(Felix.java:2661)
Hi Rajini,
Thanks for reporting this issue. Could you please file a JIRA for this.
I basically agree that this is probably a synchronization issue, which
might not be caught correctly right now.
Could you also try the SCR 1.0.1-SNAPSHOT ? This contains some more
logging, which could help resolve
Intermittent IllegalArgumentException while using declarative services
-
Key: FELIX-539
URL: https://issues.apache.org/jira/browse/FELIX-539
Project: Felix
Issue Type
Felix,
Thank you, I have raised a JIRA (
https://issues.apache.org/jira/browse/FELIX-539).
Unfortunately, since the failure is very intermittent, I haven't been able
to recreate it with SCR 1.0.1-SNAPSHOT yet. I will update the JIRA if I get
any more information.
On 4/16/08, Felix Meschberger <
Hi Rajini,
Am Mittwoch, den 16.04.2008, 12:19 +0100 schrieb Rajini Sivaram:
> Felix,
>
> Thank you, I have raised a JIRA (
> https://issues.apache.org/jira/browse/FELIX-539).
Thanks.
>
> Unfortunately, since the failure is very intermittent, I haven't been able
> to recreate it with SCR 1.0.1-
[
https://issues.apache.org/jira/browse/FELIX-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall closed FELIX-104.
-
Resolution: Fixed
Closing at Clement's request.
> Mixing iPOJO and OSGi projects within a parent
In the trunk we have modified the framework so that it no longer tries
to log to an available LogService for the time being, so this issue
should be gone. When we have the time, we will try to reinstate the
feature if we can find a suitable workaround.
-> richard
Tim Moloney wrote:
Thanks fo
I am not sure why maven-felix-plugin has been added to the build anyway,
it used to be excluded.
As far as I understand, there is no progress on this, it was just a
proof of concept, so it probably shouldn't be in the build.
-> richard
Clement Escoffier wrote:
Hi,
I have an error when
Hi everybody,
If you first compile with
-Dpackaging=bundle clean install
and then run the ant script it compiles ok.
After changing the maven-felix-plugin pom with clement suggestion i get the
same error.
Walter
On Wed, Apr 16, 2008 at 8:14 PM, Clement Escoffier <
[EMAIL PROTECTED]> wrote:
>
Hi,
I have an error when trying to build the Felix trunk from scratch (empty
maven repository). It seems that the maven-felix-plugin does not target a
consistent version of the parent artifact:
felix
org.apache.felix
1.1.0-SNAPSHOT
../../../pom/pom.xml
I change i
Thanks for the info. Will this be included in the upcoming 1.0.4 release?
Tim
Richard S. Hall wrote:
In the trunk we have modified the framework so that it no longer tries
to log to an available LogService for the time being, so this issue
should be gone. When we have the time, we will try t
On 17/04/2008, Richard S. Hall <[EMAIL PROTECTED]> wrote:
>
> I am not sure why maven-felix-plugin has been added to the build anyway,
> it used to be excluded.
FYI, it was added because it is needed by the following examples
sub-project:
felix/examples/dictionaryservice.itest/pom.xml
if you
Stuart McCulloch wrote:
On 17/04/2008, Richard S. Hall <[EMAIL PROTECTED]> wrote:
I am not sure why maven-felix-plugin has been added to the build anyway,
it used to be excluded.
FYI, it was added because it is needed by the following examples
sub-project:
felix/examples/dictionaryservice
Hi there,
when trying to use the maven-bundle-plugin to generate the valid
plugin manifest for an Eclipse plugin, it seems there needs to be the
singleton directive set, something like:
Bundle-SymbolicName: org.neo4j.neoclipse;singleton:=true
instead of the generated
Bundle-SymbolicName: org.ne
On 17/04/2008, Peter Neubauer <[EMAIL PROTECTED]> wrote:
>
> Hi there,
> when trying to use the maven-bundle-plugin to generate the valid
> plugin manifest for an Eclipse plugin, it seems there needs to be the
> singleton directive set, something like:
>
>
> Bundle-SymbolicName: org.neo4j.neoclipse
Hi peter,
Have you tried to define the configuration instruction as:
...
rg.neo4j.neoclipse;singleton:=true
...
Alin
On Thu, Apr 17, 2008 at 9:34 AM, Peter Neubauer
<[EMAIL PROTECTED]> wrote:
> Hi there,
> when trying to use the maven-bundle-plugin to generate the valid
> plugin manifest for
Ahh,
${project.groupId}.${project.artifactId};singleton:=true
did the trick.
Thanks Alin!
/peter
On Thu, Apr 17, 2008 at 8:47 AM, Alin Dreghiciu <[EMAIL PROTECTED]> wrote:
> Hi peter,
> Have you tried to define the configuration instruction as:
> ...
>
> rg.neo4j.neoclipse;si
17 matches
Mail list logo
