December 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2240) refactor for easier extensibility of seam identity: seam identiy interface + seam identity base impl

by koen handekyn (JIRA)

refactor for easier extensibility of seam identity: seam identiy interface + seam identity base impl ---------------------------------------------------------------------------------------------------- Key: JBSEAM-2240 URL: http://jira.jboss.com/jira/browse/JBSEAM-2240 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.GA Reporter: koen handekyn Priority: Optional to allow easier extensibility of the seam identity class it would be useful to have a clear seam identity interface with complementary base impl from (package org.jboss.seam.security) use case: i'm trying to define my own seam identiy that contains as an extra parameter domain (login@domain/password). to have a complete implementation (which also saves the domain into a cookie) i'm stuck as 1. i don't know have an interface that I should satisfy if I wanted to make an implementation from scratch 2. extending from seam idenity has some issues : i missing some protected accessors to some private members (that maybe could be protected?) alternatively my question would be solved if i could have extension points within initFromCookie and at "setCookieValueIfEnabled( getUsername() ); from method postAuthenticate()" such that i could combine and split login and domain when saving/reading the cookie. -- 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

14 years, 8 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4229) RichFaces loses skin with login-required="true" in pages.xml

by Moritz Winter (JIRA)

RichFaces loses skin with login-required="true" in pages.xml ------------------------------------------------------------ Key: JBSEAM-4229 URL: https://jira.jboss.org/jira/browse/JBSEAM-4229 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.CR2 Environment: Seam 2.1.1.GA on JBoss 5.0.0.GA. Reporter: Moritz Winter -- 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

14 years, 8 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4399) Specify the Quartz job name for @Asynchronous methods

by Nikolay Elenkov (JIRA)

Specify the Quartz job name for @Asynchronous methods ----------------------------------------------------- Key: JBSEAM-4399 URL: https://jira.jboss.org/jira/browse/JBSEAM-4399 Project: Seam Issue Type: Feature Request Affects Versions: 2.2.0.GA Environment: JBoss 4.2.x, JBoss 5.x, Quartz Reporter: Nikolay Elenkov Attachments: quartz-job-name.patch When using the Quartz dispatcher, Seam implements asynchronous methods by creating Quartz job and trigger for every method, annotated with @Asynchronous. The QuartzDispatcher class uses UIDs for the job and trigger names, in order to generate unique names. While this is OK for one-off jobs and asynchronous events, it is not suitable for repeatable and cron jobs that might have to be paused, cancelled or rescheduled by the application. Jobs should have meaningful names, especially when they are saved in a database store. Requesting a means to specify the Quartz job name when declaring an asynchronous method. One way to do this is to add a new parameter annotation, JobName. The Quartz dispatcher should inspect the asynchronous method parameters and use the one annotated with @JobName (if any) as the base for the job/trigger name. -- 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

14 years, 8 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3938) Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them.

by John Sublette (JIRA)

Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them. --------------------------------------------------------------------------------------------------- Key: JBSEAM-3938 URL: https://jira.jboss.org/jira/browse/JBSEAM-3938 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Environment: SEAM 2.1.1.GA with seam-resteasy patch described in https://jira.jboss.org/jira/browse/JBSEAM-3449, and RestEasy 1.0.1.GA. Reporter: John Sublette Priority: Minor Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them as described in RestEasy's documentation (section 28.2 - Sharing an interface...). An interface with tagged @Path throws an exception when it is registered - because an interface doesn't have a constructor. See org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap Line 112 through 138 for how RestEasy handles this by default - (using Scannotation) -- 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

14 years, 9 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4192) s.tld in jboss-seam.ui.jar/MANIFEST.MF/ is not valid

by Wolfgang Schwach (JIRA)

s.tld in jboss-seam.ui.jar/MANIFEST.MF/ is not valid ---------------------------------------------------- Key: JBSEAM-4192 URL: https://jira.jboss.org/jira/browse/JBSEAM-4192 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.1.2.CR2 Environment: all platforms Reporter: Wolfgang Schwach s.tld in jboss-seam.ui.jar/MANIFEST.MF/ is not valid as it contains two errors. There are two attribute entries in s.tld that are invalid according to the schema defined in http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd . These attribute entries can easily be found as both contain the words "Alias for" in their description element. It's my guess that these two entries are generated out of the alias entries in \ui\src\main\config\component\selectItems.xml -- 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

14 years, 9 months

6
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4460) <begin-conversation killPrevious="true"/>

by deanhiller (JIRA)

<begin-conversation killPrevious="true"/> ----------------------------------------- Key: JBSEAM-4460 URL: https://jira.jboss.org/jira/browse/JBSEAM-4460 Project: Seam Issue Type: Feature Request Affects Versions: 2.2.0.GA, 2.2.0.CR1, 2.1.2.GA, 2.1.2.CR2 Reporter: deanhiller Please please please add the ability to kill the previous conversation when starting a new one. Nearly all seam code I have seen for starting a conversation would typically use this as this is typically the default that would be wanted(but does not yet exist). For backwards compatibility, keep the default false I guess, BUT have a property in components.xml or somewhere where developers can set previousKillDefaultValue="true" so the default will be true for all of my current begin conversation tags. I have looked in my project and start 16 conversations in different places all of which want to kill off the previous conversation instead of a debug.xhtml page popping up (or in production, the "a bug has occurred in our software, we are sorry for the inconvenience". thanks, Dean -- 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

14 years, 9 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3996) Seam should ignore duplicate classes on classpath

by Max Rydahl Andersen (JIRA)

Seam should ignore duplicate classes on classpath ------------------------------------------------- Key: JBSEAM-3996 URL: https://jira.jboss.org/jira/browse/JBSEAM-3996 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA, 2.1.0.SP1 Reporter: Max Rydahl Andersen Assignee: Dan Allen Fix For: 2.1.2.GA As discussed in JBIDE-3623 then Seam is reporting "Two components with the same name and precedence - component name: <name>, component classes: <classname>" when the class name is exactly the same. In that case it should only be the one that is first on the classpath that is used; that the class exist in other locations is irrelevant since you won't be able to load the class anyway since in java classloading first-found wins. -- 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

14 years, 9 months

5
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2095) Multiple DataSources in same EAR, hib2ddl and import.sql run on all

by Ian Darwin (JIRA)

Multiple DataSources in same EAR, hib2ddl and import.sql run on all ------------------------------------------------------------------- Key: JBSEAM-2095 URL: http://jira.jboss.com/jira/browse/JBSEAM-2095 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.CR1 Environment: EAR deployment, POJO beans setup by Seam-Gen. OS not relevant; tried JDK1.6 and 1.7EA. DB is PostgreSQL 8. Reporter: Ian Darwin When using multiple DataSources in an EJB3 EAR, as suggested by Gavin the the URL referenced below, using Hibernate as the underlying persistence, it appears that the "schema export" and the /import.sql get applied to both. It would be nice if there could be a more fine-grained mechanism for associating import.sql and hbm2ddl with particular entities. I have two Datasources, call them "all" and "bugs" (the idea being that the bugs database will be shared by all developers and should be permanent, whereas the "all" database should be dropped and recreated/imported each tim). 16:07:55,345 INFO [SchemaExport] Running hbm2ddl schema export 16:07:55,345 INFO [SchemaExport] exporting generated schema to database 16:07:55,504 INFO [SchemaExport] Executing import script: /import.sql 16:07:55,568 INFO [SchemaExport] schema export complete ... 16:07:55,710 INFO [SchemaExport] Running hbm2ddl schema export 16:07:55,711 INFO [SchemaExport] exporting generated schema to database 16:07:55,857 INFO [SchemaExport] Executing import script: /import.sql 16:07:55,911 INFO [SchemaExport] schema export complete It would be most convenient if one could specify more precisely which entities go in which Schema. I have added the @PersistenceContext annotation on the BugsHome class' EntityManager: @PersistenceUnit(name="tcpseambug") @In EntityManager bugEntityManager; public EntityManager getEntityManager() { return bugEntityManager; } Note that if I disable the hbm2ddl export on the "bugs" database, then schema setup quits when one of the tables in the "all" database shows up missing. N.B. Will be happy to write up a complete example for the Reference Manual once this is working :-), as there are several related questions on the Forums. -- 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

14 years, 9 months

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3744) Security in components.xml not isolated between wars in ear in Seam 2.1.0. Identity component should be scoped to the WAR module

by Susanne Jarl (JIRA)

Security in components.xml not isolated between wars in ear in Seam 2.1.0. Identity component should be scoped to the WAR module -------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3744 URL: https://jira.jboss.org/jira/browse/JBSEAM-3744 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.0.SP1 Environment: JBoss AS 4.2.3 SDK 6 Reporter: Susanne Jarl This is exactly the same problem as described in JBSEAM-2523. I have no myFacesExtension filter in my web.xml and this worked perfectly fine with Seam 2.0.2.GA. You can also read my forum post: http://www.seamframework.org/Community/ComponentsxmlNotIsolatedBetweenWar... -- 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

14 years, 9 months

6
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3903) CRUD is conversational, but seam-gen apps are not conversational enough

by Francisco Jose Peredo Noguez (JIRA)

CRUD is conversational, but seam-gen apps are not conversational enough ----------------------------------------------------------------------- Key: JBSEAM-3903 URL: https://jira.jboss.org/jira/browse/JBSEAM-3903 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.0.SP1 Reporter: Francisco Jose Peredo Noguez Lets say you have 2 classes: class Parent{ private Long id; private Integer version; private String name; private Set <Child> children; } and class Child{ private Long id;private Integer version; private String name; private Parent parent; } with a typical one to many / many to one relationship (Parent.children.Child/Child.parent.Parent) So you want them to become @Entities and add the required @Annotations. Then you run seam-gen on them, and run you generated application: 1. You click the Parent List menu option. 2. You are presented with the page ParentList.seam that allows you search parents, or to create a new one. 3. You click the Create parent button. 4. You write a name for the parent: "Peter". 5. You click "Save". 6. You are presented with the page Parent.seam, that displays you newly persisted entity in a "read-only way" 7. You click "Done" so far so good... but then 1. You click the Child List menu option. 2. You are presented with the page ChildList.seam that allows you search children, or to create a new one 3. You click the Create child button. 4. You are presented with the page ChildEdit.seam. 5. You write a name for your new Child entity: "John" 6. You decide that you want connect this new Child entity with a parent entity, and then you click "Select parent". 7. You are presented again with ParentList.seam that allows you to "select" a parent. 8. So, you select "Peter" by clicking in the "Select" link 9. And you return to ChildEdit.seam, but the value for the name property of the Child is now LOST. I think seam-gen should be able to do this correctly (without losing the values in ChildEdit.seam). -- 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

14 years, 9 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2009