July 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1474) Add examples with use of Facelets source tags

by Mikhail Grushinskiy (JIRA)

Add examples with use of Facelets source tags --------------------------------------------- Key: JBSEAM-1474 URL: http://jira.jboss.com/jira/browse/JBSEAM-1474 Project: JBoss Seam Issue Type: Feature Request Components: Examples Affects Versions: 1.3.0.BETA1, 1.3.0.BETA2, 1.3.0.GA, 1.3.1.GA Reporter: Mikhail Grushinskiy Add examples with use of Facelets source tags. I think Facelets source tags is very useful feature which has to be demonstrated in examples provided with Seam -- 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, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1406) Create method to end/destroy other conversations

by Bruno E. Grossi (JIRA)

Create method to end/destroy other conversations ------------------------------------------------ Key: JBSEAM-1406 URL: http://jira.jboss.com/jira/browse/JBSEAM-1406 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Bruno E. Grossi In some situations we need to end/destroy other conversations different from the actual one. Manager has a private method Manager.destroyConversation(String conversationId, ContextAdaptor session) that can do it, but it private and requires a session ContextAdaptor. My suggestion to create a public method on Manager (or some other appropriate class) that receives an id the clean up that conversation. -- 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, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1394) Null @Out attributes for stateless bean before/after method invocations

by H K (JIRA)

Null @Out attributes for stateless bean before/after method invocations ----------------------------------------------------------------------- Key: JBSEAM-1394 URL: http://jira.jboss.com/jira/browse/JBSEAM-1394 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: H K Priority: Optional Adding the ability to null @Out attributes for stateless session beans before/after method invocations should eliminate the chances of sharing the @Out instance variables when the stateless bean is being reused by the EJB container. Perhaps the tricky part here might be dealing with exceptions thrown by the intercepted methods. A possible solution might be to null the @Out attributes not only after the invocation but also before the invocation. Of course, this should be done only for stateless session bean. -- 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, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1204) java.lang.StringIndexOutOfBoundsException: String index out of range: -1

by Petr Ferschmann (JIRA)

java.lang.StringIndexOutOfBoundsException: String index out of range: -1 ------------------------------------------------------------------------ Key: JBSEAM-1204 URL: http://jira.jboss.com/jira/browse/JBSEAM-1204 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 1.2.1.GA Environment: I am using Seam for other serlvets too (SeamFilter). Reporter: Petr Ferschmann Problem is that MockViewHandler expects that there is always . in URL (but in my case it is not). String index out of range: -1 RequestURI=/pes/userAccount/create/ Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1762) at java.lang.String.substring(String.java:1735) at org.jboss.seam.mock.MockViewHandler.getActionURL(MockViewHandler.java:41) at org.jboss.seam.core.Manager.redirect(Manager.java:1054) at org.jboss.seam.core.Redirect.execute(Redirect.java:137) at org.jboss.seam.exceptions.DebugPageHandler.handle(DebugPageHandler.java:29) at org.jboss.seam.core.Exceptions.handle(Exceptions.java:79) at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:91) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:73) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391) at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:268) at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126) at cz.softeu.rewriter.RewriterFilter.doFilter(RewriterFilter.java:173) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:146) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:285) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:751) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:500) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:329) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475) -- 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, 1 month

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-854) Explicit conversation id is lost when using nested conversation

by Yevgen Bushuyev (JIRA)

Explicit conversation id is lost when using nested conversation --------------------------------------------------------------- Key: JBSEAM-854 URL: http://jira.jboss.com/jira/browse/JBSEAM-854 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.6.GA Environment: Linux localhost 2.6.3-7mdk #1 Wed Mar 17 15:56:42 CET 2004 i686 unknown unknown GNU/Linux Reporter: Yevgen Bushuyev Each click on <s:link id="action" value="Act" action="#{somethingHome.beginAction}"/> @Begin(nested=true, id="action") public String beginAction() { } leads to creation of a new ConversationEntry, which means that explicit id is ignored. -- 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, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-672) Allow Query restrictions without value bindings

by Christian Bauer (JIRA)

Allow Query restrictions without value bindings ----------------------------------------------- Key: JBSEAM-672 URL: http://jira.jboss.com/jira/browse/JBSEAM-672 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 1.1.1.GA Reporter: Christian Bauer In framework/Query.java line 164: if (valueBinding==null) { throw new IllegalArgumentException("no value binding in restriction: " + restriction); } I want to have restrictions without value bindings, e.g. in my extended EntityQuery: public List<String> getRestrictions() { List<String> restrictions = new ArrayList<String>(); restrictions.add("parentNode is null"); return restrictions; } -- 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, 1 month

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1075) Documentation enhancement for injecting Logger (make clear when static is required)

by Arjan van Bentem (JIRA)

Documentation enhancement for injecting Logger (make clear when static is required) ----------------------------------------------------------------------------------- Key: JBSEAM-1075 URL: http://jira.jboss.com/jira/browse/JBSEAM-1075 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 1.2.0.GA Environment: All Reporter: Arjan van Bentem Priority: Optional The documentation of @Logger in "3.6 Logging" states at http://fisheye.jboss.com/browse/JBoss/jboss-seam/doc/reference/en/modules... It doesn't matter if you declare the log variable static or not—it will work either way. I think this should be enhanced to read, for example: It doesn't matter if you declare the log variable static or not—it will work either way, except for entity beans which needs the logger to be static. ...maybe followed by an example: @Entity @Name("member") @Table(uniqueConstraints = @UniqueConstraint(columnNames = "membername")) public class Member implements Serializable { @Logger private static Log log; : public void setMemberName(String memberName) { log.info("setting memberName"); this.memberName = memberName; } : } At least, that's what I've found; when not declaring it static it will not get injected or is lost (I'm not sure which), and thus would yield a NullPointerException upon usage. Likewise, "22.2. Annotations for bijection" at http://fisheye.jboss.com/browse/JBoss/jboss-seam/doc/reference/en/modules... now states Specifies that a component field is to be injected with an instance of org.jboss.seam.log.Log. ...but maybe this could be extended to read: Specifies that a component field is to be injected with an instance of org.jboss.seam.log.Log. Remember that for entity beans the actual variable needs to be declared static. Cheers, 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, 1 month

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1383) Add conversation propogation="clone" ability

by Michael Youngstrom (JIRA)

Add conversation propogation="clone" ability -------------------------------------------- Key: JBSEAM-1383 URL: http://jira.jboss.com/jira/browse/JBSEAM-1383 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Michael Youngstrom I think the ability to clone a conversation would be useful. Currently if I have an s:link and I do an "open in new window" on that link I now have 2 windows linked to the same conversation which may produce undesirable side effects to the user. So the idea is with s:link or other "GET" types of requests where the user might be inclined to do an "Open in new Window" type of operation we add the ability to clone the conversation when executed. If applied to an s:link the conversation would always be cloned when that link is executed. That way if the user did do an "Open in new window" each window would have 2 independent conversations. This would obviously have the side effect of an orphaned conversation if the user didn't do an "open in new window or tab" so the user would have to weigh the cost of creating orphaned conversations against maintaining the Conversation per window type of semantics this feature would provide. -- 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, 1 month

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1745) SpringTransaction fails with HibernateJpaDialect and FlushMode.MANUAL

by Darryl Smith (JIRA)

SpringTransaction fails with HibernateJpaDialect and FlushMode.MANUAL ---------------------------------------------------------------------- Key: JBSEAM-1745 URL: http://jira.jboss.com/jira/browse/JBSEAM-1745 Project: JBoss Seam Issue Type: Bug Components: Spring Reporter: Darryl Smith When using flushMode = MANUAL with org.springframework.orm.jpa.vendor.HibernateJpaDialect, the flushMode is changed to AUTO when beginning transaction SessionImpl.setFlushMode(FlushMode) line: 1286 HibernateSessionProxy.setFlushMode(FlushMode) line: 381 SeamHibernateJpaDialect(HibernateJpaDialect).beginTransaction(EntityManager, TransactionDefinition) line: 60 JpaTransactionManager.doBegin(Object, TransactionDefinition) line: 326 JpaTransactionManager(AbstractPlatformTransactionManager).getTransaction(TransactionDefinition) line: 350 SpringTransaction.begin() line: 74 Unless the transaction definition is set to readOnly spring will change the flushMode to manual HibernateJpaDialect:45 -------------------------------- public Object beginTransaction(EntityManager entityManager, TransactionDefinition definition) throws PersistenceException, SQLException, TransactionException { super.beginTransaction(entityManager, definition); Session session = getSession(entityManager); FlushMode flushMode = session.getFlushMode(); FlushMode previousFlushMode = null; if (definition.isReadOnly()) { // We should suppress flushing for a read-only transaction. session.setFlushMode(FlushMode.MANUAL); previousFlushMode = flushMode; } else { // We need AUTO or COMMIT for a non-read-only transaction. if (flushMode.lessThan(FlushMode.COMMIT)) { session.setFlushMode(FlushMode.AUTO); previousFlushMode = flushMode; } } return new SessionTransactionData(session, previousFlushMode); } Perhaps SpringTransaction should set should pass readOnly transaction def to Spring when the flushMode is manual. Current Workaround: use DefaultJpaDialect -- 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, 1 month

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-866) Ajax4JSF integration for Wiki

by Gavin King (JIRA)

Ajax4JSF integration for Wiki ----------------------------- Key: JBSEAM-866 URL: http://jira.jboss.com/jira/browse/JBSEAM-866 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Gavin King The following features should use Ajax4JSF instead of navigation or full page submits. * Preview panel should be dynamically rendered as user types in the edit box * Edit page and edit directory should use an ajax include instead of navigation * The operations in the edit directory box should use partial submit/render * Login should be implemented using a partial submit/render -- 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, 1 month

2
5
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