before deploy "myapp.war" on glassfish 4 i have to
jdbc-connection-pool
does not work by itself... fine from asadmin)jdbc-resource
same as above)property javax.persistence.schema-generation.create-database-schemas
, but is bogus)now i'm doing:
asadmin add-resources ...
asadmin create-auth-realm ...
asadmin deploy ...
asadmin disable myapp ...
nano /.../glassfish/applications/myapp/WEB-INF/classes/META-INF/persistence.xml
ctrl+o
, enter
, ctrl+x
, enter
asadmin enable myapp ...
rm -Rf /tmp/install
and without other suggestion i'm planning to:
chmod +x deploy.sh
./deploy.sh
and the script will take care of everything. but i'd like to upload only a war file via glassfish http console and obtain the same result.
is there a way to have a class or script called before contextInitialized
?
how would you deploy this thing?
for completeness here are some additional info:
/myapp/WEB-INF/classes/META-INF/persistence.xml
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
<persistence-unit name="myapp" transaction-type="JTA">
<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
<jta-data-source>jdbc/myapp</jta-data-source>
<exclude-unlisted-classes>false</exclude-unlisted-classes>
<shared-cache-mode>NONE</shared-cache-mode>
<properties>
<property name="javax.persistence.jdbc.driver" value="com.mysql.jdbc.Driver"/>
<property name="javax.persistence.jdbc.url" value="jdbc:mysql://localhost:3306/myapp"/>
<property name="javax.persistence.jdbc.user" value="root"/>
<property name="javax.persistence.jdbc.password" value="password"/>
<property name="javax.persistence.schema-generation.database.action" value="create"/>
<property name="javax.persistence.schema-generation.create-database-schemas" value="false"/>
<property name="javax.persistence.schema-generation.scripts.action" value="drop-and-create"/>
<property name="javax.persistence.schema-generation.scripts.create-target" value="C:/tmp/myapp_create.ddl"/>
<property name="javax.persistence.schema-generation.scripts.drop-target" value="C:/tmp/myapp_drop.ddl"/>
<property name="eclipselink.deploy-on-startup" value="true"/>
<property name="eclipselink.target-database" value="MySQL"/>
<!-- <property name="eclipselink.ddl-generation" value="create-tables"/> -->
<!-- <property name="eclipselink.ddl-generation.output-mode" value="database"/> -->
<!-- <property name="eclipselink.create-ddl-jdbc-file-name" value="myapp.ddl"/> -->
<!-- <property name="eclipselink.logging.level" value="FINE" /> -->
<!-- <property name="eclipselink.logging.level.sql" value="FINE"/> -->
<!-- <property name="eclipselink.logging.parameters" value="true"/> -->
<!-- <property name="eclipselink.logging.logger" value="org.eclipse.persistence.logging.DefaultSessionLog"/> -->
</properties>
</persistence-unit>
</persistence>
/myapp/WEB-INF/glassfish-resources.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE resources PUBLIC "-//GlassFish.org//DTD GlassFish Application Server 3.1 Resource Definitions//EN" "http://glassfish.org/dtds/glassfish-resources_1_5.dtd">
<resources>
<jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="com.mysql.jdbc.jdbc2.optional.MysqlDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="jdbc/myapp_pool" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.DataSource" statement-timeout-in-seconds="-1" steady-pool-size="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
<property name="serverName" value="localhost"/>
<property name="portNumber" value="3306"/>
<property name="databaseName" value="myapp"/>
<property name="User" value="root"/>
<property name="Password" value="password"/>
<property name="URL" value="jdbc:mysql://localhost:3306/myapp"/>
<property name="driverClass" value="com.mysql.jdbc.Driver"/>
</jdbc-connection-pool>
<jdbc-resource enabled="true" jndi-name="jdbc/myapp" object-type="user" pool-name="jdbc/myapp_pool"/>
</resources>
while glassfish understands /myapp/.../persistence.xml (sometimes executing also CREATE SCHEMA myapp
, sometimes not, apparently random - but it's fine),
i definitely can't make glassfish read /myapp/WEB-INF/glassfish-resources.xml. it ignores this file.
UPDATE
glassfish reads the file but prefixes jndi names with java:app/
breaking other references. being aware of this thing i rewrite references with prefix and now it is working fine.
lastly, i noted that if glassfish-resources.xml
is inside META-INF
(instead of WEB-INF
) glassfish reads the file and it is also present in http ui under "applications > myapp > descriptors"
Azure provides different sources to deploy your web app some of them are: Since we want to deploy our We App from our GitHub profile, click on GitHub. It will ask you to sign-in to your GitHub profile. Now select App Service build survice build provider. This feature helps us to perform changes in our Web App in Azure.
How to build a web app: A beginner's guide (2021) 1 Step 1 – Source an idea. Before making a web app, you must first understand what you intend on building, and more importantly why? 2 Step 2 – Market Research. 3 Step 3 - Define your web apps functionality. 4 Step 4 - Sketch your web app. 5 Step 5 – Plan your web apps workflow. More items
You’ve sourced your idea, validated it, designed and developed your web app, and chosen your hosting provider. You’re now at the last step. Well done! The deployment step includes is how your web application gets from your source control on your computer to your cloud hosting from step 11.
Enter the location of your build output relative to your app's location or leave blank if it has not build. Enter build because that is where create-react-app generates the built files. Wait for the deployment to finish. In VS Code, in the Azure explorer, right-click your static web app's Application Settings and select Add New Setting.
finally i found a solution:
database create/upgrade: in ServletContextListener.contextInitialized
i use compile-time-generated ddl script to create database if not exists, or use liquibase to upgrade database if exists. no more persistence.xml usage for database generation.
authentication realm deploy: i don't deploy or create any container-specific realm. in ServletContextListener.contextInitialized
i register a custom JASPIC implementation, which is itself a JAAS login module wrapper. thanks to @ArjanTijms for this aricle and this answer
You can configure application scoped resources for the jdbc-connection-pool and jdbc-resource inside the glassfish-resources.xml and when you deploy your WAR file they will be created. When you undeploy your WAR they will go away. That solves the problem of manually adding them with asadmin. What I usually do it set it up manually using the GUI, then copy and paste the <jdbc-connection-pool>
and <jdbc-resource>
elements from the domain.xml into glassfish-resources.xml then I change the jndi-name to be application scoped, for example:
<jdbc-resource pool-name="MyAppPool" jndi-name="java:app/jdbc/my-app-pool"></jdbc-resource>
Then I make sure glassfish-resources.xml is packaged into the appropriate place in the WAR file, namely in the WEB-INF folder.
From what I have read in the Oracle documentation for Glassfish 4 it does not appear that you can package the auth-realm configuration with the application like you can for the JDBC stuff. I have filed an enhancement request for this glassfish auth-realm packaging enhancement It only appears that you can package the association to the realm in various deployment descriptors, see the "How to set a realm for an Application or Module" section of this guide for details.
HACK Alert
Actually I just thought of something which is a bit of a hack but might work around this issue. You could create a simple web APP which includes your real applications WAR file in it (in a resource directory). This wrapper app would include a REST client (like Jersey client) which would make REST calls to the Glassfish administration REST API to see if the auth-realm is there and configured. If it is it would use the REST API to deploy the embedded WAR file. If it isn't it would use the REST API to create the auth-realm and then it would deploy the WAR.
I'm not quite clear on the issues you are having with schema generation but that's all supported via the persistence.xml and works fine. If you want even more functionality in the way of automatic migration scripting then I would look at integrating a package like FlyAway
Here's an example of a glassfish-resources.xml file with app scoped resources which works for me under Glassfish 3.1.2. Some of the attributes you have I don't and I also don't use a JDBC JNDI naming style for the pool-name on the jdbc-resource.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE resources PUBLIC
"-//GlassFish.org//DTD GlassFish Application Server 3.1 Resource Definitions//EN"
"http://glassfish.org/dtds/glassfish-resources_1_5.dtd">
<resources>
<jdbc-connection-pool validation-table-name="TABLEVALIDATION" allow-non-component-callers="true"
statement-cache-size="200" associate-with-thread="true" statement-timeout-in-seconds="300"
non-transactional-connections="true" connection-leak-reclaim="true"
lazy-connection-association="true" connection-creation-retry-attempts="12"
lazy-connection-enlistment="true" validate-atmost-once-period-in-seconds="120"
statement-leak-timeout-in-seconds="360"
datasource-classname="oracle.jdbc.pool.OracleDataSource" res-type="javax.sql.DataSource"
connection-leak-timeout-in-seconds="420" statement-leak-reclaim="true"
name="UnitTestPool" is-connection-validation-required="true">
<property name="DataSourceName" value="OracleDataSource"></property>
<property name="ImplicitCachingEnabled" value="false"></property>
<property name="NetworkProtocol" value="tcp"></property>
<property name="DatabaseName" value="unittestdb"></property>
<property name="LoginTimeout" value="0"></property>
<property name="Password" value="tester"></property>
<property name="URL" value="jdbc:oracle:thin:@testbed:1521:xe"></property>
<property name="User" value="testertester"></property>
<property name="PortNumber" value="1521"></property>
<property name="ExplicitCachingEnabled" value="false"></property>
<property name="dynamic-reconfiguration-wait-timeout-in-seconds" value="960"></property>
<property name="MaxStatements" value="0"></property>
</jdbc-connection-pool>
<jdbc-resource pool-name="UnitTestPool" jndi-name="java:app/jdbc/unittestdb-pool"></jdbc-resource>
</resources>
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With