You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@click.apache.org by iv...@uniplus.hr on 2010/02/28 11:11:24 UTC
(Unknown)
Hi again,
yes im getting this message when trying to deploy app on Websphere :
Error 404: SRVE0202E: Servlet [click-servlet]:
org.apache.click.extras.spring.SpringClickServlet was found, but is
corrupt: SRVE0227I: 1. Check that the class resides in the proper package
directory. SRVE0228I: 2. Check that the classname has been defined in the
server using the proper case and fully qualified package. SRVE0229I: 3.
Check that the class was transferred to the filesystem using a binary
transfer mode. SRVE0230I: 4. Check that the class was compiled using the
proper case (as defined in the class definition). SRVE0231E: 5. Check that
the class file was not renamed after it was compiled.
My web.xml file looks like this (part of servlet configuration).
<servlet>
<servlet-name>click-servlet</servlet-name>
<servlet-class>org.apache.click.extras.spring.SpringClickServlet</servlet-class>
<load-on-startup>0</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>click-servlet</servlet-name>
<url-pattern>*.htm</url-pattern>
</servlet-mapping>
Am I missing this part (found on click examples) when deploying on
websphere (without it it works perfectly on Apache Tomcat)
<servlet-mapping>
<servlet-name>ClickServlet</servlet-name>
<url-pattern>/click/*</url-pattern>
</servlet-mapping>
Thank you,
Ivan
On 26.2.2010 21:21, Malcolm Edgar wrote:
> you should not have to rebuild the Click jars. Have you seen a problem?
>
> regards Malcolm
>
> 2010/2/27 Ivan Furdi <iv...@uniplus.hr>:
>> Hi everyone,
>>
>> I have a question with deploying click app on websphere .
>>
>> Im using a IBM WebSphere 6.1 which uses IBM Java 1.5.0.
>> My question is - should i rebuild all click jar files (sources ) with IBM
>> java and then deploy it on websphere?
>>
>> Does anyone has some experience or advice concerning the subject?
>>
>> Thank you ,
>> Ivan Furdi
>>
>>
>>
>>
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 9.0.733 / Virus Database: 271.1.1/2711 - Release Date:
02/26/10 08:34:00
>>
--
Srdačan pozdrav,
Ivan Furdi
Re: Deploying click on websphere
Posted by Bob Schellink <sa...@gmail.com>.
Interesting. There isn't perhaps another version of Click somewhere on the classpath?
bob
On 1/03/2010 09:36 PM, Ivan Furdi wrote:
> Hi,
> this is also a part of log concerning WebSphere :
>
> WebSphere Platform 6.1 [ND 6.1.0.23 cf230910.10] running with process
> name twas11Cell01\twas11Node01\server3 and process id 5944
> Detailed IFix information: No IFixes applied to this build
> Host Operating System is Windows Server 2008, version 6.0 build 6002
> Service Pack 2
> Java version = 1.5.0, Java Compiler = j9jit23, Java VM name = IBM J9 VM
> was.install.root = C:/IBM/WebSphere/AppServer
> user.install.root = C:\IBM\WebSphere\AppServer\profiles\AppSrv01
> Java Home = C:\IBM\WebSphere\AppServer\java\jre
>
> As you can see it states that the Java version is 1.5.0.
>
> Ill try to search in WebSphere docs if there is an option to explicitly
> use java version.
>
> kind regards,
> Ivan
>
>
> On 1.3.2010 11:27, Bob Schellink wrote:
>> Hi Ivan,
>>
>> On 1/03/2010 09:00 PM, Ivan Furdi wrote:
>>
>>> LinkageError while defining class: org.apache.click.util.ClickUtils
>>> java.lang.UnsupportedClassVersionError:
>>> (org/apache/click/util/ClickUtils) bad major version at offset=6
>>> at java.lang.ClassLoader.defineClassImpl(Native Method)
>>
>>
>> I'm pretty sure this exception occurs because WAS 6.1 is running under
>> Java 1.4, while Click is compiled with 1.5.
>>
>> Can you confirm?
>>
>> kind regards
>>
>> bob
>>
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG -www.avg.com
>> Version: 9.0.733 / Virus Database: 271.1.1/2715 - Release Date: 02/28/10 20:34:00
>>
>>
>
>
> --
> Srdačan pozdrav,
>
> Ivan Furdi
>
>
Re: Deploying click on websphere
Posted by Ivan Furdi <iv...@uniplus.hr>.
Hi,
this is also a part of log concerning WebSphere :
WebSphere Platform 6.1 [ND 6.1.0.23 cf230910.10] running with process
name twas11Cell01\twas11Node01\server3 and process id 5944
Detailed IFix information: No IFixes applied to this build
Host Operating System is Windows Server 2008, version 6.0 build 6002
Service Pack 2
Java version = 1.5.0, Java Compiler = j9jit23, Java VM name = IBM J9 VM
was.install.root = C:/IBM/WebSphere/AppServer
user.install.root = C:\IBM\WebSphere\AppServer\profiles\AppSrv01
Java Home = C:\IBM\WebSphere\AppServer\java\jre
As you can see it states that the Java version is 1.5.0.
Ill try to search in WebSphere docs if there is an option to explicitly
use java version.
kind regards,
Ivan
On 1.3.2010 11:27, Bob Schellink wrote:
> Hi Ivan,
>
> On 1/03/2010 09:00 PM, Ivan Furdi wrote:
>
>> LinkageError while defining class: org.apache.click.util.ClickUtils
>> java.lang.UnsupportedClassVersionError:
>> (org/apache/click/util/ClickUtils) bad major version at offset=6
>> at java.lang.ClassLoader.defineClassImpl(Native Method)
>
>
> I'm pretty sure this exception occurs because WAS 6.1 is running under
> Java 1.4, while Click is compiled with 1.5.
>
> Can you confirm?
>
> kind regards
>
> bob
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.733 / Virus Database: 271.1.1/2715 - Release Date: 02/28/10 20:34:00
>
>
--
Srdačan pozdrav,
Ivan Furdi
Re: Deploying click on websphere
Posted by Bob Schellink <sa...@gmail.com>.
Hi Ivan,
On 1/03/2010 09:00 PM, Ivan Furdi wrote:
> LinkageError while defining class: org.apache.click.util.ClickUtils
> java.lang.UnsupportedClassVersionError:
> (org/apache/click/util/ClickUtils) bad major version at offset=6
> at java.lang.ClassLoader.defineClassImpl(Native Method)
I'm pretty sure this exception occurs because WAS 6.1 is running under Java 1.4, while Click is
compiled with 1.5.
Can you confirm?
kind regards
bob
Re: Deploying click on websphere
Posted by Ivan Furdi <iv...@uniplus.hr>.
Hi,
i used binary transfer mode when transfering files.
I tried using several builds for click - using original and re-compiled
jar files - (compiled with IBM Java)
but i keep getting errors from websphere .
Here is the log cut out :
[ERROR] [org.springframework.web.context.ContextLoader] Context
initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException:
Unexpected exception parsing XML document from ServletContext resource
[/WEB-INF/spring-beans.xml]; nested exception is java.lang.LinkageError:
LinkageError while defining class: org.apache.click.util.ClickUtils
java.lang.UnsupportedClassVersionError:
(org/apache/click/util/ClickUtils) bad major version at offset=6
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:222)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:148)
at
com.ibm.ws.classloader.CompoundClassLoader._defineClass(CompoundClassLoader.java:526)
at
com.ibm.ws.classloader.CompoundClassLoader.findClass(CompoundClassLoader.java:477)
at
com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:373)
at java.lang.ClassLoader.loadClass(ClassLoader.java:561)
at
org.apache.click.extras.spring.PageScopeResolver.resolveScopeMetadata(PageScopeResolver.java:97)
at
org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:207)
at
org.springframework.context.annotation.ComponentScanBeanDefinitionParser.parse(ComponentScanBeanDefinitionParser.java:84)
at
org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:69)
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1297)
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1287)
at
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:135)
at
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:92)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:507)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:398)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:342)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
at
org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:124)
at
org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:92)
at
org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:123)
at
org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:422)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352)
at
org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at
com.ibm.ws.wswebcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:605)
at
com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:265)
at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:271)
at
com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:88)
at
com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157)
at
com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:653)
at
com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:606)
at
com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:333)
at
com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:549)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1295)
at
com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1129)
at
com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:567)
at
com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:814)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:948)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2114)
at
com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:340)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1498)
--- end Original exception----
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:420)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:342)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
at
org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:124)
at
org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:92)
at
org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:123)
at
org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:422)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352)
at
org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at
com.ibm.ws.wswebcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:605)
at
com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:265)
at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:271)
at
com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:88)
at
com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157)
at
com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:653)
at
com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:606)
at
com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:333)
at
com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:549)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1295)
at
com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1129)
at
com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:567)
at
com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:814)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:948)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2114)
at
com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:340)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1498)
Caused by:
java.lang.LinkageError: LinkageError while defining class:
org.apache.click.util.ClickUtils
Could not be defined due to: (org/apache/click/util/ClickUtils) bad
major version at offset=6
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.
This is my spring-beans.xml
<beans:beans xmlns="http://www.springframework.org/schema/security"
xmlns:beans="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:context="http://www.springframework.org/schema/context"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-2.5.xsd
http://www.springframework.org/schema/security
http://www.springframework.org/schema/security/spring-security-2.0.4.xsd">
<context:component-scan base-package="hr.uniplus.im"
scope-resolver="org.apache.click.extras.spring.PageScopeResolver"/>
<!-- Spring Security Setup -->
</beans:beans>
Thanks,
Ivan Furdi
On 28.2.2010 19:07, Henry Saputra wrote:
> Hi Ivan,
>
> From the error message it maybe that jar files could not be read.
>
> Maybe you were using FTP with ASCII instead of binary mode when moving
> the files?
>
> - Henry
>
> 2010/2/28 <ivanf@uniplus.hr <ma...@uniplus.hr>>
>
> Hi again,
> yes im getting this message when trying to deploy app on Websphere :
>
> Error 404: SRVE0202E: Servlet [click-servlet]:
> org.apache.click.extras.spring.SpringClickServlet was found, but is
> corrupt: SRVE0227I: 1. Check that the class resides in the proper
> package
> directory. SRVE0228I: 2. Check that the classname has been defined
> in the
> server using the proper case and fully qualified package.
> SRVE0229I: 3.
> Check that the class was transferred to the filesystem using a binary
> transfer mode. SRVE0230I: 4. Check that the class was compiled
> using the
> proper case (as defined in the class definition). SRVE0231E: 5.
> Check that
> the class file was not renamed after it was compiled.
>
>
> My web.xml file looks like this (part of servlet configuration).
>
> <servlet>
> <servlet-name>click-servlet</servlet-name>
> <servlet-class>org.apache.click.extras.spring.SpringClickServlet</servlet-class>
> <load-on-startup>0</load-on-startup>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>click-servlet</servlet-name>
> <url-pattern>*.htm</url-pattern>
> </servlet-mapping>
>
>
> Am I missing this part (found on click examples) when deploying on
> websphere (without it it works perfectly on Apache Tomcat)
> <servlet-mapping>
> <servlet-name>ClickServlet</servlet-name>
> <url-pattern>/click/*</url-pattern>
> </servlet-mapping>
>
> Thank you,
> Ivan
>
> On 26.2.2010 21:21, Malcolm Edgar wrote:
> > you should not have to rebuild the Click jars. Have you seen a
> problem?
> >
> > regards Malcolm
> >
> > 2010/2/27 Ivan Furdi <ivanf@uniplus.hr <ma...@uniplus.hr>>:
> >> Hi everyone,
> >>
> >> I have a question with deploying click app on websphere .
> >>
> >> Im using a IBM WebSphere 6.1 which uses IBM Java 1.5.0.
> >> My question is - should i rebuild all click jar files (sources
> ) with IBM
> >> java and then deploy it on websphere?
> >>
> >> Does anyone has some experience or advice concerning the subject?
> >>
> >> Thank you ,
> >> Ivan Furdi
> >>
> >>
> >>
> >>
> >>
> >>
> >> No virus found in this incoming message.
> >> Checked by AVG - www.avg.com <http://www.avg.com>
> >> Version: 9.0.733 / Virus Database: 271.1.1/2711 - Release Date:
> 02/26/10 08:34:00
> >>
>
>
> --
> Srdačan pozdrav,
>
> Ivan Furdi
>
>
>
>
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.733 / Virus Database: 271.1.1/2713 - Release Date: 02/27/10 20:34:00
>
>
--
Srdačan pozdrav,
Ivan Furdi
Re:
Posted by Henry Saputra <he...@gmail.com>.
Hi Ivan,
>From the error message it maybe that jar files could not be read.
Maybe you were using FTP with ASCII instead of binary mode when moving the
files?
- Henry
2010/2/28 <iv...@uniplus.hr>
> Hi again,
> yes im getting this message when trying to deploy app on Websphere :
>
> Error 404: SRVE0202E: Servlet [click-servlet]:
> org.apache.click.extras.spring.SpringClickServlet was found, but is
> corrupt: SRVE0227I: 1. Check that the class resides in the proper package
> directory. SRVE0228I: 2. Check that the classname has been defined in the
> server using the proper case and fully qualified package. SRVE0229I: 3.
> Check that the class was transferred to the filesystem using a binary
> transfer mode. SRVE0230I: 4. Check that the class was compiled using the
> proper case (as defined in the class definition). SRVE0231E: 5. Check that
> the class file was not renamed after it was compiled.
>
>
> My web.xml file looks like this (part of servlet configuration).
>
> <servlet>
> <servlet-name>click-servlet</servlet-name>
>
> <servlet-class>org.apache.click.extras.spring.SpringClickServlet</servlet-class>
> <load-on-startup>0</load-on-startup>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>click-servlet</servlet-name>
> <url-pattern>*.htm</url-pattern>
> </servlet-mapping>
>
>
> Am I missing this part (found on click examples) when deploying on
> websphere (without it it works perfectly on Apache Tomcat)
> <servlet-mapping>
> <servlet-name>ClickServlet</servlet-name>
> <url-pattern>/click/*</url-pattern>
> </servlet-mapping>
>
> Thank you,
> Ivan
>
> On 26.2.2010 21:21, Malcolm Edgar wrote:
> > you should not have to rebuild the Click jars. Have you seen a problem?
> >
> > regards Malcolm
> >
> > 2010/2/27 Ivan Furdi <iv...@uniplus.hr>:
> >> Hi everyone,
> >>
> >> I have a question with deploying click app on websphere .
> >>
> >> Im using a IBM WebSphere 6.1 which uses IBM Java 1.5.0.
> >> My question is - should i rebuild all click jar files (sources ) with
> IBM
> >> java and then deploy it on websphere?
> >>
> >> Does anyone has some experience or advice concerning the subject?
> >>
> >> Thank you ,
> >> Ivan Furdi
> >>
> >>
> >>
> >>
> >>
> >>
> >> No virus found in this incoming message.
> >> Checked by AVG - www.avg.com
> >> Version: 9.0.733 / Virus Database: 271.1.1/2711 - Release Date:
> 02/26/10 08:34:00
> >>
>
>
> --
> Srdačan pozdrav,
>
> Ivan Furdi
>
>
>
>
>
Re: (unknown)
Posted by Bob Schellink <sa...@gmail.com>.
Hi Ivan,
The error is not very descriptive. Is there perhaps a stackTrace with more information? Click 2.1.0
was compiled with Sun JVM 1.5, so should be OK for WebSphere 6.1 without having to recompile. Of
course it wouldn't hurt to recompile it with IBM's 1.5 JVM and try it out. It should be as simple as:
/click-2.1.0/build> ant get-deps
/click-2.1.0/build> ant build-distribtion
On 28/02/2010 09:11 PM, ivanf@uniplus.hr wrote:
>
> Am I missing this part (found on click examples) when deploying on
> websphere (without it it works perfectly on Apache Tomcat)
> <servlet-mapping>
> <servlet-name>ClickServlet</servlet-name>
> <url-pattern>/click/*</url-pattern>
> </servlet-mapping>
>
You only need the above mapping if Click cannot deploy its files to the file system. I know WebLogic
is quite restrictive, but WebSphere should be OK. I've tested WebSphere 6.0 in the past and didn't
have any problems.
kind regards
bob