Hi all, I got a ear deployed on WAS 4.0, and I use IBM Http server. Using my browser, I can access a jsp page, but not a html one. For example, http://www.myserver.com/wbstore/index.jsp works fine while http://www.myserver.com/wbstore/index.html returns error 404. I have added a ibm-web-ext.xmi file in the WebINF with FileServingEnabled = true, but it seems I need something else to solve my problem. Any idea ? (Note : the same ear works fine when deployed on Weblogic or Sybase EAS) (Thanks Kyle, and sorry for the typo) [This message has been edited by Bill Bailey (edited November 16, 2001).]
/ JeanLouis<br /><i>"software development has been, is, and will remain fundamentally hard" (Grady Booch)</i><br /> <br />Take a look at <a href="http://www.epfwiki.net/wikis/openup/" target="_blank" rel="nofollow">Agile OpenUP</a> in the Eclipse community
I'm sorry, but did you mean to say "index.html" in the second line? Otherwise I'm confused... (you may want to edit your post)... Kyle ------------------ Kyle Brown, Author of Enterprise Java (tm) Programming with IBM Websphere See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.
Well, something is really puzzling me. I've rebuilt my ear file using IBM AAT. (I mean just used my former ear file and clicked 1 button to generate another ear) I've deployed it and the application is now up and running. The only difference beween the 2 ear seems to be the ibm-web-ext.xmi and ibm-web-bnd.xmi files. Here are my questions 1) The xmi files are not part of the J2EE specification but seem to be mandatory for an application to work fine using WAS 4. Am I right ? 2) Did someone already experienced the same kind of problem ? Maybe I've missed something important somewhere