October 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMPERSIST-55) @Transactional annotation on @SessionScoped bean fails on cluster

by Marek Schmidt (JIRA)

@Transactional annotation on @SessionScoped bean fails on cluster ----------------------------------------------------------------- Key: SEAMPERSIST-55 URL: https://issues.jboss.org/browse/SEAMPERSIST-55 Project: Seam Persistence Issue Type: Bug Affects Versions: 3.0.0.Final Environment: JBoss AS 6.1 SNAPSHOT, mod_jk Reporter: Marek Schmidt Assignee: Stuart Douglas Fix For: Future a session containing a @Transactional @SessionScoped bean fails to replicate with {quote} [org.infinispan.interceptors.InvocationContextInterceptor] (ajp-127.0.1.1-8009-2) Execution error: : org.infinispan.CacheException: java.lang.RuntimeException: Failure to marshal arguments(s) at org.infinispan.util.Util.rewrapAsCacheException(Util.java:477) [:4.2.0.FINAL] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommands(CommandAwareRpcDispatcher.java:123) [:4.2.0.FINAL] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:399) [:4.2.0.FINAL] ... Caused by: java.lang.RuntimeException: Failure to marshal argument(s) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher$ReplicationTask.marshallCall(CommandAwareRpcDispatcher.java:243) [:4.2.0.FINAL] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher$ReplicationTask.call(CommandAwareRpcDispatcher.java:270) [:4.2.0.FINAL] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommands(CommandAwareRpcDispatcher.java:121) [:4.2.0.FINAL] ... 76 more Caused by: org.infinispan.CacheException: Unable to marshall value AtomicHashMap{delegate=org.infinispan.util.FastCopyHashMap@32ed99af} at org.infinispan.marshall.MarshalledValue.serialize(MarshalledValue.java:100) [:4.2.0.FINAL] at org.infinispan.marshall.MarshalledValue.getRaw(MarshalledValue.java:156) [:4.2.0.FINAL] at org.infinispan.marshall.MarshalledValue$Externalizer.writeObject(MarshalledValue.java:248) [:4.2.0.FINAL] ... Caused by: java.io.NotSerializableException: org.jboss.seam.transaction.DefaultSeamTransaction at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) [:1.6.0_24] {quote} No that in this environment, the workaround for SEAMPERSIST-49 doesn't help. -- 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

[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-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: (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: (SEAMCONFIG-46) Typos in documentation

by Jozef Hartinger (JIRA)

Typos in documentation ---------------------- Key: SEAMCONFIG-46 URL: https://issues.jboss.org/browse/SEAMCONFIG-46 Project: Seam Config Issue Type: Bug Components: Documentation Affects Versions: 3.0.0.Final Reporter: Jozef Hartinger Assignee: Stuart Douglas Priority: Minor Fix For: Future * seperating * availible * precidence * modifiying * Inital * eligable * functionallity -- 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

[JBoss JIRA] Created: (SOLDER-124) GenericBeanAlternativeTest fails on AS7

by Marek Schmidt (JIRA)

GenericBeanAlternativeTest fails on AS7 --------------------------------------- Key: SOLDER-124 URL: https://issues.jboss.org/browse/SOLDER-124 Project: Seam Solder Issue Type: Bug Components: Generic Beans Affects Versions: 3.1.0.Beta2 Environment: jboss-as-7.0.1.Final Reporter: Marek Schmidt test passes on AS6 and Weld Embedded, fails on AS7 and Glassfish 3.1.1 testGenericAlternatives(org.jboss.solder.test.bean.generic.alternative.GenericBeanAlternativeTest): null expected:<[Alternative ]Big Bam> but was:<[]Big Bam> testGenericProducerMethodAlternatives(org.jboss.solder.test.bean.generic.alternative.GenericBeanAlternativeTest): null expected:<[Alternative ]Big Bam> but was:<[]Big Bam> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

9
15
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

[JBoss JIRA] Created: (SEAMFACES-193) PrettyFaces URL rewriting is not happening when intercepted via @LoginView

by Bill Elliot (JIRA)

PrettyFaces URL rewriting is not happening when intercepted via @LoginView -------------------------------------------------------------------------- Key: SEAMFACES-193 URL: https://issues.jboss.org/browse/SEAMFACES-193 Project: Seam Faces Issue Type: Bug Components: Security, View Configuration Affects Versions: 3.0.2 Environment: JBoss AS6, Seam Faces 3.0.2, PrettyFaces 2.2 Reporter: Bill Elliot When starting as not logged in and you request a page mapped with PrettyFaces that has a security constraint (defined in pages @ViewConfig) which has a @LogonView, you are sent to the login screen first. Then once you login successfully you are takes to the requested page, but without the PrettyFaces URL rewriting. You get the raw URL. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues October 2011