Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 31530 invoked by uid 500); 21 Apr 2003 13:10:14 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 31493 invoked from network); 21 Apr 2003 13:10:12 -0000 Received: from smtp-1.indo.net.id (202.159.32.91) by daedalus.apache.org with SMTP; 21 Apr 2003 13:10:12 -0000 Received: (qmail 3563 invoked from network); 21 Apr 2003 20:10:05 +0700 Received: from smtp.indo.net.id (202.159.32.81) by smtp-1.indo.net.id with SMTP; 21 Apr 2003 20:10:05 +0700 Received: (qmail 1686 invoked from network); 21 Apr 2003 13:09:30 -0000 Received: from unknown (HELO id3.intercitra.com) (202.153.254.241) by smtp.indo.net.id with SMTP; 21 Apr 2003 13:09:30 -0000 Message-Id: <5.2.1.1.0.20030421202627.00ad6de0@mail.adelva.com> X-Sender: java@intercitra.com@mail.adelva.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 21 Apr 2003 20:27:41 +0700 To: cocoon-users@xml.apache.org From: Frans Thamura Subject: Re: [CimandeUpgrade] strange xsp:attribute handling -> ????? In-Reply-To: <3EA3D69D.8050605@gmx.de> References: <5.2.1.1.0.20030420051914.00aa69c8@mail.adelva.com> <5.2.1.1.0.20030420051914.00aa69c8@mail.adelva.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_387945946==.ALT" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --=====================_387945946==.ALT Content-Type: text/plain; charset="us-ascii" yah smiliar. thanks, so i have to wait for the patch.. mm keep working with this, hopefully i can finish it, the new, and search is finish.. and next step is result, and drop table, and generate table.. I love if my script run on top of Cocoon 2, and hopefully the cocoon 2 is stable enough to handle my script. several time crash in cocoon 1.. Thanks Jeorg Frans At 01:31 PM 4/21/2003 +0200, you wrote: >Hello Frans, > >there is a bug known about xsp:attribute (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15841). Does it apply to your problem? > >Regards, > >Joerg > >Frans Thamura wrote: >>I am upgrading my project from Cocoon 1 to Cocoon 2, >>I have a worked xsp:logic using Cocoon 1 (run well in my client website, and production), and in Cocoon 2, there is a *strange behavior*, if I put a new xml tag together with an xsp:attribute, the xsp:attribute is not add an element to the tag where the position of the pointer, but to the new tag >>Cocoon 2, have a silly behavior. how can? >>this is the logic: >>*Cocoon 1, i can put the xsp:logic together. >>* >> >>sGA_USER=(String)session.getAttribute("GA_USER"); >>if (sGA_USER!=null) { >> login >> >> >> >>} else { // session time out... >>logout >>} // END of session time out >> >> >> >>*Cocoon 2, I have to split 2 xsl:logic >>* >> >> >>sGA_USER=(String)session.getAttribute("GA_USER"); >>if (sGA_USER!=null) { >> login >> >>} else { >>logout >> >> >>if (sGA_USER!=null) { >> >> >> >>} else { // session time out... >>} // END of session time out >> >> >> >>I cannot use Cocoon 1 step, because cocoon engine will put the session attribute in the information tag, and put the information tag as a root. that is silly..BUGS I think? >>if I run the Cocoon 1 step in Cocoon 2 engine there will be an out put like this >> >> >> >> >> >> >>but the result that I want is >>as an attribute of contentmanager tag; >> >> >> >> >>*Comment plz.. >> >>*Frans > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org >For additional commands, e-mail: cocoon-users-help@xml.apache.org > Ikutan dong ke jug-indonesia@yahoogroups.com, biar bisa diskusi Java. Kita buat Java User Group Indonesia. cara subscribe, jug-indonesia-subscribe@yahoogroups.com Topik Java Open Source . Frans Thamura Intercitra Innovation Center Inspiring the Uninspired http://www.intercitra.com HP: +62 - 855 - 7888 - 699 Guerilla will help everyone exchange information and develop value to stakeholder. --=====================_387945946==.ALT Content-Type: text/html; charset="us-ascii" yah smiliar. thanks, so i have to wait for the patch..

mm keep working with this, hopefully i can finish it, the new, and search is finish.. and next step is result, and drop table, and generate table..

I love if my script run on top of Cocoon 2, and hopefully the cocoon 2 is stable enough to handle my script. several time crash in cocoon 1..

Thanks Jeorg

Frans



At 01:31 PM 4/21/2003 +0200, you wrote:
Hello Frans,

there is a bug known about xsp:attribute (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15841). Does it apply to your problem?

Regards,

Joerg

Frans Thamura wrote:
I am upgrading my project from Cocoon 1 to Cocoon 2,
I have a worked xsp:logic using Cocoon 1 (run well in my client website, and production), and in Cocoon 2, there is a *strange behavior*, if I put a new xml tag together with an xsp:attribute, the xsp:attribute is not add an element to the tag where the position of the pointer, but to the new tag
Cocoon 2, have a silly behavior. how can?
this is the logic:
*Cocoon 1, i can put the xsp:logic together.
*<xsl:template name="contentmanager">
<xsl:copy><xsp:logic>
sGA_USER=(String)session.getAttribute("GA_USER");
if (sGA_USER!=null) {
 <xsp:attribute name="session">login</xsp:attribute>
  <information>
        <statusset title="Login Session" param="Activated."/>
</information>
} else { // session time out...
<xsp:attribute name="session">logout</xsp:attribute>
} // END of session time out
</xsp:logic>
</xsl:copy>                                    
</xsl:template>
*Cocoon 2, I have to split 2 xsl:logic
*<xsl:template name="contentmanager">
<xsl:copy>
<xsp:logic>
sGA_USER=(String)session.getAttribute("GA_USER");
if (sGA_USER!=null) {
 <xsp:attribute name="session">login</xsp:attribute>
                                               
} else {
<xsp:attribute name="session">logout</xsp:attribute>
</xsp:logic>
<xsp:logic>    
if (sGA_USER!=null) {
<information>
        <statusset title="Login Session" param="Activated."/>
</information>
} else { // session time out...
} // END of session time out
</xsp:logic>
</xsl:copy>                                    
</xsl:template>
I cannot use Cocoon 1 step, because cocoon engine will put the session attribute in the information tag, and put the information tag as a root. that is silly..BUGS I think?
if I run the Cocoon 1 step in Cocoon 2 engine there will be an out put like this
<information session="login">
        <statusset title="Login Session" param="Activated."/>
</information>
<contentmanager >
</contentmanager>

but the result that I want is
as an attribute of contentmanager tag;
<contentmanager session="login">
        <statusset title="Login Session" param="Activated."/>
</contentmanager>

*Comment plz..

*Frans


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org

Ikutan dong ke jug-indonesia@yahoogroups.com, biar bisa diskusi Java.

Kita buat Java User Group Indonesia.

cara subscribe, jug-indonesia-subscribe@yahoogroups.com

Topik Java Open Source .

Frans Thamura
Intercitra Innovation Center
Inspiring the Uninspired
http://www.intercitra.com

HP: +62 - 855 - 7888 - 699

Guerilla will help everyone exchange information and develop value to stakeholder. --=====================_387945946==.ALT--