February 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2283) Seam-gen library usage

by Pete Muir (JIRA)

Seam-gen library usage ---------------------- Key: JBSEAM-2283 URL: http://jira.jboss.com/jira/browse/JBSEAM-2283 Project: JBoss Seam Issue Type: Task Components: Tools Affects Versions: 2.0.0.GA Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.1.GA Seam-gen duplicates a few libraries from /lib - dates from when Seam shipped with a very old hibernate and -all.jars -- 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

16 years, 8 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2090) Improve handling of h:selectManyXXX updating the mode with a new list

by Pete Muir (JIRA)

Improve handling of h:selectManyXXX updating the mode with a new list --------------------------------------------------------------------- Key: JBSEAM-2090 URL: http://jira.jboss.com/jira/browse/JBSEAM-2090 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.x Currently JSF sets a new list on the model which causes a load of deletes and inserts. Perhaps we can handle this better (dunno how) -- 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

16 years, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2608) Natural conversation for wildcard view-id

by Jacob Orshalick (JIRA)

Natural conversation for wildcard view-id ----------------------------------------- Key: JBSEAM-2608 URL: http://jira.jboss.com/jira/browse/JBSEAM-2608 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.1.GA Reporter: Jacob Orshalick Priority: Optional When a natural conversation spans a number of pages you currently have to explicitly state the named conversation for each view-id. It would be nice to simply specify the natural conversation for a wildcard view-id. For example, if my conversation spans the following: Code: <conversation name="Checkout" parameter-name="cart" parameter-value="#{cart.cartId}"/> <page view-id="/checkout/checkout1.jsp" conversation="Checkout" /> <page view-id="/checkout/checkout2.jsp" conversation="Checkout" /> <page view-id="/checkout/checkout3.jsp" conversation="Checkout" /> <page view-id="/checkout/confirm.jsp" conversation="Checkout" /> Instead I would prefer to use: Code: <page view-id="/checkout/*" conversation="Checkout" /> This is also especially useful for free navigation situations within the conversation that do not have navigation rules (i.e. the conversation spans many pages but can access any page at any time) to avoid specifying each view-id in pages.xml. -- 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

16 years, 8 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2525) Split out Spring and microcontainer support into separate jars

by Pete Muir (JIRA)

Split out Spring and microcontainer support into separate jars -------------------------------------------------------------- Key: JBSEAM-2525 URL: http://jira.jboss.com/jira/browse/JBSEAM-2525 Project: JBoss Seam Issue Type: Task Components: Build Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.1.0.GA -- 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

16 years, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2422) Rendering Email from a servlet

by Tim Timson (JIRA)

Rendering Email from a servlet ------------------------------ Key: JBSEAM-2422 URL: http://jira.jboss.com/jira/browse/JBSEAM-2422 Project: JBoss Seam Issue Type: Bug Components: Mail Environment: Windows Glassfish server Reporter: Tim Timson Assigned To: Pete Muir Pete Muir asked me to created this issue when I posted this forum entry: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=126443 -- 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

16 years, 8 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1266) Mathematical captcha & Email obfuscator

by Stephan Kleine (JIRA)

Mathematical captcha & Email obfuscator --------------------------------------- Key: JBSEAM-1266 URL: http://jira.jboss.com/jira/browse/JBSEAM-1266 Project: JBoss Seam Issue Type: Patch Affects Versions: 1.3.0.BETA1 Environment: Tested with Seam CVS on JBoss AS 4.2.0CR2 Reporter: Stephan Kleine Hello, I would like to donate some stuff to seam: 1. A component that converts strings into (hexa)decimal html entities. 2. A tag to use this obfuscator (mainly a shortcut for h:outputText escape="false" ...). 3. A mathematical captcha that asks for the solutions of simple equations (like they use at jroller). The equation can be obuscated with the tag described at 2.. 4. A tag to obfuscate email addresses (see [url]http://www.seowebsitepromotion.com/obfuscate_email.asp[/url] for more details). Would be great if you include it in 1.3 ;) Regards Stephan -- 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

16 years, 8 months

4
12
0 / 0

[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

16 years, 8 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

16 years, 8 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

16 years, 8 months

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

16 years, 8 months

4
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2008