[
https://jira.jboss.org/browse/ARQ-166?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-166:
-------------------------------
Two open questions remain:
1. Should XML be all uppercase in the configuration properties domainXml and
resourcesXml?
2. Should we provide the configuration defaultDataSourceName that sets up an
org.apache.derby.jdbc.EmbeddedDataSource?
The reason for #2 is that the default data source in GlassFish (named jdbc/__default)
connects to a remote Derby instance, which will not likely be available to an embedded
GlassFish instance.
Allow domain.xml and sun-resources.xml to be configured for embedded
GlassFish container
----------------------------------------------------------------------------------------
Key: ARQ-166
URL:
https://jira.jboss.org/browse/ARQ-166
Project: Arquillian
Issue Type: Feature Request
Components: GlassFish Containers
Affects Versions: 1.0.0.Alpha2
Reporter: Dan Allen
Attachments: ARQ-166-patch.txt
In addition to specifying the instance root, the embedded GlassFish container allows a
distinct domain.xml file to be specified. Support this override in the container
configuration.
private String domainXml;
public String getDomainXml()
{
return domainXml;
}
public void setDomainXml(String domainXml)
{
this.domainXml = domainXml;
}
Often times, the developer is fixing the instance root in order to setup container
resources (JDBC resources, JMS destinations). Instead of using the instance root for this
purpose, allow the developer to specify a sun-resources.xml file. Use the embedded
GlassFish command runner to execute the add-resources asadmin command to feed the
resources defined in this file into the serer in the container setup method.
private String resourcesXml;
public String getResourcesXml()
{
return resourcesXml;
}
public void setResourcesXml(String resourcesXml)
{
this.resourcesXml = resourcesXml;
}
See
http://blogs.sun.com/arungupta/entry/totd_133_jpa2_jpql_criteria
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira