Now the project uses Spring 3. This will ensure that the hosted repository application starts ahead of applications deployed from pickup or via the admin console. Is the order of the Import-Bundle so important? XMLBeans dependency [ message is a reply to message ]. I hope that at least helps explain the situation and shows a way forward. Please can you raise a bug. 
| Uploader: | Mejora |
| Date Added: | 15 November 2004 |
| File Size: | 6.99 Mb |
| Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
| Downloads: | 81217 |
| Price: | Free* [*Free Regsitration Required] |
The modularized application that we have in mind is composed by: Is the order of the Import-Bundle so important? Hi, the context is the following. Note that my application was developed using Spring 2.
Wed, 20 October Each bundle uses two different kind of libraries: XMLBeans dependency [ message is a reply to message ]. Hi Glyn, I followed your instruction, but the result is the same.
Download xmlbeans JAR files with all dependencies
Otherwise, if the jar file is in the remote repository I got a strange error: We obviously have no problem with the OSGi library. So it seems parts of your application and the "oxm" bundle are resolved before the hosted repository application has finished initialising - xmlbeasn asynchronous operation xxmlbeans it uses Spring DM. A used by my application. The error is the same: Hi Marco Thanks for your patience. Page generated in 0.
Hi Glyn, Thank you for the support. I'm guessing some of these are fairly basic Spring bundles and if so, this would explain why "oxm" is resolved early.
Glyn, I exploit this thread for one question about dependency. It's not so easy to create a simple test case. It seems that the "oxm" bundle is still being resolved relatively early and the optional import xmlbesns being dropped because the XMLBeans JAR is not found at that time because the hosted repository application is not yet running. Tools like bundlor can help with generating such manifests. I don't know if the following information is useful to you.
Please can you raise a bug. Report message to a moderator.
Download jsr173_1.0_api-xmlbeans-2.2.0.jar : jsr173 « j « Jar File Download
No, that's quite sufficient thanks. If you would like us to consider lifting this restriction, please raise an enhancement bugzilla and we can consider it in due course. Fri, 15 October I got a remote virgo repository linked my my local virgo server. If you have the time to create a minimal testcase to reproduce the problem and attach it to the bug, that would be extremely helpful.
The usual trick for 3rd party JARs that you can't crack open is to include them in the bundle classpath of a bundle. Another workaround is to change the startup order of the Virgo user region by making the hosted repository application one of the artefacts initially deployed in the user region instead of deploying it from pickup. However, a more general solution is 2.2 create a bundle which contains just xmlbeana 3rd party JAR on the bundle classpath and simply exports all the packages of the 3rd party JAR and imports any dependencies, very much like the manifest you would have liked to have put in the 3rd party JAR if you were able to crack it open.
xmlbeansjar - JAR Search -
Eclipse Community Forums Forum Search: This sounds like a bug or xmlbeeans a setup error. I hope that at least helps explain the situation and shows a way forward.
I'm trying to install an existing WAR in virgo. Can anyone explain me what's the problem?
No comments:
Post a Comment