[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2482) Possible work around for Weblogic "varargs" EJB issue

[Jay Balunas (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-2482?page=comments#action_12407321 ] 
            
Jay Balunas commented on JBSEAM-2482:
-------------------------------------

The above mentioned patch does fix the varargs issue, however there is another weblogic issues that occurs after that (see attached jiras, and forum references for details). 

This means the EJBTimer still does not work on WebLogic.  Pete has made the changes for the "jboss-seam-wls-compatible.jar" file.  This does not contain the "org/jboss/seam/async
/TimerServiceDispatcher" EJB.  When seam is built this jar will be in the "lib/interop" directory.  It can be used with Weblogic instead of "jboss-seam.jar" to get around this issue.

Once BEA fixes there issue and it is verified then these changes can be removed.



> Possible work around for Weblogic "varargs" EJB issue
> -----------------------------------------------------
>
>                 Key: JBSEAM-2482
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2482
>             Project: JBoss Seam
>          Issue Type: Task
>          Components: Documentation Issues, Examples, Platform interoperability
>    Affects Versions: 2.0.1.CR1
>            Reporter: Jay Balunas
>         Assigned To: Jay Balunas
>            Priority: Minor
>         Attachments: full-stack-of-ejb-transient-error.txt
>
>
> There is a know issue with weblogic and support for EJBs that use variable arguments.  This is documented in the reference guide for more details.
> I've attached the full stack trace from the console.
> The main errors revolve around EJB3 timers - there may be a way to disable timers through the weblogic.xml deployment descriptor, or perhaps a different file. 
> There are other warnings around EJB synchronization, but they may still function.
> If solved the reference docs should be updated.

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