December 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3159) Debug/development mode control

by Pete Muir (JIRA)

Debug/development mode control ------------------------------ Key: JBSEAM-3159 URL: http://jira.jboss.com/jira/browse/JBSEAM-3159 Project: Seam Issue Type: Task Components: Tools Reporter: Pete Muir Priority: Critical Fix For: 2.1.0.BETA2 Currently we have a very overloaded system which is hard to use: 1) debug flag is used to control parsing of hot-deploy (/dev) which is odd 2) to view the debug page at all you must both include jboss-seam-debug.jar and enable debug mode in components.xml. Further, if you do this, then the debug page handler is installed, which screws with the exception handling. I propose that by simply including jboss-seam-debug.jar you get 1) hot deployment enabled 2) use of the debug page by calling /debug.seam BUT not as a redirect off the exception handler and, further, by <exception:exceptions enable-debug-page="true" /> (better ideas for attribute name?) you can automagically redirect to the debug page when an exception occurs. The default for this is false, and this should be set in seam-gen (the seam-gen app should include a link to debug.seam in perhaps its footer) -- 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

15 years

4
6
0 / 0

[JBoss JIRA] Created: (JBSEAM-4511) Allow superscript in p:font

by Robert Morse (JIRA)

Allow superscript in p:font ---------------------------- Key: JBSEAM-4511 URL: https://jira.jboss.org/jira/browse/JBSEAM-4511 Project: Seam Issue Type: Feature Request Components: PDF Affects Versions: 2.2.0.GA Reporter: Robert Morse Be nice to have a superscript option in p:font. Currently, there's no apparent way to superscript text like a copyright or trademark symbol. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-4510) PDF generation fails when added as attachment to mail if <p:document... isn't on first row

by Marcus Smedman (JIRA)

PDF generation fails when added as attachment to mail if <p:document... isn't on first row ------------------------------------------------------------------------------------------ Key: JBSEAM-4510 URL: https://jira.jboss.org/jira/browse/JBSEAM-4510 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.2.0.GA Reporter: Marcus Smedman Assignee: Pete Muir When using swedish characters (ISO-8859-1) 'åäö' in a pdf template I have to include <?xml version="1.0" encoding="iso-8859-1"?> to the template to make it work. org.jboss.seam.mail.ui.UIAttachment will only render a pdf/excel file correct if the first line/child in the (pdf/excel) xhtml template contains a pdf/excel tag. If I add a <?xml version="1.0" encoding="iso-8859-1"?> line at the top of my pdf template it will fail when added as an attachment, but it will be renderder correct to a pdf when not used as an attachment. <?xml version="1.0" encoding="iso-8859-1"?> <p:document xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:p="http://jboss.com/products/seam/pdf" type="PDF" pageSize="A4" title="test"> <p:paragraph>Test! åäö</p:paragraph> </p:document> Attaching patch to fix this problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-4507) Current conversation lost from page scope on intermediate AJAX request with conversationPropagation=none

by Thomas W (JIRA)

Current conversation lost from page scope on intermediate AJAX request with conversationPropagation=none -------------------------------------------------------------------------------------------------------- Key: JBSEAM-4507 URL: https://jira.jboss.org/jira/browse/JBSEAM-4507 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.1.1.GA Reporter: Thomas W The application uses RichFaces. There are modal dialogs that use conversation scoped beans and there are requests ("AJAX push") being processed in the background are not to participate in those dialog conversations (logically separate). I can get the desired temporary conversation by using <input type="hidden" name="conversationPropagation" value="none"/> on the page, but after one of these posts was processed, the original conversation will no longer be attached to the dialog that is active in parallel. That's because the conversation id is no longer retained in the page scope. The long running conversation is not terminated (expected) but becomes orphaned (not expected). I'm attaching the source code for extended version of FacesManager that produces the desired behavior. I think that this should be the default behavior, otherwise propagation mode "none" makes no sense in the context of an AJAX app. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
2
0 / 0

[JBoss JIRA] Moved: (JBSEAM-4504) Conversation are only for JSF: Please make then available for plain servlets and JSP

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-4504?page=com.atlassian.jira.pl... ] Pete Muir moved WELD-295 to JBSEAM-4504: ---------------------------------------- Project: Seam (was: Weld) Key: JBSEAM-4504 (was: WELD-295) Component/s: (was: Conversations) Affects Version/s: (was: 1.0.0.GA) > Conversation are only for JSF: Please make then available for plain servlets and JSP > ------------------------------------------------------------------------------------ > > Key: JBSEAM-4504 > URL: https://jira.jboss.org/jira/browse/JBSEAM-4504 > Project: Seam > Issue Type: Feature Request > Reporter: Francisco Jose Peredo Noguez > > Aacording to Weld the docs: > The conversation context is active during any JSF request. > and at the code of org.jboss.weld.servlet.ConversationPropagationFilter > One can read > FIXME This filter is specifically for JSF and should be repackaged or split up to support non-JSF environments. > All that indicates that conversations are only for JSF. Please make them available for plain servlets (and JSPs) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-4497) s:convertPojo key="<fieldName>" component

by deanhiller (JIRA)

s:convertPojo key="<fieldName>" component ----------------------------------------- Key: JBSEAM-4497 URL: https://jira.jboss.org/jira/browse/JBSEAM-4497 Project: Seam Issue Type: Feature Request Components: JSF Controls Affects Versions: 2.2.0.GA Reporter: deanhiller Priority: Minor It would be awesome if we could have an <s:convertPojo key="<unique field>"> component with a key attribute that identifies a unique key in the pojo to do translation with. ie. s:convertEntity uses the primary key of the entity but convertPojo could be used for entities that are not in the database yet if for instance the name was a unique. Also, it could just be used for pojos from a webservice or something for that matter. It could even throw a NonUniqueException if in the list of pojo's it finds two with the same exact key so people use it correctly and an exceptions is thrown when not used correctly so we know. Anyways, just thought this would be a nice feature add to an already pretty damn sweet toolbox called seam. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4247) Seam managed @Provider not registered

by Matthew Bowman (JIRA)

Seam managed @Provider not registered ------------------------------------- Key: JBSEAM-4247 URL: https://jira.jboss.org/jira/browse/JBSEAM-4247 Project: Seam Issue Type: Bug Components: WS Affects Versions: 2.1.2.GA Reporter: Matthew Bowman Example: @Name("serviceExceptionMapper") @Scope(ScopeType.APPLICATION) @Provider public class ServiceExceptionMapper implements ExceptionMapper<ServiceException> { public Resposne toResponse(ServiceException ex) { return Response.noContent().build(); } } This custom ExceptionMapper provider will not be registered with ResteasyProviderFactory. If I remove the @Name + @Scope annotations, the provider is registered. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state

by David Thompson (JIRA)

Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state -------------------------------------------------------------------------------------- Key: JBSEAM-4388 URL: https://jira.jboss.org/jira/browse/JBSEAM-4388 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot deploy. Reporter: David Thompson Priority: Blocker We currently write struts apps. One of the things we do is hot deploy these apps by setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when an app is deployed with "ant deploy", the session data can be stored out--app is torn down-- then when new app deploys the session data restores. If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the Conversation Context when the app is deployed, then JBoss throws an error trying to reload the component and no SESSION data is restored. For example, all logged in users (data stored in Identity or Credentials) do not restore so all users get the boot. This doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy to our production system, this causes problems for us. The ideal solution, would be to have the conversations to come back to life, but we could also live with the conversations not being reestablished--but we really need the other session data (such as login credentials) to live through the deploy. AFAIK, I have looked all over the web and read the seam reference as well as Seam In Action and can't find any information about how Conversations can persist over a session (such as a redeploy this way) or over a cluster. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
11
0 / 0

[JBoss JIRA] Created: (JBSEAM-4502) pages.xml expires attribute : invalid Expires HTTP header with french JVM default locale

by Gonzalez Adrian (JIRA)

pages.xml expires attribute : invalid Expires HTTP header with french JVM default locale ---------------------------------------------------------------------------------------- Key: JBSEAM-4502 URL: https://jira.jboss.org/jira/browse/JBSEAM-4502 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.1.0.SP1 Reporter: Gonzalez Adrian Hello, I'm using expires attribute in pages.xml : <page view-id="/js/global.jspx" expires="846000"> <header name="Cache-control" value="max-age=864000"/> </page> I'm running with a French OS (default locale french). When using firebug, I see the following HTTP header value : Expires sam., 19 déc. 2009 13:06:38 CET This syntax is invalid (http://www.ietf.org/rfc/rfc0822.txt - section 5.1. SYNTAX). Just changing the following line of code in Page.java) corrects the bug : Change : SimpleDateFormat format = new SimpleDateFormat(RFC_1123_DATE); With : SimpleDateFormat format = new SimpleDateFormat(RFC_1123_DATE, Locale.ENGLISH); And produces the expected output : Expires Sat, 19 Dec 2009 09:39:48 CET -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-4496) Seam 2 EAR project deployed on EAP5 - using RichFaces API in Seam EJB component causes java.lang.NoClassDefFoundError

by Tihomir Surdilovic (JIRA)

Seam 2 EAR project deployed on EAP5 - using RichFaces API in Seam EJB component causes java.lang.NoClassDefFoundError --------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4496 URL: https://jira.jboss.org/jira/browse/JBSEAM-4496 Project: Seam Issue Type: Bug Affects Versions: 2.2.0.GA, 2.1.2.GA Reporter: Tihomir Surdilovic When creating a Seam 2 EJB project and deploying it in EAP5, if a Seam EJB component uses the RichFaces API directly, for example to create a HtmlDropDownMenu programatically causes exception: Caused by: java.lang.NoClassDefFoundError: org/richfaces/component/html/HtmlDropDownMenu at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2427) at java.lang.Class.privateGetPublicMethods(Class.java:2547) at java.lang.Class.getMethods(Class.java:1410) at org.jboss.seam.Component.hasAnnotation(Component.java:1158) at org.jboss.seam.Component.<init>(Component.java:218) at org.jboss.seam.Component.<init>(Component.java:205) at org.jboss.seam.init.Initialization.addComponent(Initialization.java:1186) ... 73 more Caused by: java.lang.ClassNotFoundException: org.richfaces.component.html.HtmlDropDownMenu from BaseClassLoader@5c594008 at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:448) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) ... 81 more Same project works fine on EAP 4.3. Uploaded is a project created with JBDS 2.1 which illustrates issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2009