May be you should tell what problem you want to solve rather than trying
out various combinations of technologies? I see you want to use
persistence, then just localise that in a bundle and export an EMF as a
service. That will avoid to have many bundles depending on JPA provider.
I don't know why you want to use Spring - what problem it solves, but
Spring in OSGi is what OSGi blueprint is. So, just use blueprint if you
need that functionality. I would also ask you to evaluate CDI if you
have the flexibility to move a Java EE technology. OSGi and CDI play
quite well in GlassFish.
If none of the above is acceptable for whatever reason, then I hope you
find solution to the issue at hand. May be some Spring guy has the answer.
Sahoo
On Thursday 09 February 2012 04:48 PM, forums_at_java.net wrote:
> Regarding my previous post (http://forums.java.net/node/883164 [1]):
> I was
> trying to deploy spring + blueprint as osgi bundles. They refer to the
> "Spring-Context" header. However I could not continue in that direction
> because it requested to deploy spring-orm as bundle, spring-orm
> depends on
> hibernate, and hibernate 3.5.6 is not available as a bundle.
>
> So I am trying to give another chance to the POC and put spring inside
> war,
> now I fail with the described exception
> in PathMatchingResourcePatternResolver. I will check if I can configure
> spring to work with another pattern resolver.
>
>
>
>
> [1] http://forums.java.net/node/883164
>
> --
>
> [Message sent by forum member 'okna2000']
>
> View Post: http://forums.java.net/node/883365
>
>