December 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1103) Deploying Seam example app into /trunk causes ZipException

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-1103?page=all ] Ales Justin updated JBSEAM-1103: -------------------------------- Attachment: Scanner.java > Deploying Seam example app into /trunk causes ZipException > ---------------------------------------------------------- > > Key: JBSEAM-1103 > URL: http://jira.jboss.com/jira/browse/JBSEAM-1103 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Environment: r61655 of /trunk and jboss-seam-1.2.0.PATCH1 > Reporter: Charles Crouch > Assigned To: Ales Justin > Fix For: 2.0.x > > Attachments: cglib-nodep-2.1_3.jar, el-api.jar, el-ri.jar, jboss-seam-numberguess.ear, Scanner.java > > > Deploying a modified version of jboss-seam-numberguess.ear into the current Beta2 server causes ZipException's to be thrown during startup and trying to hit http://localhost:8080/seam-numberguess produces 500's. Deploying the same app into Beta1 works fine. > Steps to reproduce: > 1) Copy > jboss-seam-1.2.0.PATCH1\lib\el-api.jar > and > jboss-seam-1.2.0.PATCH1\lib\el-ri.jar > to > build\output\jboss-5.0.0.Beta2\server\default\deployers\jbossweb.deployer\jsf-libs > 2) Copy > cglib-nodep-2.1_3.jar (version probably doesn't matter) > to > build\output\jboss-5.0.0.Beta2\server\default\lib > 3) Copy modified jboss-seam-numberguess.ear > to > build\output\jboss-5.0.0.Beta2\server\default\deploy > 4) Start the server and you get several exceptions like the following... > 12:09:11,896 INFO [Catalina] Server startup in 190 ms > 12:09:20,769 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=Dispatcher,service=EJB3 with dependencies: > 12:09:24,244 INFO [EJBContainer] STARTED EJB: org.jboss.seam.core.Dispatcher ejbName: Dispatcher > 12:09:24,484 WARN [JBossTimerServiceFactory] TIMER SERVICE IS NOT INSTALLED > 12:09:24,484 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=TransactionListener,service=EJB3 with dependencies: > 12:09:26,216 INFO [EJBContainer] STARTED EJB: org.jboss.seam.core.TransactionListener ejbName: TransactionListener > 12:09:29,441 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war > 12:09:35,319 INFO [TomcatDeployment] deploy, ctxPath=/seam-numberguess, vfsUrl=jboss-seam-numberguess.ear/jboss-seam-numberguess.war > 12:09:38,895 INFO [ServletContextListener] Welcome to Seam 1.2.0.PATCH1 > 12:09:38,995 INFO [Scanner] scanning: vfsfile:/C:/usr/projects/current/jboss/trunk/build/output/jboss-5.0.0.Beta2/server/default/deploy/jboss-seam-numberguess.ear/jboss-seam.jar > 12:09:38,995 WARN [Scanner] could not read entries > java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:203) > at java.util.zip.ZipFile.<init>(ZipFile.java:234) > at org.jboss.seam.deployment.Scanner.handleArchive(Scanner.java:110) > at org.jboss.seam.deployment.Scanner.scan(Scanner.java:96) > at org.jboss.seam.deployment.NamespaceScanner.getPackages(NamespaceScanner.java:34) > at org.jboss.seam.init.Initialization.addNamespaces(Initialization.java:590) > at org.jboss.seam.init.Initialization.<init>(Initialization.java:80) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3854) -- 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, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1103) Deploying Seam example app into /trunk causes ZipException

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-1103?page=all ] Ales Justin updated JBSEAM-1103: -------------------------------- Attachment: (was: Scanner.java) > Deploying Seam example app into /trunk causes ZipException > ---------------------------------------------------------- > > Key: JBSEAM-1103 > URL: http://jira.jboss.com/jira/browse/JBSEAM-1103 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Environment: r61655 of /trunk and jboss-seam-1.2.0.PATCH1 > Reporter: Charles Crouch > Assigned To: Ales Justin > Fix For: 2.0.x > > Attachments: cglib-nodep-2.1_3.jar, el-api.jar, el-ri.jar, jboss-seam-numberguess.ear, Scanner.java > > > Deploying a modified version of jboss-seam-numberguess.ear into the current Beta2 server causes ZipException's to be thrown during startup and trying to hit http://localhost:8080/seam-numberguess produces 500's. Deploying the same app into Beta1 works fine. > Steps to reproduce: > 1) Copy > jboss-seam-1.2.0.PATCH1\lib\el-api.jar > and > jboss-seam-1.2.0.PATCH1\lib\el-ri.jar > to > build\output\jboss-5.0.0.Beta2\server\default\deployers\jbossweb.deployer\jsf-libs > 2) Copy > cglib-nodep-2.1_3.jar (version probably doesn't matter) > to > build\output\jboss-5.0.0.Beta2\server\default\lib > 3) Copy modified jboss-seam-numberguess.ear > to > build\output\jboss-5.0.0.Beta2\server\default\deploy > 4) Start the server and you get several exceptions like the following... > 12:09:11,896 INFO [Catalina] Server startup in 190 ms > 12:09:20,769 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=Dispatcher,service=EJB3 with dependencies: > 12:09:24,244 INFO [EJBContainer] STARTED EJB: org.jboss.seam.core.Dispatcher ejbName: Dispatcher > 12:09:24,484 WARN [JBossTimerServiceFactory] TIMER SERVICE IS NOT INSTALLED > 12:09:24,484 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=TransactionListener,service=EJB3 with dependencies: > 12:09:26,216 INFO [EJBContainer] STARTED EJB: org.jboss.seam.core.TransactionListener ejbName: TransactionListener > 12:09:29,441 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war > 12:09:35,319 INFO [TomcatDeployment] deploy, ctxPath=/seam-numberguess, vfsUrl=jboss-seam-numberguess.ear/jboss-seam-numberguess.war > 12:09:38,895 INFO [ServletContextListener] Welcome to Seam 1.2.0.PATCH1 > 12:09:38,995 INFO [Scanner] scanning: vfsfile:/C:/usr/projects/current/jboss/trunk/build/output/jboss-5.0.0.Beta2/server/default/deploy/jboss-seam-numberguess.ear/jboss-seam.jar > 12:09:38,995 WARN [Scanner] could not read entries > java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:203) > at java.util.zip.ZipFile.<init>(ZipFile.java:234) > at org.jboss.seam.deployment.Scanner.handleArchive(Scanner.java:110) > at org.jboss.seam.deployment.Scanner.scan(Scanner.java:96) > at org.jboss.seam.deployment.NamespaceScanner.getPackages(NamespaceScanner.java:34) > at org.jboss.seam.init.Initialization.addNamespaces(Initialization.java:590) > at org.jboss.seam.init.Initialization.<init>(Initialization.java:80) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3854) -- 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, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2056) Add a way to specify the type of Richfaces HTML parser for a particular view in components.xml

by Adrian Mitev (JIRA)

Add a way to specify the type of Richfaces HTML parser for a particular view in components.xml ---------------------------------------------------------------------------------------------- Key: JBSEAM-2056 URL: http://jira.jboss.com/jira/browse/JBSEAM-2056 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.CR2 Reporter: Adrian Mitev Priority: Minor Here is a sample code for this <context-param> <param-name>org.ajax4jsf.xmlparser.ORDER</param-name> <param-value>TIDY,NEKO,NONE</param-value> </context-param> <context-param> <param-name>org.ajax4jsf.xmlparser.TIDY</param-name> <param-value>/pages/repeater.xhtml,/pages/tabs.xhtml</param-value> </context-param> -- 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, 1 month

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2199) remove javax.servlet:servlet-api and javax.el:el-api as hard dependencies in Maven 2

by Dan Allen (JIRA)

remove javax.servlet:servlet-api and javax.el:el-api as hard dependencies in Maven 2 ------------------------------------------------------------------------------------ Key: JBSEAM-2199 URL: http://jira.jboss.com/jira/browse/JBSEAM-2199 Project: JBoss Seam Issue Type: Task Components: Core Affects Versions: 2.0.0.GA Reporter: Dan Allen Assigned To: Pete Muir Fix For: 2.0.0.GA I feel that both the javax.servlet:servlet-api and javax.el:el-api dependencies should always be declared at provided (or optional). Currently, the hard dependencies are as such: javax.servlet:servlet-api - debug, pdf, remoting, ioc javax.el:el-api - core, debug, mail, pdf, ui The provided scope, as you know, will be available for compile and tests, but not deployed. Personally I feel that provided is the best choice because optional forces developers to add it as a dependency when it is likely they will need it to compile. The JSF POM files uses provided for the javax.servlet:servlet-api dependency, so perhaps we should follow suit. Basically, if the user wants to include a library that is part of Java EE 5 in their project as a deployment dependency (compile or runtime), then they can comfortably add it. Otherwise,they are forced to use a barrage of exclusions to get it booted. As it stands now the JSF libraries are not included by default, so it stands to reason that the servlet and EL APIs are also out. It is very easy for someone to include a build profile in their project that throws these artifacts in for an older spec deployment. Of course, this brings up the point that Maven 2 is really lame in how it does exclusions. Wouldn't it be nice just to say "I never want this artifact, I don't care what you say". Nope, let's just do it the hard way (says the Maven 2 folks), it is more fun. -- 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, 1 month

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2293) Include nestedbooking example in the Seam distribution

by Jacob Orshalick (JIRA)

Include nestedbooking example in the Seam distribution ------------------------------------------------------ Key: JBSEAM-2293 URL: http://jira.jboss.com/jira/browse/JBSEAM-2293 Project: JBoss Seam Issue Type: Feature Request Components: Examples Affects Versions: 2.0.0.GA Reporter: Jacob Orshalick Priority: Minor Attachments: nestedbooking-v1.zip Currently there no examples included in the Seam distribution that demonstrate the use of nested conversations. The attached zip is a 2.0.0.GA compatible version of the of the example distributed with the article: http://developer.redhatmagazine.com/2007/10/31/continuing-the-conversatio... Thanks. -- 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, 1 month

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1998) javassist 3.3 and 3.4 are both imported by maven when I declare hibernate dependency

by Michael Yuan (JIRA)

javassist 3.3 and 3.4 are both imported by maven when I declare hibernate dependency ------------------------------------------------------------------------------------ Key: JBSEAM-1998 URL: http://jira.jboss.com/jira/browse/JBSEAM-1998 Project: JBoss Seam Issue Type: Bug Reporter: Michael Yuan Assigned To: Pete Muir Priority: Minor Fix For: 2.0.0.GA I have the following dependencies defined: <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate</artifactId> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-validator</artifactId> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-annotations</artifactId> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-entitymanager</artifactId> </dependency> And the generate WAR has both: javassist-3.3.ga.jar javassist-3.4.GA.jar Perhaps one of them should be removed. Thanks. -- 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, 1 month

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1984) Please add icefaces dependency jars to the jboss maven repo

by Michael Yuan (JIRA)

Please add icefaces dependency jars to the jboss maven repo ----------------------------------------------------------- Key: JBSEAM-1984 URL: http://jira.jboss.com/jira/browse/JBSEAM-1984 Project: JBoss Seam Issue Type: Feature Request Reporter: Michael Yuan Assigned To: Pete Muir Fix For: 2.0.0.CR2 We need to make icefaces a dependency for the icefaces-seam-booking example and the icefaces-based seam-gen. The JARs we need are: Icefaces release 1.6.1: * icefaces.jar * icefaces-facelets.jar * icefaces-comps.jar Commons digester 1.6: * commons-digester.jar Commons fileupload 1.2: * commons-fileupload.jar Backport util concurrent 2.2: * backport-util-concurrent.jar All other icefaces dependencies are already satisfied by Seam. -- 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, 1 month

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2192) AbstractMap from org.jboss.seam.international.Messages needs containsKey()

by Damian Harvey (JIRA)

AbstractMap from org.jboss.seam.international.Messages needs containsKey() -------------------------------------------------------------------------- Key: JBSEAM-2192 URL: http://jira.jboss.com/jira/browse/JBSEAM-2192 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Environment: Mac OSX, Jboss 4.2.1 Reporter: Damian Harvey Performing a containsKey() on the AbstractMap from org.jboss.seam.international.Messages results in severe performance problems (800ms on 1,800 properties compared to under 1ms for a get()) eg: @In Map<String, String> messages; //This is the Seam messages bundle public void aMethod() { if(messages.containsKey("key.mykey")) { //do something } } I traced the containsKey for a while but it went on a mad run through ELResolvers and Pages.java etc. Simple solution is to add a containsKey to the AbstractMap: public boolean containsKey(String key) { if(messages.get(key).equals(key)) { return false; } else { return true; } } Would be nice to know why this 'mad run' happened though. Hopefully not symptomatic of something wrong deeper down. Cheers, Damian. -- 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, 1 month

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2125) Maven: jboss-seam has wrong packaging

by Stephan Bublava (JIRA)

Maven: jboss-seam has wrong packaging ------------------------------------- Key: JBSEAM-2125 URL: http://jira.jboss.com/jira/browse/JBSEAM-2125 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR2 Reporter: Stephan Bublava Priority: Minor Since jboss-seam is an EAR module it should have <packaging>ear</packaging> in it's pom.xml. This requires adding <type>ejb</type> to all dependency declarations. -- 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, 1 month

2
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1972) s:decorate input control ID change from 1.2.1 to 2.0

by steve tynor (JIRA)

s:decorate input control ID change from 1.2.1 to 2.0 ---------------------------------------------------- Key: JBSEAM-1972 URL: http://jira.jboss.com/jira/browse/JBSEAM-1972 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.CR1 Reporter: steve tynor I'm not sure if this is a bug or is intended behavior, but component ID's have changed from Seam version 1.2.1 to 2.0.0.CR1. This has broken our Selenium integration tests and many of our Javascript functions which access and manipulate the input controls via DHTML. Given something like: <s:decorate id="fooDecoration" template="/WEB-INF/facelets/templates/edit.xhtml"> <ui:define name="label">Foo</ui:define> <h:inputText id="foo" value="#{fooHome.instance.foo}"/> </s:decorate> In Seam1.2.1, the control was addressable as "fooForm:foo". In Seam2, that has changed and we must address it as "fooForm:fooDecoration:foo". Is this intentional? Is it likely to change before 2.0.0GA? -- 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, 1 month

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2007