I solved this problem with a bit of trickery using Ant within Maven.
The behaviour is correct to the EJB3 spec of scoping rules for persistence.xml.
I've submitted an issue with Surefire here which goes into more detail,
including the ant hack:
http://jira.codehaus.org/browse/SUREFIRE-443
Vie
I don't think there is one, at least not with the multi module project layout.
Vote for the issue if interested: http://jira.jboss.org/jira/browse/JBSEAM-2371
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120742#4120742
Reply to the post :
http://www.jboss
Would anyone be able to post a complete example of a successful Seam 2.0
SeamTest (as an EJB jar deployed to the embedded container) using Maven and
TestNG? We have spent several weeks working on a solution without success.
View the original post :
http://www.jboss.com/index.html?module=bb&op=
I am not sure I understand what exactly is the problem. Considering your test
persistence unit has a different name than the one for production doesn't
Peristence.createEntityManagerFactory(persistenceUnitName) just work for you?
View the original post :
http://www.jboss.com/index.html?module=b
In regards to ordering in 2.0.8:
The ordering is not a concern. The problem is that both persistence.xml files
are loaded and parsed. So my solution is important to ensure that the "main"
persistence.xml is not used for unit tests.
View the original post :
http://www.jboss.com/index.html?modul
Tbh, considering how much maven projects' (especially multimodule projects)
layout is different from Seam project layout and considering how the Seam test
framework 'tuned' for certain configurations and defaults I think it requires
major work to make Seam tests work in maven projects.
In the m
Cool,
Surefire Plugin version 2.4 is finally out. Supporting TestNG as a first
citizen. I will try it out over the weekend if the combination maven, seam
combo is working now as expected.
Regards,
Cyrill
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=41203
That is good news :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119858#4119858
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119858
___
jboss-user mailing list
jboss-user
Btw, maven starting from 2.0.8 puts test classpath before the source classpath
(which wasn't the case before). This should make configuration quite simple.
You'd need to enforce maven version then of course :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=411
There is a problem with eclipse (if use WTP configuration) is that it doesn't
like more than one persistence unit defined.
As a workaround I defined the test persistence unit programmatically in my unit
tests.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=41
Thanks Andrew, I added this to the Seam knowledgebase
http://alpha.seamframework.org:/Documentation/SeamWithMaven
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118647#4118647
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=
I got it working, but it was a configuration pain. For those that read this
post here is a very quick howto:
| * create src/main/conf - this will be files that are added to the war but
not added to target/classes on build (and therefore will not interfere with
testing)
| * move src/main/
Try to add it in:
src/test/resources/META-INF
I haven't done this though.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114071#4114071
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114071
13 matches
Mail list logo
