April 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1146) Include optional Ant build-${profile}.xml in seam-gen/build-scripts

by Stephan Heffner (JIRA)

Include optional Ant build-${profile}.xml in seam-gen/build-scripts ------------------------------------------------------------------- Key: JBSEAM-1146 URL: http://jira.jboss.com/jira/browse/JBSEAM-1146 Project: JBoss Seam Issue Type: Patch Affects Versions: 1.2.1.GA Reporter: Stephan Heffner Attachments: build.xml  <import file="build-${profile}.xml" optional="true"/> -- 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, 8 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2773) JPA example on Tomcat 6.X throws a NoClassDefFoundError: org/objectweb/asm/Type

by Jay Balunas (JIRA)

JPA example on Tomcat 6.X throws a NoClassDefFoundError: org/objectweb/asm/Type ------------------------------------------------------------------------------- Key: JBSEAM-2773 URL: http://jira.jboss.com/jira/browse/JBSEAM-2773 Project: JBoss Seam Issue Type: Bug Components: Examples, Platform interoperability Affects Versions: 2.0.2.GA Environment: Tomcat 6.0.16 Java 1.5 Linux fedora 8 x86 Reporter: Jay Balunas Assigned To: Jay Balunas Fix For: 2.0.2.GA, 2.1.0.BETA1 Follow the instructions for the JPA example deploying to tomcat 6.0. When deploying the JPA example you will see the exception below. Caused by: java.lang.NoClassDefFoundError: org/objectweb/asm/Type at net.sf.cglib.core.TypeUtils.parseType(TypeUtils.java:180) at net.sf.cglib.core.KeyFactory.<clinit>(KeyFactory.java:66) at net.sf.cglib.proxy.Enhancer.<clinit>(Enhancer.java:69) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:117) at org.hibernate.proxy.pojo.cglib.CGLIBProxyFactory.postInstantiate(CGLIBProxyFactory.java:43) at org.hibernate.tuple.entity.PojoEntityTuplizer.buildProxyFactory(PojoEntityTuplizer.java:162) at org.hibernate.tuple.entity.AbstractEntityTuplizer.<init>(AbstractEntityTuplizer.java:135) at org.hibernate.tuple.entity.PojoEntityTuplizer.<init>(PojoEntityTuplizer.java:55) at org.hibernate.tuple.entity.EntityEntityModeToTuplizerMapping.<init>(EntityEntityModeToTuplizerMapping.java:56) at org.hibernate.tuple.entity.EntityMetamodel.<init>(EntityMetamodel.java:295) at org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:434) at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:109) at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:226) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:730) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:121) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:83) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:60) at org.jboss.seam.persistence.EntityManagerFactory.createEntityManagerFactory(EntityManagerFactory.java:81) at org.jboss.seam.persistence.EntityManagerFactory.startup(EntityManagerFactory.java:50) ... 38 more -- 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, 8 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2666) ManagedPersistenceContext closed in a clustered environment

by Clint Popetz (JIRA)

ManagedPersistenceContext closed in a clustered environment ----------------------------------------------------------- Key: JBSEAM-2666 URL: http://jira.jboss.com/jira/browse/JBSEAM-2666 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.GA Reporter: Clint Popetz Attachments: mpc-passivate.diff ManagedPersistenceContext, upon passivation, checks to see if the entity manager is dirty, and if not, closes it. I presume this is intended as an optimization. But in a clustered environment, where a snapshot of the session is taken upon each request that dirties the session, passivation will occur frequently within a conversation. In this case, the entity manager is frequently closed and recreated upon the next request, and entities in conversational beans become detached, and all sorts of bad things happen when I try to use them in the new session. I think that to preserve the promise of long conversations, we have to keep the persistence context open across passivation, regardless of whether it's dirty. The attached patch removes the entityManager close(). -- 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, 8 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1228) Add sort option to <s:selectItems>

by Stephan Bublava (JIRA)

Add sort option to <s:selectItems> ---------------------------------- Key: JBSEAM-1228 URL: http://jira.jboss.com/jira/browse/JBSEAM-1228 Project: JBoss Seam Issue Type: Patch Components: JSF Affects Versions: 1.2.1.GA Reporter: Stephan Bublava Attachments: sort-selectitems-patch.txt The attached patch adds a sort option to <s:selectItems>, that allows the entries to be sorted by their label. Example: <h:selectOneMenu value="#{person.honorific}"> <s:selectItems value="#{honorifics}" var="honorific" label="#{honorific.label}" noSelectionLabel="Please select" sort="ascending" /> <s:convertEnum /> </h:selectOneMenu> This version has not been tested in depth (especially interactions with "noSelectionLabel"), but I've been using similar code in our project (based upon Seam SelectItems 1.1.1beta1) for some time now and not encountered any problems. -- 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, 8 months

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1981) enable validation on file upload component

by Bruno Bieth (JIRA)

enable validation on file upload component ------------------------------------------ Key: JBSEAM-1981 URL: http://jira.jboss.com/jira/browse/JBSEAM-1981 Project: JBoss Seam Issue Type: Patch Reporter: Bruno Bieth Currently file upload can't be validated. The attached patch allow to use the hibernate validation framework with byte[] attribute. You may have, for instance, to check if an uploaded file is an Image. About the patch : First the submittedValue is not set so the validation phase is skipped, second file upload doesn't use the standard "value" attribute (needed by the ModelValidator) but "data". To work you have to use a value attribute to your fileupload component. At the moment this work only with Facelets. For backward compatibility the data attribute is kept (but validation won't work). -- 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, 8 months

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1387) Support for overriding .cfg.xml properties in HibernateFactory (patch included)

by Przemyslaw Jaskierski (JIRA)

Support for overriding .cfg.xml properties in HibernateFactory (patch included) -------------------------------------------------------------------------------- Key: JBSEAM-1387 URL: http://jira.jboss.com/jira/browse/JBSEAM-1387 Project: JBoss Seam Issue Type: Feature Request Environment: Microcontainer Reporter: Przemyslaw Jaskierski Fix For: 1.3.0.ALPHA Attachments: HibernateFactory-patch.diff.zip Currently HibernateFactory supports only one type of configuration at a time: .cfg.xml file or "programmatic" one passed by the cfgProperties property. It would be great to have the ability to override individual properties from the specified .cfg.xml file using cfgProperties property. For example, when you want to have special value for hibernate.hbm2ddl.auto in case of tests only, and normal one in case of production environment. Applying my patch makes the following thing possible (instead of maintaing two almost identicall hibernate.cfg.xml files): <bean name="pecpHibernateSessionFactoryFactory" class="pecp.core.seam.HibernateFactory"> <property name="cfgResourceName"> <inject bean="pecpHibernateConfigurationLocation"/> </property> <property name="namingStrategy"> <inject bean="underscoreAwareNamingStrategy"/> </property> <property name="cfgProperties"> <map class="java.util.Hashtable" keyClass="java.lang.String" valueClass="java.lang.String"> <entry> <key>hibernate.hbm2ddl.auto</key> <value>create-drop</value> </entry> </map> </property> </bean> I've kept original logical code flow intact, so when there is no cfgResourceName and no cfgProperties set, Seam (as in original case) tries to call configuration.configure() and try to configure from hibernate.cfg.xml file. To make override functionality work you need to specify cfgResourceName property. -- 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, 8 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1961) ConversationEntry.isCurrent returns incorrect value when the ConversationEntry represents a temporary conversation

by Chris Rudd (JIRA)

ConversationEntry.isCurrent returns incorrect value when the ConversationEntry represents a temporary conversation ------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-1961 URL: http://jira.jboss.com/jira/browse/JBSEAM-1961 Project: JBoss Seam Issue Type: Bug Reporter: Chris Rudd ConversationEntry.isCurrent always returns false for the CE that represents the current conversaion if that conversation is not long running. This was discovered when attempting to to work around JBSEAM-1901. I would expect the CE to return true if it represents the current conversation reguarless of the longRunning/temporary state of the conversation. -- 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, 8 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2744) In the ejb home classes isWired() method, boolean types are checked with if( value == 0) which does'nt compile.

by David Cloutier (JIRA)

In the ejb home classes isWired() method, boolean types are checked with if( value == 0) which does'nt compile. ---------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2744 URL: http://jira.jboss.com/jira/browse/JBSEAM-2744 Project: JBoss Seam Issue Type: Bug Components: EJB3 Affects Versions: 2.1.0.A1, 2.0.1.GA Reporter: David Cloutier In the ejb home classes isWired() method, boolean types are checked with if( value == 0) which does'nt compile. -- 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, 8 months

2
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2677) Injection And Child Objects

by Tom Goring (JIRA)

Injection And Child Objects --------------------------- Key: JBSEAM-2677 URL: http://jira.jboss.com/jira/browse/JBSEAM-2677 Project: JBoss Seam Issue Type: Bug Components: Core, EL Affects Versions: 2.0.1.CR1 Reporter: Tom Goring Priority: Minor When an EL expression uses a property from a child object the parent object does not have any of it's dependencies injected. Here an example and discussion: http://www.seamframework.org/Community/InjectionAndChildObjects -- 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, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2321) only generate-entities creates views that begin with uppercase

by Dan Allen (JIRA)

only generate-entities creates views that begin with uppercase -------------------------------------------------------------- Key: JBSEAM-2321 URL: http://jira.jboss.com/jira/browse/JBSEAM-2321 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.GA Reporter: Dan Allen Fix For: 2.0.x This is a blaring bug that has someone been overlooked up until now. The generate-entities command (now generate-ui) creates pages using the naming pattern FooBar.xhtml whereas all of the other commands use the naming pattern fooBar.xhtml. We should definitely bring generate-entities in line with the rest of the crowd. It is very unconventional to start pages with uppercase characters (going by experience) -- 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, 8 months

3
6
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 April 2008