Persistence unit and @Service deployment order has changed i

[matt10]

My enterprise app relies on all persistence units being deployed when a particular @Service bean starts. The service scans all persistence units, and cannot know what persistence units there are at compile-time.

In Jboss AS 4.2.x, the Persistence Units were started before session beans and service beans. Thus, there was no problem.

In 5.0.0.GA the behaviour seems to have changed. Jboss AS 5 attempts to deploy the service in question before creating any Persistence Units.

In a simpler use-case I could add an explicit dependency on my service, like this:

@Depends("persistence.unit:unitName=MyApp.ear/MyApp.jar#persistenceUnitName")

This is not appropriate for my use case however. I need the service to wait for all persistence units to have started before it starts up... but the persistence units are not known at compile-time (It's a dynamic toolkit which scans for entity beans on startup.)

How can I get this working again under JBoss 5.0.0.GA?
Restoring the previous behavior of "deploy the Persistence Units first" would work.

Regards
Matt

[peterj]

Try this: create the directory server/xxx/deploy/last and place your service there. Then it should be deployed last. (Come to think of it, I haven't verified that this behavior is still true in 5.0.0.GA, so let me know if it works.)

[matt10]

Thanks Peter, didn't know that was possible.
But.. it's a self-contained EAR app.
And worse, because everything else depends on this service, it can't start *last*, it has to start first but after the persistence units. :/

[peterj]

What is the order of the components in application.xml? My understanding is that the components are deployed in the order in which they appear in that file.

[matt10]

There is one jar only in application.xml - containing all application code and services.

Regards,
Matt