I'm not knocking down webapps, I just think that it's important to call things what they are. J2EE is a published spec, there's no particular merit to using all it has to offer, nor is there particular merit in only using servlets. Calling an xwork/webwork2 solution with hibernate a J2EE app, to me at least, seems dishonest. This not not a comment on the quality of said app, in fact, chances are it works a hell of a lot better than a 'traditional' jsp/ejb/jms/whatever 'J2EE' app, but lets stick to calling things what they are, rather than what we'd like them to be.
On Sunday, August 17, 2003, at 10:00 PM, Jason Carreira wrote:
So who's building full J2EE apps without a web front end (at least for the adminsitration)? Even someone doing big batch processes needs to see how they're progressing sometimes...
_072303_01/01-----Original Message----- From: Hani Suleiman [mailto:[EMAIL PROTECTED] Sent: Sunday, August 17, 2003 8:38 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Simplicity of WW2 - Practical ideas
Just to play the devil's advocate, people using full J2EE are unlikely to be huge xwork/webwork fans anyway. Unless of course you mean servlets/web containers, rather than J2EE. As surprising as it is, an app with xwork, webwork, lucene, hibernate, sitemesh, and oscache is not a particularly J2EE app. All it uses is jdbc (now part of the core JDK) and servlets.
On Sunday, August 17, 2003, at 06:24 PM, Mike Cannon-Brookes wrote:
Anders,instantiate the
I have to say that this is a _bad_ idea.
You can already test actions to setup xwork.xml - justobject, call your setter methods and run!most of the
People doing J2EE understand XML, they have to. All descriptors are XML. Xwork.xml is not _that_ complex for a hello world example,elements are optional.if a view is
However, there _is_ a problem with WW2 at the moment that("action returnednot found, no debug page is shown. I think it should be"input" but not "input" view found).system which will
M
On 18/8/03 8:03 AM, "boxed" ([EMAIL PROTECTED]) penned the words:
I had a discussion on #java with Epesh, and he expressed the sentiment that WW2 might be turning into a too complexit leavesalienate new users and be "popular with the gearheads and such when"Simplicity in WW2"nerd-domain". After reading the responses to thethat willemail I must agree that it looks like this.
Now, to make me sound less like a whiner and more like someone with good ideas, here is a practical proposal:
The way you have to declare each action in a rather complex XML config file before even rudimentary testing increases the learning-curve needlessly. I propose a few simple featuresActions maphelp the average users:
Actions can be run with the fully qualified class name.the exposedby default to 1. a view document with the name of the action. 2. if 1 fails, a debug document that displays a list ofworld typeproperties and their current value.
This will cut the amount of explaining needed for a hellothat will cutapp down by an entire step. Anyone else got ideas like thisare availabledown on the learning curve for newbies?
Anders Hovmöller
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and ForumsStudio .NET.now. Download today and enter to win an XBOX or Visualsites includinghttp://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.NETData 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
_______________________________________________
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
------------------------------------------------------- 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
