[jboss-user] [JBoss Seam] - Re: Seam 2.0.1GA : EJB Blockers with Weblogic 9.x/10.x
Hi Christian, could you let me know the case number with BEA ? Since I opened a case myself I could refer to your number when talking to BEA. You can send me the case number to : [EMAIL PROTECTED] Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127675#4127675 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127675 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam 2.0.1GA : EJB Blockers with Weblogic 9.x/10.x
Hi, does that mean the changes (finally :-) find their way into the next release of Seam ? That is at least what I'd expect and as far as I understood from Gavin, support for other appservers than JBoss has become a top priority for the Seam project (see respect. Seam 2.0.0 announcment thread in TheServerSide). @Christian : again, thanks for that excellent piece of work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127534#4127534 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127534 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam 2.0.1GA : EJB Blockers with Weblogic 9.x/10.x
Excellent - brilliant - what more can I say ? Apparently someone finally spent some fforts in resolving this issue entirely and got Seam work fine in Weblogic. Now, that not only the vararg issue is resolved but also any subsequent issue and the Seam examples running fine (incl. the TimerServiceDispatcher EJB) I'd strongly suggest to include these changes into the next release. Just excluding the TimerService from the seam deployment should not be an option anymore, now that there is a solution available. You made my day :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127250#4127250 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127250 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam 2.0.1GA : EJB Blockers with Weblogic 9.x/10.x
Hi, I don't think that there will be a problem running JBoss with jrockit, since the part that decompiles the EJB's and creates the source code seem to be weblogic/appserver specific and has nothing to do with the plain underlying JVM. Apparently, JBoss is working fine in this respect - anyhow, a simple test case could be to deploy the seam samples as they are in JBoss using a jrockit JVM. Since Seam contains the TimerServiceDispatcher EJB using varargs that should trigger the problem - or not :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126581#4126581 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126581 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam 2.0.1GA : EJB Blockers with Weblogic 9.x/10.x
Hi, since my company owns a support contract with BEA, I did open an official "CASE" with BEA - let's see what happens. I will keep you informed. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126534#4126534 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126534 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam 2.0.1GA : EJB Blockers with Weblogic 9.x/10.x
Hi, I added some more comments to the existing BEA forum, so anyone being interested can read : http://forums.bea.com/thread.jspa?messageID=36290 I very much appreciate Pete's comment and would naturally be happy either way it is done - using arrays/ArrayLists or having a separate jboss-seam.jar for weblogic is perfectly fine with me :-) Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126515#4126515 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126515 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Seam 2.0.1GA : EJB Blockers with Weblogic 9.x/10.x
Hi, first of all congratulations for the Seam 2.0.1GA release and thanks for the updated documentation, especially how to run Seam in appservers other than JBoss. As I read from the docs the varargs issue with Bea Weblogic still persists. As far as I understood, BEA claims this issue to be an ambiguity within the Java specs, since the same flag is used to mark fields transient as it is used to mark methods have variable arguments. I furthermore understood, that this issue is not necessarily related to EJB's only, but actually apply to any java code. The fact that the issue shows up with EJB's only is due to jrockits re-compiles the EJB's during deployment. As per my understanding, a compiler/interpreter should be in a position to handle the transient/vararg flag different for fields and methods (as Sun's implementation apparently does) so I actually see it BEA's responsibility to fix that issue. Anyhow, according to my experience I'd not expect such a fix is being delivered by BEA within the next 12 months, if at all. Since the next 1 or 2 years certainly will be very important for the roll-out and further distribution of Seam, would it make sense to fix that (rather "work around") within Seam in the meantime ? As far as I understood, the proposed work around is to use arrays instead of varargs in methods/constructors to avoid the issue. This seem to be an acceptable work around for me to overcome the issue for any of my projects/developments. The only problem remaining is : how many Seam internal EJB's are using varargs currently and if it makes sense to use arrays instead of varargs to have some kind of Weblogic/JRockit compatibility ? I mean I fully understand that using varargs is the proper implementation, but I'd consider using arrays as a valid work around and if it's only the "TimerService" ejb that currently causes the problem in JRockit/Weblogic, why not take a step back (=use arrays) and therefore have another major player (Weblogic) on board. I made much bigger comprises during my IT career so far :-) If a fix for jrockit is provided that can naturally been reversed. Any thoughts ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126499#4126499 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126499 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
