February 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-839) Mail example logs errors at DEBUG level

by Peter Muir (JIRA)

Mail example logs errors at DEBUG level --------------------------------------- Key: JBSEAM-839 URL: http://jira.jboss.com/jira/browse/JBSEAM-839 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 1.1.6.GA Reporter: Peter Muir Assigned To: Peter Muir Priority: Minor Fix For: 1.1.7.GA Should be ERROR level -- 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

17 years, 11 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-840) Mail example doesn't work ootb on tomcat

by Peter Muir (JIRA)

Mail example doesn't work ootb on tomcat ---------------------------------------- Key: JBSEAM-840 URL: http://jira.jboss.com/jira/browse/JBSEAM-840 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 1.1.6.GA Reporter: Peter Muir Assigned To: Peter Muir Priority: Trivial Fix For: 1.1.7.GA Mail example uses meldware (ear) to as an smtp server, this won't work on Tomcat. Need a note in the example explaining this -- 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

17 years, 11 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-861) class not found error javax.interceptor.InvocationContext when running hibernate2 example on head

by youngm (JIRA)

class not found error javax.interceptor.InvocationContext when running hibernate2 example on head ------------------------------------------------------------------------------------------------- Key: JBSEAM-861 URL: http://jira.jboss.com/jira/browse/JBSEAM-861 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.7.GA Reporter: youngm Fix For: 1.1.7.GA class not found error javax.interceptor.InvocationContext when running hibernate2 example in jboss. The source of the problem appears to be the addition of "new EE5SeamInvocationContext" in RootInterceptor:145. -- 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

17 years, 11 months

3
17
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-862) Minor error in view.xhtml.ftl Seam Gen Template

by Damian Harvey (JIRA)

Minor error in view.xhtml.ftl Seam Gen Template ----------------------------------------------- Key: JBSEAM-862 URL: http://jira.jboss.com/jira/browse/JBSEAM-862 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.6.GA Reporter: Damian Harvey Priority: Minor If you have a ManyToOne association that goes more than one level deep eg. A PERSON associated with a COMPANY associated with a COUNTRY then the SeamGen view template has a small error on line 83 of the view.xhtml.ftl It is currently: Code: ${'#'}{${parentName}.${parentProperty.name}.${ parentPojo .identifierProperty.name}} but should be: Code: ${'#'}{${parentName}.${parentProperty.name}.${ parentParentPojo .identifierProperty.name}} It results in an error in the generated View page as the property is set as such: Code: <h:column> <f:facet name="header">countryCode countryId</f:facet> #{company.countryCode.companyId}  </h:column> -- 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

17 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-860) Documentation of page navigation is incorrect

by Mike Quilleash (JIRA)

Documentation of page navigation is incorrect --------------------------------------------- Key: JBSEAM-860 URL: http://jira.jboss.com/jira/browse/JBSEAM-860 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash All the examples in section 5.1.1.2 of Seam page navigation have </navigation-rule> as the closing element when it should be </page>. -- 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

17 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-857) Identity.login() should use SEVERITY_ERROR for "login failed" message

by Stephan Bublava (JIRA)

Identity.login() should use SEVERITY_ERROR for "login failed" message --------------------------------------------------------------------- Key: JBSEAM-857 URL: http://jira.jboss.com/jira/browse/JBSEAM-857 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 1.1.6.GA Reporter: Stephan Bublava Priority: Trivial -- 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

17 years, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-856) @Restrict on a class doesn't restrict access to methods implemented in super-classes

by Stephan Bublava (JIRA)

@Restrict on a class doesn't restrict access to methods implemented in super-classes ------------------------------------------------------------------------------------ Key: JBSEAM-856 URL: http://jira.jboss.com/jira/browse/JBSEAM-856 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 1.1.6.GA Reporter: Stephan Bublava Example: public class AbstractComponent { public String action1() { return null; } } @Name("component") @Restrict public class Component extends AbstractComponent { public String action2() { return null; } } With this setup, using #{component.action1} does not cause a permission check. -- 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

17 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-713) Using FacesMessages results in stale component rendering

by Christian Bauer (JIRA)

Using FacesMessages results in stale component rendering -------------------------------------------------------- Key: JBSEAM-713 URL: http://jira.jboss.com/jira/browse/JBSEAM-713 Project: JBoss Seam Issue Type: Bug Reporter: Christian Bauer Priority: Minor Tough one... before I isolate the problem to a standalone test, these are the symptoms: A page has two <h:datatable> components, let's say tableA and tableB. There is a <h:form> around tableB with a <h:commandButton>. When this button is pressed, I execute an action method on a conversational component and update some data in the current conversation that is shown by tableA. The page is rendered again and tableA shows the updated data. However, if in the action method I use FacesMessages.instance().add("Updated object"); (or any other variation of FacesMessages), tableA is not re-rendered but shown with old state. If I click the commandButton again, tableA is rendered fine (!). Now, if I replace the call to FacesMessages with this FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Updated Object")); all works as expected and on every RenderResponse of the page, tableA is rerendered. I verified that the tableA datacomponent is not rendered again. Interestingly, the backing bean data for tableA is called during RenderResponse every time, it just displays the same old component (which, I think, it remembers somehow from the RestoreView phase). -- 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

17 years, 11 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-852) Internal Seam log messages are not producing line numbers or method name under Log4J.

by Mike Quilleash (JIRA)

Internal Seam log messages are not producing line numbers or method name under Log4J. ------------------------------------------------------------------------------------- Key: JBSEAM-852 URL: http://jira.jboss.com/jira/browse/JBSEAM-852 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash Example of the Seam log during startup. INFO [javax.servlet.ServletContextListener] [main] (?:?) - Welcome to Seam 1.1.6.GA The ?:? indicate the logging could not determine the method and line number. I only believe this is a problem with Log4J. This is because the core Seam code is using Logging.getLogProvider() rather than Logging.getLog() like the @Logging injection does and the FQCN passed to Log4J is LogImpl which the LogProvider path does not call. Example private static final LogProvider log = Logging.getLogProvider(ServletContextListener.class); Doing a search/replace to replaces "Logging.getLogProvider(" with "Logging.getLog(" should fix the problem. A minor optimisation would be to modify LogImpl.interpolate() to (add the length check) to avoid calling/creating the interpolate component needlessly. private Object interpolate(Object object, Object... params) { if (object instanceof String && params.length > 0) { return Interpolator.instance().interpolate( (String) object, params ); } else { return object; } } -- 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

17 years, 11 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-850) License violation

by Petr Ferschmann (JIRA)

License violation ----------------- Key: JBSEAM-850 URL: http://jira.jboss.com/jira/browse/JBSEAM-850 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.6.GA Environment: any Reporter: Petr Ferschmann JBoss Seam has LGPL license. JCaptcha (according to content of jcaptcha-all-1.0-RC3.jar) is GPL. When running JBoss Seam without jcaptcha I get this NoClassDefFoundError: java.lang.NoClassDefFoundError: com/octo/captcha/service/image/ImageCaptchaService at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2427) at java.lang.Class.getDeclaredMethods(Class.java:1791) at org.jboss.seam.Component.initMembers(Component.java:413) at org.jboss.seam.Component.<init>(Component.java:253) at org.jboss.seam.Component.<init>(Component.java:204) at org.jboss.seam.init.Initialization.addComponent(Initialization.java:742) at org.jboss.seam.init.Initialization.addComponents(Initialization.java:674) at org.jboss.seam.init.Initialization.init(Initialization.java:429) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33) This mean I can't use Seam without GPL software. Solution is to make JCaptcha optional. -- 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

17 years, 11 months

4
5
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 2007