November 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3473) seambay example throws an exception when viewing "Whistler's Mother" item

by Jozef Hartinger (JIRA)

seambay example throws an exception when viewing "Whistler's Mother" item ------------------------------------------------------------------------- Key: JBSEAM-3473 URL: https://jira.jboss.org/jira/browse/JBSEAM-3473 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.CR1 Environment: jdk5 JBoss AS 4.2.3 Reporter: Jozef Hartinger Priority: Minor When attempting to view the "Whistler's Mother" item the browser shows a JSF error page, and the exception below is in the logs: Caused by: line 1:346: unexpected char: 0xFFFD at org.jboss.seam.text.SeamTextLexer.nextToken(SeamTextLexer.java:230) at antlr.TokenBuffer.fill(Unknown Source) at antlr.TokenBuffer.LA(Unknown Source) at antlr.LLkParser.LA(Unknown Source) at org.jboss.seam.text.SeamTextParser.line(SeamTextParser.java:651) at org.jboss.seam.text.SeamTextParser.paragraph(SeamTextParser.java:401) -- 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

17 years

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3584) permissionManager.grantPermissions(..) is not persisting values into the database it is called by a @Webremote Method

by Marco RÃÂ¶ÃÂ¶sli (JIRA)

permissionManager.grantPermissions(..) is not persisting values into the database it is called by a @Webremote Method --------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3584 URL: https://jira.jboss.org/jira/browse/JBSEAM-3584 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.0.GA Reporter: Marco RÃÂ¶ÃÂ¶sli If you call permissionManager.grantPermissions(..) form a Remote Method (@Webremote) it will not persist the values into the database. I made a dummy project that implements this bug. You can download it from here: http://user.enterpriselab.ch/~taroeoes/seam/dummy_testcase.zip the lib dir is empty. I used the seam libs form 17.10.2008 you have to login first with (user: admin passwort: <blank> ) before you press the RPC Call Button in my dummy project Greetz Marco -- 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

17 years

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3664) change the priority of PermissionResolvers

by Marco RÃÂ¶ÃÂ¶sli (JIRA)

change the priority of PermissionResolvers ------------------------------------------ Key: JBSEAM-3664 URL: https://jira.jboss.org/jira/browse/JBSEAM-3664 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.0.GA Reporter: Marco RÃÂ¶ÃÂ¶sli Fix For: 2.1.1.GA If the Jpa Permission Store is used and a rule-based-permission-resolver and a persistent-permission-resolver is configured, the order for looking up permissions is: 1) DroolsFile, 2)persistent-permission-resolver 3) Other permission-resolvers what implments the permission-resolver interface It would be nice if it's possible to change the order for looking up the permissions -- 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

17 years

2
3
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

17 years

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3732) seambay example - category listing does not load

by Jozef Hartinger (JIRA)

seambay example - category listing does not load ------------------------------------------------ Key: JBSEAM-3732 URL: https://jira.jboss.org/jira/browse/JBSEAM-3732 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.1.CR1 Environment: JDK 5 Tomcat 6.0.18 + JBoss Embedded Reporter: Jozef Hartinger To reproduce: 1.) Log in 2.) Choose sell menu item in the top menu 3.) Enter some description and proceed further 4.) On the next page there is "Loading categories" but the categories do never load. This issue is probably related to the webservice testpage malfunction on tomcat + jboss embedded -- 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

17 years

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3726) Methods with an InvocationContext parameter annotated with javax.ejb.PostActivate cause a validation exception in WebSphere v7.0

by Denis Forveille (JIRA)

Methods with an InvocationContext parameter annotated with javax.ejb.PostActivate cause a validation exception in WebSphere v7.0 --------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3726 URL: https://jira.jboss.org/jira/browse/JBSEAM-3726 Project: Seam Issue Type: Bug Components: EJB3 Affects Versions: 2.1.0.SP1 Environment: WebSphere v7.0 Reporter: Denis Forveille When starting our app in WebSphere v7.0 with seam v2.1.0.SP1, we receive the exception below Is it possible that annotation "javax.ejb.PostActivate" is used instead of "org.jboss.seam.annotations.intercept.PostActivate" annotation and that the former does not accept any parameter for the annotated method (At least in WebSphere v7.0) and the latter does... The method in question is declared as @PostActivate public void postActivate(InvocationContext invocation) throws Exception This method siganture is present in classes SessionBeanInterceptor, EntityManagerProxyInterceptor and HibernateSessionProxyInterceptor Exception: [18/11/08 16:17:51:537 EST] 0000001a annotations E AnnotativeMetadataManagerImpl merge Caught exception while merging com.ibm.wsspi.amm.validate.ValidationException: For method, org.jboss.seam.persistence.EntityManagerProxyInterceptor.postActivate(Lorg/jboss/seam/intercept/InvocationContext;)V[com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl@1b8e1b8e], parameters were specified, but null was the expected comparison -- 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

17 years

7
35
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3572) Seam nested booking example - NoSuchEJBException on undeploy

by Jozef Hartinger (JIRA)

Seam nested booking example - NoSuchEJBException on undeploy ------------------------------------------------------------ Key: JBSEAM-3572 URL: https://jira.jboss.org/jira/browse/JBSEAM-3572 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.GA Environment: JDK 5 JBoss AS 4.2.3 Reporter: Jozef Hartinger I am getting plenty of javax.ejb.NoSuchEJBException-s when undeploying nested booking example. For exceptions to appear preceeding interaction with example is needed. For details see attached log. -- 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

17 years

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3672) JpaPermissionStore throws IAE "Cannot resolve principal name for principal.."

by Stefano Travelli (JIRA)

JpaPermissionStore throws IAE "Cannot resolve principal name for principal.." ------------------------------------------------------------------------------ Key: JBSEAM-3672 URL: https://jira.jboss.org/jira/browse/JBSEAM-3672 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.0.SP1 Environment: JBoss 4.2.2 JVM 1.6.0 Reporter: Stefano Travelli Given the following conditions: - JpaPermissionStore configured with a permission entity having PermissionRole and PermissionUser properties mapped as @ManyToOne relations. - that @ManyToOne relations are lazy - checking a permission for a Class target (resolved by ClassIdentifierStrategy) JpaPermissionStore throws an IllegalStateException "Cannot resolve principal name for principal..". I'm figuring out the reason and working on a patch. -- 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

17 years

2
4
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

17 years

10
23
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3168) Allow page params to put values directly into the event scope

by Daniel Wiell (JIRA)

Allow page params to put values directly into the event scope ------------------------------------------------------------- Key: JBSEAM-3168 URL: http://jira.jboss.com/jira/browse/JBSEAM-3168 Project: Seam Issue Type: Feature Request Affects Versions: 2.0.2.SP1 Reporter: Daniel Wiell It would be great if a request parameter could be put directly into the event scope: <page view-id="/test.xhtml"> <param name="testParam" value="#{test}"/> </page> Currently this gives an exception: java.lang.NullPointerException at org.jboss.seam.navigation.Param.validateConvertedValue(Param.java:248) at org.jboss.seam.navigation.Pages.convertAndValidateStringValuesInPageContext(Pages.java:753) at org.jboss.seam.navigation.Pages.postRestore(Pages.java:400) at org.jboss.seam.jsf.SeamPhaseListener.postRestorePage(SeamPhaseListener.java:544) at org.jboss.seam.jsf.SeamPhaseListener.afterRestoreView(SeamPhaseListener.java:390) at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:226) at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:192) at com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:175) -- 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

17 years

3
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2008