September 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1518) support for H2 in seam-gen

by Dan Allen (JIRA)

support for H2 in seam-gen -------------------------- Key: JBSEAM-1518 URL: http://jira.jboss.com/jira/browse/JBSEAM-1518 Project: JBoss Seam Issue Type: Patch Components: Tools Affects Versions: 1.3.0.ALPHA Environment: seam CVS trunk Reporter: Dan Allen Priority: Minor Currently, the seam-gen questionnaire does not support H2, even though there is a dialect for Hibernate that functions with a H2 database. I have discovered that H2 is far more suitable than HSQLDB and prefer to use it now whenever I am doing prototype development. Naturally, it is annoying to always have to make my case the exception when supporting H2 is just a matter of filling in the proper blanks in the seam-gen build.xml file. Without further delay, I did just that. -- 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, 6 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1806) EL function library

by Mikhail Grushinskiy (JIRA)

EL function library ------------------- Key: JBSEAM-1806 URL: http://jira.jboss.com/jira/browse/JBSEAM-1806 Project: JBoss Seam Issue Type: Feature Request Components: EL Environment: all Reporter: Mikhail Grushinskiy JSTL EL function library is too limited. Seam needs own EL function library. Here is a thread with code for initial set of functions: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074609#4074609 -- 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, 6 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2007) new-entity and generate-entities don't use same package name

by Dan Allen (JIRA)

new-entity and generate-entities don't use same package name ------------------------------------------------------------ Key: JBSEAM-2007 URL: http://jira.jboss.com/jira/browse/JBSEAM-2007 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Fix For: 2.0.0.GA Attachments: JBSEAM-2007-v1.txt The *Home.java and *List.java classes that are produced by new-entity do not use the same package as the same classes produced by generate-entities. Assuming the entity name is MyEntity, here is how the two actions play out. new-entity: src/action/com/company/action/MyEntityHome.java src/action/com/company/action/MyEntityList.java generate-entities: src/action/com/company/model/MyEntityHome.java src/action/com/company/model/MyEntityList.java Notice that generate-entities uses "model" while the new-entity uses "action". This behavior is due to a limitation in the hbmtemplate task which assumes that the Java files created will be in the same package as the model. However, it is possible to work around this problem. I have created such a patch. I believe that new-entity exhibits the correct behavior and puts the classes in the expected location. The only limitation of doing this patch is that it is necessary to use a star import for the model classes since the hbmtemplate task assumes the current package is the package of the entity (hence even pojo.importType() wouldn't work). However, this shouldn't really be an issue since the IDE can cleanup the star imports. I would much rather have the consistency of the same package. Besides, *List.java and *Home.java are action components, not models. -- 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, 6 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1999) Improve documentation of when the ConversationList component is populated

by Jacob Orshalick (JIRA)

Improve documentation of when the ConversationList component is populated ------------------------------------------------------------------------- Key: JBSEAM-1999 URL: http://jira.jboss.com/jira/browse/JBSEAM-1999 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.CR1 Reporter: Jacob Orshalick Priority: Minor The conversationList is only populated with a ConversationEntry if entry.isDisplayable() returns true (which requires a description entry in pages.xml). 6.7.1 and 6.7.2 show how to set the descriptions for pages in the pages.xml to populate the ConversationList, but neither sections 6.7.1, 6.7.2, 6.7.3, or 28.4 describe this behavior. Having this described in the documentation would likely help new users. In addition, a nice-to-have would be a warning in the log or some default description if the conversationList is requested and a ConversationEntry is not displayable. The documentation could state something like: The conversationList component will only be populated with a ConversationEntry if a description of the conversation's view-id is provided in pages.xml. Adding descriptions to a view-id in pages.xml is described in Sections 6.7.1 and 6.7.2. -- 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, 6 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1967) UIGraphic accesses lazy loaded data beyond transaction boundaries

by Christian Bauer (JIRA)

UIGraphic accesses lazy loaded data beyond transaction boundaries ----------------------------------------------------------------- Key: JBSEAM-1967 URL: http://jira.jboss.com/jira/browse/JBSEAM-1967 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.CR1 Reporter: Christian Bauer Priority: Minor I have a lazy loaded byte[] in my domain model which is enhanced with the Hibernate instrument task. So it's only loaded on access. If I bind this to a <s:graphicImage>, this loading is triggered after the transaction of the RENDER RESPONSE phase was committed. In that case, Hibernate will just grab a database connection to load the property, which will never be closed. JBoss AS doesn't like that: (http-127.0.0.1-8080-2hread) 15:18:51,492 TRACE [SeamPhaseListener] after phase: RENDER_RESPONSE 6 (http-127.0.0.1-8080-2hread) 15:18:51,492 DEBUG [SeamPhaseListener] committing transaction after phase: RENDER_RESPONSE 6 (http-127.0.0.1-8080-2hread) 15:18:51,492 DEBUG [UTTransaction] committing JTA transaction (http-127.0.0.1-8080-2hread) 15:18:51,493 TRACE [RootInterceptor] intercepted: fileHome.isIdDefined (http-127.0.0.1-8080-2hread) 15:18:51,493 TRACE [RootInterceptor] intercepted: fileMetaMap.getFielMetaMap (http-127.0.0.1-8080-2hread) 15:18:51,494 DEBUG [Manager] Storing conversation state: 72 (http-127.0.0.1-8080-2hread) 15:18:51,494 DEBUG [FacesLifecycle] After render response, destroying contexts (http-127.0.0.1-8080-2hread) 15:18:51,495 DEBUG [FacesLifecycle] <<< End JSF request (http-127.0.0.1-8080-2hread) 15:18:51,496 INFO [CachedConnectionManager] Closing a connection for you. Please close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@60b945 java.lang.Throwable: STACKTRACE at org.jboss.resource.connectionmanager.CachedConnectionManager.registerConnection(CachedConnectionManager.java:290) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:417) at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842) at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88) at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69) at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423) at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144) at org.hibernate.jdbc.AbstractBatcher.prepareSelectStatement(AbstractBatcher.java:123) at org.hibernate.persister.entity.AbstractEntityPersister.initializeLazyPropertiesFromDatastore(AbstractEntityPersister.java:786) at org.hibernate.persister.entity.AbstractEntityPersister.initializeLazyProperty(AbstractEntityPersister.java:758) at org.hibernate.intercept.AbstractFieldInterceptor.intercept(AbstractFieldInterceptor.java:73) at org.hibernate.intercept.javassist.FieldInterceptorImpl.readObject(FieldInterceptorImpl.java:82) at org.jboss.seam.wiki.core.model.File.$javassist_read_data(File.java) at org.jboss.seam.wiki.core.model.File.getData(File.java:87) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at javax.el.BeanELResolver.getValue(BeanELResolver.java:62) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:64) at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71) at javax.faces.component.UIGraphic.getValue(UIGraphic.java:137) at org.jboss.seam.ui.graphicImage.GraphicImageRendererBase.doEncodeBegin(GraphicImageRendererBase.java:31) at org.jboss.seam.ui.util.cdk.RendererBase.encodeBegin(RendererBase.java:79) at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:788) at com.sun.faces.renderkit.html_basic.OutputLinkRenderer.encodeChildren(OutputLinkRenderer.java:148) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:812) at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:271) at com.sun.faces.renderkit.html_basic.GridRenderer.encodeChildren(GridRenderer.java:242) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:812) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:886) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:892) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:892) at javax.faces.render.Renderer.encodeChildren(Renderer.java:137) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:812) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:886) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:892) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:892) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:892) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:892) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:577) It seems like this behavior was OK or has change, I didn't get this exception with Hibernate 3.2.3 but now with Hibernate 3.2.5. -- 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, 6 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1965) Fix GWT example

by Pete Muir (JIRA)

Fix GWT example --------------- Key: JBSEAM-1965 URL: http://jira.jboss.com/jira/browse/JBSEAM-1965 Project: JBoss Seam Issue Type: Task Components: Examples, Remoting Affects Versions: 2.0.0.CR1 Reporter: Pete Muir Assigned To: Shane Bryzak Fix For: 2.0.0.GA -- 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, 6 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1514) seam-gen should normalize project name

by Dan Allen (JIRA)

seam-gen should normalize project name -------------------------------------- Key: JBSEAM-1514 URL: http://jira.jboss.com/jira/browse/JBSEAM-1514 Project: JBoss Seam Issue Type: Patch Components: Tools Affects Versions: 1.3.0.ALPHA Environment: Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode) seam CVS HEAD Reporter: Dan Allen seam-gen uses the name of the project in a lot of (dangerous) places when generating the code and configurations. If a project created with seam-gen is going to work correctly, this name must have "safe" characters (safe for JNDI, safe for value binding expressions, etc). Currently, if the person using seam-gen enters a space character or a hyphen in the name (two very standard use cases), then the resulting project will not work correctly. I have provided a patch that will normalize this name. It is implemented as an Ant task that filters the name for spaces and hyphens and replaces them with underscores. It then does a second pass to eliminate duplicate underscore characters. Granted, doing this filtering will not honor the exact name for the project that the user provides, but then again, what is the use if the project is broken. -- 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, 6 months

3
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1515) Use = sign consistently in hibernate-console.properties

by Dan Allen (JIRA)

Use = sign consistently in hibernate-console.properties ------------------------------------------------------- Key: JBSEAM-1515 URL: http://jira.jboss.com/jira/browse/JBSEAM-1515 Project: JBoss Seam Issue Type: Patch Components: Tools Affects Versions: 1.3.0.ALPHA Environment: seam CVS HEAD Reporter: Dan Allen Priority: Trivial Attachments: JBSEAM-1515.txt Sorry, there was no priority level labeled "Ultra Trivial," so I just had to go with "Trivial." The hibernate-console.properties file uses the blank space delimiter for one of the properties, yet uses = for the rest. -- 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, 6 months

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1988) AuthorizationException not redirected properly

by Samuel Mendenhall (JIRA)

AuthorizationException not redirected properly ---------------------------------------------- Key: JBSEAM-1988 URL: http://jira.jboss.com/jira/browse/JBSEAM-1988 Project: JBoss Seam Issue Type: Bug Components: Security Reporter: Samuel Mendenhall Assigned To: Shane Bryzak pages.xml: <exception class="org.jboss.seam.security.AuthorizationException"> <redirect> <message>You don't have permission to do this</message> </redirect> </exception> Should have: <redirect view-id="/error.xhtml"> Causes a redirect error in the browser otherwise. -- 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, 6 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1992) Upgrade MVEL library to 1.2.final

by Joshua Jackson (JIRA)

Upgrade MVEL library to 1.2.final --------------------------------- Key: JBSEAM-1992 URL: http://jira.jboss.com/jira/browse/JBSEAM-1992 Project: JBoss Seam Issue Type: Task Components: Drools Affects Versions: 2.0.0.CR1 Reporter: Joshua Jackson Fix For: 2.0.0.CR2 Upgrade the current mvel library that is used by drools to mvel 1.2.final as it has some fixes -- 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, 6 months

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2007