See below...

> -----Original Message-----
> From: Thomas Escobar [mailto:[EMAIL PROTECTED] 
> Sent: Monday, March 17, 2003 11:45 AM
> To: [EMAIL PROTECTED]
> Subject: [OS-webwork] Re: Is component.xml compulsory?
> 
> 
> Bernard and I had a similar weekend - I'm porting a WW
> 1.0 app to WW/Xwork (for fun, not production), ran
> into the same null pointer and resolved it the same
> way (root components in otherwise empty
> components.xml).  I'll pull my ServletContextListener
> as the real solution.  Thanks!
> 
> However, the reason I had added the
> ServletContextListener was as a (shot-in-the-dark)
> attempt to resolve another null pointer I was getting:
> 
> 
> ActionContext.getSession() always returns a null Map.
> 
> I've replaced this with:
> 
> ServletActionContext.getRequest().getSession() 
> 
> ...and all is fine, but I'm wondering if I haven't 
> misconfigured something (although walking through the code, 
> there's nothing in WW 2.0 that seems to set the session).  
> ActionContext.getSession() was useful in WW 1.0 for returning 
> a convenient wrapper around the HttpSession (SessionMap) - is 
> this not going to be the case anymore?  Will there be a 
> return of SessionAware eventually?

I believe both should be supported. I'll write this up as a bug. It's
something that should be done in the Webwork 2 side of the code, since
Xwork doesn't handle the HTTP side.

> 
> The other issue I ran into was the absence of many of
> the WW 1.0 JSP tags - url, action and bean in
> particular.  The roadmap makes no mention of these and
> I couldn't find details in the archives so I'll just
> ask: what are the status of these tags - deprecated,
> not yet implemented, terminated?

Not Implemented. For every feature you find missing in Webwork 2, please
create a Jira issue at jira.opensymphony.com for Webwork and assign the
version to be 2.0 and the person to be either myself or Patrick. That
way we can track all of the issues and create a realistic roadmap.

> 
> I'm not particularly distraught as there are clear
> techniques to switch to and (largely because of the 
> testimonials I've been reading in this list) I'm going to try 
> out Velocity but I am still curious about the absence of the tags.
> 
> Otherwise the port has been as smooth as can be.  The 
> interceptors and validation scheme have been excellent.  Great work!

I'm glad it's working well for you. If you think of anything else you
need added put a Jira issue in and we'll take a look. Also, if you find
anything lacking documentation, either put in a Jira issue for that, or
update the docs on the Wiki.

Jason


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to