[Logo] Enterprise Client Community
  [Search] Search   [Recent Topics] Recent Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
Using Wildfly? Clean up web.xml...  XML
Forum Index -> Deployment
Author Message
CaptainCasa

Power User
[Avatar]

Joined: 21/11/2007 12:23:06
Messages: 5258
Offline

(from mail conversation)

In October we moved all servlet/filter registrations from the web.xml into an API-based registration. The web.xml that is created with new projects is very short as consequence and only includes one listene registration for activating CaptainCasa.

Code:
   <listener>
     <listener-class>org.eclnt.jsfserver.util.CCServletContextListener</listener-class>
   </listener>


...in principal there was no need to clean up existing web.xml because both can coexist. - But: not with Wildfly application server: here resgistrations are "doubled" if they are both exsiting in web.xml and in the API registration.

There are "funny"effects from this: e.g. the compression filter is registered twice, so the result is a double-zipping of content - which the client has a bit problems to correctly understand... ;-)

So: clean up your web.xml! We attached the web.xml_template below which comes with new projects.

Regards, Björn
 Filename web.xml_template [Disk] Download
 Description
 Filesize 2 Kbytes
 Downloaded:  435 time(s)


Björn Müller, CaptainCasa GmbH
unger

Power User

Joined: 22/07/2008 05:19:28
Messages: 249
Offline

Hello Björn,

is that mandatory for Wildfly? I get org.eclnt.client.comm.http.SessionTimeoutException
starting a Swing application (jnlp and Client Browser).

Regards,
Joachim
CaptainCasa

Power User
[Avatar]

Joined: 21/11/2007 12:23:06
Messages: 5258
Offline

Hi,
yes, according to our experience this is mandatory for Wildfly.
Kind regards, Björn

Björn Müller, CaptainCasa GmbH
 
Forum Index -> Deployment
Go to:   
Powered by JForum 2.1.6 © JForum Team