• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Jboss 5.0 and porting Tomcat projects

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
As per a reply I made to another post I am porting a project which runs on a Tomcat 6.0 server to Jboss 5.0.

The problem I have is that the parameters I defined in the conf/context.xml are rejected by Jboss.

I would like to know where best to set up server wide settings on Jboss for potentially dynamically deployed projects.

e.g. for development, integration, Uat, Production, I would have a parameter set so that the application can show within which server environment it is running.
 
author
Posts: 5856
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You could try placing them in server/xxx/deployers/jbossweb.deployer/web.xml. Other than that, you would have to place them in each individual web.xml file.
 
Andy Davie
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I tried the 1st web.xml suggestion, but the values here do not seem to override the ones in the applications web.xml (set as defaults).

Putting them in the application web.xml is ok for a default but not much good for a standard environment setup. It would need reconfiguring every time the application is redployed - very messy.

With Tomcat there is a clear hierarchy:

conf/context.xml values take first (unless override value is set)
(you can use the conf/web.xml as well but I like the idea of the separate file)
conf/Catalina/localhost/<context>.xml has second precedence
(drawback here is that it is recopied from the applications META-INF/context.xml each time the application is redeployed)
and finally the values in the application, META-INF/context.xml and WEB-INF/web.xml.

------------------
I will try removing the parameters from the application web.xml and see if this helps at all. I am still interested in hearing how others set up the static server context for their applications.
 
Andy Davie
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
ok, I removed the default values from the applications web.xml and I am now getting the ones from the jbossweb.deployer web.xml.

Good enough I guess.
 
Get me the mayor's office! I need to tell her about this tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic