September 2010 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3387) Pages.xsd - Page element's scheme attribute use enum of http and https

by Arron Ferguson (JIRA)

Pages.xsd - Page element's scheme attribute use enum of http and https ---------------------------------------------------------------------- Key: JBSEAM-3387 URL: https://jira.jboss.org/jira/browse/JBSEAM-3387 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.BETA1 Environment: N/A Reporter: Arron Ferguson Priority: Optional Currently the pages.xml file has the following page element's scheme attribute defined as: <xs:attribute name="scheme"/> Since the user will be using one of two protocols: http or https, the scheme attribute should have: <xs:attribute name="scheme" default="false"> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="http"/> <xs:enumeration value="https"/> </xs:restriction> </xs:simpleType> </xs:attribute> -- 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

15 years, 4 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3828) Seam GWT servlet should no longer use deprecated SerializableException

by Jan Vorwerk (JIRA)

Seam GWT servlet should no longer use deprecated SerializableException ---------------------------------------------------------------------- Key: JBSEAM-3828 URL: https://jira.jboss.org/jira/browse/JBSEAM-3828 Project: Seam Issue Type: Patch Components: GWT Reporter: Jan Vorwerk Priority: Optional Since GWT 1.5 the usage of SerializableException has been deprecated, while Seam Remoting servlet for GWT compells its usage as a base class for serializable exceptions to be marshalled from the server to the client. See code in: org.jboss.seam.remoting.gwt.GWTService#processCall(String) // Serialize the exception back to the client if it's a declared // exception if (cause instanceof SerializableException) -- 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

15 years, 4 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3247) Seam without hibernate: Please make org.jboss.seam.core.Validators independent from Hibernate

by Francisco Jose Peredo Noguez (JIRA)

Seam without hibernate: Please make org.jboss.seam.core.Validators independent from Hibernate ---------------------------------------------------------------------------------------------- Key: JBSEAM-3247 URL: https://jira.jboss.org/jira/browse/JBSEAM-3247 Project: Seam Issue Type: Feature Request Affects Versions: 2.0.2.GA Reporter: Francisco Jose Peredo Noguez I think org.jboss.seam.core.Validators should implement and interface, so that it could be possible to replace it with one that doesn't use org.hibernate.validator.ClassValidator I guess with that we could say that Seam can be used in a 100% free of Hibernate way I really like Hibernate, but sometimes, for really simple projects, or for projects full of interactions with stored procedures , it might be overkill or innapropiate, so it would be nice to be able to use Seam without having any Hibernate dependencies. -- 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

15 years, 4 months

5
9
0 / 0

[JBoss JIRA] Created: (JBSEAM-4698) Hibernate search does not work in JBAS 6

by Tomaz Cerar (JIRA)

Hibernate search does not work in JBAS 6 ---------------------------------------- Key: JBSEAM-4698 URL: https://jira.jboss.org/browse/JBSEAM-4698 Project: Seam Issue Type: Bug Components: Search Affects Versions: 2.2.1.CR2 Environment: Jboss AS 6 M4, hibernate-search-3.2.1.Final, Jboss Seam 2.2.1.RC2 Reporter: Tomaz Cerar injection of FullTextEntityManager fails on jboss as 6 @In FullTextEntityManager entityManager; exception: Caused by: java.lang.IllegalArgumentException: could not set field value: searchAction.entityManager at org.jboss.seam.Component.setFieldValue(Component.java:1930) [:2.2.1.CR2] at org.jboss.seam.Component.access$600(Component.java:127) [:2.2.1.CR2] at org.jboss.seam.Component$BijectedField.set(Component.java:2966) [:2.2.1.CR2] at org.jboss.seam.Component.injectAttributes(Component.java:1739) [:2.2.1.CR2] at org.jboss.seam.Component.inject(Component.java:1557) [:2.2.1.CR2] at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:61) [:2.2.1.CR2] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [:2.2.1.CR2] at org.jboss.seam.transaction.TransactionInterceptor$1.work(TransactionInterceptor.java:97) [:2.2.1.CR2] at org.jboss.seam.util.Work.workInTransaction(Work.java:61) [:2.2.1.CR2] at org.jboss.seam.transaction.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:91) [:2.2.1.CR2] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [:2.2.1.CR2] at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) [:2.2.1.CR2] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [:2.2.1.CR2] at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) [:2.2.1.CR2] at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:185) [:2.2.1.CR2] at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:103) [:2.2.1.CR2] at com.parsekstores.catalog.SearchAction_$$_javassist_seam_9.validate(SearchAction_$$_javassist_seam_9.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_20] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_20] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_20] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_20] at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) [:2.2.1.CR2] at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) [:2.2.1.CR2] at org.jboss.seam.Component.callComponentMethod(Component.java:2275) [:2.2.1.CR2] at org.jboss.seam.Component.callCreateMethod(Component.java:2198) [:2.2.1.CR2] at org.jboss.seam.Component.newInstance(Component.java:2158) [:2.2.1.CR2] ... 85 more Caused by: java.lang.IllegalArgumentException: Could not set field value by reflection: SearchAction.entityManager on: com.parsekstores.catalog.SearchAction with value: class $Proxy266 at org.jboss.seam.util.Reflections.set(Reflections.java:86) [:2.2.1.CR2] at org.jboss.seam.Component.setFieldValue(Component.java:1926) [:2.2.1.CR2] ... 110 more Caused by: java.lang.IllegalArgumentException: Can not set org.hibernate.search.jpa.FullTextEntityManager field com.parsekstores.catalog.SearchAction.entityManager to $Proxy266 at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:146) [:1.6.0_20] at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:150) [:1.6.0_20] at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:63) [:1.6.0_20] at java.lang.reflect.Field.set(Field.java:657) [:1.6.0_20] at org.jboss.seam.util.Reflections.set(Reflections.java:71) [:2.2.1.CR2] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
13
0 / 0

[JBoss JIRA] Created: (JBSEAM-4689) Make SEAM work with Apache Tomcat 6 and unpackWARs="false"

by Cedrik Mayer (JIRA)

Make SEAM work with Apache Tomcat 6 and unpackWARs="false" ---------------------------------------------------------- Key: JBSEAM-4689 URL: https://jira.jboss.org/browse/JBSEAM-4689 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.1.CR1 Environment: Apache Tomcat 6.0.24, Ubuntu 10.4 Reporter: Cedrik Mayer Priority: Critical Fix For: 2.2.1.CR2 Attachments: 0001-Try-to-load-.page.xml-from-ServletContext-in-packed-.patch Currently SEAM is not able to run in a Tomcat that does not unpack its war files. This is because WarRootDeploymentStrategy + URLScanner is not capable of retrieving files from the ServletContext so that *.page.xml files won't be found. The attached patch tries to work around this problem but it's more of a hack than a bugfix. It does not work properly as the information from the *.page.xml is read but not fully used (e.g. rewrite pattern will work but s:link does not use them). And it also spits many warnings to the console regarding getRealPath()-failures. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3706) JEE5 Booking Example fails on Glassfish

by Dmitry Shultz (JIRA)

JEE5 Booking Example fails on Glassfish --------------------------------------- Key: JBSEAM-3706 URL: https://jira.jboss.org/jira/browse/JBSEAM-3706 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.SP1 Environment: Leopard OS X Server, latest Glassfish installation (9.1_02 (build b04-fcs)), Seam version from todays trunk. Reporter: Dmitry Shultz Priority: Blocker 1. Buld Seam, build JEE5 Booking Example, deploy it on Glassfish using Web Interface. 2. Create new User, do login 3. Go to the Search Hotels page, put letter 'd' in the input field, press Find Hotels 4. Click on 'View Hotel' Link for top hotel, you should see the seam.debug page. -- 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

15 years, 4 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4443) Clustering Seam Application + Drools Serialization exception

by Karl Max (JIRA)

Clustering Seam Application + Drools Serialization exception ------------------------------------------------------------ Key: JBSEAM-4443 URL: https://jira.jboss.org/jira/browse/JBSEAM-4443 Project: Seam Issue Type: Bug Components: Drools Affects Versions: 2.2.0.GA Environment: Windows Vista, Seam 2.2.0.GA, JBoss 5.1.0.GA, Eclipse 3.5, JBoss Tools latest,Java 6 (latest) Reporter: Karl Max http://seamframework.org/Community/ClusteringSeamApplicationDroolsSeriali... I try eliminite this problem by using of drools rule agent+Drools Guvnor, but It was not scuccess I get the same exception. -- 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

15 years, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBSEAM-4710) Seam gen forgot "base package name" in the next setup action...

by hantsy bai (JIRA)

Seam gen forgot "base package name" in the next setup action... --------------------------------------------------------------- Key: JBSEAM-4710 URL: https://jira.jboss.org/browse/JBSEAM-4710 Project: Seam Issue Type: Bug Affects Versions: 2.2.1.CR2 Environment: Windows 7 32bit, Sun Java 6 update 21, ant 1.8.1 Reporter: hantsy bai I run "seam setup" in the seam folder to config seam, after create first project.. When I run the "seam setup" again, my customized "base package name" value is missing, it use the default value of seam. It should remember my settings like other option and display it in the next time. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-4702) NPE at org.richfaces.renderkit.PickListRenderer.getConvertedItems(PickListRenderer.java:531)

by Flo Gle (JIRA)

NPE at org.richfaces.renderkit.PickListRenderer.getConvertedItems(PickListRenderer.java:531) -------------------------------------------------------------------------------------------- Key: JBSEAM-4702 URL: https://jira.jboss.org/browse/JBSEAM-4702 Project: Seam Issue Type: Bug Affects Versions: 2.2.1.CR2 Environment: Jboss AS 5.1, Linux Reporter: Flo Gle <rich:pickList id="myid" value="#{orderCriteria.selectedSessions}"> <s:selectItems var="_session" noSelectionLabel="Please select ..." value="#{sessionList.resultList}" label="#{_session.name} - #{_session.date}" /> <s:convertEntity /> </rich:pickList> works with 2.2.1.CR1 but not with 2.2.1.CR2. It also works with 2.2.1.CR2 if i use richfaces*jar from 2.2.1.CR1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-4675) LogImpl.interpolate() is broken

by Stephan Bublava (JIRA)

LogImpl.interpolate() is broken ------------------------------- Key: JBSEAM-4675 URL: https://jira.jboss.org/browse/JBSEAM-4675 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.1.CR1 Reporter: Stephan Bublava This is the implementation of LogImpl.interpolate(): private Object interpolate(Object object, Object... params) { if (object instanceof String) { try { return Interpolator.instance().interpolate( (String) object, params ); } catch (Exception e) { log.error("exception interpolating string: " + object, e); } finally { return object; } } else { return object; } } The return statement in the finally block is bogus, because it trumps the other one. In other words the method always returns "object" and discards the result of the interpolation. This is a regression from 2.2.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
1
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 2010