August 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3097) Modify Filter to allow Collection Values

by Craig Savolainen (JIRA)

Modify Filter to allow Collection Values ---------------------------------------- Key: JBSEAM-3097 URL: http://jira.jboss.com/jira/browse/JBSEAM-3097 Project: Seam Issue Type: Feature Request Components: Core Reporter: Craig Savolainen Priority: Minor The current HibernatePersistenceProvider/ManagedHibernateSession implementations will not correctly pass a collection of values to the underlying filter. -- 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, 5 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3190) Redirect error page to current view

by Pete Muir (JIRA)

Redirect error page to current view ----------------------------------- Key: JBSEAM-3190 URL: https://jira.jboss.org/jira/browse/JBSEAM-3190 Project: Seam Issue Type: Bug Components: Exception Handling, JSF Integration Reporter: Pete Muir Fix For: 2.0.3.GA The code which tries to redirect to the current view isn't called because it checks for null rather than an empty string. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3118) Unclear ItemValidator example in reference (31.2)

by Richard Richter (JIRA)

Unclear ItemValidator example in reference (31.2) ------------------------------------------------- Key: JBSEAM-3118 URL: http://jira.jboss.com/jira/browse/JBSEAM-3118 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.1.0.A1 Reporter: Richard Richter In section 31.2 of Seam reference (2.1 version) there is an example which is not very clear: @Name("itemValidator") @BypassInterceptors @Validator public class ItemValidator implements Validator { public void validate(FacesContext context, UIComponent cmp, Object value) throws ValidatorException { ItemController ItemController = (ItemController) Component.getInstance("itemController"); return itemController.validate(value); } } First thing is that if you accept one import for Validator, the other usage of that type is broken - there are both Hibernate Validator annotation and JSF Validator interface used (I'd use FQN for this one probably). Other thing is that there is return of something for void method. Example is rather confusing as it is now. -- 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, 5 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3014) Email / PDF rendering ignores custom taglibs defined with facelets.LIBRARIES in web.xml

by Gena Batalski (JIRA)

Email / PDF rendering ignores custom taglibs defined with facelets.LIBRARIES in web.xml --------------------------------------------------------------------------------------- Key: JBSEAM-3014 URL: http://jira.jboss.com/jira/browse/JBSEAM-3014 Project: Seam Issue Type: Bug Components: Mail, PDF Affects Versions: 2.1.0.A1, 2.0.2.GA Environment: 2.1.0.A1, Facelets shipped with Seam-gen, trinidad latest Reporter: Gena Batalski Assigned To: Pete Muir During the rendering of email/pdf occurs an exception, if the email or pdf uses custom facelets taglibs defined with context parameter facelets.LIBRARIES . -- 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, 5 months

2
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3137) Numberguess example throws NoClassDefFoundError: org/richfaces/webapp/taglib/UIComponentELTagBase

by Stan Silvert (JIRA)

Numberguess example throws NoClassDefFoundError: org/richfaces/webapp/taglib/UIComponentELTagBase ------------------------------------------------------------------------------------------------- Key: JBSEAM-3137 URL: http://jira.jboss.com/jira/browse/JBSEAM-3137 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.BETA1 Reporter: Stan Silvert If I run the trunk version of numberguess, I get: javax.servlet.ServletException: java.lang.NoClassDefFoundError: org/richfaces/webapp/taglib/UIComponentELTagBase org.apache.jasper.servlet.JspServlet.service(JspServlet.java:273) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) I'm looking through the code and I noticed that org.jboss.seam.ui.util.cdk.UIComponentTagBase extends the RichFaces UIComponentELTagBase. I assume that is the problem? I assume you don't want Seam to be dependent on RichFaces? Also, Seam's UIComponentTagBase is marked as @deprecated. So I'm not sure how to proceed. I could add the RichFaces jar to numberguess, but that's probably not the correct fix. -- 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, 5 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3218) Add Doc on accessing Remote EJB3s

by Samuel Mendenhall (JIRA)

Add Doc on accessing Remote EJB3s --------------------------------- Key: JBSEAM-3218 URL: https://jira.jboss.org/jira/browse/JBSEAM-3218 Project: Seam Issue Type: Task Components: EJB3 Affects Versions: 2.1.0.A1, 2.0.3.CR1, 2.0.2.SP1 Reporter: Samuel Mendenhall Priority: Minor There needs to be documentation highlighting the caveats when accessing Remote EJB3s which are also Seam Components, ie. No traditional HTTP Session, security-constraint required to pass the security context to the EJB3, best practices, simple example, ect... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3206) Upload jexcel jars to jboss repo

by Daniel Roth (JIRA)

Upload jexcel jars to jboss repo -------------------------------- Key: JBSEAM-3206 URL: https://jira.jboss.org/jira/browse/JBSEAM-3206 Project: Seam Issue Type: Task Components: Excel Reporter: Daniel Roth Attachments: jxl.jar As discussed with Pete M, we need to get the jxl jars into the jboss repo: 2.6.6 is availible in this maven repo: http://www4.rothamsted.bbsrc.ac.uk/ondex/maven2/jexcelapi/jxl/2.6.6/ 2.6.8 is not to be found in any maven repo, but will be attached. This is the preferred library to upload. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3209) GWTService RPC does not transfer SerializableExceptions for GWT 1.4

by Adrian Stachowiak (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-3209?page=com.atlassian.jira.pl... ] Adrian Stachowiak updated JBSEAM-3209: -------------------------------------- Summary: GWTService RPC does not transfer SerializableExceptions for GWT 1.4 (was: GWTService RPC doesn not transfer SerializableExceptions for GWT 1.4) > GWTService RPC does not transfer SerializableExceptions for GWT 1.4 > ------------------------------------------------------------------- > > Key: JBSEAM-3209 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3209 > Project: Seam > Issue Type: Bug > Components: Remoting > Affects Versions: 2.1.0.A1 > Reporter: Adrian Stachowiak > Assignee: Shane Bryzak > Attachments: GWTService-patch.txt > > > GWTRemote is constucted in a way that it parses InvocationTargetExceptions in the processCall method. It looks for the cause of the exception and if it is a SerializableException it prepares an answer that contains the actual exception. Unfortunately in the next if statement this already prepared answer is overwritten by the standard "The call failed on the server; see server log for details" message. This way no SerializableException is ever transferred to the client. Only the standard error response. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3157) Generate profile-specific components.properties definitions through seam-gen

by Jacob Orshalick (JIRA)

Generate profile-specific components.properties definitions through seam-gen ---------------------------------------------------------------------------- Key: JBSEAM-3157 URL: http://jira.jboss.com/jira/browse/JBSEAM-3157 Project: Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.1.0.A1 Reporter: Jacob Orshalick Priority: Optional Seam-gen profiles provides a great way for Ant users to enable environment-specific configuration. It would be great to also provide the option to configure Seam components based on profile without having to edit the build (currently seam-gen is using filter tokens to swap out env-config reported at JBSEAM-3031). The approach is described here: http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-con... Essentially creation of the following in a seam-gen'd project: components-dev.properties components-test.properties components-prod.properties and using the build to pick the appropriate properties file based on the current profile. Dependendent on JBSEAM-3031. -- 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, 5 months

2
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3031) components.properties not being used in seam-gen EAR

by Dan Allen (JIRA)

components.properties not being used in seam-gen EAR ---------------------------------------------------- Key: JBSEAM-3031 URL: http://jira.jboss.com/jira/browse/JBSEAM-3031 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.A1, 2.0.2.GA Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.2.SP1, 2.1.0.BETA1 In the EAR build produced by seam-gen, the components.properties never gets a chance to do its job because the replacement tokens in components.xml are being filled in by the Ant build instead. -- 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, 5 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2008