|
»
DWR 3.0 RC1 and WAS
|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
 |
DWR 3.0 RC1 and WAS
by zcurtis
::
Rate this Message:
DWR 3.0 RC1 / WebSphere (WAS) 6.0.2.31 / Java 1.4.2 I had been using DWR 2.0.5 previously with success. I am now attempting to use the latest DWR release for its support of handling file uploads. I have up to six files for upload along with other form fields. I wanted to validate file size on the server before doing an entire form post. I don't believe file size can be validated other than on the server due to the nature security in the browser and with JavaScript. I am not able to get the latest DWR release to work at all. Any suggestions? I removed AnnotationsConfigurator.class from the jar as done in the previous version, and get the following during server startup: [4/27/09 12:09:41:391 MDT] 0000004f DefaultNamesp W org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver initHandlerMappings Ignoring namespace handler [org.directwebremoting.spring.DwrAnnotationNamespaceHandler]: problem with handler class file or dependent class java.lang.LinkageError: LinkageError while defining class: org.directwebremoting.spring.DwrAnnotationNamespaceHandler Could not be defined due to: org/directwebremoting/spring/DwrAnnotationNamespaceHandler (Unsupported major.minor version 49.0) This is often caused by having a class defined at multiple locations within the classloader hierarchy. Other potential causes include compiling against an older or newer version of the class that has an incompatible method signature. Dumping the current context classloader hierarchy: ... Additionally, I removed DwrAnnotationNamespaceHandler.class (and its two inner classes) from the jar, and get this when running the web app: [4/27/09 11:56:15:896 MDT] 0000005e WebApp E SRVE0026E: [Servlet Error]-[dwr-invoker]: java.lang.Exception: java.lang.LinkageError: LinkageError while defining class: org.directwebremoting.servlet.DwrServlet Could not be defined due to: org/directwebremoting/servlet/DwrServlet (Unsupported major.minor version 49.0) This is often caused by having a class defined at multiple locations within the classloader hierarchy. Other potential causes include compiling against an older or newer version of the class that has an incompatible method signature. Dumping the current context classloader hierarchy: ... Thank you. Zach The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you |
|
|
RE: DWR 3.0 RC1 and WAS
by RJones1
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
You need to use the java 1.4 version built using retroweaver,
you can get it here: https://dwr.dev.java.net/servlets/ProjectDocumentList?folderID=10313&expandFolder=10313&folderID=0 David, We should probably put an additional link for the 1.4 version on
the download page. Randy From: ZCurtis@...
[mailto:ZCurtis@...]
The information contained in this communication (including any
attachments hereto) is confidential and is intended solely for the personal and
confidential use of the individual or entity to whom it is addressed. If the
reader of this message is not the intended recipient or an agent responsible
for delivering it to the intended recipient, you are hereby notified that you
have received this communication in error and that any review, dissemination,
copying, or unauthorized use of this information, or the taking of any action
in reliance on the contents of this information is strictly prohibited. If you
have received this communication in error, please notify us immediately by
e-mail, and delete the original message. Thank you |
|
|
|
|
|
|
|
|
|
|
|
RE: DWR 3.0 RC1 and WAS
by zcurtis
::
Rate this Message:
I tried using http://retrotranslator.sourceforge.net/ against the base DWR 3.0 RC1 jar. I still end up with errors trying to run my web app when invoking DWR. Is anyone using this release with Java 1.4?
[4/28/09 13:47:16:165 MDT] 0000005d ServletWrappe E Uncaught init() exception thrown by servlet dwr-invoker [4/28/09 13:47:16:196 MDT] 0000005d WebApp E SRVE0026E: [Servlet Error]-[dwr-invoker]: org.directwebremoting.extend.ContainerConfigurationException: java.lang.NullPointerException at org.directwebremoting.impl.StartupUtil.createAndSetupDefaultContainer(StartupUtil.java:193) at org.directwebremoting.servlet.DwrServlet.createContainer(DwrServlet.java:97) at org.directwebremoting.servlet.DwrServlet.init(DwrServlet.java:64) at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:321) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:621) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3226) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:253) at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:229) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1970) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:120) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:434) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:373) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:101) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952) at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1475) Caused by: java.lang.NullPointerException at org.directwebremoting.impl.DefaultScriptSessionManager.afterContainerSetup(DefaultScriptSessionManager.java:70) at org.directwebremoting.impl.AbstractContainer.callInitializingBeans(AbstractContainer.java:55) at org.directwebremoting.impl.AbstractContainer.callInitializingBeans(AbstractContainer.java:39) at org.directwebremoting.impl.DefaultContainer.setupFinished(DefaultContainer.java:180) at org.directwebremoting.impl.StartupUtil.setupDefaultContainer(StartupUtil.java:264) at org.directwebremoting.impl.StartupUtil.createAndSetupDefaultContainer(StartupUtil.java:188) ... 17 more Thanks. Zach
|
|
|
Re: DWR 3.0 RC1 and WAS
by davidmarginian
::
Rate this Message:
Zach,
Well this certainly doesn't look like a Java version error so maybe you are getting somewhere. From the stack trace it is very difficult to tell exactly what the problem is. I would download the DWR source and place a few breakpoints in the code to pin-point where the problem is. I would start at the beginning of StartupUtil.createAndSetupDefaultContainer and find out what is null. I am sorry I can't help further but it seems you have a pretty unique/outdated setup and mimicking it would take a lot of time. -David zcurtis wrote: > I tried using http://retrotranslator.sourceforge.net/ against the base DWR > 3.0 RC1 jar. I still end up with errors trying to run my web app when > invoking DWR. Is anyone using this release with Java 1.4? > > [4/28/09 13:47:16:165 MDT] 0000005d ServletWrappe E Uncaught init() > exception thrown by servlet dwr-invoker > [4/28/09 13:47:16:196 MDT] 0000005d WebApp E SRVE0026E: [Servlet > Error]-[dwr-invoker]: > org.directwebremoting.extend.ContainerConfigurationException: > java.lang.NullPointerException > at > org.directwebremoting.impl.StartupUtil.createAndSetupDefaultContainer(StartupUtil.java:193) > at > org.directwebremoting.servlet.DwrServlet.createContainer(DwrServlet.java:97) > at org.directwebremoting.servlet.DwrServlet.init(DwrServlet.java:64) > at > com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:321) > at > com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:621) > at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3226) > at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:253) > at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:229) > at > com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1970) > at > com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:120) > at > com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:434) > at > com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:373) > at > com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:101) > at > com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566) > at > com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619) > at > com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952) > at > com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039) > at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1475) > Caused by: java.lang.NullPointerException > at > org.directwebremoting.impl.DefaultScriptSessionManager.afterContainerSetup(DefaultScriptSessionManager.java:70) > at > org.directwebremoting.impl.AbstractContainer.callInitializingBeans(AbstractContainer.java:55) > at > org.directwebremoting.impl.AbstractContainer.callInitializingBeans(AbstractContainer.java:39) > at > org.directwebremoting.impl.DefaultContainer.setupFinished(DefaultContainer.java:180) > at > org.directwebremoting.impl.StartupUtil.setupDefaultContainer(StartupUtil.java:264) > at > org.directwebremoting.impl.StartupUtil.createAndSetupDefaultContainer(StartupUtil.java:188) > ... 17 more > > Thanks. > Zach > > > > http://www.nabble.com/DWR-3.0M1-RC2-and-Java-1.4-td16908541.html > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
RE: DWR 3.0 RC1 and WAS
by ronifx
::
Rate this Message:
add in the DWR servlet (web.xml)
<init-param> <param-name>scheduledThreadPoolExecutor</param-name> <param-value>org.directwebremoting.impl.AutoShutdownScheduledThreadPoolExecutor</param-value> </init-param> <init-param> <param-name>compressor</param-name> <param-value></param-value> </init-param> DefaultContainer.initializeBean: java.util.concurrent.ScheduledThreadPoolExecutor after retroweaver: edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor And unset default compressor. Sorry for my google's translation Best regards Ronaldo Marques
|
|
|
RE: DWR 3.0 RC1 and WAS
by zcurtis
::
Rate this Message:
I have come back to tryng to use DWR 3.0.0.0.116. I added the init-param you mentioned. I was not able to get it to work with DWR Java1.4 jar using retroweaver. However, it did work when using a jar I built thru retrotranslator. This appears to be working now with my environment of WAS 6.0/Java 1.4. Thx!
|
| Free embeddable forum powered by Nabble | Forum Help |
