An Import-Package could not be resolved. Caused by missing constraint in bundle <com.foo.bar_1.0.0>
constraint: <Import-Package: org.springframework.ws.soap.addressing.server; version="0.0.0"> constrained to bundle <org.springframework.ws> constrained bundle version range "[2.0.0.RELEASE,2.0.0.RELEASE]"
An Import-Package could not be resolved. Caused by missing constraint in bundle <org.springframework.ws_2.0.0.RELEASE>
constraint: <Import-Package: org.springframework.aop.support; version="[3.0.5,4.0.0)">
Note I tried to repackage Spring WS 2.0.2.RELEASE into an OSGi bundle by including the jar on the buildpath, exporting all the classes in the manifest, and then copying out spring.handlers and spring.schemas into my META-INF folder (so the Spring XML can be parsed). I did this because the SpringSource EBR only has up to 2.0.0.RELEASE. Unfortunately, Virgo/Spring can't seem to find the spring.handlers and spring.schemas files and so the Namespace can't resolve.
On the face of it, org.springframework.ws_2.0.0.RELEASE cannot be resolved because the package org.springframework.aop.support;version="[3.0.5,4.0.0) cannot be resolved, but this package is normally available in Virgo.
Os this occurring with or without your home-brewed Spring WS 2.0.2.RELEASE bundle?
I upgraded the user region to Spring Framework 3.0.5 per the FAQ and with that, Spring WS 2.0.0.RELEASE will at least complete startup.
Now, however, I'm stuck with an unsatisfiable dependency on CGLIB. Despite heading to Spring ERB and downloading the bundle, and installing it to the user region, and listing it as an import bundle, I continue to get an exception indicating it needs to be on the classpath.