Github user lukaszlenart commented on the issue:
https://github.com/apache/struts/pull/158
> I don't see where new parameter ActionInvocation is actually used. Is
that yet to come?
Not yet :)
---
If your project is set up for it, you can reply to this email and have your
rep
Github user cnenning commented on the issue:
https://github.com/apache/struts/pull/158
Using `AbstractContentTypeHandler` to implement deprecated methods to log
on WARN seems like a good idea.
I don't see where new parameter `ActionInvocation` is actually used. Is
that yet to
Github user lukaszlenart commented on the issue:
https://github.com/apache/struts/pull/153
Thanks a lot :) I see now what's going on but have no idea why :\
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user aleksandr-m commented on the issue:
https://github.com/apache/struts/pull/153
Sure. No problem.
Test project -
https://github.com/aleksandr-m/struts2-objectfactory-container/
This commit adds custom date converter -
https://github.com/aleksandr-m/struts2-
Github user lukaszlenart commented on the issue:
https://github.com/apache/struts/pull/153
I don't see any other options now to merge this. @aleksandr-m could you
prepare that example app? I will be able to investigate what's wrong with my
solution ;-)
---
If your project is set up
Hi,
Can you take a look on this?
Thanks in advance
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2017-08-02 15:02 GMT+02:00 lukaszlenart :
> GitHub user lukaszlenart opened a pull request:
>
> https://github.com/apache/struts/pull/158
>
> WW-4835: Configurable handlers
>
> T
GitHub user lukaszlenart opened a pull request:
https://github.com/apache/struts/pull/158
WW-4835: Configurable handlers
This PR changes API a bit to allow pass current `ActionInvocation` to the
REST content type handlers to allow implement different behaviour based on a
current ac
> > Are we, volunteers, allowed to help/contribute with such structural
> > changes? I hope yes. If so, I have passion in `support for
> > actors/asynchronous request handling`. Could you please register an
> > issue with a few directive details? then we can pick and start work on
> > that :) same
Github user cnenning commented on the issue:
https://github.com/apache/struts/pull/44
> I wonder how hard it will be to make this configurable
Making this configurable would be cool. But when looking at changed files,
and all those different file types, i fear it would be har
Github user sdutry commented on the issue:
https://github.com/apache/struts/pull/157
Ok,
I will wait.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user lukaszlenart commented on the issue:
https://github.com/apache/struts/pull/157
Could you wait a bit with merging this PR? I have asked somebody to take a
look on this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
GitHub user sdutry opened a pull request:
https://github.com/apache/struts/pull/157
WW-4834 fixed faulty regex
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sdutry/struts WW-4834
Alternatively you can review and apply these ch
Github user lukaszlenart commented on the issue:
https://github.com/apache/struts/pull/156
Ach... you did merge it :\ But this isn't a valid RegEx :(
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does no
13 matches
Mail list logo
