April 2009 - seam-issues - Jboss List Archives

[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, 2 months

3
2
0 / 0

[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

15 years, 2 months

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

15 years, 2 months

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

15 years, 2 months

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

15 years, 2 months

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

15 years, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3893) Seambay example - debug page after submitting empty registration form

by Jozef Hartinger (JIRA)

Seambay example - debug page after submitting empty registration form --------------------------------------------------------------------- Key: JBSEAM-3893 URL: https://jira.jboss.org/jira/browse/JBSEAM-3893 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.1.GA Environment: JDK 5 JBoss AS 4.2.3.GA Reporter: Jozef Hartinger Assignee: Jozef Hartinger Priority: Minor Fix For: 2.1.2.CR1 Submitting empty registration results into debug page caused by org.hibernate.validator.InvalidStateException -- 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

15 years, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4084) Hard-to-read sentence caused by typo, in Tutorial

by Ian Darwin (JIRA)

Hard-to-read sentence caused by typo, in Tutorial ------------------------------------------------- Key: JBSEAM-4084 URL: https://jira.jboss.org/jira/browse/JBSEAM-4084 Project: Seam Issue Type: Patch Components: Documentation Issues Affects Versions: 2.1.1.GA Environment: All Reporter: Ian Darwin Attachments: id Paragraph begins "If we being a nested conversation..." - takes a while to figure out what's meant is "If we *begin*..." rather than "if we be in,.." :-) -- 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

15 years, 2 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3771) URL Rewriting Not Occurring

by Dave Everson (JIRA)

URL Rewriting Not Occurring --------------------------- Key: JBSEAM-3771 URL: https://jira.jboss.org/jira/browse/JBSEAM-3771 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.CR1 Environment: Windows Vista, JBoss 4.2.0, JRockit 1.5 Reporter: Dave Everson We have just updated Seam to 2.1.1CR1 We started to use the rewrite functionality within pages.xml. We have the following pages defined: <page view-id="/pages/account/check.xhtml"> <rewrite pattern="/newFamilyAccount" /> <begin-conversation join="true"/> <action execute="#{registerFamily.startEdit}"/> <navigation from-action="#{registerFamily.doAccountCheck}"> <rule if-outcome="exists"> <redirect view-id="/pages/account/existing.xhtml"/> </rule> <rule if-outcome="new"> <redirect view-id="/pages/account/new.xhtml"/> </rule> </navigation> </page> <page view-id="/pages/account/existing.xhtml"> <rewrite pattern="/existingAccounts" /> <begin-conversation join="true"/> </page> We are able to access /newFamilyAccount without issue and a conversation is started After entering data that already exists in the database, we should be taken to the /existingAccounts (/pages/account/existing.xhtml) view. We are taken to the view, however the URL shows: https://localhost/a/pages/account/existing.seam?cid=9. We have tried several things and can't see to ever have the rewritten URL appear. Does anyone have any suggestions on what we are doing incorrectly. Thanks. -- 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

15 years, 2 months

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

15 years, 2 months

7
35
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2009