[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4374) GWT Example does not work with GWT from trunk.
by Sand Lee (JIRA)
GWT Example does not work with GWT from trunk.
----------------------------------------------
Key: JBSEAM-4374
URL: https://jira.jboss.org/jira/browse/JBSEAM-4374
Project: Seam
Issue Type: Thirdparty Change
Components: Remoting
Affects Versions: 2.2.0.GA, 2.2.1.CR1
Environment: linux, jboss 4.2.3, seam 2.2.1-SNAPSHOT, GWT from trunk (r5989)
Reporter: Sand Lee
Assignee: Shane Bryzak
way to reproduce:
cd /tmp
svn co http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_2 seam
svn checkout http://google-web-toolkit.googlecode.com/svn/tools/ tools
svn checkout http://google-web-toolkit.googlecode.com/svn/trunk/ trunk
export GWT_TOOLS=/tmp/tools
cd /tmp/trunk
ant
cd /tmp/seam/examples/remoting/gwt
sed -i 's/C:\/java\/gwt-windows-1.5.2/\/tmp\/trunk\/build\/lib\//g' build.properties
ant clean gwt-compile deploy
pressing ask on http://localhost:8080/seam-gwt/HelloWorld.html produces following output on the server side:
12:41:55,928 INFO [EARDeployer] Started J2EE application: file:/opt/jboss-4.2.3.GA/server/default/deploy/jboss-seam-gwt.ear |@LOCATION: org.jboss.deployment.EARDeployer.start(EARDeployer.java:368)
12:45:00,807 ERROR [[/seam-gwt]] Exception while dispatching incoming RPC call |@LOCATION: org.apache.catalina.core.ApplicationContext.log(ApplicationContext.java:660)
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.extract(ServerSerializationStreamReader.java:617)
at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.readInt(ServerSerializationStreamReader.java:432)
at com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.prepareToRead(AbstractSerializationStreamReader.java:38)
at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.prepareToRead(ServerSerializationStreamReader.java:383)
at org.jboss.seam.remoting.gwt.GWTService.RPC_decodeRequest(GWTService.java:376)
at org.jboss.seam.remoting.gwt.GWTService.processCall(GWTService.java:203)
at org.jboss.seam.remoting.gwt.GWTService$1.process(GWTService.java:120)
at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53)
at org.jboss.seam.remoting.gwt.GWTService.getResource(GWTService.java:105)
at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:619)
--
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
14 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4434) Broken wicket instrumentation instructions for Ant
by Christian Bauer (JIRA)
Broken wicket instrumentation instructions for Ant
--------------------------------------------------
Key: JBSEAM-4434
URL: https://jira.jboss.org/jira/browse/JBSEAM-4434
Project: Seam
Issue Type: Bug
Components: Wicket
Affects Versions: 2.2.0.GA
Reporter: Christian Bauer
Attachments: screenshot-1.jpg
1. The HTML documentation of the wicket chapter is broken, see attached screenshot.
2. The PDF documentation includes the following instructions for enhancing the Wicket components:
<taskdef name="instrumentWicket"
classname="org.jboss.seam.wicket.ioc.WicketInstrumentationTask">
<classpath>
<pathelement location="lib/jboss-seam-wicket-ant.jar"/>
<pathelement location="web/WEB-INF/lib/jboss-seam-wicket.jar"/>
<pathelement location="lib/javassist.jar"/>
<pathelement location="lib/jboss-seam.jar"/>
</classpath>
</taskdef>
<instrumentWicket outputDirectory="${build.instrumented}" useAnnotations="true">
<classpath refid="build.classpath"/>
<fileset dir="${build.classes}" includes="**/*.class"/>
</instrumentWicket>
What is "build.classpath"?Nobody can look at the examples/wicket/build.xml and figure that one out either. So it's a total mystery why an additional classpath needs to be referenced within the task, when the task definition already lists all (you'd think) required classes. Users will not know what should be defined on that classpath.
Without this classpath setting or with just guessing what could/should be on that classpath, you will get "java.lang.RuntimeException: javassist.NotFoundException: HelloWorldApplication" (the only classes in build.classes are the ones for a Wicket HelloWorld, so this is just the first class file found).
--
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
14 years, 7 months