In thinking further about the namespaces concept, I think that you could take it a step further by applying it to components. Right now, you can scope components (components.xml) as app, session, or request. You could extend this to be app, session, or request per namespace. In other words declare a component as one that spans namespaces or is per namespace. Spanning namespaces is what it is doing now. However adding the "per namespace" would allow me to have different instances of a component for each namespace. Programmatically, this would just require a simple naming convention like namespace.component in the session. This way, instead of having a session Counter for all parts of my application, each sub application(namespace) can have it's own little instance. I suppose you can add a third declaration, as well, where you declare that the component is just for a certain namespace(s).
Thoughts? LES www.mindmeld.ws [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, June 08, 2003 4:12 PM To: [EMAIL PROTECTED] Subject: [OS-webwork] NameSpaces Disclaimer:: OK, I've looked through the list to see if this has been discussed before and don't see it. So, if this is a repeat feel free to direct me to the previous response. :) I really like the namespace concept in the configuration. However, I have three questions. - Should the ww:url tag not automatically default the current namespace along with the servlet context? In other words, right now if I pull up a jsp page in the testNameSpace and that page has <ww:url value="another.jsp"/> in it. Should it not fill the url with http://www.mysite.com/servletcontext/testNameSpace/another.jsp? - As an extension to the last question, would it not complete the inheritence model that you have established in packages if the <ww:url> tag would first look to see if another.jsp exists in the current context and then if not iterate up the inheritence tree until it finds an ancestor namespace that does contain it? This would allow you to "share" pages and actions across namespaces and override others for some namespaces. I would think this would be a very nice feature. I would think that other tags like action would also have to support this. - Would it be possible to extend the package tag to include a fileref attribute? This fileref would point to another configuration file that defines the actions, interceptors, etc for that package. It would use the same inheritence approach mentioned previously to search for the file (checking for the file in the different namespaces or class paths. This would improve the modularization of the application, turning packages into web sub-components (or sup apps). Just some thoughts I had will I was working with ww2. BTW, did I mention how much I like it? :) LES www.mindmeld.ws [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
