July 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1637) document "autoCreate" option on @Factory

by Matt Drees (JIRA)

document "autoCreate" option on @Factory ---------------------------------------- Key: JBSEAM-1637 URL: http://jira.jboss.com/jira/browse/JBSEAM-1637 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.BETA1 Reporter: Matt Drees Priority: Minor The documentation (chapter 26) doesn't explain that you can use autoCreate=true in a @Factory 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

18 years, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1611) CJK character support for iText

by Takayoshi Kimura (JIRA)

CJK character support for iText ------------------------------- Key: JBSEAM-1611 URL: http://jira.jboss.com/jira/browse/JBSEAM-1611 Project: JBoss Seam Issue Type: Feature Request Components: PDF Affects Versions: 2.0.0.BETA1, 1.2.1.GA Reporter: Takayoshi Kimura Hello, We cannot use CJK character with the p:font family attribute. It doesn't support CJK character. I will attach a patch against jboss-seam CVS trunk. It includes patch for the UIFont.java and the itext.xml documentation. The changes is fully backward compatibile, if the name and encoding parameters are not given, it does nothing. We strongly hope this fix to be included in 2.0.0.GA. This issue is originally reported by Toshirou Okazaki. Best regards, Japan JBoss user group -- 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, 4 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-761) Modify the default interception practices

by Mike Quilleash (JIRA)

Modify the default interception practices ----------------------------------------- Key: JBSEAM-761 URL: http://jira.jboss.com/jira/browse/JBSEAM-761 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.0.GA Environment: Any. Reporter: Mike Quilleash Currently all methods on a Seam component will be intercepted. In some circumstances this can make debugging difficult as a lot of debuggers call toString() on objects visible from the breakpoint which executes all the Bijection incl the DisInjection which can damage the state of the object depending where the breakpoint is in the process. Perhaps the interception logic could ignore calls to any method on the Object class so the default toString() doesn't cause problems. Another complementary change would be to expand the @Intercept to be allowed on methods (and fields?) to allow the interception logic to be configured on individual methods (like a custom toString()) method. -- 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, 4 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1628) Injecting uiComponent with required = false fails against Sun RI when component is not present

by Daniel Young (JIRA)

Injecting uiComponent with required = false fails against Sun RI when component is not present ---------------------------------------------------------------------------------------------- Key: JBSEAM-1628 URL: http://jira.jboss.com/jira/browse/JBSEAM-1628 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Daniel Young Priority: Critical Fix For: 2.0.0.CR1 If you inject a UIComponent into a bean as follows: @In(required = false, value = "#{uiComponent['XXX']}") It fails for any method call that occurs on the bean at a time when the component is unavailable under the ViewRoot. An IllegalArgumentException is thrown by the Sun RI from UIComponentBase:588 if findComponent(id) is unsuccessful, whereas MyFaces simply returns null. This can be fixed by patching org.jboss.seam.faces.UIComponent to catch the IllegalArgumentException and return null. We were working around this by avoiding using @In for this and looking under the FacesContext.ViewRoot manually, but eventually decided to patch Seam ourselves until this issue is fixed in CVS. The above fix is working well for us. -- 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, 4 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1603) remove "CRUD-Application Generator" section from docs

by Matt Drees (JIRA)

remove "CRUD-Application Generator" section from docs ----------------------------------------------------- Key: JBSEAM-1603 URL: http://jira.jboss.com/jira/browse/JBSEAM-1603 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 2.0.0.BETA1 Reporter: Matt Drees Priority: Minor The CRUD-Application Generator has been replaced by seam-gen, and having it in the docs is confusing. -- 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, 4 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1632) ResourceBundle and UberResourceBundle should be Serializable

by Darryl Smith (JIRA)

ResourceBundle and UberResourceBundle should be Serializable ------------------------------------------------------------ Key: JBSEAM-1632 URL: http://jira.jboss.com/jira/browse/JBSEAM-1632 Project: JBoss Seam Issue Type: Bug Reporter: Darryl Smith According to seam WARN [jboss.seam.Component] - <Component class should be serializable: org.jboss.seam.core.resourceBundleFactory> and [07/10 03:28:33] DEBUG [seam.core.Events] - <Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.core.resourceBundleFactory> Jul 10, 2007 3:28:33 AM com.sun.faces.lifecycle.ProcessValidationsPhase execute WARNING: setAttribute: Non-serializable attribute java.lang.IllegalArgumentException: setAttribute: Non-serializable attribute at org.apache.catalina.session.StandardSession.setAttribute(StandardSession.java:1255) at org.apache.catalina.session.StandardSession.setAttribute(StandardSession.java:1233) at org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:129) at com.sun.faces.context.SessionMap.put(ExternalContextImpl.java:965) at org.jboss.seam.contexts.BasicContext.set(BasicContext.java:80) -- 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, 4 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1606) Seam variable resolver for drools

by Gavin King (JIRA)

Seam variable resolver for drools --------------------------------- Key: JBSEAM-1606 URL: http://jira.jboss.com/jira/browse/JBSEAM-1606 Project: JBoss Seam Issue Type: Feature Request Components: Drools Reporter: Gavin King Assigned To: Gavin King Fix For: 2.0.0.CR1 Drools now supports "pulling" globals. http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/drools-core/src/test/... -- 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, 4 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1630) use dist directory inside project during build

by Dan Allen (JIRA)

use dist directory inside project during build ---------------------------------------------- Key: JBSEAM-1630 URL: http://jira.jboss.com/jira/browse/JBSEAM-1630 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Dan Allen Priority: Minor This is a nit picky request, but I have always felt that a build should stay confined, not placing files in parent directories. Currently, when you run the main Seam build, it creates a folder with the ${dist.name} value one directory up from the source folder. I recommend the use of a "dist" directory to hold such artifacts. The line that needs to be changed is as follows: Old: <property name="dist.dir" value="${basedir}/../${dist.name}" /> New: <property name="dist.dir" value="${basedir}/dist/${dist.name}" /> -- 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, 4 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1618) Improve the documentation for Identity.addRole()

by Shane Bryzak (JIRA)

Improve the documentation for Identity.addRole() ------------------------------------------------ Key: JBSEAM-1618 URL: http://jira.jboss.com/jira/browse/JBSEAM-1618 Project: JBoss Seam Issue Type: Task Components: Security Reporter: Shane Bryzak Assigned To: Shane Bryzak Priority: Critical Fix For: 2.0.0.CR1 Everyone is confused about how addRole() works. It really needs to be spelled out clearly in the security chapter of the documentation exactly what it does, probably with a big diagram or something. -- 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, 4 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1624) seam-gen generates incorrect jboss.home property in build.properties

by Joshua Jackson (JIRA)

seam-gen generates incorrect jboss.home property in build.properties -------------------------------------------------------------------- Key: JBSEAM-1624 URL: http://jira.jboss.com/jira/browse/JBSEAM-1624 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Reporter: Joshua Jackson Fix For: 2.0.0.CR1 Instead of generating the path inserted from seam-gen console, seam-gen created 'Applications/jboss-4.2.0.GA' path. Which seems to be hardcoded. -- 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, 4 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 July 2007