[Resin-interest] javax Validation provider change between 4.0.23 and 4.0.30?
I just built a new webapp that uses javax Validation. It works on my local machine with 4.0.30, but doesn't work on my server with 4.0.23. I'm wondering if between those two, a validation provider was included in resin? The error I get on the server is: javax.validation.ValidationException: Unable to find a default provider -- Rick ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] javax Validation provider change between 4.0.23 and 4.0.30?
- Original Message - Subject: [Resin-interest] javax Validation provider change between 4.0.23 and 4.0.30? Date: Tue, 28 Aug 2012 03:42:24 -0700 From: Rick Mann I just built a new webapp that uses javax Validation. It works on my local machine with 4.0.30, but doesn't work on my server with 4.0.23. I'm wondering if between those two, a validation provider was included in resin? The error I get on the server is: javax.validation.ValidationException: Unable to find a default provider Rick Hibernate validator implementation is under webapp-jars. Would you happen to have different classpath configs...? -- ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] javax Validation provider change between 4.0.23 and 4.0.30?
Yes, it's possible the resin.xml or resin.sh scripts are from a version before 4.0.23. Thanks! On Aug 28, 2012, at 3:49 , Mattias Jiderhamn wrote: > - Original Message - > Subject: [Resin-interest] javax Validation provider change between 4.0.23 and > 4.0.30? > Date: Tue, 28 Aug 2012 03:42:24 -0700 > From: Rick Mann >> >> I just built a new webapp that uses javax Validation. It works on my local >> machine with 4.0.30, but doesn't work on my server with 4.0.23. I'm >> wondering if between those two, a validation provider was included in resin? >> The error I get on the server is: >> >> javax.validation.ValidationException: Unable to find a default provider >> >> >> Rick > > Hibernate validator implementation is under webapp-jars. Would you happen to > have different classpath configs...? > -- > > > > > ___ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest -- Rick ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] rollover-count question
Hello
I have my resin log being changed every night with
parameters :
timestamp="[%y-%m-%d %H:%M:%S.%s] {%{thread}} "
rollover-size="1mb"
rollover-period="1D"
rollover-count="60"/>
I thought that rollover-count="60" would
make resin delete oldest file if there are more than 60. But I
have 225 files in my log directory. The docs says : "maximum
number of rollover files before the oldest ones get
overwritten". I don't undestrand why it talks about
"overwriting".
What is the best way to clean old resin log files ?
Thanks a lot.
--
Riccardo Cohen
+33 (0)6 09 83 64 49
Société Realty-Property.com
1 rue de la Monnaie
37000 Tours
France
www.appartement-maison.fr
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] JSP encoding issues
On 08/27/2012 05:04 PM, Rick Mann wrote: > Oh, I can also put that empty page directive at the end of my include file, > and it also triggers the correct behavior. What, exactly isn't working? The parsing of the page? Or the content-type header? I just created a filter and JSP to reproduce this, and in all cases the res.setCharacterEncoding or res.setContentType is passed through to the output. -- Scott > > On Aug 27, 2012, at 16:39 , Rick Mann wrote: > >> I'm trying to serve everything UTF-8. To this end, I wrote a request filter >> that sets the input and output encodings to UTF-8, and I've used that >> successfully in the past. I've been able to avoid putting a page encoding >> directive in each page. >> >> With resin 4.0.30, I'm seeing something odd. I only get the right behavior >> if the JSP page as an extra <%@ page %> at the top somewhere. The actual >> directive inside doesn't seem to matter. I had an import directive, but >> tried it without one and still got the right behavior. >> >> I also have, before that, at <%@ include directive, which must also be >> present. It includes the following: >> >> <%@ page contentType="text/html; charset=UTF-8" %> >> >> Without that, the resulting encoding isn't correct, either. >> >> What's odd is the empty page directive required to make it work. >> >> Any ideas? >> >> -- >> Rick >> >> >> >> >> ___ >> resin-interest mailing list >> resin-interest@caucho.com >> http://maillist.caucho.com/mailman/listinfo/resin-interest > ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] JSP encoding issues
Sorry, I should've been more clear. The problem I'm experiencing is not that the headers aren't being properly set. It's that UTF-8 in my source page is getting mangled. In this case, a copyright symbol (©), while still rendered in the page, is preceded by a capital A with an accent (not sure of the exact character) when finally rendered in Safari or FireFox. Somewhere in the long chain of processing, a conversion is happening. -- Rick On Aug 28, 2012, at 10:15 , Scott Ferguson wrote: > On 08/27/2012 05:04 PM, Rick Mann wrote: >> Oh, I can also put that empty page directive at the end of my include file, >> and it also triggers the correct behavior. > > What, exactly isn't working? The parsing of the page? Or the > content-type header? > > I just created a filter and JSP to reproduce this, and in all cases the > res.setCharacterEncoding or res.setContentType is passed through to the > output. > > -- Scott > >> >> On Aug 27, 2012, at 16:39 , Rick Mann wrote: >> >>> I'm trying to serve everything UTF-8. To this end, I wrote a request filter >>> that sets the input and output encodings to UTF-8, and I've used that >>> successfully in the past. I've been able to avoid putting a page encoding >>> directive in each page. >>> >>> With resin 4.0.30, I'm seeing something odd. I only get the right behavior >>> if the JSP page as an extra <%@ page %> at the top somewhere. The actual >>> directive inside doesn't seem to matter. I had an import directive, but >>> tried it without one and still got the right behavior. >>> >>> I also have, before that, at <%@ include directive, which must also be >>> present. It includes the following: >>> >>> <%@ page contentType="text/html; charset=UTF-8" %> >>> >>> Without that, the resulting encoding isn't correct, either. >>> >>> What's odd is the empty page directive required to make it work. >>> >>> Any ideas? >>> >>> -- >>> Rick >>> >>> >>> >>> >>> ___ >>> resin-interest mailing list >>> resin-interest@caucho.com >>> http://maillist.caucho.com/mailman/listinfo/resin-interest >> > > > > ___ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest -- Rick ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] JSP encoding issues
On 08/28/2012 01:50 PM, Rick Mann wrote: > Sorry, I should've been more clear. > > The problem I'm experiencing is not that the headers aren't being properly > set. It's that UTF-8 in my source page is getting mangled. In this case, a > copyright symbol (©), while still rendered in the page, is preceded by a > capital A with an accent (not sure of the exact character) when finally > rendered in Safari or FireFox. > > Somewhere in the long chain of processing, a conversion is happening. > Have you tried setting the utf-8 in the resin.xml? When parsing the JSP page, Resin doesn't look at the dynamic value of the character encoding. And the default value is iso-8859-1 according to the spec. So when the page is parsed, that value needs to be set, either in the page itself or the . Filters don't matter in this case. -- Scott ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] JSP encoding issues
On Aug 28, 2012, at 14:29 , Scott Ferguson wrote: > On 08/28/2012 01:50 PM, Rick Mann wrote: >> Sorry, I should've been more clear. >> >> The problem I'm experiencing is not that the headers aren't being properly >> set. It's that UTF-8 in my source page is getting mangled. In this case, a >> copyright symbol (©), while still rendered in the page, is preceded by a >> capital A with an accent (not sure of the exact character) when finally >> rendered in Safari or FireFox. >> >> Somewhere in the long chain of processing, a conversion is happening. >> > > Have you tried setting the > utf-8 in the resin.xml? I had not, but I've put that in now. I tried to first reproduce the problem as originally described, but I could not. It very clearly and reliably would reproduce as originally described, but I've made so many changes to the pages since then that whatever triggers the behavior seems to be permanently "correct." In any case, I've added the character-encoding tag to my resin.xml file. Why, oh why, did they standardize on iso-8859-1? > > When parsing the JSP page, Resin doesn't look at the dynamic value of > the character encoding. And the default value is iso-8859-1 according to > the spec. So when the page is parsed, that value needs to be set, either > in the page itself or the . Filters don't matter in > this case. > > -- Scott > > > ___ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest -- Rick ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] JSP encoding issues
We had that issue when using jsp:include (jsp:include content wouldn't get UTF-8 encoded), but switching it out for c:import worked. Not sure if this applies in your case, but if the copyright is jsp:include'd you might try to c:import and see if you get different results. No matter what you did in the highest level JSP (the controller if you will) it didn't encode stuff brought in via the jsp:include. I thought that had been fixed at one point, but possibly not. Aaron > -Original Message- > From: resin-interest-boun...@caucho.com [mailto:resin-interest- > boun...@caucho.com] On Behalf Of Rick Mann > Sent: Tuesday, August 28, 2012 3:50 PM > To: General Discussion for the Resin application server > Subject: Re: [Resin-interest] JSP encoding issues > > Sorry, I should've been more clear. > > The problem I'm experiencing is not that the headers aren't being properly > set. It's that UTF-8 in my source page is getting mangled. In this case, a > copyright symbol (C), while still rendered in the page, is preceded by a > capital A with an accent (not sure of the exact character) when finally > rendered in Safari or FireFox. > > Somewhere in the long chain of processing, a conversion is happening. > > -- > Rick > > On Aug 28, 2012, at 10:15 , Scott Ferguson wrote: > > > On 08/27/2012 05:04 PM, Rick Mann wrote: > >> Oh, I can also put that empty page directive at the end of my include file, > and it also triggers the correct behavior. > > > > What, exactly isn't working? The parsing of the page? Or the > > content-type header? > > > > I just created a filter and JSP to reproduce this, and in all cases > > the res.setCharacterEncoding or res.setContentType is passed through > > to the output. > > > > -- Scott > > > >> > >> On Aug 27, 2012, at 16:39 , Rick Mann wrote: > >> > >>> I'm trying to serve everything UTF-8. To this end, I wrote a request filter > that sets the input and output encodings to UTF-8, and I've used that > successfully in the past. I've been able to avoid putting a page encoding > directive in each page. > >>> > >>> With resin 4.0.30, I'm seeing something odd. I only get the right behavior > if the JSP page as an extra <%@ page %> at the top somewhere. The actual > directive inside doesn't seem to matter. I had an import directive, but tried it > without one and still got the right behavior. > >>> > >>> I also have, before that, at <%@ include directive, which must also be > present. It includes the following: > >>> > >>> <%@ page contentType="text/html; charset=UTF-8" %> > >>> > >>> Without that, the resulting encoding isn't correct, either. > >>> > >>> What's odd is the empty page directive required to make it work. > >>> > >>> Any ideas? > >>> > >>> -- > >>> Rick > >>> > >>> > >>> > >>> > >>> ___ > >>> resin-interest mailing list > >>> resin-interest@caucho.com > >>> http://maillist.caucho.com/mailman/listinfo/resin-interest > >> > > > > > > > > ___ > > resin-interest mailing list > > resin-interest@caucho.com > > http://maillist.caucho.com/mailman/listinfo/resin-interest > > > -- > Rick > > > > > ___ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] JSP encoding issues
On Aug 28, 2012, at 13:55 , Aaron Freeman wrote: > We had that issue when using jsp:include (jsp:include content wouldn't get > UTF-8 encoded), but switching it out for c:import worked. Not sure if this > applies in your case, but if the copyright is jsp:include'd you might try to > c:import and see if you get different results. No matter what you did in > the highest level JSP (the controller if you will) it didn't encode stuff > brought in via the jsp:include. I thought that had been fixed at one point, > but possibly not. I originally did NOT use jsp:include, just had the markup right there in the page. The only thing I did was include (using <%@ page include>) was a prefix file that included a few tag libraries, and set the content type of the page. (As I understand it, you have to set the content type of all the pages, even jsp:include ones.) In any case, I tried reverting to that same arrangement, and could no longer reproduce the problem. But I've experimented with so many ways of setting the encoding, I'm sure I didn't get back to exactly where I was (where an empty <%@ page%> directive would make the difference). > > Aaron > > >> -Original Message- >> From: resin-interest-boun...@caucho.com [mailto:resin-interest- >> boun...@caucho.com] On Behalf Of Rick Mann >> Sent: Tuesday, August 28, 2012 3:50 PM >> To: General Discussion for the Resin application server >> Subject: Re: [Resin-interest] JSP encoding issues >> >> Sorry, I should've been more clear. >> >> The problem I'm experiencing is not that the headers aren't being properly >> set. It's that UTF-8 in my source page is getting mangled. In this case, a >> copyright symbol (C), while still rendered in the page, is preceded by a >> capital A with an accent (not sure of the exact character) when finally >> rendered in Safari or FireFox. >> >> Somewhere in the long chain of processing, a conversion is happening. >> >> -- >> Rick >> >> On Aug 28, 2012, at 10:15 , Scott Ferguson wrote: >> >>> On 08/27/2012 05:04 PM, Rick Mann wrote: Oh, I can also put that empty page directive at the end of my include > file, >> and it also triggers the correct behavior. >>> >>> What, exactly isn't working? The parsing of the page? Or the >>> content-type header? >>> >>> I just created a filter and JSP to reproduce this, and in all cases >>> the res.setCharacterEncoding or res.setContentType is passed through >>> to the output. >>> >>> -- Scott >>> On Aug 27, 2012, at 16:39 , Rick Mann wrote: > I'm trying to serve everything UTF-8. To this end, I wrote a request > filter >> that sets the input and output encodings to UTF-8, and I've used that >> successfully in the past. I've been able to avoid putting a page encoding >> directive in each page. > > With resin 4.0.30, I'm seeing something odd. I only get the right > behavior >> if the JSP page as an extra <%@ page %> at the top somewhere. The actual >> directive inside doesn't seem to matter. I had an import directive, but > tried it >> without one and still got the right behavior. > > I also have, before that, at <%@ include directive, which must also be >> present. It includes the following: > > <%@ page contentType="text/html; charset=UTF-8" %> > > Without that, the resulting encoding isn't correct, either. > > What's odd is the empty page directive required to make it work. > > Any ideas? > > -- > Rick > > > > > ___ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest >>> >>> >>> >>> ___ >>> resin-interest mailing list >>> resin-interest@caucho.com >>> http://maillist.caucho.com/mailman/listinfo/resin-interest >> >> >> -- >> Rick >> >> >> >> >> ___ >> resin-interest mailing list >> resin-interest@caucho.com >> http://maillist.caucho.com/mailman/listinfo/resin-interest > > > ___ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest -- Rick ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
