February 2008 - seam-issues - Jboss List Archives

[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

16 years, 10 months

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

16 years, 10 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2695) Field triggerName of QuartzTriggerHandle should be public

by Vassilis Petropoulos (JIRA)

Field triggerName of QuartzTriggerHandle should be public --------------------------------------------------------- Key: JBSEAM-2695 URL: http://jira.jboss.com/jira/browse/JBSEAM-2695 Project: JBoss Seam Issue Type: Feature Request Components: Async Affects Versions: 2.0.0.GA Environment: win xp, jboss 4.2.2, jdk 1.5 Reporter: Vassilis Petropoulos QuartzTriggerHandle declares triggerName as private field. This field is the 'bridge' for methods on org.quartz.Scheduler. Suppose that a new QuartzTriggerHandle created and persisted to db. As long as triggerName is hidden there's no way to find extra info about QuartzTriggerHandle, for example getFireTimeAfter. It also affects the way QuartzTriggerHandle can be persisted, meaning that just triggerName should be enough instead of an entire serializable Lob. -- 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, 10 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-270) Annotations @DataModelSelection and @DataModelSelectionIndex can't be used in one component together

by Eirik Rosvold Larsen (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-270?page=comments#action_12400805 ] Eirik Rosvold Larsen commented on JBSEAM-270: --------------------------------------------- We have the same problem in our current project (SEAM-2.1.0.A1). Any progress on this? > Annotations @DataModelSelection and @DataModelSelectionIndex can't be used in one component together > ---------------------------------------------------------------------------------------------------- > > Key: JBSEAM-270 > URL: http://jira.jboss.com/jira/browse/JBSEAM-270 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF Integration > Affects Versions: 1.0 > Environment: WinXP Professional > JBoss AS 4.0.4.GA (ejb3.deployer libs replaced by EJB3 RC8 libs) > myFaces Core 1.1.3 > Tomahawk 1.1.3 > Facelets (as in Seam 1.0.0.GA) > JDK1.5.0_06 > Reporter: Jens Weintraut > Priority: Minor > > A seam component can't use both annotations @DataModelSelection and @DataModelSelectionIndex at once. If both are used deployment shows this error message: > java.lang.IllegalStateException: Multiple @DataModelSelection fields for: messageList > at org.jboss.seam.Component.initMembers(Component.java:533) > at org.jboss.seam.Component.<init>(Component.java:199) > at org.jboss.seam.Component.<init>(Component.java:159) > at org.jboss.seam.Component.<init>(Component.java:154) > at org.jboss.seam.Component.<init>(Component.java:149) > at org.jboss.seam.init.Initialization.addComponent(Initialization.java:381) > at org.jboss.seam.init.Initialization.addComponents(Initialization.java:343) > at org.jboss.seam.init.Initialization.init(Initialization.java:195) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:32) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3729) > ... -- 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, 10 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2687) Reset Password feature does not activate accounts

by Christian Bauer (JIRA)

Reset Password feature does not activate accounts ------------------------------------------------- Key: JBSEAM-2687 URL: http://jira.jboss.com/jira/browse/JBSEAM-2687 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Users are trying to use the Reset Password feature to resend an activation e-mail. This doesn't work, inactive accounts can't reset their password. The bug is that the UI doesn't show that, in fact, the password of an inactive account is actually reset properly, but the account is still not activated. We have two choices here: a) Do not allow users to reset the password of an inactive account, period. This means we can continue using the 'ACTIVE' flag as an administrative tool for banning users after abuse. Required change is a check in the UserPasswordReset action with an appropriate message when the user tries to reset an inactive account. b) Do allow users to reset the password of an inactive account (like we already do) but also activate the account on password reset, if it was inactive. This would make the 'ACTIVE' flag useless for administrative purposes but give us a "resend activation e-mail" feature that many users already expect behind a "reset password" function. -- 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, 10 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Deleted: (JBSEAM-2686) NPE

by Christian Bauer (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-2686?page=all ] Christian Bauer deleted JBSEAM-2686: ------------------------------------ > NPE > --- > > Key: JBSEAM-2686 > URL: http://jira.jboss.com/jira/browse/JBSEAM-2686 > Project: JBoss Seam > Issue Type: Bug > Reporter: toni > 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

16 years, 10 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2686) NPE in ManagedEntityIdentityInterceptor

by toni (JIRA)

NPE in ManagedEntityIdentityInterceptor --------------------------------------- Key: JBSEAM-2686 URL: http://jira.jboss.com/jira/browse/JBSEAM-2686 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.GA Environment: SUN JDK 1.5_14,JBoss 4.2.2 GA, Linux 2.6.23.1 Reporter: toni Priority: Blocker To reproduce: 1. Download http://213.239.213.83/test-seam2.tgz 2. Extract to /tmp/ and move to /tmp/calc/ 3. Create symlink /opt/jboss which points to JBoss 3.2.2 4. Execute Ant -> Webapplication is deployed 5. Open browser and call http://localhost:8080/calc/test.jsp You will get a NPE in the ManagedEntityIdentityInterceptor The application is very simple and runs under seam 1.2.1 To reproduce (alternative): 1. Download http://213.239.213.83/calc.ear.tgz 2. Extract to deploy directory of JBoss 3.2.2 3. Open browser and call http://localhost:8080/calc/test.jsp -- 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, 10 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2685) s:link view should work with relative paths

by Reind D (JIRA)

s:link view should work with relative paths ------------------------------------------- Key: JBSEAM-2685 URL: http://jira.jboss.com/jira/browse/JBSEAM-2685 Project: JBoss Seam Issue Type: Feature Request Reporter: Reind D It would be convenient if <s:link view="index.seam"/> worked. Currently the value of the "view" attribute must begin with a "/". Sometimes it's more convenient to use relative paths. For example, I would like to be able to use a template like: <ui:insert name="nav"> <s:link view="index.xhtml" value="Index"/> </ui:insert> Most cases the default "nav" is fine and this makes template client pages more clean. I can't do that though because I must pass the full viewid including the current directory (which changes). -- 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, 10 months

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

16 years, 10 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2671) Content length for new documents/comments is not checked properly

by Christian Bauer (JIRA)

Content length for new documents/comments is not checked properly ----------------------------------------------------------------- Key: JBSEAM-2671 URL: http://jira.jboss.com/jira/browse/JBSEAM-2671 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Critical Content length is only checked if users type into the textarea and on persist() (with an uncatched Hibernate InvalidStateException). However, if users paste much text into the textarea, the text preview shows a negative number of characters left, and persist() fails with an exception. -- 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, 10 months

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