2013/10/11 Volker Krebs :
> Am 11.10.2013 13:22, schrieb Lukasz Lenart:
>
>> 2013/10/11 Volker Krebs :
>>>
>>> Thank you, good news.
>>>
>>> If you want you can give me the current state and I can run it on our
>>> test
>>> system. We're implicitly testing quite a lot of struts2 functionality.
>>
>
Set to false.
But having same results set to true.
I'm using action="index" approach. Now, cancel always launches 404.
El Martes, 15 de Octubre de 2013 12:59:32 p.m., Paul Benedict escribió:
If you want to do a redirect, you need your action mapping to handle
"cancel" and use a redirectActi
is DMI set to true?
2013/10/15 Antonio Sánchez :
> Support for redirectAction: and redirect: prefixes was removed as from
> version 2.3.15.1. So, let's forget redirection this way.
>
> I was using redirection because using
>
> (the
> same than name="action:index"?)
>
> throws error 404, resource
Support for redirectAction: and redirect: prefixes was removed as from
version 2.3.15.1. So, let's forget redirection this way.
I was using redirection because using
(the same than
name="action:index"?)
throws error 404, resource not available: "myapp/index.action".
Using method does not wo
If you want to do a redirect, you need your action mapping to handle
"cancel" and use a redirectAction result.
On Tue, Oct 15, 2013 at 12:53 PM, Antonio Sánchez
wrote:
> Hi.
>
> Simple CRUD sample application, paramsPrepareParams, wildcard method
> selection.
>
> Cancel button in edit form, when
Hi.
Simple CRUD sample application, paramsPrepareParams, wildcard method
selection.
Cancel button in edit form, when reached for creating a new employee
bean, is not cancelling and redirecting to index, but actually
performing form action, which is "save". Conversely, cancel is working
pro
Thanks
On Tue, Oct 15, 2013 at 11:08 AM, Dave Newton wrote:
> The ClassFinder stuff in XWork; for annotation processing.
>
>
> On Tue, Oct 15, 2013 at 10:56 AM, Greg Lindholm >wrote:
>
> > Which features of S2 use ASM?
> >
> > The S2 project dependencies
> > (http://struts.apache.org/release/2
The ClassFinder stuff in XWork; for annotation processing.
On Tue, Oct 15, 2013 at 10:56 AM, Greg Lindholm wrote:
> Which features of S2 use ASM?
>
> The S2 project dependencies
> (http://struts.apache.org/release/2.3.x/struts2-core/dependencies.html)
> shows that xworks depends on:
> - asm-3.3.
Which features of S2 use ASM?
The S2 project dependencies
(http://struts.apache.org/release/2.3.x/struts2-core/dependencies.html)
shows that xworks depends on:
- asm-3.3.jar
- asm-commons-3.3.jar
- asm-tree-3.3.jar
These ASM jar don't seems to actually be needed by a project I have so I'm
guessin
Dave,
i am agree with you, i just followed doc and than it started giving me some
strange issues in validations.
I tried to debug underlying API but with no success.
On doing some more Googling i came across create new instance outside
getModel() and it started working as expected.
Thanks
Umesh
Wouldn't this return a new ProfileDTO every single time getModel() is
called?
This, in turn, would mean that if you were validating model.foo and
model.bar that it'd be called twice.
I have not verified this, perhaps there's some magic (e.g., spooky) caching
happening somewhere, but to my mind, w
> Just to add more information by changing code to
>
> ProfileDTOgetModel md=new ProfileDTOgetModel();
> @Valid
> public ProfileDTOgetModel()
> {
> return md;
> }
> }
>
> Bean Validation is working fine, so i am confused which is right way to
use
> Model driven.
> I took ref
Just to add more information by changing code to
ProfileDTOgetModel md=new ProfileDTOgetModel();
@Valid
public ProfileDTOgetModel()
{
return md;
}
}
Bean Validation is working fine, so i am confused which is right way to use
Model driven.
I took reference from
http://struts.
Hi Umesh,
Both you mentioned are same.
ModelDriven is best used to create new object if they do not exist.
So your getModel method must be
ProfileDTOModel md;
public ProfileDTOModel getModel()
{
if(md != null)// Or Some other condition as required by your model.
Typically check for Id
Hi All,
Have rarely used model driven interface and not sure about how exactly it
work.
Can any one point me what will be difference between
ProfileDTOModel md = new ProfileDTOModel();
publicProfileDTOModel getModel()
{
return md;
}
and
public ProfileDTOModel getMod
No, my issue is something different..
some how underlying Valitor API is not validating all fields and its
happening only when i am using Model driven, for rest cased everything is
working fine for same bean object and for same validations.
On Tue, Oct 15, 2013 at 3:15 PM, Christoph Nenning <
chr
Hi Greg.
> So the statement about Backwards Compatibility on
> http://struts.apache.org/release/2.3.x/docs/s2-018.html is incorrect?
>
> *Backward Compatibility*
> After upgrading to Struts >= 2.3.15.2, applications using the "action:"
> should still work as expected.
>
> This doesn't appear to
> Hi All,
>
> I am facing a strange issue while trying to validate a bean using bean
> validation.I am using model driven interface to pass form field values
to
> Action and here is the action code
>
> public class ModelDriven extends ActionSupport implements
> com.opensymphony.xwork2.ModelDriv
Hi All,
I am facing a strange issue while trying to validate a bean using bean
validation.I am using model driven interface to pass form field values to
Action and here is the action code
public class ModelDriven extends ActionSupport implements
com.opensymphony.xwork2.ModelDriven{
@Valid
Really I was using a custom type
converter (with annotations on getters & setters) but I had
the problem that when typeconversionexception was thrown the
dynamic contents on my web page (objects retrieved from db or from
actions) didn't display.
Really I don
>
> Thank you so much, I solved the special characters problems by setting
> the struts i18n constant to ISO-8859-1!
> About the conversion error, I know it was a dev mode warning, but when
> the exception was thrown every dynamic content in my page disappeard...
> Anyway I solved the issue by
21 matches
Mail list logo
