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
On 3/7/07, Daniel López <[EMAIL PROTECTED]> wrote:
> We create the .project structure so it points to our build directories
> through virtual links (so the built artifacts do not end up in the
> "source" directory) and with that and calling Ant from inside Eclipse,
> it's enough for us.
I'm not su
I meant "last". (Perhaps it was a freudian slip betraying my
hope-against-hope of first rate jstl support in Resin).
On 3/6/07, Josh Rehman <[EMAIL PROTECTED]> wrote:
> This won't be the first JSTL bug you run into.
>
> On 3/6/07, Jose Quinteiro <[EMAIL PROTECTED
This won't be the first JSTL bug you run into.
On 3/6/07, Jose Quinteiro <[EMAIL PROTECTED]> wrote:
> This just caused me a couple of hours of frustration. The taglib URI on
> this page http://www.caucho.com/resin-3.1/doc/jstl.xtp will not work.
> This URI will: http://java.sun.com/jsp/jstl/core
Hello,
I'm getting a 500 exception when trying to use the xml forEach tag,
stack trace below. I've included the jsp needed to duplicate.
Interestingly, the other xml tags seem to work. I also double checked
standard.jar and verified that UnresolvableException does exist.
This issue does not occur
On 1/24/07, Josh Rehman <[EMAIL PROTECTED]> wrote:
> BTW I'm running into more problems with JSTL support (the SQL tags
> this time). I will post when I have a good test case.
Well, I don't know what actually causes this, but it turns out that if
your deployment descriptor
On 12/4/06, Scott Ferguson <[EMAIL PROTECTED]> wrote:
>
> On Dec 3, 2006, at 5:41 PM, Josh Rehman wrote:
>
> >
> > 2) Adding this configuration doesn't fix the problem. The "doc"
> > attribute of x:parse is most certainly supported by JSTL 1.1:
Than
ed."
So Resin actually implements "have your cake and eat it too" but it's
not working in your case. Perhaps there is some error when the
comparison is made - perhaps the clocks on the two systems are not in
sync. Or something. :)
Peace,
Josh
On 1/8/07, Josh Rehman <[EMAIL PRO
Corrections below:
On 1/8/07, Josh Rehman <[EMAIL PROTECTED]> wrote:
...
> While there are [[hacky]] ways to notify the "offline" server of state changes
...
> How can you have your cake and eat it too? You need some way for nodes
> to see if they are participating in a
Hi Jacky,
Please forgive my comment - I don't use distributed sessions, but I
think that you are running into a theoretical limitation of the
feature: offline servers participating in a cluster cannot, in
general, be notified of changes to session state of online servers.
This fact could cause so
On 12/4/06, Scott Ferguson <[EMAIL PROTECTED]> wrote:
>
> On Dec 3, 2006, at 5:41 PM, Josh Rehman wrote:
>
> >
> > 2) Adding this configuration doesn't fix the problem. The "doc"
> > attribute of x:parse is most certainly supported by JSTL 1.1:
>
seperate bug in Resin: if I disable fast jstl, I would expect the
application to fail faster with a "taglib not found" type of error.
I am very much hoping that there is some oversight on my part. I do
not like JBoss's baroque configuration at all and would very much l
12 matches
Mail list logo
