http://blog.flexive.org/2009/02/11/weblogic-103-compatibility/ Mon, 31 Aug 2009 14:40:15 +0000 hourly 1 http://wordpress.com/ http://blog.flexive.org/2009/02/11/weblogic-103-compatibility/#comment-106 Roy Mon, 31 Aug 2009 14:40:15 +0000 http://blog.flexive.org/?p=100#comment-106 What suitable entry is used in ejb-jar.xml to over come this issue? What suitable entry is used in ejb-jar.xml to over come this issue?

]]> http://blog.flexive.org/2009/02/11/weblogic-103-compatibility/#comment-98 Saket Agrawal Fri, 24 Jul 2009 07:03:45 +0000 http://blog.flexive.org/?p=100#comment-98 Yes I too faced this issue of Weblogic. But if you actually add suitable entry in ejb-jar.xml this issue disappears and you are allowed to pass the inner class as parameter. Though adding the entry is not required by EJB3.0 spec. So to fix this issue one can have EJB3.0 with inner class as one of the parameter and specify transaction attribute in ejb-jar.xml. Yes I too faced this issue of Weblogic. But if you actually add suitable entry in ejb-jar.xml this issue disappears and you are allowed to pass the inner class as parameter. Though adding the entry is not required by EJB3.0 spec. So to fix this issue one can have EJB3.0 with inner class as one of the parameter and specify transaction attribute in ejb-jar.xml.

]]>