Mailing-List: contact taglibs-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tag Libraries Users List" <taglibs-user@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: domain of brodseba@gmail.com designates
 66.249.92.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references;
        b=HppV5HYwQVwanojSx9CWrTX00fdQ4atn4iYqmR+u0wfUt+yTnWZJAdQy7sR6R+h9nh5e4yI6U4OZbv3qQ0G2lQkpdLQAZCaGSEfi45zyeTkx2XVgrCSN8UvPH5Pbl8LMtEFJwo09dXtrIRWSOWbypcz7YudljTngjPaXtwJ9iZ8=
Message-ID: <b9a4fc270701310949nbb6203cj4e580f2c2d835195@mail.gmail.com>
Date: Wed, 31 Jan 2007 12:49:31 -0500
From: "=?ISO-8859-1?Q?S=E9bastien_Brodeur?=" <brodseba@gmail.com>
Reply-To: brodseba@iname.com
To: "Tag Libraries Users List" <taglibs-user@jakarta.apache.org>
Subject: Re: Problem when a use a x:forEach into another x:forEach
In-Reply-To: <541410.50363.qm@web56408.mail.re3.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_10653_30325502.1170265771007"
References: <541410.50363.qm@web56408.mail.re3.yahoo.com>

------=_Part_10653_30325502.1170265771007
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I open a ticket with Jakarta (
http://www.v-teams.com/so/php.html?gclid=3DCI6rhOXyiooCFR3VgAod8Va7dg) and =
the
problem is cause (in part) by the taglibs.  They give me a fixed
standard.jar. When I tested the fixed standard.jar locally on my Tomcat 5,
the problem is  fix.

But the problem is still happening on WebSphere 6.0.  After some
investigation, we realize that WebSphere use a fork Xalan library and that
maybe for this reason the problem is not fixed.  I will next open a ticket
with IBM about this issue.

Stay tune for me :-)

On 1/31/07, Rashmi Rubdi <dev_subscriptions@yahoo.com> wrote:
>
> This : http://www.xml.com/lpt/a/933 shows how to merge multiple XML sourc=
e
> files into one, and it works in XSLT 1.0
>
> -Rashmi
>
> ----- Original Message ----
> From: Rashmi Rubdi <dev_subscriptions@yahoo.com>
> To: Tag Libraries Users List <taglibs-user@jakarta.apache.org>
> Sent: Sunday, January 28, 2007 1:20:45 AM
> Subject: Re: Problem when a use a x:forEach into another x:forEach
>
>
> In both JSTL 1.1 and 1.0 specifications nothing is mentioned about nested
> x:forEach loops where the inner x:forEach iterates over the parsed result=
s
> of a *different* xml file.
>
> Since this scenario is not officially mentioned anywhere, I can't really
> tell for sure if the set-up you have is supposed to work or not. I didn't
> test it with JSTL 1.0, but since you say it worked in JSTL 1.0 I can't se=
e
> why it shouldn't work with 1.1.
>
> It is probably a bug in JSTL 1.1. I think this is where one could file a
> bug/ feature request: http://jakarta.apache.org/taglibs/#Bugs
>
> I also searched on ways to combine two different XML files into one with
> XSLT, it is possible on the command line with a parser like Saxon, but I
> couldn't find ways to do it programatically at least with XSLT 1.0 which
> is supported by the most recent version of Xalan which is used by JSTL. B=
ut
> you can check with a XSLT mailing list if you want to take that approach.
>
> Another approach would be to generate a merged XML file instead of two
> separate XML files.
>
> -Rashmi
>
>
>
>
> _________________________________________________________________________=
___________
> Be a PS3 game guru.
> Get your game face on with the latest PS3 news and previews at Yahoo!
> Games.
> http://videogames.yahoo.com/platform?platform=3D120121
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: taglibs-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: taglibs-user-help@jakarta.apache.org
>
>


--=20
S=E9bastien Brodeur
brodseba@iname.com
Site Web : http://www.un-programmeur-php.ca/

------=_Part_10653_30325502.1170265771007--