[
https://issues.jboss.org/browse/SEAMFORGE-210?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on SEAMFORGE-210:
-----------------------------------------------
From mail on forge-dev May 11:
well, is that info persisted somewhere so other plugins can read the info ?
persistence.xml does not have it and as discussed at JBW I believe deploment time DB info
<> development DB info.
What would be great is if the persistence plugin would have a single or even list of named
JPADataSource's which have enough info for data query, reverse engineering etc. could
be done withuot having to repeat it at every generate-entity call.
Forge should provide development profiles API for datasources and
other configs
-------------------------------------------------------------------------------
Key: SEAMFORGE-210
URL:
https://issues.jboss.org/browse/SEAMFORGE-210
Project: Seam Forge
Issue Type: Feature Request
Components: Plugin API
Affects Versions: 1.0.0.Alpha3
Reporter: Lincoln Baxter III
lincolnthree
It gives you what is in persistence.xml
11:22
maxandersen
it wasn't there a jbossworld
11:22
lincolnthree
that's been there from the beginning
11:22
maxandersen
yes - persistence.xml says datasources
nothing about the actual connection info
11:23
lincolnthree
oh right
well
connection info is stored on the server
forge doesn't know that
unless it's in the persistence.xml
11:23
maxandersen
lincolnthree: exaactly - but it has to know that eventually.
11:23
lincolnthree
as properties
11:23
maxandersen
lincolnthree: it wont be
lincolnthree: this is why tools like rails, hibernate tools and others have notion of
"profiles" or simply just property overrides for use at design time and for use
at runtime
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira