If you dont want a PC in that deployment, dont put the persistence.XML file in the ear. I dont get the problem. Sent from my iPhone On Dec 1, 2008, at 4:22 PM, "Dan Allen" <dan.j.allen(a)gmail.com&gt; wrote: > One of the changes in JBoss AS 5 that comes as a surprise for many > Seam developers/users familiar with the behavior of JBoss AS 4 is the > automatic loading of persistence units from /META-INF/persistence.xml. > (As expected, we had to change several of the Seam examples to > accommodate this change). This is one of those configuration by > exception features in Java EE 5, with one significant exception. While > the container will locate the /META-INF/persistence.xml file on its > own, a container that goes by the book will only deploy the > persistence unit if a resource reference is declared in the descriptor > file (web.xml or ejb-jar.xml). JBoss AS does not wait for this signal. > > In my opinion, there is a problem with the JBoss AS approach. What if > you have persistence units that you don't want to deploy? One use case > is that you have persistence units for different environments and a > configuration file can toggle between them. Another use case is that > you have another library, such as Spring or Seam, which bootstraps the > persistence unit instead. Sure, you could rename the file, but then > you break all the IDE behavior that expects the file to be named > persistence.xml. Personally, I think there should be some way to > disable the behavior in JBoss AS and make it look for the persistence > unit references. I agree to keep the automatic loading as the default, > but it is pretty inconvenient not to be able to disable it. > > Anyone else agree? Disagree? Why? > > -Dan > > -- > Dan Allen > Software consultant | Author of Seam in Action > > http://mojavelinux.com > http://mojavelinux.com/seaminaction > > NOTE: While I make a strong effort to keep up with my email on a daily > basis, personal or other work matters can sometimes keep me away > from my email. If you contact me, but don't hear back for more than a > week, > it is very likely that I am excessively backlogged or the message was > caught in the spam filters. Please don't hesitate to resend a message if > you feel that it did not reach my attention. > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev

There is plenty of control, if you know how to enable it. ;-)

We should fix AS 5 to have something that can allow it to be disabled (preferably without having to change AS 5 structure deployers as Ales suggest)

Could you give me an example on how to use jboss-structure.xml to have it not pick-up META-INF/persistence.xml even if it is there (i.e. to allow a thirdparty library pick it up) ? /max >> We should fix AS 5 to have something that can allow it to be disabled >> (preferably >> without having to change AS 5 structure deployers as Ales suggest) > > See my #4 --> jboss-structure.xml. > Changing structure deployers was more severe option. ;-) > > jboss-structure.xml is non invasive, > it will work on JBossAS, but won't interfere with other environments. > > Or what more do you want? :-)

AS 4.x did not do this, so it was never an issue before - hence looking for ways to have those apps still be able to deploy without a lot of changes.

We are not saying the default is bad, just that we would like to control it for issues listed.

> AS 4.x did not have a lot of things. ;-) Yep, and I am very glad to see them in JBoss AS 5. >> We are not saying the default is bad, just that we would like to control >> it for issues listed. > > That's how the default work. > Argue with the spec, not me. As far as I know, though I'm open to be proved wrong, according to the spec the persistence units are only loaded when a reference is found (either in the descriptor or in an annotation). That's pretty easy to avoid if you aren't using Java EE components (such as Spring beans or Seam JavaBeans). So we aren't really arguing with the spec. But then again, I'm fine with the stuff automatically loading (spares us the XML soup) but we do need to be able to disable it from within the application (not by modifying JBoss AS). If you are saying that we can put this XML file in the application, then that is exactly what I am looking for. Why not jboss-web.xml or jboss-app.xml? -Dan -- Dan Allen Software consultant | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

...until we can provide them with instructions.

On Tue, Dec 2, 2008 at 11:37 AM, Ales Justin <ales.justin(a)gmail.com&gt; wrote: >> ...until we can provide them with instructions. > > Can you push this to JBoss5 forum? I can bring it up there. > Or/and provide me with example - probably the one mentioned in JIRA? > And I'll add JBoss5 specific info that will make it work - hopefully > transparently. :-) Yes, transparently is what we are looking for. Here is what you need to do (I'm being very specific even though I figure you have Seam checked out from SVN). svn co http://anonsvn.jboss.org/repos/seam/trunk ant build set jboss.home in build.properties to point to an JBoss AS 5 installation cd examples/spring ant jbosswar watch for failed deployment in the log files: java.lang.IllegalArgumentException: Can't find a persistence unit named 'null' in AbstractVFSDeploymentContext@15139323{vfszip:/home/dallen/opt/jboss-as-5.0.0.preGA/server/default/deploy/jboss-seam-spring.war} at org.jboss.jpa.resolvers.DefaultPersistenceUnitDependencyResolver.resolvePersistenceUnitSupplier(DefaultPersistenceUnitDependencyResolver.java:141) at org.jboss.web.tomcat.service.TomcatInjectionContainer.resolvePersistenceUnitSupplier(TomcatInjectionContainer.java:676) at org.jboss.injection.PersistenceUnitHandler.addPUDependency(PersistenceUnitHandler.java:123) at org.jboss.injection.PersistenceContextHandler.loadXml(PersistenceContextHandler.java:76) at org.jboss.web.tomcat.service.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:544) ... Cheers, Dan -- Dan Allen Software consultant | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

> AS 4.x did not do this, so it was never an issue before - hence looking > for ways > to have those apps still be able to deploy without a lot of changes. AS 4.x did not have a lot of things. ;-)

> We are not saying the default is bad, just that we would like to > control it for issues listed. That's how the default work. Argue with the spec, not me.