July 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1471) @Child annotation for GWT

by Gavin King (JIRA)

@Child annotation for GWT ------------------------- Key: JBSEAM-1471 URL: http://jira.jboss.com/jira/browse/JBSEAM-1471 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Reporter: Gavin King Assigned To: Shane Bryzak The EntryPoint class is ugly boilerplate. You should be able to annotate your GWT class with @Child("theId") and it will be automagically added in when the module loads. -- 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, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1741) Seam Text links render incorrectly when no text provided

by Shane Bryzak (JIRA)

Seam Text links render incorrectly when no text provided -------------------------------------------------------- Key: JBSEAM-1741 URL: http://jira.jboss.com/jira/browse/JBSEAM-1741 Project: JBoss Seam Issue Type: Bug Reporter: Shane Bryzak -- 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, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1633) Mock Log

by Bieth Bruno (JIRA)

Mock Log -------- Key: JBSEAM-1633 URL: http://jira.jboss.com/jira/browse/JBSEAM-1633 Project: JBoss Seam Issue Type: Feature Request Reporter: Bieth Bruno Priority: Minor I would like to unit test a Seam SFSB which uses an injected logger. I didn't find any MockLog so I use the logging factory like that : Code: setField( editor, "log", Logging.getLog( "test" ) ); It solves the NullPointerException and the test are working fine but when logging, the Interpolator try to access the context which doesnt exist and throws an IllegalStateException ... It may be useful to have a mockLog method in the SeamTest class which look for a @Logger annotation and inject a MockLog. The MockLog will basically print any log on the console. -- 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, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1322) MutlipartRequest parser occasionally throws ArrayIndexOutOfBoundsException

by ROB b (JIRA)

MutlipartRequest parser occasionally throws ArrayIndexOutOfBoundsException -------------------------------------------------------------------------- Key: JBSEAM-1322 URL: http://jira.jboss.com/jira/browse/JBSEAM-1322 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA, 1.2.0.GA Environment: Windows Vista, Java 1.6u1, JBoss Seam 1.2.1, JBoss AS 4.0.5.GA Reporter: ROB b During an upload, the MultipartRequest checkSequence function does not to proper boundary checking on function parameters. It will occasionally (rarely actually) throw an ArrayIndexOutOfBoundsException at the high end due to the +1 offset when accessing the data array. I'm not actually sure why this +1 is there and was wondering if somehow it was a mistake. This class is a little hard to follow, so I'm not sure how everything works, but the function description seems to indicate that it is checking for the end of a byte array at a specific location which is 0-indexed, but the +1 would seem to indicate otherwise. The following exception gets thrown: java.lang.ArrayIndexOutOfBoundsException: 2048 at org.jboss.seam.web.MultipartRequest.checkSequence(MultipartRequest.java:466) at org.jboss.seam.web.MultipartRequest.parseRequest(MultipartRequest.java:333) at org.jboss.seam.web.MultipartRequest.getParam(MultipartRequest.java:507) at org.jboss.seam.web.MultipartRequest.getParameter(MultipartRequest.java:558) at org.apache.myfaces.context.servlet.RequestParameterMap.getAttribute(RequestParameterMap.java:39) at org.apache.myfaces.context.servlet.AbstractAttributeMap.get(AbstractAttributeMap.java:87) at com.sun.facelets.tag.ui.UIDebug.debugRequest(UIDebug.java:119) at com.sun.facelets.FaceletViewHandler.restoreView(FaceletViewHandler.java:305) at org.ajax4jsf.framework.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:116) at org.ajax4jsf.framework.ajax.AjaxViewHandler.restoreView(AjaxViewHandler.java:147) at org.apache.myfaces.lifecycle.LifecycleImpl.restoreView(LifecycleImpl.java:141) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:66) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:137) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:74) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96) at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Unknown Source) -- 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, 2 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1545) Define a means to provide alternate implementations of interceptors.

by Chris Rudd (JIRA)

Define a means to provide alternate implementations of interceptors. -------------------------------------------------------------------- Key: JBSEAM-1545 URL: http://jira.jboss.com/jira/browse/JBSEAM-1545 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.3.0.ALPHA Reporter: Chris Rudd Priority: Minor It would be nice if interceptors could be replaced / extened by defining a replacement interceptor to use instead of a stock one. This would allow end user customization of some of the Seam functionality that must occur in the interceptors themselves. ( JBSEAM-1544 is one example where this could be used to extend the SecurityInterceptor to provide additional functionality not currently present. ) -- 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, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1145) "javax.persistence.TransactionRequiredException: no transaction is in progress" thrown during flush of a transient entity in a @Transactional POJO

by Alex Savitsky (JIRA)

"javax.persistence.TransactionRequiredException: no transaction is in progress" thrown during flush of a transient entity in a @Transactional POJO -------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1145 URL: http://jira.jboss.com/jira/browse/JBSEAM-1145 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Environment: Tomcat + Microcontainer (has also been tried on Tomcat + JOTM, Tomcat + Atomikos, Tomcat + JBoss Transactions, all with the same result) Seam-managed Tx and PC, long-running conversations with manual flush Reporter: Alex Savitsky When persisting a transient entity during manual flush, an exception "javax.persistence.TransactionRequiredException: no transaction is in progress" is thrown, unless getEntityManager().joinTransaction() is executed prior to flush() - despite declaring the POJO as @Transactional and using Seam-managed transactions and persistence contexts. When persisting a managed entity, however, no exceptions are thrown and update completes normally. -- 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, 2 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1034) Usage of jBPM core:process-definitions needs clarification

by Arjan van Bentem (JIRA)

Usage of jBPM core:process-definitions needs clarification ---------------------------------------------------------- Key: JBSEAM-1034 URL: http://jira.jboss.com/jira/browse/JBSEAM-1034 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 1.2.0.GA Environment: All Reporter: Arjan van Bentem Priority: Minor The Seam documentation for "21.6. Configuring jBPM in Seam" describes how to add jBPM process definitions to components.xml: <core:jbpm> <core:pageflow-definitions> <value>createDocument.jpdl.xml</value> <value>editDocument.jpdl.xml</value> <value>approveDocument.jpdl.xml</value> </core:pageflow-definitions> <core:process-definitions> <value>documentLifecycle.jpdl.xml</value> </core:process-definitions> </core:jbpm> Nice, but as a side-effect a new copy is inserted into the database each time JBoss AS is started, even if the deployed EAR has not changed. This, of course, can only be noticed if in the example hibernate.cfg.xml from the DVD Store example the line <property name="hbm2ddl.auto">create-drop</property> is changed into <property name="hbm2ddl.auto">update</property> Apparently using <core:pageflow-definitions> is considered to be a developers tool: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=98430 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=90206 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103819 I think this needs some clarification in the documentation, but unfortunately (right now) I would not know what is the preferred way to deploy processes in Seam on a production machine. The third topic might include some ideas from others on that. Arjan. -- 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, 2 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-652) Allow use of EHCache with <s:cache/>

by Gavin King (JIRA)

Allow use of EHCache with <s:cache/> ------------------------------------ Key: JBSEAM-652 URL: http://jira.jboss.com/jira/browse/JBSEAM-652 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Priority: Minor -- 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, 2 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1692) Rome tag library

by Gavin King (JIRA)

Rome tag library ---------------- Key: JBSEAM-1692 URL: http://jira.jboss.com/jira/browse/JBSEAM-1692 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King The wiki example renders Atom via the Rome library. We should wrap it in JSF tags. -- 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, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-650) <s:formattedText value="#{post.body}" highlight="#{word}"/>

by Gavin King (JIRA)

<s:formattedText value="#{post.body}" highlight="#{word}"/> ----------------------------------------------------------- Key: JBSEAM-650 URL: http://jira.jboss.com/jira/browse/JBSEAM-650 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1.5.GA Seam needs to support wikitext ootb. -- 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, 2 months

5
11
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 July 2007