ActionSupport extends BaseActionSupport which implements LocaleAware and
LocallizedTextUtil.getText().is therefore used to lookup UI tag labels.
In my app, there is no need for localization at this point but
LocalizedTextUtil logs a warning every time time it cannot find a
localized name. I
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.opensymphony.com/secure/ViewIssue.jspa?key=XW-76
Here is an overview of the issue:
Title: Any examples of WebWork/WebWork2 using XSLT as the view mechanism?
Hi All,
I've been looking at a few frameworks for an upcoming project and would like to use XSLT as the view mechanism. I checked the JavaDoc for WebWork and saw that there's an XSLT Servlet but I haven't been able
On 8/17/03 10:05 PM, Jason Carreira [EMAIL PROTECTED] wrote:
Along the lines of making it easier for new users, we need something like
this:
http://www.springframework.org/docs/MVC-step-by-step/Spring-MVC-step-by-step.h
tml
If someone else wants to do it, great... If not, I'll eventually
can we have a sneak peak at what you've done?
I was about to post a question asking if anyone has started to work on
anykind of xwork/webwork2 introductory article or tutorial.
Tracy Snell wrote:
On 8/17/03 10:05 PM, Jason Carreira [EMAIL PROTECTED] wrote:
Along the lines of making it easier
This will cut the amount of explaining needed for a hello world type app
down by an entire step. Anyone else got ideas like this that will cut
down on the learning curve for newbies?
Of course, start with providing a tutorial.
---
This
Hello..
i'm a new user of iReports and i face the following problem:
I'm preparing a report and the SUMMARY part of the ouput shud get me the
SUM of values of the FIELD NAME ACT_LIAB1 only when the field
PROD_SUB_TYPE = ACD..This is one particular condition.
How do i go about this..?
I
On Sun, 17 Aug 2003, Hani Suleiman wrote:
A whole big bunch of people. If you want to show progress of batch
processes, a web app is probably the absolutely stupidest way of doing
it. A request/response paradigm is a pretty foolish way of providing
continuous feedback. A swing client would be
In the WW1.3 distribution there are a couple of examples. Look in the views.properties
file and you will find some references to XSLT views (for example from the actions
Primes and LoanCalc). The XSLT files are located somewhere in the examples/web folder.
I do not use this myself so I do not
Francisco,
If the iteratorstatus hasn't been copied from webwork1, then it should
be. Iterator status has more than just count, it has isFirst, isLast,
odd, even, modulus etc.
If this doesn't exist in webwork2, please add a JIRA issue.
Cheers,
Scott
Francisco Hernandez wrote:
anyone else
Rainer,
What were these used for? Loading global i18n properties files, or loading
other WW properties?
If it's the first I'm definitely for re-adding it - I've been looking for
this feature.
M
On 18/8/03 6:04 PM, Rainer Hermanns ([EMAIL PROTECTED]) penned the
words:
With webwork1.x you
Mike,
as far as I know, they were used for both... Will look into this in more
detail...
I can readd and commit this feature later today.
--Rainer
Mike Cannon-Brookes wrote:
Rainer,
What were these used for? Loading global i18n properties files, or loading
other WW properties?
If it's the
Thanks. Could have done it for you, just wasn't sure if I was configuring
everything correctly.
/Ian
--
From Down Around, Inc.
Innovative IT solutions
Software Architecture * Design * Development
~~
web:www.fdar.com
email: [EMAIL PROTECTED]
Francisco,
Take a look at the Counter utility bean, this is what it's for. Look at the
expressions.jsp (or used to be called that) in the examples.
Cheers,
Mike
On 18/8/03 9:37 PM, Francisco Hernandez ([EMAIL PROTECTED]) penned the
words:
anyone else think it would be useful to add a count
i believe line 71 in ServletRedirectResult should be:
response.sendRedirect(request.getContextPath() + / + location);
it currently is:
response.sendRedirect(request.getContextPath() + location);
I just checked out cvs, and this file is at version 1.3 so im assuming
this problem also exists in
Title: Message
My issue was not with fully qualified names in the
xwork.xml file. I agree that this would not be worth the extra
complexity. I would like to avoid creating *any* entry in the
configfor simple actions. Only create an entry in the config when
the default behaviour is not
540 modelos de cartas comerciais e diversos outros documentos essenciais
para a comunicação de empresas e profissionais liberais.
Nunca mais perca tempo tentando redigir documentos novos.
Modelos revisados e atualizados conforme as normas mais recentes de
comunicação comercial.
Indispensável
Jira seems to be down still.
- Original Message -
From: Jason Carreira [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 18, 2003 2:59 AM
Subject: RE: [OS-webwork] Simplicity of WW2 - Practical ideas
I'm open to having a package-wide default action package which would be
There is a facility for adding global i18n message files...
com.opensymphony.xwork.util.LocalizedTextUtil:
public static void addDefaultResourceBundle(String resourceBundleName)
It has a static initializer to load the default:
static {
Keep in mind we already have the ability to add more config files for
action configs in the include element in xwork.xml. There's only about
5 or 5 properties used by WW2 from the webwork.properties, so I'm not
sure how useful it is to split this up across multiple files...
-Original
Do the current tags try to use getText() all the time? This should be
changed to not do this by default, if possible. To get localized text,
you should do text('myKey'). This could be part of the problem with
render speed.
-Original Message-
From: Dag Liodden [mailto:[EMAIL PROTECTED]
Ok, who remembers the servlet spec details? Does it need the /? This
is my fault, anyway... The reason for 1.3 vs. 1.4 is the switch to
java.net CVS.
Jason
-Original Message-
From: Francisco Hernandez [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2003 9:54 AM
To: [EMAIL
Title: Message
How
would you suggest it's found? How does it default? How are views defined? How
does it know what class you're talking about? What about extending a package
with another package?
-Original Message-From: John Patterson
[mailto:[EMAIL PROTECTED] Sent: Monday,
Hi,
This can sound very basic but I'm looking for some insights to make my decisions on
Webwork
1development ...
I'll build an application with i18n support and looking at my view options with
Webwork I saw only
JSP examples, I'd like to use Velocity templates, but how can I get properties and
I tried this in tomcat 4.x and getContextPath() was not returning the
ending slash, I havent bothered testing on other servers
Jason Carreira wrote:
Ok, who remembers the servlet spec details? Does it need the /? This
is my fault, anyway... The reason for 1.3 vs. 1.4 is the switch to
java.net
Hi Dick,
It looks like XSLT support hasn't made it's way into the webwork2
distribution yet (I'm hoping it's planned and hasn't been dropped). Thanks
for the info, I'm checking webwork out of CVS right now and will take it for
a spin.
Regards,
Peter
-Original Message-
From: [EMAIL
Ok, I've fixed it.
Everyone who's checking things in, please update the changes.txt file in
the root directory of the project (either webwork2 or xwork). Thanks.
Jason
-Original Message-
From: Francisco Hernandez [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2003 2:46 PM
To:
Please open a feature request in JIRA so we don't forget about this before
the 2.0 release. Thanks!
- Original Message -
From: Peter White [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 18, 2003 12:04 PM
Subject: RE: [OS-webwork] Any examples of WebWork/WebWork2 using XSLT
I've written up a short press release to go as an announcement to TSS
and JavaLobby and on the OpenSymphony site. Take a look at let me know
what you think:
The OpenSymphony team is proud to announce the first beta releases of
XWork 1.0 and WebWork 2.0.
This is the first release of a complete
1) I don't see the need to cuss webwork1.
2) The portlet sentence seems rather bizarre to me, a portal
dispatcher? JSR-168 says very little about portals, so a portal
dispatcher is certainly not self-explanatory, to me at any rate.
3) 'Two strategies for handling form submission' seems another
I agree with Hani's points - but must add that on the whole this is awesome!
Very solid, lots of text, good points made throughout.
I know Hani meant to commend you on the overall quality, but forgot (or he
hadn't taken his bile hat off ;)).
M
On 19/8/03 11:29 AM, Hani Suleiman ([EMAIL
Here's some updated text:
The OpenSymphony team is proud to announce the first beta releases of
XWork 1.0 and WebWork 2.0.
This is the first release of a complete rewrite of WebWork, a
hierarchical pull-MVC framework. While WebWork 1 provided a good
separation of the general command framework
On Monday, August 18, 2003, at 09:56 PM, Jason Carreira wrote:
-Original Message-
From: Hani Suleiman [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2003 9:29 PM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] XW/WW2 press release text for review
1) I don't see the need to cuss
Ok, gotcha. Try this for the first paragraph:
This is the first release of a complete rewrite of WebWork, a
hierarchical pull-MVC framework. Many web frameworks suffer from being
tightly coupled to the Servlet spec when it is not necessary, especially
Struts. This makes both unit testing your
After it's done, I'll put it in JDJ :)
On Tue, 19 Aug 2003, Mike Cannon-Brookes wrote:
I agree with Hani's points - but must add that on the whole this is awesome!
Very solid, lots of text, good points made throughout.
I know Hani meant to commend you on the overall quality, but forgot (or
Hani Suleiman wrote:
1) I don't see the need to cuss webwork1.
He's not cussing WebWork. He's explaining what is and why it is.
2) The portlet sentence seems rather bizarre to me, a portal
dispatcher? JSR-168 says very little about portals, so a portal
dispatcher is certainly not
36 matches
Mail list logo
