You should try out the FQN plugin for IDEA... It makes it as easy as CTRL-SHIFT-Q to get the fully qualified name.
> -----Original Message----- > From: Lars Fischer [mailto:[EMAIL PROTECTED] > Sent: Saturday, August 16, 2003 3:53 AM > To: [EMAIL PROTECTED] > Subject: RE: [OS-webwork] Simplicity of WW2 > > > You should give IDEA a try ... > > > I would think that using the fully qualified classname isn't any > > harder since most of the time you are copy pasting it anyway. > > > > Also, when using refactoring tools to rename classes, or move them, > > the tools can often update xml or text files. This > wouldn't work with > > short names. > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > On Behalf Of > > Jason Carreira > > Sent: Friday, 15 August 2003 2:15 PM > > To: [EMAIL PROTECTED] > > Subject: RE: [OS-webwork] Simplicity of WW2 > > > > > > Create a jira for <default-action-package> for XWork 1.0 and we'll > > take a look at what it will take to make it happen. > > > > -----Original Message----- > > From: John Patterson [mailto:[EMAIL PROTECTED] > > Sent: Thursday, August 14, 2003 4:00 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [OS-webwork] Simplicity of WW2 > > > > > > That is a great improvement! Still one extra step per > action though. > > It would not be very often that one would want to change > the default > > action-view search behaviour. Just setting a java package property > > would be enough > (<defaultActionPackage>com.myorg.myapp.actions</...). > > > > I just thought that if I saw such an ease of use feature > when looking > > for a framework that would have impressed me. I hate having to > > configure things with xml that should be default. One more > step that > > can go wrong. Smart defaults are a developers friend. > > > > ----- Original Message ----- > > From: Jason Carreira <mailto:[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Sent: Thursday, August 14, 2003 7:51 PM > > Subject: RE: [OS-webwork] Simplicity of WW2 > > > > I'm not sure about this... this sounds more complicated to me than > > explicitly telling it what to look for... you have to read > a lot more > > docs for what the defaults are, etc. With the stuff I did > to make the > > default stuff pulled out into a separate file, here's what the > > xwork.xml for the Config Browser app looks like: > > > > <!DOCTYPE xwork PUBLIC "-//OpenSymphony Group//XWork 1.0//EN" > > "http://www.opensymphony.com/xwork/xwork-1.0.dtd"> > > > > <xwork> > > <include file="webwork-default.xml"/> > > > > <package name="default" extends="webwork-default" namespace="/"> > > <interceptors> > > <interceptor-stack name="config-browser-default"> > > <interceptor-ref name="component"/> > > <interceptor-ref name="validationWorkflowStack"/> > > </interceptor-stack> > > </interceptors> > > <default-interceptor-ref name="config-browser-default"/> > > <global-results> > > <result name="error" type="velocity">error.vm</result> > > </global-results> > > <action name="namespace" > > class="com.opensymphony.webwork.config_browser.NamespaceAction"> > > <result type="velocity" > > name="success">namespaces.vm</result> > > <result type="velocity" > name="input">namespaces.vm</result> > > </action> > > <action name="actionNames" > > class="com.opensymphony.webwork.config_browser.ActionNamesAction"> > > <result type="velocity" > > name="success">actionNames.vm</result> > > <result type="velocity" > name="input">actionNames.vm</result> > > </action> > > <action name="showConfig" > > class="com.opensymphony.webwork.config_browser.ShowConfigAction"> > > <result type="velocity" > > name="success">showConfig.vm</result> > > <result type="velocity" > name="input">showConfig.vm</result> > > </action> > > </package> > > </xwork> > > > > That's the whole thing. It's pretty simple, I think. > > > > Jason > > > > -----Original Message----- > > From: John Patterson [mailto:[EMAIL PROTECTED] > > Sent: Thursday, August 14, 2003 7:40 AM > > To: Webwork > > Subject: [OS-webwork] Simplicity of WW2 > > > > > > When searching for a good web framework I looked for > simplicity first > > and power second. The thing which stood out about WW1 was that it > > seemed easier to get new actions up and running quickly. > Being able > > to define a default package made the config very simple. I > think that > > some of this has been lost in WW2. > > > > I would like to suggest the ability to have "default" > mappings between > > action aliases, action classes and views so that if I enter the URL > > "/action/search" or "search.action" the framework will look for a > > class named SearchAction and a view of "/search.jsp" > (success result). > > > > This must be able to be configured so that instead of jsp > some other > > view technology could be used as the default. The > directory in which > > the default jsp view should be searched for should also be > able to be > > specified ("/" as default) > > > > The action search path should be able to be specified. If > an action > > with a namespace is used ("/products/search") then the action class > > should be searched for in the sub package "products" of > every package > > in the search path. > > > > Of course this would only work for actions that only need > one specific > > result (may use global results) > > > > To my mind, this kind of shortcut makes a framework appear easy to > > use. In reality it is easy to configure every action in > your xml file > > but it is an obvious way to show "look how easy it is to > use Webwork". > > The fine grained control would remain for more complicated actions. > > > > John. > > > > > > > > ------------------------------------------------------- > 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/psa00100003ave/direct;at.aspnet _072303_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- 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/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork