January 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-967) JBoss Seam - Support authentication from a realm (on Tomcat)

by Bradley Smith (JIRA)

JBoss Seam - Support authentication from a realm (on Tomcat) ------------------------------------------------------------ Key: JBSEAM-967 URL: http://jira.jboss.com/jira/browse/JBSEAM-967 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Bradley Smith Please see discussion in the JBoss forum reference. The idea is to allow the Seam Identity (security) component to get the Principal from the HttpServletRequest and to delegate the hasRole() calls to the HttpServletRequest as well. This is because, in my case, Tomcat has already forced the user to authenticate if necessary and the authentication, authorization information is available in the container's HttpServletRequest impl. Principal userPrincipal = httpServletRequest.getUserPrincipal(); boolean hasRole(String roleName) { return httpServletRequest.isUserInRole(roleName); } public String getUsername() { return httpServletRequest.getRemoteUser(); } public boolean isLoggedIn() { return httpServletRequest.getUserPrincipal() != null; } -- 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

15 years, 7 months

4
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2523) Identity component should be scoped to the WAR module

by Reind D (JIRA)

Identity component should be scoped to the WAR module ----------------------------------------------------- Key: JBSEAM-2523 URL: http://jira.jboss.com/jira/browse/JBSEAM-2523 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 2.0.1.CR1 Environment: JBoss 4.2.2.GA (also tested on 4.2.0.GA) Reporter: Reind D I have an EAR with two web modules. I have configured the 'Identity authenticateMethod' in components.xml to use a different a method for each WAR (authA.authenticate, authB.authenticate). When attempting to login to the 'b' webapp it invokes the authenticateMethod defined in a.war. Attempting to login to the 'a' webapp works as expected. It appears as though the Identity component is not scoped to the WAR. The EAR is packaged as follows: my-application.ear/ a.war/ WEB-INF/ components.xml ... b.war/ WEB-INF/ components.xml ... web.jar Congure authentication as follows in both components.xml files: a.war/WEB-INF/components.xml <security:identity authenticate-method="#{authA.authenticate}" /> b.war/WEB-INF/components.xml <security:identity authenticate-method="#{authB.authenticate}" /> -- 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

15 years, 7 months

6
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1587) page parameters: option to bypass model-based validations

by Hung Tang (JIRA)

page parameters: option to bypass model-based validations --------------------------------------------------------- Key: JBSEAM-1587 URL: http://jira.jboss.com/jira/browse/JBSEAM-1587 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Hung Tang -- 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

15 years, 7 months

7
21
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2232) Reduce debug log level for events

by Christian Bauer (JIRA)

Reduce debug log level for events --------------------------------- Key: JBSEAM-2232 URL: http://jira.jboss.com/jira/browse/JBSEAM-2232 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Christian Bauer Priority: Critical Debug logging with Seam 2.x is completely useless. The most critical information in the debug log is the instantiation and lookup of components, however, if you enable DEBUG for org.jboss.seam.Component, you get thousands of these: 12:26:06,282 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events 12:26:06,282 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events 12:26:06,282 DEBUG [Component] done initializing: org.jboss.seam.core.events We need to exclude the event firing from debug logging, even if we hardcode it. And, are these events really useful? I have no idea why and when I'd want to listen to "context variable initialized" events. -- 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

15 years, 8 months

9
24
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2436) Session-scoped SFSB which holds entities leaks memory

by Susanne Jarl (JIRA)

Session-scoped SFSB which holds entities leaks memory ----------------------------------------------------- Key: JBSEAM-2436 URL: http://jira.jboss.com/jira/browse/JBSEAM-2436 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Environment: Suse Linux, JBoss 4.2.2.GA, Java 1.6.03, PostgreSQL 8.2 Reporter: Susanne Jarl Session-scoped SFSB which has entities in an object does not get destroyed. It leads to memory leak in production. Please read: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=126542 The problem appeared after upgrading to Seam 2.0.0.GA. My code worked fine in Seam 1.2.1. -- 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

15 years, 8 months

7
22
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2026) Maven archetypes

by Pete Muir (JIRA)

Maven archetypes ---------------- Key: JBSEAM-2026 URL: http://jira.jboss.com/jira/browse/JBSEAM-2026 Project: JBoss Seam Issue Type: Feature Request Reporter: Pete Muir Assigned To: Dan Allen Fix For: 2.0.x Create some maven archetypes to compliment seam-gen. -- 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

15 years, 9 months

9
20
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1662) seam-gen apps deploying to tomcat

by Matt Drees (JIRA)

seam-gen apps deploying to tomcat --------------------------------- Key: JBSEAM-1662 URL: http://jira.jboss.com/jira/browse/JBSEAM-1662 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.BETA1 Reporter: Matt Drees Priority: Minor Now that tomcat deployment is much easier (by using embedded Jboss), can seam-gen'd build.xml files (1) have a deploy.tomcat target? (2) have an explode.tomcat target? (for hot deploy functionality) -- 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

15 years, 9 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-881) seam-gen suppport for Tomcat

by alberto Gori (JIRA)

seam-gen suppport for Tomcat ----------------------------- Key: JBSEAM-881 URL: http://jira.jboss.com/jira/browse/JBSEAM-881 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 1.1.6.GA Reporter: alberto Gori I would like to see seam-gen support for different AS, expecially Tomcat (and maybe Glassfish...?). -- 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

15 years, 9 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-994) seam-gen and mutiple foreign keys

by Niels Hoogeveen (JIRA)

seam-gen and mutiple foreign keys --------------------------------- Key: JBSEAM-994 URL: http://jira.jboss.com/jira/browse/JBSEAM-994 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 1.2.0.GA Environment: JBoss-4.0.5 Reporter: Niels Hoogeveen I have generated a project with seam-gen based on generate-entities. All works fine, except for the generation of the home interfaces. In one of my tables I have two foreign keys to the same table. In the home interface two references are created to the appropriate object, but with the same name (which of course doesn't compile). Here is a simplified example: Table 1 Code: CREATE TABLE test ( id int4 NOT NULL DEFAULT nextval('test_id_seq'::regclass), name varchar, id_test2_1 int4, id_test2_2 int4, CONSTRAINT test_pkey PRIMARY KEY (id), CONSTRAINT test_id_test2_1_fkey FOREIGN KEY (id_test2_1) REFERENCES test2 (id) MATCH SIMPLE ON UPDATE NO ACTION ON DELETE NO ACTION, CONSTRAINT test_id_test2_2_fkey FOREIGN KEY (id_test2_2) REFERENCES test2 (id) MATCH SIMPLE ON UPDATE NO ACTION ON DELETE NO ACTION ) Table2 Code: CREATE TABLE test2 ( id int4 NOT NULL DEFAULT nextval('test2_id_seq'::regclass), name varchar, CONSTRAINT test2_pkey PRIMARY KEY (id) ) First Entity Code: @Entity @Table(name = "test", schema = "public") public class Test implements java.io.Serializable { private int id; private Test2 test2ByIdTest22; private Test2 test2ByIdTest21; private String name; public Test() { } public Test(int id) { this.id = id; } public Test(int id, Test2 test2ByIdTest22, Test2 test2ByIdTest21, String name) { this.id = id; this.test2ByIdTest22 = test2ByIdTest22; this.test2ByIdTest21 = test2ByIdTest21; this.name = name; } @Id @Column(name = "id", unique = true, nullable = false) @NotNull public int getId() { return this.id; } public void setId(int id) { this.id = id; } @ManyToOne(fetch = FetchType.LAZY) @JoinColumn(name = "id_test2_2") public Test2 getTest2ByIdTest22() { return this.test2ByIdTest22; } public void setTest2ByIdTest22(Test2 test2ByIdTest22) { this.test2ByIdTest22 = test2ByIdTest22; } @ManyToOne(fetch = FetchType.LAZY) @JoinColumn(name = "id_test2_1") public Test2 getTest2ByIdTest21() { return this.test2ByIdTest21; } public void setTest2ByIdTest21(Test2 test2ByIdTest21) { this.test2ByIdTest21 = test2ByIdTest21; } @Column(name = "name", length = 0) @Length(max = 0) public String getName() { return this.name; } public void setName(String name) { this.name = name; } } second entity Code: @Entity @Table(name = "test2", schema = "public") public class Test2 implements java.io.Serializable { private int id; private String name; private Set<Test> testsForIdTest21 = new HashSet<Test>(0); private Set<Test> testsForIdTest22 = new HashSet<Test>(0); public Test2() { } public Test2(int id) { this.id = id; } public Test2(int id, String name, Set<Test> testsForIdTest21, Set<Test> testsForIdTest22) { this.id = id; this.name = name; this.testsForIdTest21 = testsForIdTest21; this.testsForIdTest22 = testsForIdTest22; } @Id @Column(name = "id", unique = true, nullable = false) @NotNull public int getId() { return this.id; } public void setId(int id) { this.id = id; } @Column(name = "name", length = 0) @Length(max = 0) public String getName() { return this.name; } public void setName(String name) { this.name = name; } @OneToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY, mappedBy = "test2ByIdTest21") public Set<Test> getTestsForIdTest21() { return this.testsForIdTest21; } public void setTestsForIdTest21(Set<Test> testsForIdTest21) { this.testsForIdTest21 = testsForIdTest21; } @OneToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY, mappedBy = "test2ByIdTest22") public Set<Test> getTestsForIdTest22() { return this.testsForIdTest22; } public void setTestsForIdTest22(Set<Test> testsForIdTest22) { this.testsForIdTest22 = testsForIdTest22; } } Home interface of first entity. Here we have two Test2Home references, both with the name test2Home. Code: @Name("testHome") public class TestHome extends EntityHome<Test> { @In(create = true) Test2Home test2Home; @In(create = true) Test2Home test2Home; public void setTestId(Integer id) { setId(id); } public Integer getTestId() { return (Integer) getId(); } @Override protected Test createInstance() { Test test = new Test(); return test; } public void wire() { Test2 test2ByIdTest22 = test2Home.getDefinedInstance(); if (test2ByIdTest22 != null) { getInstance().setTest2ByIdTest22(test2ByIdTest22); } Test2 test2ByIdTest21 = test2Home.getDefinedInstance(); if (test2ByIdTest21 != null) { getInstance().setTest2ByIdTest21(test2ByIdTest21); } } public boolean isWired() { return true; } public Test getDefinedInstance() { return isIdDefined() ? getInstance() : null; } } BTW. I used the latest seam version from CVS. -- 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

15 years, 9 months

10
23
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2051) please put WEB-INF under view instead of resources (seam-gen)

by Dan Allen (JIRA)

please put WEB-INF under view instead of resources (seam-gen) ------------------------------------------------------------- Key: JBSEAM-2051 URL: http://jira.jboss.com/jira/browse/JBSEAM-2051 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.x I am aware that there is no hotter issue than this one. But PAUSE before rejecting it and hear me out. The current seam-gen project structure is src action model resources WEB-INF META-INF view IDEs choke on this structure, but it really comes down to just one folder. The src/ and resources/ directory really aren't a problem. The real problem is that WEB-INF/ just needs to be under view/. Seriously, if that can happen, the IDEs really will be happier. People are not arguing for the sake of arguing. This convention is the way that Sun laid out more than a decade ago and vendors have catered to it ever since (even JBoss). It's not like we woke up one day and said, gee, let's put WEB-INF/ in the folder with web artifacts. Rather than try to change the whole world, can we just move this one folder? I promise I am not arguing to read my own writing. Proposed structure src action model resources META-INF view WEB-INF -- 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

15 years, 9 months

6
11
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2008