| Spring dm, eclipselink and weaving hell [message #782980] |
Tue, 24 January 2012 21:30  |
|
Hi,
I'm so sorry to importunate you, but I'm really stuck on my project.
I'm trying to make Pax, Spring-dm, Eclipselink & atomikos running together (gemini-web and blueprint are too tied to Virgo for now).
I found an old post on Martin's springweaver to enable weaving on classes.
The problem is that it is only weaving either my configurable equinoxtransactionadapter or my woven model bundle if I refresh it (normally, you'll see an oh yes in the stack when persisting an object).
I join my sample (a simple helloworld).
It is missing some jars because of forum restriction:
* jacocoagent.jar on the root lib folder.
* ant-1.6.5.jar and core-3.1.1.jar (jdt) on orthank-sample\orthank-sample.java\orthank-sample.java.web\orthank-sample.java.web.simple\src\main\webapp\WEB-INF\lib in order to make jsf working.
Web services are broken because of this, so you have to desactivate the ws.client bundle and skiping tests in order to make the example work.
(mvn clean install -Dskip-tests=true and mvn pax:provision to run).
I'll be very happy to have a (or some) OSGI experts discussing on the problem or the architecture (I know it is not wonderfull, but it will be improved in the future), I'm near to have a full jee stack to contribute on many modeling projects (obeo designer, emf), pax, atomikos tx, and maybe jetty or cxf/servicemix, and a good future maven archetype embedding this stack.
Best regards, Charlie
(you can contact me on cmordant1@gmail.com if you're interested or have any question)
|
|
|
|
| Re: Spring dm, eclipselink and weaving hell [message #783218 is a reply to message #783182] |
Wed, 25 January 2012 09:58  |
|
Hi Violeta,
Quote:(gemini-web and blueprint are too tied to Virgo for now).
It's just for some little things, but too wierd:
When you want to use gemini web for loading context in your web.xml:
<context-param>
<param-name>contextClass</param-name>
<param-value>org.eclipse.virgo.web.dm.ServerOsgiBundleXmlWebApplicationContext
</param-value>
</context-param>
You must have, by transitivity, all virgo's core, medic... dependencies.
By the way, you must have to configure your entire project in Virgo style (settings up all Virgo properties files...).
IMO Configuring DM-style web modules and blueprint style jars is not so convenient for end users.
I think that's the same for weaving (I saw OSGICompliantLoadTimeWeaver spec & impl on a Virgo medic bundle).
I'm just waiting for Virgo-decoupling on these sides in order to move spring-dm service resolution to the Gemini ones.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.09362 seconds
] 
Search
Help
Register
Login
Home
