6:52 a.m.
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of assumptions
that are made by seam-gen that render it incompatible with a generic Java EE-compliant
application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:33 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=all ]
Dan Allen updated JBSEAM-1619:
------------------------------
Attachment: glassfish-datasource.xml
I have attached the glassfish-datasource.xml to complement the datasource-ds.xml file used
for the JBoss AS deployment. The destination file is handled differently for the Glassfish
deployment. It is not just copied into the deployment directory as is done for JBoss AS.
Instead, the file is fed into the Glassfish add-resources command to setup the pool and
data source in the JNDI tree. This can only be done once, so it may need a special target
in the ant script to run it.
The add-resources command is:
${glassfish.home}/bin/asadmin add-resources $PWD/resources/glassfish-dev-datasource.xml
and
${glassfish.home}/bin/asadmin add-resources $PWD/resources/glassfish-prod-datasource.xml
The absolute file name is important. If it is relative, Glassfish will look for it in the
domain configuration directory. Glassfish must be running for this command to be
executed.
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:38 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=comments#action_12368162 ]
Dan Allen commented on JBSEAM-1619:
-----------------------------------
We should probably establish the property glassfish.home early on as it will become useful
for executing commands for adding resources and deploying the exploded directory.
If the .war suffix is removed from the exploded archive, the following command will work
to deploy to Glassfish:
${glassfish.home}/bin/asadmin deploydir $PWD/exploded-archives/project_name
Unfortunately, if the directory has a .war suffix, Glassfish becomes confused and thinks
that it is supposed to be an actual .war file. Fortunately this does not mess up
compatibility with JBoss since the files are still copied into the JBoss deployment
directory in a directory that contains the .war suffix.
The nice part about Glassfish is that no further coping must be done to repeatedly deploy
files.
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:20 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=comments#action_12368169 ]
Gavin King commented on JBSEAM-1619:
------------------------------------
Great, thanks Dan, much appreciated, we should try and get this integrated asap.
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.0.0.GA
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:20 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=all ]
Gavin King updated JBSEAM-1619:
-------------------------------
Fix Version/s: 2.0.0.GA
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.0.0.GA
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:57 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=comments#action_12378220 ]
Dan Allen commented on JBSEAM-1619:
-----------------------------------
It appears that the standard file extension for a Glassfish resource file is
.sun-resource
We should probably follow that convention.
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.0.0.GA
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:41 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=comments#action_12378224 ]
Pete Muir commented on JBSEAM-1619:
-----------------------------------
Dan, we shouldn't deploy the -all.jar files, but instead just copy the necessary
(real) jars (i.e. hibernate.jar, hibernate-entitymanager.jar, hibernate-annotations.jar
etc).
Can you write a patch against seam-gen for this? IMO we should write ant targets to wrap
up the glassfish deploy commands. I think this will need a way to check if glassfish is
currently running, and if not perhaps prompt to start it.
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.0.0.GA
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:51 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=comments#action_12378302 ]
Daniel Kimmig commented on JBSEAM-1619:
---------------------------------------
I was thinking about requesting a feature concerning seam-gen for a long time. That
feature would have been to make seam-gen aware of other containers such as Glassfish and
Tomcat.
Although I am happy to see that there is work in progress to decouple seam-gen from JBoss
AS, I think it is quite disappointing that you rule out Tomcat like that. Bringing Tomcat
to seam-gen would help Seam adoption much more then Glassfish imho, because the biggest
concern about Seam adoption is still the environment restriction it emposes. By
aggressively showing RAD with seam-gen on a container like Tomcat, much of the "Do i
need to use EJB on one of those huge and complicated appservers?"-FUD could be
negated.
As Michael Yuan pointed out in his blog (
http://www.michaelyuan.com/blog/2007/07/24/seam-20-and-tomcat/ ), there are two ways to
use Seam on Tomcat, either with Embedded JBoss MC or without the MC but restricted to Seam
POJOs. If that is the case, why is it so hard to ask the user during seam-setup which
container he chooses and if he enters Tomcat, then ask which of these two options should
be used.
My concern for this issue relies in the fact that in my company we evaluated Seam and
found its features quite nice, especially for a new project that needs JSF components
ajaxified with each other. It was great to read about seam-gen, a tool that supposedly
should get you started with the project structure and build process. Unfortunately a lot
of development effort has been done using Spring/Hibernate on Tomcat during the last years
and therefor all of theapplications are hosted on a unique instance of Tomcat.
I think I am by far not alone with an environment like that. If you want to compete with
Spring, you need to be able to live in the same environment that Spring does. This is the
only way that you can make developers choose Seam for their next project. Because in real
life, no one will port their production applications to a different container/appserver
JUST to make the new project executable.
I opened a thread concerning this issue in the Seam forum.
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087856#...
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.0.0.GA
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:20 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=comments#action_12378348 ]
Dan Allen commented on JBSEAM-1619:
-----------------------------------
Please let's keep this issue focused on Glassfish V2. I do not want to distract the
goal here.
Pete, I have a better understanding now of what it takes to get the app deployed to
Glassfish and I am prepared to make a new patch with your suggestions (though it may be
that Hibernate isn't even required)
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.0.0.GA
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:16 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=all ]
Norman Richards updated JBSEAM-1619:
------------------------------------
Fix Version/s: 2.0.1.GA
(was: 2.0.0.GA)
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.0.1.GA
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:58 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=all ]
Pete Muir updated JBSEAM-1619:
------------------------------
Fix Version/s: 2.0.x
(was: 2.0.1.GA)
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.0.x
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=comments#action_12401167 ]
David Sachdev commented on JBSEAM-1619:
---------------------------------------
What is the current status of this issue? I would be very interested in Seam-gen working
seamlessly with Glassfish.
Reference pages:
http://jkook.blogspot.com/2007/12/kooking-seam-with-glassfish.html
http://joshuajava.wordpress.com/2008/01/29/deploying-seam-pojo-apps-on-gl...
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.1.x
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:39 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=comments#action_12401529 ]
Dan Allen commented on JBSEAM-1619:
-----------------------------------
Seam in Action chapter 2 also details exactly what needs to be done for a glassfish
deployment.
I know there is some opposition to having seam-gen support multiple appservers, but I
think that is an unwise position. We really need to figure out how to get a couple of
additional options baked into seam-gen. I went with Glassfish because it behaves and thus
the changes were minimal. I guess Tomcat could go just as smoothly with the prerequisite
of having the Embedded JBoss installed.
I recognize that additional appserver support results in more to maintain and test, but we
are out there promising folks that we will test it for them, so yeah, I think we have to
take on that responsibility. Let's just start with Glassfish. It's more about
proving it is possible then making everyone happy. Next, we move on to Tomcat, which by
the way needs a separate issue report.
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.1.x
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:34 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=comments#action_12401572 ]
Max Andersen commented on JBSEAM-1619:
--------------------------------------
Dan, please realize if seam-gen does jboss tools should also be changed. It is this N x N
configuration setup that is the reason for us to keep things *simple* and then simply
explain in docs how to adjust.
The changes are not exactly trivial to implement in something like seam-gen without
introducing a big dependency and version mismatch...
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.1.x
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:53 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=comments#action_12401575 ]
Max Andersen commented on JBSEAM-1619:
--------------------------------------
note: if someone can explain me how we can do this without breaking every release of
seamgen and jbosstools when something gets updated then I am *very interested*...
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.1.x
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:10 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=comments#action_12401583 ]
Dan Allen commented on JBSEAM-1619:
-----------------------------------
Aside from one naming issue, this is really just a packaging issue. It's just a matter
of having build.xml include targets that package it properly for a different server. I
don't really see how that affects jbosstools, but I could be lacking the
understanding.
The biggest issue is the java:/ prefix on the datasource. JBoss is the only appserver that
seems to understand this notation. To avoid having to modify the persistence.xml file for
different environments, I propose that we use the standard JNDI naming (something like
jdbc/datasource). This can be enabled in the -ds.xml file by using
<use-java-context>false</use-java-context>.
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.1.x
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:32 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=comments#action_12401729 ]
Max Andersen commented on JBSEAM-1619:
--------------------------------------
if it purely changes in the build.xml then probably i'm fine...but if it changes where
things are supposed to go or different set of jars etc. we should at least do it in a way
so it is possible for us to reuse the set of libraries and where thing goes.
the naming issue will be relevant if it changes the way templates will be processed and
how things run in the embedded container.
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.1.x
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:17 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[ http://jira.jboss.com/jira/browse/JBSEAM-1619?page=comments#action_12420230 ]
Samuel Doyle commented on JBSEAM-1619:
--------------------------------------
There is a lot of noise on this subject and I believe Dan is correct in that adding
GlassFish support will increase the adoption rate of Seam.
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: http://jira.jboss.com/jira/browse/JBSEAM-1619
Project: Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: The future
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:06 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[
https://jira.jboss.org/jira/browse/JBSEAM-1619?page=com.atlassian.jira.pl...
]
Dan Allen commented on JBSEAM-1619:
-----------------------------------
Fixed. The only change that was made to the shared templates is that I renamed
Authenticator to AuthenticatorJavaBean, make Authenticator a @Local interface, and
introduced the @Stateless bean AuthenticatorBean. So the generator for WAR projects has to
copy AuthentictorJavaBean to Authenticator.java
Please see the following entries documenting the progression for how I implemented it this
support.
http://www.mojavelinux.com/blog/archives/2008/10/deploying_a_seamgen_proj...
http://code.google.com/p/seaminaction/wiki/DeployingToGlassFish
http://in.relation.to/Bloggers/JBossAS5AndGlassFishSupportAddedToSeamgen
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: https://jira.jboss.org/jira/browse/JBSEAM-1619
Project: Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Fix For: 2.1.2.CR1
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:06 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Resolved: (JBSEAM-1619) support for Glassfish in seam-gen
[
https://jira.jboss.org/jira/browse/JBSEAM-1619?page=com.atlassian.jira.pl...
]
Dan Allen resolved JBSEAM-1619.
-------------------------------
Fix Version/s: 2.1.2.CR1
(was: The future)
Resolution: Done
Assignee: Dan Allen
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: https://jira.jboss.org/jira/browse/JBSEAM-1619
Project: Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 2.1.2.CR1
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:41 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1619) support for Glassfish in seam-gen
[
https://jira.jboss.org/jira/browse/JBSEAM-1619?page=com.atlassian.jira.pl...
]
Dan Allen commented on JBSEAM-1619:
-----------------------------------
Ignore the comment about Authenticator.java. I restored the previous template so that it
doesn't break JBoss Tools. I just use new file names for the @Stateless and @Local
classes (AuthenticatorLocal.java and AuthenticatorBean.java).
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: https://jira.jboss.org/jira/browse/JBSEAM-1619
Project: Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 2.1.2.CR1
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:21 p.m.
New subject: [JBoss JIRA] Closed: (JBSEAM-1619) support for Glassfish in seam-gen
[
https://jira.jboss.org/jira/browse/JBSEAM-1619?page=com.atlassian.jira.pl...
]
Pete Muir closed JBSEAM-1619.
-----------------------------
support for Glassfish in seam-gen
---------------------------------
Key: JBSEAM-1619
URL: https://jira.jboss.org/jira/browse/JBSEAM-1619
Project: Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Environment: Glassfish V2
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 2.1.2.CR1
Attachments: glassfish-datasource.xml
Original Estimate: 1 day
Remaining Estimate: 1 day
I believe that adding support for Glassfish will help promote the adoption of Seam. In my
mind, Tomcat is not nearly as important because it is not a Java EE-compliant environment
and seam-gen is all about creating compliant projects.
Supporting Glassfish is actually quite straightforward. There are a couple of
assumptions that are made by seam-gen that render it incompatible with a generic Java
EE-compliant application server. Here is what needs to change:
1. The java:/ prefix on the data source causes problems with other servers. This can be
easily brought into compliance by adding
<use-java-context>false</use-java-context> to the *-ds.xml files and removing
the java:/ prefix from the persistence-*.xml files in the seam-gen/resources/META-INF
directory
2. Glassfish does not use Hibernate EntityManager as the default JPA provider, and
therefore does not have any of its jar files. Of course, we could just make everyone copy
necessary hibernate jar files into the glassfish installation directory, but that just
isn't going to go over well. I think a better approach is to modify the build.xml
file to copy the following three libraries if the property hibernate.needed=true is set:
hibernate-all.jar
thirdparty-all.jar
jboss-archive-browsing.jar (not currently in the seam distribution, but stuck inside the
jboss-embedded-all.jar file)
3. Make the hibernate.transaction.manager_lookup_class parameterized, perhaps asking
during setup
4. Removing the .war suffix on the exploded archive directory (so that Glassfish can
deploy the directory using asadmin deploydir)
That's it! Then you can have Glassfish working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5263
days inactive
6192
days old
21 comments
8 participants
participants (8)
-
Dan Allen (JIRA) -
Daniel Kimmig (JIRA)
-
David Sachdev (JIRA)
-
Gavin King (JIRA)
-
Max Andersen (JIRA)
-
Norman Richards (JIRA)
-
Pete Muir (JIRA)
-
Samuel Doyle (JIRA)