Re: [OS-webwork] issue with ApplicationLifecycleListener
On Sunday, August 3, 2003, at 11:36 PM, Scott Farquhar wrote: Some application servers pass null to init() and dispose() events. Old versions of Orion even passed null to init() when the server was shut down. As for fixing it - it should be easy to see where the null pointer exception is ;) Yup, and as I said in my original message, I know exactly where the NPE is occurring, and I could easily add a check for null there to skip the offending code. Thanks for the tidbit about some app. servers doing funky things with these listeners - I'll check into it. My concern was more systemic since I have not buried myself completely in WW2 code to see if some other piece of code could have been nulling something erroneously or something along those lines. Erik --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
[OS-webwork] [JIRA-Opensymphony] Created: (WW-240) Caching of writer incompatible with tag reuse
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-240
Here is an overview of the issue:
-
Key: WW-240
Summary: Caching of writer incompatible with tag reuse
Type: Bug
Status: Assigned
Priority: Major
Project: WebWork
Components:
Views
Versions:
2.0
Assignee: Patrick Lightbody
Reporter: Conor MacNeill
Created: Mon, 4 Aug 2003 4:45 AM
Updated: Mon, 4 Aug 2003 4:45 AM
Environment: JBoss 3.2.1, Win2k, Jetty
Description:
The caching of the writer instance in the AbstractUITag class' mergeTemplate method is
not correct
if (writer == null) {
writer = pageContext.getOut();
}
When the tag is reused, the incorrect writer is used and content appears in odd
places. The following change
Writer outputWriter = writer;
if (outputWriter == null) {
outputWriter = pageContext.getOut();
}
and using the outputWriter in place of writer in the merge call should fix this while
still allowing the writer to be explicitly set.
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.opensymphony.com/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
[OS-webwork] [JIRA-Opensymphony] Created: (XW-70) OGNL does not allow explicit false for boolean properties
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.opensymphony.com/secure/ViewIssue.jspa?key=XW-70
Here is an overview of the issue:
-
Key: XW-70
Summary: OGNL does not allow explicit false for boolean properties
Type: Bug
Status: Assigned
Priority: Critical
Project: XWork
Fix Fors:
1.0-beta1
Versions:
1.0-beta1
Assignee: Jason Carreira
Reporter: Mathias Bogaert
Created: Mon, 4 Aug 2003 4:49 AM
Updated: Mon, 4 Aug 2003 4:49 AM
Description:
Here is my problem:
1. a checkbox does not set a false value, so I had to include manually a hidden field
2. try adding the following to OgnlUtilTest testSetPropertiesBoolean:
props = new HashMap();
props.put("useful", "false");
OgnlUtil.setProperties(props, foo, context);
assertEquals(false, foo.isUseful());
You'll see that it fails, while it should support explicit set of false.
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.opensymphony.com/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
[OS-webwork] [JIRA-Opensymphony] Created: (WW-241) ServletRedirectResult should redirect to contextPath + location
Message: A new issue has been created in JIRA. - View the issue: http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-241 Here is an overview of the issue: - Key: WW-241 Summary: ServletRedirectResult should redirect to contextPath + location Type: Bug Status: Assigned Priority: Critical Project: WebWork Components: Dispatch Fix Fors: 2.0-beta1 Versions: 2.0-beta1 Assignee: Patrick Lightbody Reporter: Mathias Bogaert Created: Mon, 4 Aug 2003 5:12 AM Updated: Mon, 4 Aug 2003 5:12 AM Description: When redirecting, it should include the context path. This allows applications to specify "/blah/blah.action" and not having to worry about their deployed context path. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.opensymphony.com/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
[OS-webwork] [JIRA-Opensymphony] Created: (WW-242) Checkbox check for == "true" does not happen on same class
Message: A new issue has been created in JIRA. - View the issue: http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-242 Here is an overview of the issue: - Key: WW-242 Summary: Checkbox check for == "true" does not happen on same class Type: Bug Status: Assigned Priority: Major Project: WebWork Components: Views Fix Fors: 2.0-beta1 Versions: 2.0-beta1 Assignee: Patrick Lightbody Reporter: Mathias Bogaert Created: Mon, 4 Aug 2003 5:15 AM Updated: Mon, 4 Aug 2003 5:15 AM Description: Velocity documentation: "The only exception to this is equality '==', where Velocity requires that the objects on each side of the '==' is of the same class." But the checkbox tag actual value might not be string. Attached is the simple but effective patch. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.opensymphony.com/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
[OS-webwork] [JIRA-Opensymphony] Created: (WW-243) Cache Velocity templates in production
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-243
Here is an overview of the issue:
-
Key: WW-243
Summary: Cache Velocity templates in production
Type: Bug
Status: Assigned
Priority: Major
Project: WebWork
Fix Fors:
2.0-beta1
Versions:
2.0-beta1
Assignee: Patrick Lightbody
Reporter: Mathias Bogaert
Created: Mon, 4 Aug 2003 5:52 AM
Updated: Mon, 4 Aug 2003 5:52 AM
Description:
WebWork should enable caching velocity templates in production (war file). We can
assume that the application is in 'production' when it is deployed as WAR (and thus
getRealPath("") returns null). Attached is a patch.
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.opensymphony.com/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
[OS-webwork] Webwork 1.3
To all non webwork2 junkies: Any objections to adding ui:hidden and ui:form tags to webwork 1.3? --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] issue with ApplicationLifecycleListener
Here are further details on this issue:
I turned ApplicationLifecycleListener into a
ServletContextAttributeListener too, with these methods added:
public void attributeAdded(ServletContextAttributeEvent event) {
log.info("event = " + event.getName());
}
public void attributeRemoved(ServletContextAttributeEvent event) {
log.info("event = " + event.getName());
}
public void attributeReplaced(ServletContextAttributeEvent event) {
log.info("event = " + event.getName());
}
Here is the relevant order of events:
Aug 4, 2003 11:19:37 AM
com.opensymphony.webwork.lifecycle.ApplicationLifecycleListener
contextInitialized
INFO: application = [EMAIL PROTECTED]
Aug 4, 2003 11:19:37 AM
com.opensymphony.webwork.lifecycle.ApplicationLifecycleListener
contextInitialized
INFO: container =
[EMAIL PROTECTED]
de29
Aug 4, 2003 11:19:37 AM
com.opensymphony.webwork.lifecycle.ApplicationLifecycleListener
attributeAdded
INFO: event = DefaultComponentManager
Aug 4, 2003 11:19:37 AM
com.opensymphony.webwork.lifecycle.ApplicationLifecycleListener
attributeAdded
INFO: event = ComponentConfiguration
08/04 11:19:37 user JSPServlet: init
08/04 11:19:37 info Deploying enterprise application "Flash Remoting
EAR" from: file:/C:/JRun4/lib/flashgateway.ear
08/04 11:19:37 info Deploying web application "Flash Remoting" from:
file:/C:/JRun4/lib/flashgateway.ear
08/04 11:19:38 user JSPServlet: init
08/04 11:19:38 user FlashGatewayServlet: init
Server default ready (startup time: 34 seconds)
08/04 11:19:44 user FlashGatewayServlet: destroy
Aug 4, 2003 11:19:44 AM
com.opensymphony.webwork.lifecycle.ApplicationLifecycleListener
attributeRemoved
INFO: event = ComponentConfiguration
Aug 4, 2003 11:19:44 AM
com.opensymphony.webwork.lifecycle.ApplicationLifecycleListener
attributeRemoved
INFO: event = DefaultComponentManager
Aug 4, 2003 11:19:44 AM
com.opensymphony.webwork.lifecycle.ApplicationLifecycleListener
contextDestroyed
INFO: event =
javax.servlet.ServletContextEvent[source=jrun.servlet.JRunServletContext
@52eef4]
Aug 4, 2003 11:19:44 AM
com.opensymphony.webwork.lifecycle.ApplicationLifecycleListener
contextDestroyed
INFO: application = [EMAIL PROTECTED]
Aug 4, 2003 11:19:44 AM
com.opensymphony.webwork.lifecycle.ApplicationLifecycleListener
contextDestroyed
INFO: container = null
08/04 11:19:44 error RuntimeException thrown in operation stop
[1]java.lang.NullPointerException
at
com.opensymphony.webwork.lifecycle.ApplicationLifecycleListener.conte
xtDestroyed(ApplicationLifecycleListener.java:44)
at
jrun.servlet.JRunServletContext.fireContextDestroyedEvent(JRunServlet
Context.java:365)
As you can probably tell, I added some additional logging in the
contextInitialized/Destroyed message.
So, JRun removes things from application scope before calling the
contextDestroyed method. I'll patch this up by doing a comparison and
cleanup in attributeRemoved and keep the class implementing
ServletContextAttributeListener.
After I get this all working on my end, I'll submit a patch.
Erik
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Webwork 1.3
Hani Suleiman wrote: To all non webwork2 junkies: Any objections to adding ui:hidden and ui:form tags to webwork 1.3? Not from this side of the pond. Go for it. -- ATLASSIAN - http://www.atlassian.com Expert J2EE Software, Services and Support --- Need a simple, powerful way to track and manage issues? Try JIRA - http://www.atlassian.com/software/jira --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
[OS-webwork] [JIRA-Opensymphony] Created: (XW-71) Field Errors need to be able to hold more than one error per field
Message: A new issue has been created in JIRA. - View the issue: http://jira.opensymphony.com/secure/ViewIssue.jspa?key=XW-71 Here is an overview of the issue: - Key: XW-71 Summary: Field Errors need to be able to hold more than one error per field Type: New Feature Status: Assigned Priority: Major Project: XWork Components: Validators Fix Fors: 1.0-beta1 Versions: 1.0-beta1 Assignee: Jason Carreira Reporter: Jason Carreira Created: Tue, 5 Aug 2003 12:07 AM Updated: Tue, 5 Aug 2003 12:07 AM Description: Right now field errors are held in a straight map of fieldname -> error message pairs. We need to be able to add more than one error message per field name, so I suggest these be List's of errors. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.opensymphony.com/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
