[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2635) Support for OC4J - 10.1.3

[Juan Luis Serradilla Amarilla (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-2635?page=comments#action_12417699 ] 
            
Juan Luis Serradilla Amarilla commented on JBSEAM-2635:
-------------------------------------------------------

You can read this at "http://www.um.es/atica/index.php?option=com_docman&task=cat_view&gid=163&itemid=286".

This file ("http://www.um.es/atica/documentos/prototype-oc4j-JIRA.rar") contains a prototype to test Seam2.0 on OC4J10.1.3.3, and it has been developed by Juan Miguel (juanmiguelbgNOSPAM at um.es). Thank you very much to Juan Miguel for his good job.

We hope this entry helps to solve the JBoss JIRA item  "http://jira.jboss.com/jira/browse/JBSEAM-2635".

The source is the "prototipo-oc4j-JIRA.rar" file, an Ant Eclipse project whithout libs. You can see the changes on the "persistence.xml" file that allow to work with datasources.

These are Juan Miguel's notes to explain the prototype:

"I´m working with the Latest Seam 2 release (2.0.2.SP1) and OC4J 10G Release 3 (10.1.3.3). I´ve followed through the Jason´s Lee scheme but I´ve made some changes.
I´ve used:
  RichFaces 3.2.1.GA
  JSF 1.2 (1.2_07)
  JSF Facelets 1.1.14
  Hibernate 3.2

I could not run the standard estructure of a seam 2 application, because I had problems with the seam interceptor "<around-invoke> problems", I think that you have seen this problem. I´m novice in Seam 2 and OC4J.

The estructure of the application:

EAR/
  META-INF/
    application.xml
    orion-application.xml
 WAR/
    security.drl
    *.xhtml pages, stylesheets, layouts, img (generates by seam-gen CRUD generator and other created by me)
    META-INF/
       (empty)
    WEB-LIB/
       components.xml
       faces-config.xml
       pages.xml
       web.xml
       lib/ (all the libs needed for the application - include Seam libs)
         ejb-library.jar (my EJB library)
            META-INF/
               persistence.xml (Hibernate - no toplink (but I´ve other example with toplink as JPA)
               ejb-jar.xml
               seam.properties
               the EJB compiled classes
       classes/ (log4j configuration,  messages_*.properties, seam.properties (I think that it´s not need) )

I´ve created a shared-lib to Hibernate 3.2 on OC4J, and I´ve had to remove the Oracle XML parser to solve problems with RichFaces styles (orion-application.xml).
I´ve used Facelets to solve the limitations of the OC4J JSP and Servlet versions.

But there are two problems that I can´t solve. One of them are the Stateful and Stateless annotations, if I annotated a session bean with one of  them, I had problems with the JNDI loopback, although the session bean was registered in the web.xml file. Solution: don´t use these annotations, use the Scope annotation.
The other problem is the EJB Synchronizations bean."

> Support for OC4J - 10.1.3
> -------------------------
>
>                 Key: JBSEAM-2635
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2635
>             Project: Seam
>          Issue Type: Task
>          Components: Platform interoperability
>         Environment: Solaris, Linux, Windows
>            Reporter: Chris Simons
>
> To gauge interest in Seam support, whether it be detailed documentation or actual changes to baseline, within the Oracle Container For Java (OC4J) 10.1.3.  
> 10.1.3 is also known as Oracle Application Server 10g Release 3.
> Our personal example...
> After receiving the go-ahead to use the JBoss AS on our application development contract to a U.S. military organization we were disappointed to find that ongoing software standardization efforts, of which were not communicated to contractors, are starting to take affect.  Our client is currently running a distributed Oracle AS 10g Release 2 infrastructure but we're hoping we can convince them to move to Release 3 in the near future.  Therefore, 10.1.3 support for Seam, seeing as we have invested at least a few months into the development cycle, might prove to be critical.
> Please vote for this issue if you are interested in supporting this feature request.

-- 
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