October 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2029) Identity.checkEntityPermission() fails for entities mapped using orm.xml or .hbm.xml

by Pete Muir (JIRA)

Identity.checkEntityPermission() fails for entities mapped using orm.xml or .hbm.xml ------------------------------------------------------------------------------------ Key: JBSEAM-2029 URL: http://jira.jboss.com/jira/browse/JBSEAM-2029 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 2.0.0.CR1 Reporter: Pete Muir Assigned To: Shane Bryzak Fix For: 2.0.1.GA Entity.forClass() isn't a great way to determine the entity's Class and should be done through PersistenceProvider -- 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

16 years, 9 months

4
24
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2171) Converter implementations for java 1.5 atomic classes

by Dennis Byrne (JIRA)

Converter implementations for java 1.5 atomic classes ----------------------------------------------------- Key: JBSEAM-2171 URL: http://jira.jboss.com/jira/browse/JBSEAM-2171 Project: JBoss Seam Issue Type: Feature Request Components: Core Environment: head Reporter: Dennis Byrne Assigned To: Dennis Byrne Attachments: AtomicBooleanConverter.java, AtomicIntegerConverter.java, AtomicLongConverter.java I am having some political problems getting this into Tomahawk (which is living in a java 1.4 world). The work is here and it's tested. I think this would be a good addition to Seam, considering that Seam has done so much w/ the other stuff that came out in 1.5. I intend to document this, so please advise on what the protocol is. Also, I looked around the code base and couldn't find a faces-config to register these. -- 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

16 years, 10 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1811) DefaultActionListener is not call when using s:link

by Andy Bosch (JIRA)

DefaultActionListener is not call when using s:link --------------------------------------------------- Key: JBSEAM-1811 URL: http://jira.jboss.com/jira/browse/JBSEAM-1811 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.1.GA Environment: Jboss 4.0.5 GA and JBoss 4.2.0 Reporter: Andy Bosch In JSF in faces-config.xml you can create your own actionlistener with <action-listener> com.company.MyActionListener </action-listener> This actionlistener will be executed each time, a commandLink or commandButton is pressed. When using s:link or s:button the actionlistener is not called. -- 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

16 years, 10 months

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1542) Identify process not only by root token, to allow for concurrency

by Gavin King (JIRA)

Identify process not only by root token, to allow for concurrency ----------------------------------------------------------------- Key: JBSEAM-1542 URL: http://jira.jboss.com/jira/browse/JBSEAM-1542 Project: JBoss Seam Issue Type: Feature Request Components: BPM Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.GA Currently we identify the process by the process id, and ignore the fact that jBPM allows fork-and-join using multiple Tokens. This is inflexible, especially for service orchestration. -- 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

16 years, 10 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2111) coerceToType / javaassist error when converting types for multi selection

by Damian Harvey (JIRA)

coerceToType / javaassist error when converting types for multi selection ------------------------------------------------------------------------- Key: JBSEAM-2111 URL: http://jira.jboss.com/jira/browse/JBSEAM-2111 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR2 Environment: Mac OSX. Jboss 4.2.1, Java 1.5 Reporter: Damian Harvey When trying to display values in an h:selectManyCheckbox I get an error: java.lang.IllegalArgumentException: Cannot convert com.locuslive.odyssey.entity.Groups@3960f3 of typ e class com.locuslive.odyssey.entity.Groups to class com.locuslive.odyssey.entity.Groups_$$_javassis t_219 I have created a very basic project with PERSON, GROUP and PERSONGROUP entities. I've attached it after emptying the lib directory. Essentially on the PersonEdit page I want to be able to select which Groups the Person may belong to. This is done with the selectManyCheckbox. The checkbox is populated with a list of GROUPs from a GroupList. It is bound to a variable in the PersonHome called 'groups'. This is a list of Groups that is extracted from the PersonGroup table for that user. The stacktrace is in the forum post. I have also generated the attached project under Seam 1.2.1.GA and the problem is not there. -- 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

16 years, 10 months

4
17
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1585) Update portal example to JBoss AS 4.2.0.GA

by Pete Muir (JIRA)

Update portal example to JBoss AS 4.2.0.GA ------------------------------------------ Key: JBSEAM-1585 URL: http://jira.jboss.com/jira/browse/JBSEAM-1585 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir -- 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

16 years, 10 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2107) Seam example "seampay", asynchronous scheduler don't work on Tomcat with JBoss Embedded

by Stateless Bean (JIRA)

Seam example "seampay", asynchronous scheduler don't work on Tomcat with JBoss Embedded --------------------------------------------------------------------------------------- Key: JBSEAM-2107 URL: http://jira.jboss.com/jira/browse/JBSEAM-2107 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 1.1.6.GA Environment: windows xp, java 1.5 SDK and 1.6 SDK, tomcat 5.5.13 and 6.0 Postgresql 8.2 Reporter: Stateless Bean Fix For: 2.0.0.GA I try to run example seampay on tomcat with Jboss embedded, but seam asynchonos scheduler doesn't work on tomcat, Since 1.1.6 ver. of seam still I get null. On JBoss 4.0.5 example work fine! -- 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

16 years, 10 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2132) consult class attribute on component XML declaration with namespace

by Dan Allen (JIRA)

consult class attribute on component XML declaration with namespace ------------------------------------------------------------------- Key: JBSEAM-2132 URL: http://jira.jboss.com/jira/browse/JBSEAM-2132 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Reporter: Dan Allen Assigned To: Dan Allen Priority: Critical Fix For: 2.0.1.GA When a component template class is being configured (such as EntityHome, EntityQuery, etc), the class attribute should be considered prior to deriving the class name from the namespace info + XML element name. Doing so prevents the case where two components are being configured for the same name when the developer intends only to use it for configuration. Case in point: Let's say I create a class that extends EntityHome to provide some extra behavior. @Name("myEntityHome") public class MyEntityHome extends EntityHome { } Now I want to configure the properties of this class in components.xml <framework:entity-home name="myEntityHome" class="org.example.model.MyEntityHome"> <framework:created-message>You created it! Yeah!</framework:created-message> <framework:updated-message>You updated it! Yeah!</framework:updated-message> <framework:deleted-message>You deleted it! Yeah!</framework:deleted-message> </framework:entity-home> If the class attribute is not consulted, it will look for a @Name annotation on org.jboss.seam.framework.EntityHome rather than org.example.model.MyEntityHome. When it doesn't find one on the built-in class, it tries to create a new component definition. Why would I want to use XML namespace tags in this case? Simple. Tag completion and property recognition support. Note that this works if the class resolved from XML namespace + element name is the same as the component class. In the case when the component class extends the built-in class, you get this problem. -- 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

16 years, 10 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2151) Document and use com.ibm.ws.webcontainer.invokefilterscompatibility with ajax4jsf in hibernate2/jpa examples

by Pete Muir (JIRA)

Document and use com.ibm.ws.webcontainer.invokefilterscompatibility with ajax4jsf in hibernate2/jpa examples ------------------------------------------------------------------------------------------------------------ Key: JBSEAM-2151 URL: http://jira.jboss.com/jira/browse/JBSEAM-2151 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Priority: Trivial Fix For: 2.0.1.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

16 years, 10 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2106) References to Hibernate entities in a list are null after returning from nested conversation

by Gabor Nagypal (JIRA)

References to Hibernate entities in a list are null after returning from nested conversation -------------------------------------------------------------------------------------------- Key: JBSEAM-2106 URL: http://jira.jboss.com/jira/browse/JBSEAM-2106 Project: JBoss Seam Issue Type: Bug Environment: Seam 2 CR 2, Windows XP, JDK 1.6b02 Reporter: Gabor Nagypal If a conversation- scope bean contains a list that references Hibernate entities, the references are nullified when the application returns from a nested 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

16 years, 10 months

3
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues October 2007