CFMX 8.0.1 and Websphere 6.1ND

[ejc770]

We are using WAS 6.1ND and CFMX Ent. 8.0.1 and updated the web.xml to include index.html or index.htm as default files(
<welcome-file-list id="WelcomeFileList_1034013110672">
<welcome-file>index.cfm</welcome-file>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
</welcome-file-list>
but have issues with only the first item in the list is displayed by default. If we move items around in the list always the first is displayed but the others are not. Is this a known issue?

[Newsgroup_User]

ejc770 wrote:
> We are using WAS 6.1ND and CFMX Ent. 8.0.1 and updated the web.xml to include
> index.html or index.htm as default files(
> <welcome-file-list id="WelcomeFileList_1034013110672">
> <welcome-file>index.cfm</welcome-file>
> <welcome-file>index.html</welcome-file>
> <welcome-file>index.htm</welcome-file>
> </welcome-file-list>
> but have issues with only the first item in the list is displayed by default.
> If we move items around in the list always the first is displayed but the
> others are not. Is this a known issue?

Is this the only change you made to your web.xml? Requests for .html and
.htm files should not be send to ColdFusion by WebSphere in the first
place, so I find it unlikely putting them in the WelcomeFileList has any
effect whatsoever. Did you add servlet mappings for .html and .htm as well?

Jochem

--
Jochem van Dieten
Adobe Community Expert for ColdFusion

[ejc770]

Yes, we have a servlet mapping. html and htm files are processing if they are referenced directly. Our issue is displaying the default document (ie - going to www.mysite.com and displaying index.html)

[ejc770]

does anyone have any feedback?

[Guest]

We are having the same problem with WAS 6.1 and 8.0.1. One of our vendor applications uses index.cfm and another uses default.cfm as the welcome file. If we set it up to do both accordingly it only recognizes the first one in the list. We are unfamiliar with WAS and it seems to store the active configuration files in a cryptic directory structure but even with modifying them all we were unsuccessful.

[Guest]

Out of curiosity, did you regenerate and redeploy your web server mappings after deploying the ear?

[Guest]

We deployed a default ear, then tried to make changes to the proper configuration files after we discovered the issue. Do you think building the changes into a new ear and then deploying would have some impact?

[fargond]

thanks, very informative post.

[Karzons]

Keep up the good work.