Never tried but I think but is there anything interesting in JNDI?
Thank you for the reply.
On production servers there are far more datasources defined (e.g. for other applications) than actually needed in the list. So getting them with JNDI there is still the issue of manually filtering out the ones needed.
There must be a class in Seam that reads the persistence.xml and actually keep the info for further use. Normally I would look at the EJB3 container for this but we are using Tomcat 6.0 so that's a no-go.