Can you try to use the latest 2.5.12 version? There was some issue
related to the JasperReports fixed with this release.
2017-07-14 2:10 GMT+02:00 Jon Eskin :
> I tried to make a sample project using code from a tutorial I found for the
> JasperReports plugin
>
2017-07-14 8:49 GMT+02:00 Tamás Barta :
> It seems that new version is not compatible with JRebel. Have you tried
> starting a new version struts app with JRebel?
I don't have JRebel so I have no way to test that :( But this would be
a strange thing, I do not see a change
2017-07-14 9:25 GMT+02:00 Tamás Barta :
> I updated them, I updated all the jars.
Hmm... is it the same exception as on the beginning of this conversation?
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
And If i put a breakpoint at ContainerBuilder.create, it will never stop.
The exception happens before create even if we can see it in the
stacktrace. Isn't CDI interceptors or similar somewhere?
On Fri, Jul 14, 2017 at 9:36 AM, Tamás Barta wrote:
> Yes.
>
> The very
> but this is inside "createBootstrapContainer", right?
yes
> Do you use "struts.convention.classes.reload" ?
no, I never set it
On Fri, Jul 14, 2017 at 10:52 AM, Lukasz Lenart
wrote:
> 2017-07-14 10:32 GMT+02:00 Tamás Barta :
> > When I remove
Dear Lukasz, thank you very much for your very fast support all the time.
It seems that new version is not compatible with JRebel. Have you tried
starting a new version struts app with JRebel?
If I replace the 3 struts jar files I use (core, spring-plugin,
convention-plugin) to the old version,
> JDK version you are running on?
java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> Do you use only those three jars only?
I use many other libs too but it is enough to change the "core" jar back
to
2017-07-14 9:19 GMT+02:00 Tamás Barta :
>> Do you use only those three jars only?
>
> I use many other libs too but it is enough to change the "core" jar back
> to the old version to be deployed well. Using the new core jar won't deploy.
Nope, it isn't :) You must also
2017-07-14 9:36 GMT+02:00 Tamás Barta :
> Yes.
>
> The very strange thing I don't understand are the following lines in the
> stacktrace:
>
> 07:33:09,799 ERROR [stderr] (ServerService Thread Pool -- 99) at
>
When I remove this line from DefaultConfiguration:
builder.constant(StrutsConstants.STRUTS_DEVMODE, "false");
Then no exception is thrown and when I try to enter method "create", the
"constant" method is called with "struts.devMode=true", then again with
"struts.convention.classes.reload=true",
2017-07-14 10:32 GMT+02:00 Tamás Barta :
> When I remove this line from DefaultConfiguration:
>
> builder.constant(StrutsConstants.STRUTS_DEVMODE, "false");
but this is inside "createBootstrapContainer", right?
> Then no exception is thrown and when I try to enter method
Yes, I have just wrote them an email. Thanks. It is a very big problem for
us now as we can't upgrade to the latest and maybe to future versions.
On Fri, Jul 14, 2017 at 11:02 AM, Lukasz Lenart
wrote:
> 2017-07-14 10:53 GMT+02:00 Tamás Barta :
> >>
I updated them, I updated all the jars.
On Fri, Jul 14, 2017 at 9:23 AM, Lukasz Lenart
wrote:
> 2017-07-14 9:19 GMT+02:00 Tamás Barta :
> >> Do you use only those three jars only?
> >
> > I use many other libs too but it is enough to change the
Yes.
The very strange thing I don't understand are the following lines in the
stacktrace:
07:33:09,799 ERROR [stderr] (ServerService Thread Pool -- 99) at
com.opensymphony.xwork2.inject.ContainerBuilder.constant(ContainerBuilder.java:398)
07:33:09,800 ERROR [stderr] (ServerService Thread Pool
2017-07-14 10:53 GMT+02:00 Tamás Barta :
>> but this is inside "createBootstrapContainer", right?
>
> yes
but this is only called without reading external dependencies (i.e.
struts-default,xml or struts.xml) which means JRebel has to do it O_o
- did you try to ask them for
2017-07-14 14:36 GMT+02:00 Adam Brin :
> I think I tried that originally without help.
"without help" -> it didn't work?
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
-
To
We have a number of API components that include a textBody as part of the
multipart request. In 2.5.12, these requests are being kicked out (while
in 2.5.10 they were fine. changing the constant:
to allow anything (as in the example) seems to fix the issue, but this
seems imprudent. This
2017-07-14 14:40 GMT+02:00 Adam Brin :
> Hi Lukasz,
> Out of curiosity, I'm wondering, what the protocol or choice was about
> including the security patches for struts2 in a "new" release as opposed to
> a point release for 2.5.10 (eg. 2.5.10.1)? It would seem like
Unfortunately, using the factory alone didn't help because we needed to add
the ResourceBuindles into the TextProviderInstance
On Fri, Jul 14, 2017 at 6:16 AM, Lukasz Lenart
wrote:
> 2017-07-14 14:36 GMT+02:00 Adam Brin :
> > I think I tried
Hi Lukasz,
Out of curiosity, I'm wondering, what the protocol or choice was about
including the security patches for struts2 in a "new" release as opposed to
a point release for 2.5.10 (eg. 2.5.10.1)? It would seem like the smallest
change possible should be included, but this version seemed to
thanks for the clarification.
On Fri, Jul 14, 2017 at 5:53 AM, Lukasz Lenart
wrote:
> 2017-07-14 14:40 GMT+02:00 Adam Brin :
> > Hi Lukasz,
> > Out of curiosity, I'm wondering, what the protocol or choice was about
> > including the
This is the response from JRebel team:
"Letting you know that i have reproduced the issue and passed it on to our
developers. I will let you know as soon as we have any updates on this."
2017. júl. 14. 11:11 ezt írta ("Lukasz Lenart" ):
2017-07-14 11:06 GMT+02:00 Tamás
I think I tried that originally without help. Anyway, it seems like my fix
worked.
On Thu, Jul 13, 2017 at 10:41 PM, Lukasz Lenart
wrote:
> 2017-07-13 20:08 GMT+02:00 Adam Brin :
> > // FIXME: needs to be a better way to handle this
>
2017-07-14 11:06 GMT+02:00 Tamás Barta :
> Yes, I have just wrote them an email. Thanks. It is a very big problem for
> us now as we can't upgrade to the latest and maybe to future versions.
Looks like is due to these changes, before there were two
configuration sets created
I just tried switching to 2.5.12 but I'm seeing the same error.
> On Jul 14, 2017, at 2:27 AM, Lukasz Lenart wrote:
>
> Can you try to use the latest 2.5.12 version? There was some issue
> related to the JasperReports fixed with this release.
>
> 2017-07-14 2:10
25 matches
Mail list logo