On 5/28/10 9:29, André Dietisheim wrote:
Hi Richard
thanks for the rapdi answer! I found the soultion in the meantime, it
was discussed in details when the system package missing was
"com.sun.net.ssl.internal.ssl" at
http://old.nabble.com/Unresolved-constraint-question-td23024174.html
I applied that in analogy and came to a working solution.
Allow me to say that the are a few syntax gotchas here:
- no wildcards, indicate all packages
Yeah, that sucks, but it is kind of difficult for the system bundle to
export "*".
- if setup by system properties, the packages have to be delimited by
';' (whereas by ',' in the properties file) - or do ',' work, too?
Those are for different purposes. The semicolon allows you to specify
the same set of attributes and directives for a set of packages, while
the comma separates packages that have different attributes and directives.
-> richard
Thanks again!
André
On 05/28/2010 03:22 PM, Richard S. Hall wrote:
On 5/28/10 5:31, André Dietisheim wrote:
Hi Richard, Hi Ivanhoe
thanks a lot for your inputs, that gave me insights but
unfortunately, it sillt doesn't want to run.
I added
<snip>
org.osgi.framework.system.packages.extra=com.*,sun.com.*
</snip>
You cannot use wildcards here, you must explicitly list the packages
in questions.
-> richard
(and removed the extra setting in the boot delegation) but spring
ldap still complains about the same missing package imports:
<snip>
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.springframework.ldap [98]: package;
(&(package=com.sun.jndi.ldap)(version>=0.0.0))
</snip>
I'm kind of stuck here, if you have some more thoughts, I'd be more
than happy!
Thanks in advance
André
On 05/27/2010 07:29 PM, Richard S. Hall wrote:
On 5/27/10 13:25, Ivanhoe Abrahams wrote:
Hi
Try adding it to org.osgi.framework.system.packages too. I am not
sure if
that will help, but give it a try
Since the bundle appears to be importing the package, then it must
be added to system.packages since the import needs to be resolved.
If you do that, then it is not necessary to put in on boot
delegation too.
-> richard
Ivanhoe
On Thu, May 27, 2010 at 6:45 PM, André Dietisheim<
[email protected]> wrote:
Hi!
I try to run Spring ldap in felix. Unfortunately spring ldap
complains
about an unresolved dependency:
<snip>
ERROR: Error starting
inputstream:org.springframework.ldap-1.3.0.RELEASE.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.springframework.ldap [100]: package;
(&(package=com.sun.jndi.ldap)(version>=0.0.0)))
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.springframework.ldap [100]: package;
(&(package=com.sun.jndi.ldap)(version>=0.0.0))
</snip>
I found several references to issues of this kind (in spring but
in felix
karaf, too) and I was told to add com.sum.* to the
boot-delegation so that
all bundles have these packages ready. I therefore added the
following
programmatically to my launcher-class:
<snip>
configProps.put("org.osgi.framework.bootdelegation",
"sun.*,com.sun.*");
</snip>
I could do the same to the configuration properties like this:
<snip>
org.osgi.framework.bootdelegation=sun.*,com.sun.*
</snip>
Unfortunately either way does not help. I'd appreciate any hint a
lot!!
Thanks in advance
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
