DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31293>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31293

javax.servlet.ServletException: Cannot find message resources under key 
org.apache.struts.action.MESSAGE

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID
            Version|Unknown                     |1.1 Beta 3



------- Additional Comments From [EMAIL PROTECTED]  2004-09-19 12:58 -------
Ralf,

It would be better to post questions like this on the user list first, before 
raising a bug - so I'm closing this for now. I'm not sure if I can help or not 
with whats going wrong here, but post to the user list and someone else may 
know the solution to your problem. I would suggest posting a bit more detail - 
the snipet of the jsp thats causing the error and maybe the struts-config.xml 
showing how your application resources are configured would probably be useful.

The bundle attribute defaults to "org.apache.struts.action.MESSAGE" if you 
don't specify it - which is what your stack trace is showing. I'm surprised 
that if it was working before in Struts 1.1 that it isn't now.

If it does turn out to actually be a bug then you can always re-open this.

Niall


P.S. There's no need to do anything about not being able to assign bugs to 
Struts 1.2 - until its officailly *released* then anything should be logged 
against the nightly build. The vote for Struts 1.2.4 has just passed and this 
issue is on the TODO list (B5 in section 1.9) as part of the release process - 
so it should be done shortly

http://wiki.apache.org/struts/StrutsRelease124

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to