May 2011 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2764) Factory method does not create objects properly

by Bogdan Minciu (JIRA)

Factory method does not create objects properly ----------------------------------------------- Key: JBSEAM-2764 URL: http://jira.jboss.com/jira/browse/JBSEAM-2764 Project: JBoss Seam Issue Type: Bug Components: EJB3 Affects Versions: 2.0.1.GA Reporter: Bogdan Minciu Hello, It seems that my @Factory method is recognizing the created objects only in its command block. I have this class: @Stateful @Name("xtw") @Scope(ScopeType.SESSION) @AutoCreate public class XTextSessionWrapper implements LocalXTextSessionWrapper { ... @In(required=false, create=true) @Out private XLanguage activeLanguage; public String getText(String identifier) { log.info("getText(1): identifier= #0, activeLanguage= #1", identifier, getActiveLanguage()); XTextEntry xte = xTextEntryDAO.findXTextEntry(identifier, getActiveLanguage()); log.info("getText(2): identifier= #0, activeLanguage= #1", identifier, getActiveLanguage()); xte.getXtext(); } @Factory(value="activeLanguage", autoCreate=true) public void initActiveLanguage() { XLanguage xl = xLanguageDAO.findXLanguageByIdentifier("ro"); log.info("initActiveLanguage(1): activeLanguage initialized to #0", xl.getIdentifier()); setActiveLanguage(xl); log.info("initActiveLanguage(1): activeLanguage initialized to #0", getActiveLanguage().getIdentifier()); } public XLanguage getActiveLanguage() { return activeLanguage; } public void setActiveLanguage(XLanguage activeLanguage) { this.activeLanguage = activeLanguage; } ... } And i am calling the getText() method. The method calling is as expected: 1. the injected activeLanguage is detecting that it has a null value, 2. the initActiveLanguage() factory method is called 3. then the getText() method is continuing its execution. But, the problem is that when the application exists the @Factory method block, the created objects: activeLanguage is lost and reported again as null. Here is the output: 12:43:48,203 INFO [XTextSessionWrapper] initActiveLanguage(1): activeLanguage initialized to ro 12:43:48,203 INFO [XTextSessionWrapper] initActiveLanguage(1): activeLanguage initialized to ro 12:43:48,703 INFO [XTextSessionWrapper] initActiveLanguage(1): activeLanguage initialized to ro 12:43:48,703 INFO [XTextSessionWrapper] initActiveLanguage(1): activeLanguage initialized to ro 12:43:48,703 INFO [XTextSessionWrapper] getText(1): identifier= com.brit.xcms.cms.Category.12.name, activeLanguage= null 12:43:49,234 INFO [XTextSessionWrapper] getText(2): identifier= com.brit.xcms.cms.Category.12.name, activeLanguage= null Where did I went wrong? Why is the activeLanguage factoried value lost when i leave the initActiveLanguage() 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

11 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMREST-1) Support validating @FormParams, @QueryParams, @Headers, etc

by Jozef Hartinger (JIRA)

Support validating @FormParams, @QueryParams, @Headers, etc ----------------------------------------------------------- Key: SEAMREST-1 URL: https://jira.jboss.org/browse/SEAMREST-1 Project: Seam RESTEasy Issue Type: Feature Request Components: Bean Validation Reporter: Jozef Hartinger Currently, only message body parameters and @Form objects are validated. Provide support for validating @*Param parameters as well. -- 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

11 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-29) Create an example demonstrating usage of Hibernate as the persistence provider

by Ondrej Skutka (JIRA)

Create an example demonstrating usage of Hibernate as the persistence provider ------------------------------------------------------------------------------ Key: SEAMPERSIST-29 URL: https://issues.jboss.org/browse/SEAMPERSIST-29 Project: Seam Persistence Issue Type: Task Reporter: Ondrej Skutka Fix For: 3.0.0.Final -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-49) Seam Persistence Fails in clustered environment

by Thomas Andraschko (JIRA)

Seam Persistence Fails in clustered environment ----------------------------------------------- Key: SEAMPERSIST-49 URL: https://issues.jboss.org/browse/SEAMPERSIST-49 Project: Seam Persistence Issue Type: Bug Affects Versions: 3.0.0.Final Environment: Tomcat 7.0.14 with memchached session manager, Myfaces 2.0.5, Weld 1.1.2-SNAPSHOT, Persistence 3.0.0.Final, Faces 3.0.1.Final, XML Config 3.0.0.Final, Hibernate 3.6.4 Reporter: Thomas Andraschko Priority: Critical Session replication fails when using Seam Persistence. Following exceptions occurs: WARNING: Cannot serialize session attribute org.jboss.weld.context.http.HttpSessionContext#org.jboss.weld.bean-flat-ManagedBean-TestController[@javax.enterprise.context.SessionScoped()@javax.inject.Named(value=)]{TestController.userDao[@javax.inject.Inject()];TestController.newUser[@org.jboss.seam.transaction.Transactional(value=REQUIRED)@org.jboss.seam.transaction.TransactionalInterceptorBinding()]();TestController.post[(a)javax.annotation.PostConstruct()]();} for session 488BDFEE2194D758C7B76C6E60E6BD5E-n2 java.io.NotSerializableException: org.jboss.seam.transaction.TransactionExtension at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) at java.util.ArrayList.writeObject(ArrayList.java:570) 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:597) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:422) at java.util.Collections$SynchronizedCollection.writeObject(Collections.java:1602) 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:597) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) at de.javakaffee.web.msm.JavaSerializationTranscoder.writeAttributes(JavaSerializationTranscoder.java:143) at de.javakaffee.web.msm.JavaSerializationTranscoder.serializeAttributes(JavaSerializationTranscoder.java:106) at de.javakaffee.web.msm.TranscoderService.serializeAttributes(TranscoderService.java:138) at de.javakaffee.web.msm.BackupSessionTask.serializeAttributes(BackupSessionTask.java:177) at de.javakaffee.web.msm.BackupSessionTask.call(BackupSessionTask.java:111) at de.javakaffee.web.msm.BackupSessionTask.call(BackupSessionTask.java:48) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Why is it stored in the session? Can it be made serializable? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (SEAMXML-25) Introduce s:values tag

by Jozef Hartinger (JIRA)

Introduce s:values tag ---------------------- Key: SEAMXML-25 URL: https://issues.jboss.org/browse/SEAMXML-25 Project: Seam Config Issue Type: Feature Request Affects Versions: 3.0.0.Beta1 Reporter: Jozef Hartinger Priority: Minor Currently, it is quite verbose to populate a collection with configured object instances using the XML module. For example: Foo is a class having a collection (bars) of Bars <e:Foo> <e:bars> <s:value> <e:Bar id="1"/> </s:value> <s:value> <e:Bar id="2"/> </s:value> <s:value> <e:Bar id="3"/> </s:value> <s:value> <e:Bar id="4"/> </s:value> </e:bars> </e:Foo> If the s:values tag is introduced, it'll make the configuration less verbose <e:Foo> <e:bars> <s:values> <e:Bar id="1"/> <e:Bar id="2"/> <e:Bar id="3"/> <e:Bar id="4"/> </s:values> </e:bars> </e:Foo> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-23) Document why the user cannot do @Inject em and the advantages Seam Persistence gives over straight EE injection

by Stuart Douglas (JIRA)

Document why the user cannot do @Inject em and the advantages Seam Persistence gives over straight EE injection --------------------------------------------------------------------------------------------------------------- Key: SEAMPERSIST-23 URL: https://issues.jboss.org/browse/SEAMPERSIST-23 Project: Seam Persistence Issue Type: Task Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMXML-19) Seam XML tests should be more fine grained

by Stuart Douglas (JIRA)

Seam XML tests should be more fine grained ------------------------------------------ Key: SEAMXML-19 URL: https://jira.jboss.org/browse/SEAMXML-19 Project: Seam XML Bean Config Issue Type: Bug Affects Versions: 3.0.0.Alpha2 Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 3.0.0.Beta1 -- 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

11 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (SEAMXML-22) support collection and array virtual fields

by Dan Allen (JIRA)

support collection and array virtual fields ------------------------------------------- Key: SEAMXML-22 URL: https://jira.jboss.org/browse/SEAMXML-22 Project: Seam XML Configuration Issue Type: Feature Request Affects Versions: 3.0.0.Beta1 Reporter: Dan Allen Fix For: 3.0.0.Beta2 Add support for defining virtual fields that are of type collection or array. This should work already in theory, but no matter what I tried, I got errors, so it may simply be broken. There is also one piece missing. There needs to be a way to specify the collection type parameter (item type). I'm envisioning something like this: <List> <Integer/> <-- defines item type <app:DiceValues/> <value>1</value> <value>2</value> <value>3</value> <value>4</value> <value>5</value> <value>6</value> </List> defines the virtual field: @DiceValues List<Integer> anonymous; In the same way, we should support virtual arrays: <array> <Integer/> <app:DiceValues/> <value>1</value> <value>2</value> <value>3</value> <value>4</value> <value>5</value> <value>6</value> </array> producing: @DiceValues Integer[] anonymous; The nested element for the type is a bit awkward, though (I suggested it because it's currently how array's are typed). It would make more sense to use an attribute here: <List itemType="java.lang.Integer"> ... </List> Also, a way to control the implementation type: <List type="java.util.ArrayList" itemType="java.lang.Integer"> ... </List> Once working, there definitely needs to be an example (or two) added to the documentation. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (SOLDER-54) Expand documentation for generic beans

by Dan Allen (JIRA)

Expand documentation for generic beans -------------------------------------- Key: SOLDER-54 URL: https://issues.jboss.org/browse/SOLDER-54 Project: Seam Solder Issue Type: Feature Request Components: Documentation Affects Versions: 3.0.0.Beta1 Reporter: Dan Allen Assignee: Stuart Douglas Priority: Minor Fix For: 3.0.0.CR1 Expand the documentation for generic beans and add another example. This is a feature developers will need to see to understand, so the more ways to look at it, the better. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (SOLDER-71) org.jboss.seam.solder.bean is in impl when it should be in api

by Stuart Douglas (JIRA)

org.jboss.seam.solder.bean is in impl when it should be in api -------------------------------------------------------------- Key: SOLDER-71 URL: https://issues.jboss.org/browse/SOLDER-71 Project: Seam Solder Issue Type: Bug Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2011