[Resin-interest] Resin 3.1.1 is available
We've released Resin 3.1.1 The release notes are at http://caucho.com/resin-3.1/changes/ resin-3.1.1.xtp. Amber: JPA is ready to use and is nearly complete. The main missing functionality is extended transactions. But unless you're actually using those, the other functionality is complete. Web Services: The most commonly-used features of JAXB, JAX-WS and SAAJ are now available, except for Java code generation from XSchema or WSDL. Quercus: Improved Java integration and continued bug fixes and compatibility testing. Quercus now supports import com.foo.*; as a way to instantiate java objects. rewrite-dispatch: The rewriting rules can now look at HTTP header values to dispatch requests. Administration: New capabilities and displays of thread dumps, profiling, memory dumps, and caching. The profiling has low overhead, so it would be possible to enable profiling on some production servers to get real performance data. We strongly recommend looking at the new profiling and caching displays to help improve your application's cachability and performance. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] XML View Question
Can anybody provide me with any links/hints on this?
Thanks,
Aaron
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Aaron Freeman
Sent: Thursday, May 03, 2007 10:59 AM
To: resin-interest@caucho.com
Subject: [Resin-interest] XML View Question
We have a controller JSP that looks like this:
Begin Controller %@ taglib
uri=http://java.sun.com/jsp/jstl/core; prefix=c % %@
taglib uri=http://java.sun.com/jsp/jstl/functions; prefix=fn %
c:catch var=exception
... do some logic
/c:catch
c:choose
c:when test=${empty exception param.o == 'xml'}
jsp:include page=/xml/_view.jsp/
/c:when
c:when test=${empty exception}
jsp:include page=/html/_view.jsp/ /c:when
%-- An exception occured. --%
c:when test=${param.o == 'xml'}
jsp:include page=/xml/_error_view.jsp/ /c:when c:otherwise
jsp:include page=/html/_error_view.jsp/ /c:otherwise
/c:choose
End Controller
Then our xml/_view.jsp would look something like this:
Begin xml/_view.jsp jsp:root version=2.0
jsp:directive.taglib uri=http://java.sun.com/jsp/jstl/core;
prefix=c /
?xml version=1.0 encoding=UTF-8?
result
c:forEach ...
... output some XML tags
/c:forEach
/result
/jsp:root
End xml/_view.jsp
The problem is sometimes the end result has a bunch of white
space at the beginning of the document and sometimes the
c:forEach generates lots of linefeeds which cause XML
parsers to fail. What is the proper way to dump an XML view
such that there are no linefeeds in between the XML tags and
there isn't a lot of whitespace above the XML?
Thanks,
Aaron
___
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] XML View Question
On May 8, 2007, at 9:51 AM, Aaron Freeman wrote:
Can anybody provide me with any links/hints on this?
JSP 2.1 has a trimDirectiveWhitespace option for the %@ page %
tag. That would be the cleanest way to remove the extra whitespace.
-- Scott
Thanks,
Aaron
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Aaron Freeman
Sent: Thursday, May 03, 2007 10:59 AM
To: resin-interest@caucho.com
Subject: [Resin-interest] XML View Question
We have a controller JSP that looks like this:
Begin Controller %@ taglib
uri=http://java.sun.com/jsp/jstl/core; prefix=c % %@
taglib uri=http://java.sun.com/jsp/jstl/functions; prefix=fn %
c:catch var=exception
... do some logic
/c:catch
c:choose
c:when test=${empty exception param.o == 'xml'}
jsp:include page=/xml/_view.jsp/
/c:when
c:when test=${empty exception}
jsp:include page=/html/_view.jsp/ /c:when
%-- An exception occured. --%
c:when test=${param.o == 'xml'}
jsp:include page=/xml/_error_view.jsp/ /c:when c:otherwise
jsp:include page=/html/_error_view.jsp/ /c:otherwise
/c:choose
End Controller
Then our xml/_view.jsp would look something like this:
Begin xml/_view.jsp jsp:root
version=2.0
jsp:directive.taglib uri=http://java.sun.com/jsp/jstl/core;
prefix=c /
?xml version=1.0 encoding=UTF-8?
result
c:forEach ...
... output some XML tags
/c:forEach
/result
/jsp:root
End xml/_view.jsp
The problem is sometimes the end result has a bunch of white
space at the beginning of the document and sometimes the
c:forEach generates lots of linefeeds which cause XML
parsers to fail. What is the proper way to dump an XML view
such that there are no linefeeds in between the XML tags and
there isn't a lot of whitespace above the XML?
Thanks,
Aaron
___
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
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Moving from Tomcat, getting No forwarding URI for form
I had a set of pages working perfectly with Tomcat, and am trying to move them to Resin. My /j_security_check servlet seems to be blowing up with the following response javax.servlet.ServletException: No forwarding URI for form authentication. Either the login form must specify j_uri or the session must have a saved URI. I'll do either, but don't see how I am supposed to specify either. Pointers would be greatly appreciated. Thanks Pat -- Pat Farrell http://www.pfarrell.com/ ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Moving from Tomcat, getting No forwarding URI for form
Hey Pat, I'd stick with Tomcat. Resin has some excellent features that can't be found anywhere else (full EJB 2.0 and PHP support for one, and remarkably easy to use configuration files), but Tomcat is now a de facto standard and extremely well supported by an enormous community. I would wager you'd get more help with your question on tomcat-users(http://tomcat.apache.org/lists.html :) But really Tomcat's much larger user base is it's biggest selling point. Tomcat is extremely well tested, and my own travails with Resin's JSTL support show how important community testing is. I really wanted my company to move to Resin 3.0 but it just couldn't cut the mustard, so we stayed with Tomcat. I'm still hopeful, though, that Resin will emerge as the fastest bestest most featureful Java app server out there. It's classloaders, built-in XSLT engine, and easy configuration are not to be found elsewhere, and it's too bad I have to sacrifice these remarkable features just to get *reliable* compatibility with the full range of JavaEE specifications. Peace, Josh On 5/8/07, Pat Farrell [EMAIL PROTECTED] wrote: I had a set of pages working perfectly with Tomcat, and am trying to move them to Resin. My /j_security_check servlet seems to be blowing up with the following response javax.servlet.ServletException: No forwarding URI for form authentication. Either the login form must specify j_uri or the session must have a saved URI. I'll do either, but don't see how I am supposed to specify either. Pointers would be greatly appreciated. Thanks Pat -- Pat Farrell http://www.pfarrell.com/ ___ 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
