[jira] Commented: (SHALE-277) Shale is eating 500s errors
[ http://issues.apache.org/struts/browse/SHALE-277?page=comments#action_38420 ] Torsten Krah commented on SHALE-277: Same here. Added the parameter to the web.xml but my page does not get called. kind regards Shale is eating 500s errors --- Key: SHALE-277 URL: http://issues.apache.org/struts/browse/SHALE-277 Project: Shale Issue Type: Bug Components: Core Affects Versions: 1.0.4-SNAPSHOT, 1.0.3 Environment: Tomcat 5.5.17 + Myfaces 1.1.3 Reporter: Veit Guna Assigned To: Craig McClanahan When using shale-core for the s:token tag in my myfaces webapp, shale is eating 500 errors. That means if for example a Nullpointer Exception occurs, it doesn't let tomcat use the custom error page configured in the web.xml for 500 errors. If I remove shale-core from my webapp, everything works fine and the custom error-page is displayed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SHALE-312) Add serial version UIDs
Add serial version UIDs --- Key: SHALE-312 URL: http://issues.apache.org/struts/browse/SHALE-312 Project: Shale Issue Type: Bug Affects Versions: 1.0.3 Reporter: Rahul Akolkar Assigned To: Rahul Akolkar Fix For: 1.0.4-SNAPSHOT Some Serializable classes (in framework) do not define serial version UIDs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SHALE-312) Add serial version UIDs
[ http://issues.apache.org/struts/browse/SHALE-312?page=all ] Rahul Akolkar resolved SHALE-312. - Resolution: Fixed Add serial version UIDs --- Key: SHALE-312 URL: http://issues.apache.org/struts/browse/SHALE-312 Project: Shale Issue Type: Bug Affects Versions: 1.0.3 Reporter: Rahul Akolkar Assigned To: Rahul Akolkar Fix For: 1.0.4-SNAPSHOT Some Serializable classes (in framework) do not define serial version UIDs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SHALE-299) Refactor functionality from shale-core into separate modules
[ http://issues.apache.org/struts/browse/SHALE-299?page=all ] Craig McClanahan resolved SHALE-299. Resolution: Fixed Assignee: Craig McClanahan The refactorings contemplated by this issue have been completed, so marking it fixed. Refactor functionality from shale-core into separate modules Key: SHALE-299 URL: http://issues.apache.org/struts/browse/SHALE-299 Project: Shale Issue Type: Task Components: Core Reporter: Craig McClanahan Assigned To: Craig McClanahan Fix For: 1.0.4-SNAPSHOT To improve the ability of users to select which pieces of Shale functionality they wish to use, split the following functional subsets out of shale-core into their own (new) modules: * shale-application -- Application controller features * shale-validator -- Integration with Commons Validator * shale-view -- View controller, exception handling, application callbacks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SHALE-285) Test whether shale-tiger can be postprocessed for use on JDK 1.4 systems
[ http://issues.apache.org/struts/browse/SHALE-285?page=all ] Craig McClanahan resolved SHALE-285. Resolution: Not A Problem Thanks to James Mitchell's testing during ApacheCon last week, we now have evidence that the shale-sql-browser webapp (including the shale-tiger library) can run succssfully on a JDK 1.4 system, once both have been translated. Therefore, marking this one as not a problem, since it actually does work :-). Test whether shale-tiger can be postprocessed for use on JDK 1.4 systems Key: SHALE-285 URL: http://issues.apache.org/struts/browse/SHALE-285 Project: Shale Issue Type: New Feature Components: Tiger Reporter: Craig McClanahan Several Apache projects have started using postprocessors like RetroWeaver and RetroTranslater to take code that uses Java SE 5 syntax and semantics (including annotations) and make it work on a JDK 1.4 JVM. Analyze whether this approach will work for shale-tiger (and applications built with it), and (if so) decide whether to release it as a supported feature (or perhaps as a sandbox feature). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
