Ok, great.
We'll try the glassfish 2 deployment and at the same time update the
documentation on the wiki with the steps.
Also, we will start investigate how and what the jee6 upgrade will be done.

Thx.../Andreas

On Mon, Jan 4, 2010 at 1:37 PM, dmurat <damir.mu...@gmail.com> wrote:

>
> > If it is a matter of simple things I'm sure it will be done soon after
> the
> release of JEE6  and stable implementations of it (is the release official
> yet or...?).
>
> Yes, JEE 6 is officially released, and Glassfish is official reference
> implementation.
>
> > By the way, have you tried it on Glassfish 2 (JEE5 container)?
>
> Yes, I have, and again, after many trials and errors, I've finally
> succeeded. Here are steps:
>
> Domain model project
>  - Edit "src/main/resources/sculptor-generator.properties":
>      deployment.applicationServer=Tomcat
>      db.product=postgresql
>
> Web project
>  - Delete "src/main/webapp/META-INF/context.xml".
>  - Edit "src/main/webapp/WEB-INF/web.xml":
>
>    <!--
>    <web-app
>        version="2.5"
>        xmlns="http://java.sun.com/xml/ns/javaee";
>        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>        xsi:schemaLocation="
>            http://java.sun.com/xml/ns/javaee
> http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd";>
>    -->
>
>    <web-app
>        version="2.4"
>        xmlns="http://java.sun.com/xml/ns/j2ee";
>        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>        xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd";>
>
>      ...
>
>      <resource-ref>
>        <description>Aliased LibraryDS now visible in
> java:comp/env</description>
>        <res-ref-name>jdbc/LibraryDS</res-ref-name>
>        <res-type>javax.sql.ConnectionPoolDataSource</res-type>
>         <res-auth>Container</res-auth>
>      </resource-ref>
>     </web-app>
>
>  - Create "src/main/webapp/WEB-INF/sun-web.xml":
>
>    <?xml version="1.0" encoding="UTF-8" ?>
>     <!DOCTYPE
>        sun-web-app PUBLIC "-//Sun Microsystems, Inc.//DTD GlassFish
> Application Server 3.0 Servlet 3.0//EN"
>        "http://www.sun.com/software/appserver/dtds/sun-web-app_3_0-0.dtd";>
>
>    <sun-web-app>
>      <resource-ref>
>         <res-ref-name>jdbc/LibraryDS</res-ref-name>
>        <jndi-name>jdbc/LibraryDS</jndi-name>
>      </resource-ref>
>
>      <class-loader delegate="false"/>
>      <property name="useBundledJsf" value="true"/>
>     </sun-web-app>
>
>
> Please note that I've also changed POMs of domain and web projects pretty
> drastically, but I'm not sure that this is needed for successful
> deployment.
> However, if somebody is interested, I can post POMs too.
>
> Best regards,
> Damir Murat
> --
> View this message in context:
> http://old.nabble.com/helloworld-web-glassfish-deployment-tp26855630s17564p27012363.html
> Sent from the Fornax-Platform mailing list archive at Nabble.com.
>
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Fornax-developer mailing list
> Fornax-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/fornax-developer
>
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Fornax-developer mailing list
Fornax-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fornax-developer

Reply via email to