March 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2592) Seam 2.0.1 GA patched to support BEA WebLogic Server 10.x with EJB3 support

by lauerc (JIRA)

Seam 2.0.1 GA patched to support BEA WebLogic Server 10.x with EJB3 support --------------------------------------------------------------------------- Key: JBSEAM-2592 URL: http://jira.jboss.com/jira/browse/JBSEAM-2592 Project: JBoss Seam Issue Type: Patch Components: Platform interoperability Affects Versions: 2.0.1.GA Environment: BEA WebLogic Server 10.0 MP1 Reporter: lauerc Priority: Blocker Fix For: 2.0.1.GA Hi folks, I'm currently in working on the meanwhile old WebLogic compatibility issue, which is a show stopper for products which are forced to run in an BEA environment and rely on EJB features. The current situation is that the EJB3 compiler of WebLogic Server 10.x doesn't deploy JBoss Seam applications, because it doesn't support EJB3 interfaces containing methods with varars (Object...) definitions. This is obviously a bug, but it's known by the vendor of WebLogic for more than a year and meanwhile I don't believe anymore that is going to be fixed in short. This situation is critical for many projects, since this is a killer arguments against JBoss Seam. Since it is more or less unknown what more supprises this mix brings, I started an affort to patch the current JBoss Seam version (2.0.1.GA) to work wis BEA WebLogic 10.0 MP1. First of all I've replaced the varargs in interfaces to get one step beyond the known EJB3 compiler problem. This was quite easy because only one single EJB interface is affected: org.jboss.seam.async.Dispatcher I've replaced the varargs definitions (Object...) by Object[], which is what the compiler creates anyway from it. For reasons of convenience, I've also created an method which completely reduces the method to the non variable parts. Here's an example: public T scheduleTimedEvent(String type, S schedule, Object... parameters); was turned into: public T scheduleTimedEvent(String type, S schedule); public T scheduleTimedEvent(String type, S schedule, Object[] parameters); Maybe this is not as elegant as the varags solution, but it's a pragmatic way to suit our needs as I don't think BEA will fix the related problem in short. The next problem I stumbled into was a classloading problem related to another problem in BEA WebLogic 10.0 MP1. The server only works properly with it's own jsf implementation which is not deployed by default. It is packed into a war archive located at wlserver_10.0/common/deployable-libraries/jsf-1.2.war I've tried to deploy this archive which failed, so I unpacked it and placed the included jars into the 'lib' folder below my weblogic domain root. After that I found out, that one jboss jar, which is needed to run the application under other application servers was missing in the seam distribution. I placed this file (concurrent.jar) into the folder lib below by test application subproject (examples/jee5/lib). After some more deployment descriptor related changes, which I will not describe in detail, the application seems to work at first. Unfortunately I detected runtime failures when playing around with the booking application. From time to time the application failed with an InvocationTargetException. After hours of code analyzing and debugging, I found out that the problem has to be a side effect of different EJB lifecycle implementation in WebLogic Server compared to JBoss AS (I don't know which behaviour is wrong or right, and I won't judge it here). Actually the method postConstruct(...) of class org.jboss.seam.intercept.SessionBeanInterceptor seems to rule the initialization of this interceptor. This method seems to be called before any call of aroundInvoke at JBoss AS. On WebLogic Server this is different. As a result of this sometimes the injection field or method invoking for a specific object is executed using the reflection fields and methods of different component classes. To fix this problem, I've copied the initialization calls from method post construct into the method aroundInvoke to make sure that it is called prior to the actual invocation. After this change the booking demo seems to work perfectly. I've packed all source changes and the missing jar file into one zip archive and will post it into this thread. To use this, simply extract it below the exploded distro archive and rebuild first seam and then the jee5/booking demo. Best regards, Christian -- 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

17 years, 11 months

4
27
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2534) inline email attachments not showing up properly

by sandy brydon (JIRA)

inline email attachments not showing up properly ------------------------------------------------ Key: JBSEAM-2534 URL: http://jira.jboss.com/jira/browse/JBSEAM-2534 Project: JBoss Seam Issue Type: Patch Components: Mail Affects Versions: 2.0.1.CR2 Environment: JBoss-4.2.1.GA Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-241) Mozilla Thunderbird version 2.0.0.9 (20071031) Apple Mail Version 2.1.2 (753) Gmail Hotmail Reporter: sandy brydon Assigned To: Pete Muir Priority: Minor what is being produced: Header... Content-Type: multipart/mixed; boundary="outer-boundary" --outer-boundary Content-Type: image/gif; charset=ISO-8859-1; name=logo.gif Content-Transfer-Encoding: base64 Content-ID: <image-content-id> Content-Disposition: inline; filename=logo.gif BASE64=ENCODED=IMAGE=DATA== --outer-boundary Content-Type: multipart/alternative; boundary="inner-boundary" Content-Disposition: inline --inner-boundary Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline my plain text --inner-boundary Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline <html> <body> my html text<br /> <img src="cid:image-content-id" /> </body> </html> --inner-boundary-- --outer-boundary-- what i think should be there (i'm no email expert) Header... Content-Type: multipart/alternative; boundary="outer-boundary" --outer-boundary Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit my plain text --outer-boundary Content-Type: multipart/related; boundary="inner-boundary" --inner-boundary Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <body> my html text<br /> <img src="cid:image-content-id" /> </body> </html> --inner-boundary Content-Type: image/gif; name="logo.gif" Content-Transfer-Encoding: base64 Content-ID: <image-content-id> Content-Disposition: inline; filename="logo.gif" BASE64=ENCODED=IMAGE=DATA== --inner-boundary-- --outer-boundary-- - it looks like Content-Disposition: inline; is on every content declaration, i don't know if this matters - in order to have proper inline html image content it looks like both the file and the content it's being included in is required to be part of Content-Type: multipart/related; (http://tools.ietf.org/html/rfc2387) symptoms as tested: Mozilla Firefox - displays the attached files, does not display inline Apple Mail - displays the attached files then the content of the email (images show up in both) gmail - shows as having attachments, prompts to display images - images display fine hotmail - shows as having attachments, prompts to display images - images display fine ... all of this is also described in the forum thread. -- 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

17 years, 11 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2515) Abstraction of FacesMessages

by Pete Muir (JIRA)

Abstraction of FacesMessages ---------------------------- Key: JBSEAM-2515 URL: http://jira.jboss.com/jira/browse/JBSEAM-2515 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.1.0.GA Needed for support other view layers -- 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

17 years, 11 months

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2712) Document character encoding stuff

by Pete Muir (JIRA)

Document character encoding stuff ----------------------------------- Key: JBSEAM-2712 URL: http://jira.jboss.com/jira/browse/JBSEAM-2712 Project: JBoss Seam Issue Type: Task Reporter: Pete Muir -- 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

17 years, 11 months

2
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2723) Page fragment caching for plugin render

by Christian Bauer (JIRA)

Page fragment caching for plugin render --------------------------------------- Key: JBSEAM-2723 URL: http://jira.jboss.com/jira/browse/JBSEAM-2723 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Blocker The infrastructure for page fragment caching with EHCache is in place. We need to cache plugin-rendered HTML fragments with this strategy: - generate a unique cache key for each plugin, including the document ID and the macro hashcode (including position and parameters) - use a separate region for each plugin type, so that we can invalidate the cache for the whole region ("remove all cached fragments of a certain plugin no matter on what document it is rendered") - build cache regions on startup based on plugin metadata -- 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

17 years, 11 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2730) Jetty reference guide chapter with and without Jboss Embedded

by Jay Balunas (JIRA)

Jetty reference guide chapter with and without Jboss Embedded ------------------------------------------------------------- Key: JBSEAM-2730 URL: http://jira.jboss.com/jira/browse/JBSEAM-2730 Project: JBoss Seam Issue Type: Task Components: Documentation Issues, Platform interoperability Affects Versions: 2.1.0.A1, 2.0.1.GA Reporter: Jay Balunas Priority: Minor User requested reference guide chapter for Jetty with and without Jboss Embedded. Quote: "Jetty, with and without Jboss Embedded. Especially how to use mvn jetty:run to test stuff during development." Comment: http://in.relation.to/Bloggers/DeployingSeamToVariousApplicationServers#c... -- 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

17 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1531) Document pages.xsd and maybe other .xsds with xsd:documentation

by Michael Youngstrom (JIRA)

Document pages.xsd and maybe other .xsds with xsd:documentation --------------------------------------------------------------- Key: JBSEAM-1531 URL: http://jira.jboss.com/jira/browse/JBSEAM-1531 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.3.0.ALPHA Reporter: Michael Youngstrom The pages.xsd is fairly vast. It could benefit greatly by some <xsd:documentation> elements. XML editors such as Eclipse WTP will pick up these xsd:documentation elements and provide context help. -- 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

17 years, 11 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2785) Redesign PersistenceProvider to provide runtime detectetion of JPA impl in use

by Pete Muir (JIRA)

Redesign PersistenceProvider to provide runtime detectetion of JPA impl in use ------------------------------------------------------------------------------ Key: JBSEAM-2785 URL: http://jira.jboss.com/jira/browse/JBSEAM-2785 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.A1, 2.0.1.GA Reporter: Pete Muir Assigned To: Pete Muir Priority: Blocker Fix For: 2.1.0.BETA1 -- 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

17 years, 11 months

4
27
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2798) Integration Tests returns different component instances when accessing it in different ways

by Lars Huber (JIRA)

Integration Tests returns different component instances when accessing it in different ways ------------------------------------------------------------------------------------------- Key: JBSEAM-2798 URL: http://jira.jboss.com/jira/browse/JBSEAM-2798 Project: JBoss Seam Issue Type: Bug Components: Test Harness Affects Versions: 2.1.0.A1 Environment: Seam 2.1.0.A1 / WinXP / JDK 1.5.0_15 Reporter: Lars Huber When getting a component as reference the instance can be different than invoking a method over an EL expression. Example see JBoss Forum Reference below -- 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

17 years, 11 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2591) page actions fail under load testing

by Samuel Mendenhall (JIRA)

page actions fail under load testing ------------------------------------ Key: JBSEAM-2591 URL: http://jira.jboss.com/jira/browse/JBSEAM-2591 Project: JBoss Seam Issue Type: Bug Reporter: Samuel Mendenhall Priority: Critical Page actions fail to be invoked when load testing multiple requests simultaneously. Pages actions do correctly get processed when those requests are given an interval between executions, thus not concurrent. Code for reproduction: <page view-id="/home.xhtml" login-required="false"> <action execute="#{someComponent.someMethod}"/> </page> @Name("someComponent") public class SomeComponent { @Logger private Log log; @In FacesMessages facesMessages; public void someMethod() { log.info("someComponent:someMethod invoked at " + Calendar.getInstance().getTime()); facesMessages.add("someComponent:someMethod invoked at " + Calendar.getInstance().getTime()); } } There is on average of between 1-3 failed actions per 20 concurrent requests from initial analysis. The failed action presents absolutely no exception, the method is just not called, no log message in the console, and no FacesMessage added. jMeter script and screens attached. -- 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

17 years, 11 months

3
10
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues March 2008