November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2129) Verify JBossTools compatibility

by Norman Richards (JIRA)

Verify JBossTools compatibility ------------------------------- Key: JBSEAM-2129 URL: http://jira.jboss.com/jira/browse/JBSEAM-2129 Project: JBoss Seam Issue Type: Task Reporter: Norman Richards Fix For: 2.0.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

18 years, 4 months

3
24
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2149) update iText to version 2.0.6 before seam 2.0.0.GA release

by Xavier Le Vourch (JIRA)

update iText to version 2.0.6 before seam 2.0.0.GA release ---------------------------------------------------------- Key: JBSEAM-2149 URL: http://jira.jboss.com/jira/browse/JBSEAM-2149 Project: JBoss Seam Issue Type: Task Components: PDF Affects Versions: 2.0.0.CR2 Reporter: Xavier Le Vourch Priority: Minor The iText library should probably be updated to 2.0.6 before the release as there's been a number of bug fixes since 2.0.4, the current version packaged with seam. Xavier -- 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

18 years, 4 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1541) BPM enhancements for WS/mail

by Gavin King (JIRA)

BPM enhancements for WS/mail ---------------------------- Key: JBSEAM-1541 URL: http://jira.jboss.com/jira/browse/JBSEAM-1541 Project: JBoss Seam Issue Type: Feature Request Components: BPM Reporter: Gavin King Fix For: 1.3.0.GA A couple of things that would make using jBPM with services much nicer: * possibility to map conversation id == process id and have a co-extensive conversation and process scope * auto-end conversation when the current process completes Perhaps its better to model this as a persistent SERVICE_CONVERSATION context, as suggested in another JIRA issue -- 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

18 years, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2000) add excel file type to DocType enum

by Dan Allen (JIRA)

add excel file type to DocType enum ----------------------------------- Key: JBSEAM-2000 URL: http://jira.jboss.com/jira/browse/JBSEAM-2000 Project: JBoss Seam Issue Type: Feature Request Components: PDF Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Priority: Minor The document store facility (org.jboss.seam.pdf.DocumentStore) is an excellent reuse library for those who want to push down files in their Seam-based application (outside of just using the PDF tags). However, the module has one major limitation. The file types are stored in an enum and thus cannot ever be changed (enums cannot be extended or overridden). Unfortunately this renders the library completely useless if you are not using one of the 3 built-in types (PDF, RTF, HTML). Since Excel downloads are so popular in business applications, it makes sense that even though Seam doesn't export excel, the file type could be added to allow those using Seam-based applications to take advantage of this excellent document storage design. I have included a patch, but the line is simply: EXCEL("xls", "application/vnd.ms-excel") -- 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

18 years, 4 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2043) registration example throws MethodNotFoundException

by Norman Richards (JIRA)

registration example throws MethodNotFoundException --------------------------------------------------- Key: JBSEAM-2043 URL: http://jira.jboss.com/jira/browse/JBSEAM-2043 Project: JBoss Seam Issue Type: Bug Reporter: Norman Richards Priority: Minor Fix For: 2.0.1.GA Pressing the register button without entering data logs the following exception. 10:32:45,680 INFO [RegisterAction] Registered new user foobar 10:32:50,557 ERROR [SeamPhaseListener] uncaught exception javax.el.MethodNotFoundException: Method not found: RegisterAction.invalid() at org.jboss.el.util.ReflectionUtil.getMethod(ReflectionUtil.java:251) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:340) at org.jboss.el.parser.AstPropertySuffix.invoke(AstPropertySuffix.java:58) at org.jboss.el.parser.AstValue.invoke(AstValue.java:96) at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at org.jboss.seam.core.Expressions$2.invoke(Expressions.java:174) at org.jboss.seam.navigation.Page.preRender(Page.java:264) at org.jboss.seam.navigation.Pages.preRender(Pages.java:309) at org.jboss.seam.jsf.SeamPhaseListener.preRenderPage(SeamPhaseListener.java:544) at org.jboss.seam.jsf.SeamPhaseListener.beforeRenderResponse(SeamPhaseListener.java:455) at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:146) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:116) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:613) 10:32:50,558 ERROR [SeamPhaseListener] swallowing exception javax.el.MethodNotFoundException: Method not found: RegisterAction.invalid() at org.jboss.el.util.ReflectionUtil.getMethod(ReflectionUtil.java:251) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:340) at org.jboss.el.parser.AstPropertySuffix.invoke(AstPropertySuffix.java:58) at org.jboss.el.parser.AstValue.invoke(AstValue.java:96) at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at org.jboss.seam.core.Expressions$2.invoke(Expressions.java:174) at org.jboss.seam.navigation.Page.preRender(Page.java:264) at org.jboss.seam.navigation.Pages.preRender(Pages.java:309) at org.jboss.seam.jsf.SeamPhaseListener.preRenderPage(SeamPhaseListener.java:544) at org.jboss.seam.jsf.SeamPhaseListener.beforeRenderResponse(SeamPhaseListener.java:455) at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:146) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:116) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:613) It would probably be helpful to use better validation error reporting on the page too. -- 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

18 years, 4 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2318) add revoke() to PermissionCheck

by Dan Allen (JIRA)

add revoke() to PermissionCheck ------------------------------- Key: JBSEAM-2318 URL: http://jira.jboss.com/jira/browse/JBSEAM-2318 Project: JBoss Seam Issue Type: Feature Request Components: Security Affects Versions: 2.0.0.GA Reporter: Dan Allen Fix For: 2.0.1.GA Attachments: JBSEAM-2318-v1.txt A LOT of the power of using a rules engine is stripped by not allowing a toggle of the grant flag on PermissionCheck. One of the main benefits of rules is to be able to apply a general case and then apply a more specific case. If you grant() in the general case, the specific case is worthless. However, it would make sense if the specific case could access the revoke() call. -- 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

18 years, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2303) Documentation on how authenticate method might be used by seam.

by Tobias Hill (JIRA)

Documentation on how authenticate method might be used by seam. --------------------------------------------------------------- Key: JBSEAM-2303 URL: http://jira.jboss.com/jira/browse/JBSEAM-2303 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Environment: n/a Reporter: Tobias Hill See http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108008#4108008 The fact that authenticate might be called more than one time by seam (and hence ought to be side-effect-free) would be good to have in the documentation. There are some postings in the forums about observed strange behavior due to programmers not being aware of this. -- 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

18 years, 4 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2098) Documentation of explicit conversation id

by Tomas Cerny (JIRA)

Documentation of explicit conversation id ----------------------------------------- Key: JBSEAM-2098 URL: http://jira.jboss.com/jira/browse/JBSEAM-2098 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 2.0.0.CR2 Environment: -- Reporter: Tomas Cerny Documentation of explicit conversation id describes usage of annotation parameter @Begin(id="hotel#{hotel.id}") but API deprecates it. 6.6. Using an "explicit" conversation id @Begin(id="hotel#{hotel.id}") public String editHotel() { ... } in API Gavin notes to use pages.xml for explicit conversations id, but I am starting conversation on method and my pageflow starts with start-state is that also deprecated? is that in documentation? -- 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

18 years, 4 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-971) Conversations with business ids

by Gavin King (JIRA)

Conversations with business ids ------------------------------- Key: JBSEAM-971 URL: http://jira.jboss.com/jira/browse/JBSEAM-971 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Shane Bryzak Priority: Critical By defining a <conversation/> in pages.xml, pages can have the conversation propagated via a meaningful (restful) request parameter. By the way, we can make conversationIsLongRunning stuff disabled by default, unless its name is explicitly defined in components.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

18 years, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2056) Add a way to specify the type of Richfaces HTML parser for a particular view in components.xml

by Adrian Mitev (JIRA)

Add a way to specify the type of Richfaces HTML parser for a particular view in components.xml ---------------------------------------------------------------------------------------------- Key: JBSEAM-2056 URL: http://jira.jboss.com/jira/browse/JBSEAM-2056 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.CR2 Reporter: Adrian Mitev Priority: Minor Here is a sample code for this <context-param> <param-name>org.ajax4jsf.xmlparser.ORDER</param-name> <param-value>TIDY,NEKO,NONE</param-value> </context-param> <context-param> <param-name>org.ajax4jsf.xmlparser.TIDY</param-name> <param-value>/pages/repeater.xhtml,/pages/tabs.xhtml</param-value> </context-param> -- 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

18 years, 4 months

2
4
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 November 2007