February 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2634) Implement <toc> plugin

by Christian Bauer (JIRA)

Implement <toc> plugin ---------------------- Key: JBSEAM-2634 URL: http://jira.jboss.com/jira/browse/JBSEAM-2634 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer E.g. to be used on the Knowledge Base overview page. Generates a clickable table of contents of (all? best rated?) articles. -- 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

[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

16 years, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2682) Getting the Seam Component Names that were configured via components.xml

by Srinivasan N. Raguraman (JIRA)

Getting the Seam Component Names that were configured via components.xml ------------------------------------------------------------------------ Key: JBSEAM-2682 URL: http://jira.jboss.com/jira/browse/JBSEAM-2682 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.1.GA Reporter: Srinivasan N. Raguraman Provide ability to get the component name on initialization, for the components configured via components.xml. Currently this works only if the name is provided through @Name annotation. -- 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-2582) Consistency

by Gavin King (JIRA)

Consistency ----------- Key: JBSEAM-2582 URL: http://jira.jboss.com/jira/browse/JBSEAM-2582 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Gavin King Assigned To: Christian Bauer Priority: Minor The UI should be more consistent in some places: * Dir browser uses a popup menu, but member list uses an edit button. Both should use popups. * Sometimes, "Close Workspace" is called "Exit Workspace". * The FAQ "New Question" screen uses a "Cancel" button instead of "Close Workspace". Personally, I would like it if *everything* had a "Cancel" (or "Done", or "Exit") button, since I find it a bit clumsy to navigate over to the LHS to close the editors. -- 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

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2603) commons-collections version is 2.1.1 when root.pom depends on 3.2

by Jay Balunas (JIRA)

commons-collections version is 2.1.1 when root.pom depends on 3.2 ----------------------------------------------------------------- Key: JBSEAM-2603 URL: http://jira.jboss.com/jira/browse/JBSEAM-2603 Project: JBoss Seam Issue Type: Bug Components: Build Affects Versions: 2.1.0.GA Reporter: Jay Balunas Something in the wicket build is downloading an older version of commons-collections 2.1.1, while in the Seam_2_0 branch it is using 3.2. I has searched through the poms, but I think that it is one of child dependencies of wicket's dependencies. Our root.pom.xml file states a dependency on commons-collections-3.2. The symptom I'm seeing is when attempting to deploy to websphere I am getting ClassNoFoundExceptions. Not sure if it effects other deployments. Below is the snippet from the build where it is downloading 2.1.1 during wicket build after I deleted original from repository. initwicket: [echo] Build JBoss Seam wicket 2.1 [mkdir] Created dir: /rhdev/projects/jboss-seam/svn-head/jboss-seam-svn/classes/wicketclasses [copy] Copying 1 file to /rhdev/projects/jboss-seam/svn-head/jboss-seam-svn/classes/wicketclasses [artifact:dependencies] Downloading: commons-collections/commons-collections/2.1.1/commons-collections-2.1.1.pom from repository.jboss.org [artifact:dependencies] Transferring 0K from repository.jboss.org [artifact:dependencies] Downloading: commons-collections/commons-collections/2.1.1/commons-collections-2.1.1.jar from repository.jboss.org [artifact:dependencies] Transferring 171K from repository.jboss.org [artifact:dependencies] [WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for commons-collections/commons-collections/2.1.1/commons-collections-2.1.1.jar - IGNORING compilewicket: [javac] Compiling 20 source files to /rhdev/projects/jboss-seam/svn-head/jboss-seam-svn/classes/wicketclasses [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. -- 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
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2665) Seam 2.0.1 incompatibility with Trinidad

by Andrew (JIRA)

Seam 2.0.1 incompatibility with Trinidad ---------------------------------------- Key: JBSEAM-2665 URL: http://jira.jboss.com/jira/browse/JBSEAM-2665 Project: JBoss Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.0.1.GA Environment: Trinidad 1.2.6, MyFaces 1.2.2, Facelets 1.1.14, Seam 2.0.1.GA Reporter: Andrew Priority: Critical See forum reference please Here is the stack (pretty clear cause from the error message): Caused by: java.lang.ClassCastException: org.apache.myfaces.trinidad.component.core.CoreForm cannot be cast to javax.faces.component.UIForm at org.jboss.seam.ui.util.cdk.RendererUtils.getForm(RendererUtils.java:48) at org.jboss.seam.ui.renderkit.CommandButtonParameterRendererBase.doEncodeEnd(CommandButtonParameterRendererBase.java:38) at org.jboss.seam.ui.util.cdk.RendererBase.encodeEnd(RendererBase.java:104) at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:556) -- 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-2679) Forum link on front page of Seam jira still points to the old forums

by Jay Balunas (JIRA)

Forum link on front page of Seam jira still points to the old forums -------------------------------------------------------------------- Key: JBSEAM-2679 URL: http://jira.jboss.com/jira/browse/JBSEAM-2679 Project: JBoss Seam Issue Type: Bug Reporter: Jay Balunas Priority: Minor Click on the browse prroject in jira and there is a link to the old forums for users to ask questions. Should change it to seamframeowrk.org site. -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2673) Comments created by non-loggedin users are pushed to feeds without users name

by Christian Bauer (JIRA)

Comments created by non-loggedin users are pushed to feeds without users name ----------------------------------------------------------------------------- Key: JBSEAM-2673 URL: http://jira.jboss.com/jira/browse/JBSEAM-2673 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2672) @ValidateProperty annotation for action components

by Christian Bauer (JIRA)

@ValidateProperty annotation for action components -------------------------------------------------- Key: JBSEAM-2672 URL: http://jira.jboss.com/jira/browse/JBSEAM-2672 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Christian Bauer Priority: Optional I have an entity class: public class Document { @Length(min/max) String content; } This property is not mapped directly with a value binding to a GUI textarea, it has to be passed through the form controller/action (where I parse the content for magic stuff): public class DocumentHome { String formContent; persist() { instance.setContent(formContent); } } This effectively disables any validation of the @Length as only Hibernate Validator will throw an InvalidStateException on persist(). To get the message into the form, I'd have to either do manual validation calls in DocumentHome.persist() before copying the form value onto the instance, or add another @Length annotation to the form-bound property of the controller: public class DocumentHome { @Length(min/max) String formContent; persist() { instance.setContent(formContent); } } This means I need to duplicate the validation rules if one of my entity properties is not directly mapped to a form but through some intermediate processing in a controller. I'd like to connect the two, like so: public class DocumentHome { @ValidateProperty("some.syntax.that.declares.the.Document.content.property") String formContent; persist() { instance.setContent(formContent); } } I'm marking this as optional because I'm not sure this is a generic problem and that we need a generic solution. OTOH, duplicating and manual coding of validation doesn't seem to be the right approach either. -- 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-2670) uploading a file over 1048576 bytes not allowed on sfwk.org

by Keith Naas (JIRA)

uploading a file over 1048576 bytes not allowed on sfwk.org ----------------------------------------------------------- Key: JBSEAM-2670 URL: http://jira.jboss.com/jira/browse/JBSEAM-2670 Project: JBoss Seam Issue Type: Bug Components: Wiki Affects Versions: 2.1.0.A1 Environment: MySQL 5 Reporter: Keith Naas Assigned To: Christian Bauer MySQL config just needs tweaked to match the maxRequestSize on the multipart filter. Caused by: com.mysql.jdbc.PacketTooBigException: Packet for query is too large (2012624 > 1048576). You can change this value on the server by setting the max_allowed_packet' variable. at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3066) -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2008