2012/12/3 ChadDavis :
> There are (from 2.3):
>>
>> 79:dtdMappings.put("-//Apache Software Foundation//DTD Struts
>> Configuration 2.0//EN", "struts-2.0.dtd");
>> 80:dtdMappings.put("-//Apache Software Foundation//DTD Struts
>> Configuration 2.1//EN", "struts-2.1.dtd");
>> 81:
2012/12/3 ChadDavis :
> I'm happy to hear that, I've posted how to get contributor rights to docs
>
> Posted where?
http://markmail.org/message/4way2m5y2vlwkrih :-)
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
There are (from 2.3):
>
> 79:dtdMappings.put("-//Apache Software Foundation//DTD Struts
> Configuration 2.0//EN", "struts-2.0.dtd");
> 80:dtdMappings.put("-//Apache Software Foundation//DTD Struts
> Configuration 2.1//EN", "struts-2.1.dtd");
> 81:dtdMappings.put("-//Apache S
There are (from 2.3):
79:dtdMappings.put("-//Apache Software Foundation//DTD Struts
Configuration 2.0//EN", "struts-2.0.dtd");
80:dtdMappings.put("-//Apache Software Foundation//DTD Struts
Configuration 2.1//EN", "struts-2.1.dtd");
81:dtdMappings.put("-//Apache Software Fou
Why aren't there mappings for the struts-xxx.dtd's?
On Mon, Dec 3, 2012 at 1:20 AM, Lukasz Lenart wrote:
> 2012/12/1 ChadDavis :
> > Thanks Lukasz. This is very useful information. I think this clearly
> fixes
> > my problem, but I still have some questions.
> >
> > 1) when was xwork moved to
2012/11/30 Thim Anneessens
> We are using Struts 2.3.1.2 and have noticed a strange behavior in
> component parameter handling:
>
> We have a component that uses both an "id" parameter and a "title"
> parameter.
>
> What is strange is that when we use s:component, the "title" parameter
> value can
2012/12/3 ChadDavis :
> So, it seems like this should be added to the wiki on the webworks to
> struts 2 migration page . . . I'm more than willing to do provide the text.
> what do you think?
I'm happy to hear that, I've posted how to get contributor rights to docs
Regards
--
Łukasz
+ 48 606
2012/12/3 Eric Lentz :
> I'm almost there. I didn't suspect that it would work that way with the
> iterator. Should have tried it first! Thanks Dave.
>
> On the way back, such as in a post, if BaseObject is an interface or
> abstract, as I'm hoping for it to be, then Struts tries to instantiate the
So, it seems like this should be added to the wiki on the webworks to
struts 2 migration page . . . I'm more than willing to do provide the text.
what do you think?
On Mon, Dec 3, 2012 at 1:20 AM, Lukasz Lenart wrote:
> 2012/12/1 ChadDavis :
> > Thanks Lukasz. This is very useful information.
2012/11/30 Davis, Chad :
>
>> I think, the basic idea was to allow cooperate the REST plugin with the
>> Convention plugin and code behind is a deprecated plugin that will be
>> discarded soon (with 3.x)
>
> 1) So, it doesn't "depend" on it, in any technical sense?
Yes
> 2) But it's made to work
I'm almost there. I didn't suspect that it would work that way with the
iterator. Should have tried it first! Thanks Dave.
On the way back, such as in a post, if BaseObject is an interface or
abstract, as I'm hoping for it to be, then Struts tries to instantiate the
BaseObject type, which it can't
You're making OGNL calls against an object; it doesn't care about the
type--if you access foo.bar it'll call getBar() on foo, setBar() on
submission.
Dave
On Mon, Dec 3, 2012 at 11:19 AM, Eric Lentz wrote:
> I have
> List foo
>
> The list is of type BaseObjectImpl
>
> BaseObject has fields:
> St
I have
List foo
The list is of type BaseObjectImpl
BaseObject has fields:
String a
String b
BaseObjectImpl has fields:
String c
String d
Now I'm in a JSP and want to iterate foo (using ), accessing
fields c and d (inside iterator using , for example). How? As
far as Struts knows I'm dealing wit
Thanks!
On Mon, Dec 3, 2012 at 1:20 AM, Lukasz Lenart wrote:
> 2012/12/1 ChadDavis :
> > Thanks Lukasz. This is very useful information. I think this clearly
> fixes
> > my problem, but I still have some questions.
> >
> > 1) when was xwork moved to ASF?
>
> Just before 2.2.1, two years ago, bu
2012/12/3 Rohit Gupta :
> I am using XML approach, it works fine when the type is not prototype,
> understandable so since the same instance is used across requests.
As I understand you have been using session scoped actions or even
singletons - and edit worked because the instance was there all t
I am using XML approach, it works fine when the type is not prototype,
understandable so since the same instance is used across requests.
On 03/12/12 2:49 PM, "Puneet Babbar 2" wrote:
>Are you using annotations or xml approach to work with struts? And have
>you checked what happens when you do
Not sure if i am able to understand your question
Can you clarify what you mean by
*How can we achieve edit with prototype beans*
In particular *edit*
On Mon, Dec 3, 2012 at 2:49 PM, Puneet Babbar 2 wrote:
> Are you using annotations or xml approach to work with struts? And have
> you checked wha
Are you using annotations or xml approach to work with struts? And have you
checked what happens when you don't define your struts actions as prototype?
-Puneet
-Original Message-
From: rohit [mailto:ro...@in-rev.com]
Sent: Monday, December 03, 2012 2:13 PM
To: user@struts.apache.org
Su
We are defining struts action classes in spring as prototype bean, in this
while editing a particular bean a new object is being inserted, I can imagine
this would be because of prototype nature of beans.
How can we achieve edit with prototype beans?
Regards,
Rohit
2012/12/1 ChadDavis :
> Thanks Lukasz. This is very useful information. I think this clearly fixes
> my problem, but I still have some questions.
>
> 1) when was xwork moved to ASF?
Just before 2.2.1, two years ago, but DTDs where changed sometime later
http://struts.apache.org/2.x/docs/version-
20 matches
Mail list logo
