February 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-225) Maven 2 support

by Petr Ferschmann (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-225?page=comments#action_12352290 ] Petr Ferschmann commented on JBSEAM-225: ---------------------------------------- Hello, I have created Seam Maven integration. I have created "profiles" - you just say "I want to use Seam with PDF" and it will add all required dependencies. I have also created few archetypes. And now I am improving the dependencies and creating SeamGen for Maven. See http://software.softeu.cz/seam/ . I think this can help usage of Seam with Maven. > Maven 2 support > --------------- > > Key: JBSEAM-225 > URL: http://jira.jboss.com/jira/browse/JBSEAM-225 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.0 beta 2 > Environment: Maven 2.0.x > Reporter: Tuomas Kiviaho > > Mavenizing of the project would be very helpful when using cvs shapshots instead of prebuild releases. > It seems that all of the 3rd party projects previously available separately have been merged together as thirdparty-all.jar. Some of the 3rd party jars are missing like jsf-facelets.jar which should be some older version than the current release. > What is needed is a pom.xml currently producing both jboss-seam.jar and jboss-seam-ui.jar and having all of the dependencies enlisted. Most of the dependent projects are already available by default or then they exist in JBoss maven repository (refer to next gen jboss build system). I see that (propably missing) installments like jBPM have similar feature requests. pom.xml functions as a documentation where to place manually different jars in order to get for instance jboss seam digester working. > An optional feature would be to replace all of the .classpath lib references with maven2 classpath container that comes with Maven2 Eclipse plugin. This will make pom.xml useful for eclipse users even if current JBoss build engine is to be used, but requires maven2 plugin to be installed. The project wasn't not compiling for me directly when checked out from CVS, so plugin requirement is less of a pain than sonting out "broken" .classpath. -- 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

18 years, 9 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-756) exceptions.xml file for seam-gen

by Gavin King (JIRA)

exceptions.xml file for seam-gen -------------------------------- Key: JBSEAM-756 URL: http://jira.jboss.com/jira/browse/JBSEAM-756 Project: JBoss Seam Issue Type: Feature Request Reporter: Gavin King Assigned To: Gavin King Priority: Minor Fix For: 1.1.6.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

18 years, 9 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-706) Support for select multiple="true" in multipart form

by Shane Bryzak (JIRA)

Support for select multiple="true" in multipart form ---------------------------------------------------- Key: JBSEAM-706 URL: http://jira.jboss.com/jira/browse/JBSEAM-706 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.1.5.GA Reporter: Shane Bryzak Assigned To: Shane Bryzak Priority: Minor Fix For: 1.2.0.BETA1 There is limited support for <select multiple="true"> type controls in MultiPartRequest - this needs to be fixed. -- 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

18 years, 9 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-606) merge exceptions.xml into pages.xml and events.xml into components.xml

by Gavin King (JIRA)

merge exceptions.xml into pages.xml and events.xml into components.xml ---------------------------------------------------------------------- Key: JBSEAM-606 URL: http://jira.jboss.com/jira/browse/JBSEAM-606 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.2.0.BETA1 Exception mappings should go with the other UI orchestration, and this will let us have "scoped" exception mappings, which is super-useful. There is no reason to have a whole different file for event mappings, we can put them in with component definitions, they are similar. There is still a good reason to keep pages.xml separate from components.xml: namely, that the stuff in pages.xml is specific to JSF. -- 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

18 years, 9 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-767) Major redesign of exception handling

by Gavin King (JIRA)

Major redesign of exception handling ------------------------------------ Key: JBSEAM-767 URL: http://jira.jboss.com/jira/browse/JBSEAM-767 Project: JBoss Seam Issue Type: Feature Request Reporter: Gavin King Assigned To: Gavin King Priority: Blocker Fix For: 1.1.6.GA Seam exception handling is being rewritten to be much more robust, though we will lose some features. ExceptionInterceptor is going away. Instead, the servlet filter will know how to unwrap multiple layers of wrapped exceptions, when searching for a rule to match. -- 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

18 years, 9 months

1
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-762) Exceptions problem restricting access using pages.xml

by Ciro Cavani (JIRA)

Exceptions problem restricting access using pages.xml ----------------------------------------------------- Key: JBSEAM-762 URL: http://jira.jboss.com/jira/browse/JBSEAM-762 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.5.GA Reporter: Ciro Cavani Fix For: 1.1.6.GA Exception throw by Identity.instance().checkPermission(exp) is swallowed by AbstractSeamPhaseListener when restriction is set on pages.xml -- 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

18 years, 9 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-748) Wrap exception handlers around tx management in TransactionSeamPhaseListener

by Gavin King (JIRA)

Wrap exception handlers around tx management in TransactionSeamPhaseListener ---------------------------------------------------------------------------- Key: JBSEAM-748 URL: http://jira.jboss.com/jira/browse/JBSEAM-748 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.6 A very common place for exceptions to happen is during transaction mgmt, so we should try to extend the exception handling stuff to cover this. -- 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

18 years, 9 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-765) get/set pair for Identity.securityContext

by Gavin King (JIRA)

get/set pair for Identity.securityContext ----------------------------------------- Key: JBSEAM-765 URL: http://jira.jboss.com/jira/browse/JBSEAM-765 Project: JBoss Seam Issue Type: Feature Request Components: Security Affects Versions: 1.1.5.GA Reporter: Gavin King Assigned To: Gavin King Priority: Minor Fix For: 1.1.6.GA This would allow use of a configurable name, and unit testability. -- 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

18 years, 9 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-734) Security example should use encrypted passwords

by Gavin King (JIRA)

Security example should use encrypted passwords ------------------------------------------------ Key: JBSEAM-734 URL: http://jira.jboss.com/jira/browse/JBSEAM-734 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.2.0.BETA1 At least to demonstrate that it can be done ;-) -- 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

18 years, 9 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-760) Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise

by Alex Kozlenkov (JIRA)

Setting <distributable /> in web.xml results in java.lang.IllegalStateException in logs, application works otherwise -------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-760 URL: http://jira.jboss.com/jira/browse/JBSEAM-760 Project: JBoss Seam Issue Type: Bug Components: Security Environment: Microsoft Vista with Java 6 SDK, JBoss 4.0.5.GA EJB3 and EJB3 Clustered Reporter: Alex Kozlenkov A very simple application using the new 1.1.5 level security features produces a java.lang.IllegalStateException when <distributable /> is included in web.xml. The application works perfectly wikthout this setting and even with <distributable /> the exception seems to be non-fatal. The stack trace follows: 09:58:11,169 ERROR [[/helloworld]] Session attribute event listener threw exception java.lang.IllegalStateException: No application context active at org.jboss.seam.Component.forName(Component.java:1586) at org.jboss.seam.Component.getInstance(Component.java:1636) at org.jboss.seam.Component.getInstance(Component.java:1631) at org.jboss.seam.Component.getInstance(Component.java:1608) at org.jboss.seam.Component.getInstance(Component.java:1603) at org.jboss.seam.persistence.PersistenceProvider.instance(PersistenceProvider.java:45) at org.jboss.seam.core.ManagedPersistenceContext.sessionWillPassivate(ManagedPersistenceContext.java:104) at org.jboss.web.tomcat.tc5.session.ClusteredSession.passivate(ClusteredSession.java:896) at org.jboss.web.tomcat.tc5.session.JBossCacheManager.storeSession(JBossCacheManager.java:642) at org.jboss.web.tomcat.tc5.session.InstantSnapshotManager.snapshot(InstantSnapshotManager.java:49) at org.jboss.web.tomcat.tc5.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:98) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:619) Using a custom phase listener to trace JSF shows that the exception is wedged between a registration page that successfully creates a new account and a login page to which the user is redirected on success. The login page is successfully presented as well. -- 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

18 years, 9 months

2
19
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2007