RE: [C1] Installation woes [rant AND request] - PLEASE help!

[Derek Hohls]

Thanks, but as I am not using Postgres, I do not think that this is necessarliy an 
issue.

Derek.

>>> [EMAIL PROTECTED] 12/11/2001 08:54:30 >>>
Hi,

just to inform you your setting for the DBPostgres seems to be wrong.
It should be org.postgresql.Driver.

Max

> -Original Message-
> From: Lajos Moczar [mailto:[EMAIL PROTECTED]] 
> Sent: Freitag, 9. November 2001 15:47
> To: [EMAIL PROTECTED] 
> Subject: Re: [C1] Installation woes [rant AND request] - PLEASE help!
> 
> 
> Hi Derek:
> 
> Here is my cocoon.properties. Note the entire jdbc-driver section: 
> you'll see that the DBMM driver is also listed on the first line:
> 
> # These are the supported jdbc-drivers and their adaptors.
> # These properties are used by the DBFactory.
> processor.xsp.pool.database.adaptor=DBWeblogic,DBOracle,DBInst
> antDB,DBPostgres,DBSybase,DBInformix,DBMM
> processor.xsp.pool.database.adaptor.DBWeblogic=weblogic.jdbc.p
> ool.Driver
> processor.xsp.pool.database.adaptor.DBOracle=oracle.jdbc.drive
> r.OracleDriver
> processor.xsp.pool.database.adaptor.DBInstantDB=org.enhydra.in
> stantdb.jdbc.idbDriver
> processor.xsp.pool.database.adaptor.DBPostgres=postgresql.Driver
> processor.xsp.pool.database.adaptor.DBInformix=com.informix.jd
> bc.IfxDriver
> processor.xsp.pool.database.adaptor.DBSybase=com.sybase.jdbc.SybDriver
> processor.xsp.pool.database.adaptor.DBMM=org.gjt.mm.mysql.Driver
> 
> Also note the log line: this can help you see exactly where it is 
> throwing up:
> 
> processor.xsp.pool.logfile=c:\_trash\dbPool.log
> 
> I guess the next thing to look at is versions: what is your 
> tomcat, jdk 
> & mysql versions?
> 
> Also, do you explicitly load mysql_comp.jar in 
> tomcat.sh/tomcat.bat? You 
> might try that. Edit the :staticClasspath section and add it. 
> It really 
> seems like cocoon is just not able to access the jar.
> 
> Lajos
> galatea.com
> 
> 
> Derek Hohls wrote:
> 
> > Thanks - they do all already have the mysql_uncomp.jar as well...
> > 
> > 
> [EMAIL PROTECTED] 09/11/2001 10:35:02 >>>
> 
> > Dunno if this makes a difference, but I have mysql_comp.jar 
> located in $TOMCAT_HOME/webapps/cocoon/web-inf/lib
> > 
> > Another thought:  try each configuration using 
> mysql_uncomp.jar.  Perhaps one of the OS's (or one of the 
> JDK's) is having a problem reading a compressed jar.
> > 
> > HTH.
> > 
> > 
> > DR
> > 
> > 
> > 
> > At 09:44 AM 11/9/01 +0200, you wrote:
> > 
> >>Lajos
> >>Thanks - I have actually done all this - tho' I only have 
> just put mysql_comp.jar in $TOMCAT_HOME/lib
> >>That's what so frustrating... it all *looks* the same on 
> each machine [settings-wise] but behaves differently!  If you 
> could send a copy of whatever files you think are relevant, I 
> would appreciate that.
> >>Derek
> >>
> > 
> > 
> > 
> -
> > Please check that your question has not already been answered in the
> > FAQ before posting. 
> > 
> > To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> > For additional commands, e-mail: <[EMAIL PROTECTED]>
> > 
> > 
> > 
> > 
> -
> > Please check that your question has not already been answered in the
> > FAQ before posting. 
> > 
> > To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> > For additional commands, e-mail: <[EMAIL PROTECTED]>
> > 
> > 
> 
> 

-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>



-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

RE: [C1] Installation woes [rant AND request] - PLEASE help!

[Max Larsson]

Hi,

just to inform you your setting for the DBPostgres seems to be wrong.
It should be org.postgresql.Driver.

Max

> -Original Message-
> From: Lajos Moczar [mailto:[EMAIL PROTECTED]]
> Sent: Freitag, 9. November 2001 15:47
> To: [EMAIL PROTECTED]
> Subject: Re: [C1] Installation woes [rant AND request] - PLEASE help!
> 
> 
> Hi Derek:
> 
> Here is my cocoon.properties. Note the entire jdbc-driver section: 
> you'll see that the DBMM driver is also listed on the first line:
> 
> # These are the supported jdbc-drivers and their adaptors.
> # These properties are used by the DBFactory.
> processor.xsp.pool.database.adaptor=DBWeblogic,DBOracle,DBInst
> antDB,DBPostgres,DBSybase,DBInformix,DBMM
> processor.xsp.pool.database.adaptor.DBWeblogic=weblogic.jdbc.p
> ool.Driver
> processor.xsp.pool.database.adaptor.DBOracle=oracle.jdbc.drive
> r.OracleDriver
> processor.xsp.pool.database.adaptor.DBInstantDB=org.enhydra.in
> stantdb.jdbc.idbDriver
> processor.xsp.pool.database.adaptor.DBPostgres=postgresql.Driver
> processor.xsp.pool.database.adaptor.DBInformix=com.informix.jd
> bc.IfxDriver
> processor.xsp.pool.database.adaptor.DBSybase=com.sybase.jdbc.SybDriver
> processor.xsp.pool.database.adaptor.DBMM=org.gjt.mm.mysql.Driver
> 
> Also note the log line: this can help you see exactly where it is 
> throwing up:
> 
> processor.xsp.pool.logfile=c:\_trash\dbPool.log
> 
> I guess the next thing to look at is versions: what is your 
> tomcat, jdk 
> & mysql versions?
> 
> Also, do you explicitly load mysql_comp.jar in 
> tomcat.sh/tomcat.bat? You 
> might try that. Edit the :staticClasspath section and add it. 
> It really 
> seems like cocoon is just not able to access the jar.
> 
> Lajos
> galatea.com
> 
> 
> Derek Hohls wrote:
> 
> > Thanks - they do all already have the mysql_uncomp.jar as well...
> > 
> > 
> [EMAIL PROTECTED] 09/11/2001 10:35:02 >>>
> 
> > Dunno if this makes a difference, but I have mysql_comp.jar 
> located in $TOMCAT_HOME/webapps/cocoon/web-inf/lib
> > 
> > Another thought:  try each configuration using 
> mysql_uncomp.jar.  Perhaps one of the OS's (or one of the 
> JDK's) is having a problem reading a compressed jar.
> > 
> > HTH.
> > 
> > 
> > DR
> > 
> > 
> > 
> > At 09:44 AM 11/9/01 +0200, you wrote:
> > 
> >>Lajos
> >>Thanks - I have actually done all this - tho' I only have 
> just put mysql_comp.jar in $TOMCAT_HOME/lib
> >>That's what so frustrating... it all *looks* the same on 
> each machine [settings-wise] but behaves differently!  If you 
> could send a copy of whatever files you think are relevant, I 
> would appreciate that.
> >>Derek
> >>
> > 
> > 
> > 
> -
> > Please check that your question has not already been answered in the
> > FAQ before posting. 
> > 
> > To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> > For additional commands, e-mail: <[EMAIL PROTECTED]>
> > 
> > 
> > 
> > 
> -
> > Please check that your question has not already been answered in the
> > FAQ before posting. 
> > 
> > To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> > For additional commands, e-mail: <[EMAIL PROTECTED]>
> > 
> > 
> 
> 

-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

problems passing a parameter to a xsl transformation

[Joaquin Cuenca Abela]

I have
Cocoon 2.0rc1a
Tomcat 3.2.3
jdk 1.3.1
RedHat Linux 7.2 (approx)

I've put a simple application to test cocoon, but I'm not able to pass 
arguments to my xsl transformation.  Ie, if I have a file "agenda.xml" 
and another one named "agenda.xsl", and in the sitemap.xml I have 
something as:

  ...

 
 
 

  ...

When I point my navigator to http://127.0.0.1:8080/cocoon/agenda.html 
everything works like a charm.  The problem is when I try to access to 
the same page but using a parameter, as

http://127.0.0.1:8080/cocoon/agenda.html?foo=bar

(in my xsl file I have

  
)

foo is still equal to 'f' and not to 'bar', as I was expecting.

Searching with google I've found some links that suggest that the line:

 false

in the sitemap.xml may be related, but even if I change false to true I 
still get the same behaviour.

What should I do to have xsl:param's automatically read from url parameters?

Thanks in advance!

Cheers,

P.S.: I will be happy enough with a rtfm if you add an url to tfm.

--
Joaquin Cuenca Abela
[EMAIL PROTECTED]


-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

Cocoon2, OSX install problem

[terracare]

I'm trying to install Cocoon2 (downloaded from CVS on 11.9.01) on OS X
(version 10.03) and Tomcat (3.23). I followed installation instructions step
by step. As per OSX-specific issues, I was also careful to edit my ant file,
to set JAVA_HOME statically and add the correct path to classes.jar to the
classpath. I assume I don't have to worry about tools.jar on OSX. I believe
I successfully built the Cocoon.war file (i.e. no complaints from ant), but
when I try to access Cocoon via localhost:8080/cocoon/ I get a
java.lang.ClassNotFoundException: org.apache.cocoon.www.sitemap_xmap.

Checking the log directory within WEB-INF revealed no additional useful
information (for me at least). I'm a little confused, because this class
appears to be located in a cocoon directory within $TOMCAT_HOME/work.

Any tips are greatly appreciated.

Diana


-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

RE: Sitemap parameters set by Transformer

[giacomo]

On Sun, 11 Nov 2001, Luca Morandini wrote:

> Giacomo,
>
>   thanks for explaining to me the whole sitemap parameters concept.
>
>   Though... why an action or a matcher can set, say, a session parameter, and
> a transformer cannot ?

No, both are able to set session attributes. But the time line WHEN they
do it is different. When a transformer sets a session attribute during
its scan of the SAX events pased throught it there is not chance for a
Selector to cach it up.

The execution time scope of actions, matchers and selectors are
different from generators, transformers and serializers. First only
actions, matchers and selectors are executed (to asseble the pipeline)
afterwards only generators, transformers and serializers are executed
(plugged together to form the pipeline and process SAX events).

Hope it is another step forward to make it clearer.

Giacomo

>
>   I mean, there is a compelling rason for it... or it could be done but the
> developers deemed it to be unnecessary (as it probably is) ?
>
> Best regards,
>
> -
>Luca Morandini
>GIS Consultant
>   [EMAIL PROTECTED]
> http://utenti.tripod.it/lmorandini/index.html
> -
>
>
> > -Original Message-
> > From: giacomo [mailto:[EMAIL PROTECTED]]
> > Sent: Sunday, November 11, 2001 11:41 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Sitemap parameters set by Transformer
> >
> >
> > On Sat, 10 Nov 2001, Luca Morandini wrote:
> >
> > > Giacomo,
> > >
> > >   here's the sample:
> > >
> > > 1) The user goes to login.xml URI
> > > 2) A pipeline takes care of producing the proper HTML form
> > > 3) The user fills the form and activates "submit"
> > > 4) The "submit" event triggers a check-login.xml being requested
> > > 5) A pipeline takes care of calling SQLTransformer to check
> > login/password
> > > via a stored procedure.
> > > 6) The SQLTransformer emits an  element which
> > contains the
> > > value of an output parameter of the stored procedure, which may be "0"
> > > (login accepted), or "not 0" (login denied)
> > > 7) An XSL grabs the SQLTransformer's output and produces something like:
> > >   or
> > >  
> > > 8) I'd like to call another Transformer (let's call it
> > ControlTransformer)
> > > which scans the output of previous step and sets a *sitemap parameter*
> > > called "status" to match the contents of "value" attribute in
> > >  element
> > > 9) In the sitemap, using a ParameterSelector, the appropriate
> > > map:redirect-to-uri is chosen, depending on the value of "status"
> > >
> > >   I know this may be done using XSP and/or actions, but I'd
> > like to stick to
> > > XML/XSL as much as I can, hence avoiding XSP and actions,
> > though I'm open to
> > > suggestions.
> > >
> > >   Regarding the use of the *sitemap parameter* term... I'm
> > confised, since
> > > in:
> > > http://xml.apache.org/cocoon2/userdocs/selectors/selectors.html
> > >
> > >   The following sentence is reported: "ParameterSelector:
> > matches the string
> > > specified in the "test" parameter against a specified Cocoon
> > internal (e.g.
> > > sitemap) parameter;".
> > >
> > >   Hence, I supposed the term "sitemap parameter" was widely
> > used. I guess
> > > "session parameter" should be used instead, am I right ?
> >
> > Exactly. Look, there are two steps in the sitemap process:
> >
> > 1. step: evaluation.
> > 2. step: production.
> >
> > In the 1. step the sitemap assembles the components (generator,
> > transformer and serializer) to produce the requested resource. This is
> > done using actions, matchers and selectors. This means that the later
> > components are activated immediately when encountered during the sitemap
> > scan whereas the former components are activated when the pipeline is
> > complete (read has a generator, 0-n transformer and a serializer). This
> > implies that a selector or matcher or action cannot inspect the SAX
> > stream the pipeline produces because the production of the SAX stream
> > is delayed after the evaluation process.
> >
> > In your case you should probably stick with request/session attribute to
> > come along what you are trying to solve.
> >
> > Sitemap parameter are values proposed to be configuration data passed to
> > the components. These values could be produced by actions or matchers
> > and passed to pipeline components (generators, transformers or
> > serializers) but not the other way around.
> >
> > Hope this makes it clearer.
> >
> > Cheers
> >
> > Giacomo
> >
> > >
> > >   Thanks for your kind reply,
> > >
> > > -
> > >Luca Morandini
> > >GIS Consultant
> > >   [EMAIL PROTECTED]
> > > http://utenti.tripod.it/lmorandini/index.html
> > > -
> > >
> > >
> > > > -Original Message-
> > > > From: giacomo [mailto:[EMAIL

RE: Sitemap parameters set by Transformer

[Luca Morandini]

Giacomo,

thanks for explaining to me the whole sitemap parameters concept.

Though... why an action or a matcher can set, say, a session parameter, and
a transformer cannot ?

I mean, there is a compelling rason for it... or it could be done but the
developers deemed it to be unnecessary (as it probably is) ?

Best regards,

-
   Luca Morandini
   GIS Consultant
  [EMAIL PROTECTED]
http://utenti.tripod.it/lmorandini/index.html
-


> -Original Message-
> From: giacomo [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, November 11, 2001 11:41 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Sitemap parameters set by Transformer
>
>
> On Sat, 10 Nov 2001, Luca Morandini wrote:
>
> > Giacomo,
> >
> > here's the sample:
> >
> > 1) The user goes to login.xml URI
> > 2) A pipeline takes care of producing the proper HTML form
> > 3) The user fills the form and activates "submit"
> > 4) The "submit" event triggers a check-login.xml being requested
> > 5) A pipeline takes care of calling SQLTransformer to check
> login/password
> > via a stored procedure.
> > 6) The SQLTransformer emits an  element which
> contains the
> > value of an output parameter of the stored procedure, which may be "0"
> > (login accepted), or "not 0" (login denied)
> > 7) An XSL grabs the SQLTransformer's output and produces something like:
> >   or
> >  
> > 8) I'd like to call another Transformer (let's call it
> ControlTransformer)
> > which scans the output of previous step and sets a *sitemap parameter*
> > called "status" to match the contents of "value" attribute in
> >  element
> > 9) In the sitemap, using a ParameterSelector, the appropriate
> > map:redirect-to-uri is chosen, depending on the value of "status"
> >
> > I know this may be done using XSP and/or actions, but I'd
> like to stick to
> > XML/XSL as much as I can, hence avoiding XSP and actions,
> though I'm open to
> > suggestions.
> >
> > Regarding the use of the *sitemap parameter* term... I'm
> confised, since
> > in:
> > http://xml.apache.org/cocoon2/userdocs/selectors/selectors.html
> >
> > The following sentence is reported: "ParameterSelector:
> matches the string
> > specified in the "test" parameter against a specified Cocoon
> internal (e.g.
> > sitemap) parameter;".
> >
> > Hence, I supposed the term "sitemap parameter" was widely
> used. I guess
> > "session parameter" should be used instead, am I right ?
>
> Exactly. Look, there are two steps in the sitemap process:
>
> 1. step: evaluation.
> 2. step: production.
>
> In the 1. step the sitemap assembles the components (generator,
> transformer and serializer) to produce the requested resource. This is
> done using actions, matchers and selectors. This means that the later
> components are activated immediately when encountered during the sitemap
> scan whereas the former components are activated when the pipeline is
> complete (read has a generator, 0-n transformer and a serializer). This
> implies that a selector or matcher or action cannot inspect the SAX
> stream the pipeline produces because the production of the SAX stream
> is delayed after the evaluation process.
>
> In your case you should probably stick with request/session attribute to
> come along what you are trying to solve.
>
> Sitemap parameter are values proposed to be configuration data passed to
> the components. These values could be produced by actions or matchers
> and passed to pipeline components (generators, transformers or
> serializers) but not the other way around.
>
> Hope this makes it clearer.
>
> Cheers
>
> Giacomo
>
> >
> > Thanks for your kind reply,
> >
> > -
> >Luca Morandini
> >GIS Consultant
> >   [EMAIL PROTECTED]
> > http://utenti.tripod.it/lmorandini/index.html
> > -
> >
> >
> > > -Original Message-
> > > From: giacomo [mailto:[EMAIL PROTECTED]]
> > > Sent: Saturday, November 10, 2001 2:12 PM
> > > To: Cocoon-users; [EMAIL PROTECTED]
> > > Subject: Re: Sitemap parameters set by Transformer
> > >
> > >
> > > On Sat, 10 Nov 2001, Luca Morandini wrote:
> > >
> > > > Folks,
> > > >
> > > > does anyone know how to set a sitemap parameter from within
> > > a Transformer ?
> > >
> > > Why would your Transformer need to set a sitemap parameter
> (BTW what do
> > > you mean by "sitemap parameter"??) Actually there is no way (and no
> > > intention) to set any parameter (except those available from the
> > > Environment like Request, Session)
> > >
> > > > I'd like to be able to steer the sitemap flow from a
> > > Transformer, and the
> > > > best way seems to me the ability to set sitemap parameters (to
> > > be used in
> > > > some subsequent  statements).
> > >
> > > You should make a sample.
> > >
> > 

RE: Sitemap parameters set by Transformer

[giacomo]

On Sat, 10 Nov 2001, Liam Morley wrote:

> I think what Luca means is to have something like "". To
> me, it would make sense to send SAX events that trigger certain things
> to happen down the road, depending on what you have in mind.
>
> Otherwise, I'm not sure if you can set sitemap properties mid-way
> through a pipeline's execution, although it does seem like a decent
> idea. I hope you find a solution that applies to your particular
> problem.

You got the point. As soon as the pipelines starts to produce SAX
events the sitemap has already done its job and thus isn't able to
rearrange your pipeline according to some SAX events (or setting any
parameters somewhere).

Giacomo

>
> Liam Morley
>
> -Original Message-
> From: Luca Morandini [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, November 10, 2001 6:19 AM
> To: Cocoon-users
> Subject: Sitemap parameters set by Transformer
>
> Folks,
>
>   does anyone know how to set a sitemap parameter from within a
> Transformer ?
>
>   I'd like to be able to steer the sitemap flow from a
> Transformer, and the
> best way seems to me the ability to set sitemap parameters (to be used
> in
> some subsequent  statements).
>
> Best regards,
>
>
> -
>Luca Morandini
>GIS Consultant
>   [EMAIL PROTECTED]
> http://utenti.tripod.it/lmorandini/index.html
> -
>
>
>
> -
> Please check that your question has not already been answered in the
> FAQ before posting. 
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>
>
> -
> Please check that your question has not already been answered in the
> FAQ before posting. 
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>
>
>
>


-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

Re: Sitemap parameters set by Transformer

[giacomo]

On Sat, 10 Nov 2001, Luca Morandini wrote:

> Giacomo,
>
>   here's the sample:
>
> 1) The user goes to login.xml URI
> 2) A pipeline takes care of producing the proper HTML form
> 3) The user fills the form and activates "submit"
> 4) The "submit" event triggers a check-login.xml being requested
> 5) A pipeline takes care of calling SQLTransformer to check
login/password
> via a stored procedure.
> 6) The SQLTransformer emits an  element which
contains the
> value of an output parameter of the stored procedure, which may be "0"
> (login accepted), or "not 0" (login denied)
> 7) An XSL grabs the SQLTransformer's output and produces something
like:
>   or
>  
> 8) I'd like to call another Transformer (let's call it
ControlTransformer)
> which scans the output of previous step and sets a *sitemap parameter*
> called "status" to match the contents of "value" attribute in
>  element
> 9) In the sitemap, using a ParameterSelector, the appropriate
> map:redirect-to-uri is chosen, depending on the value of "status"
>
>   I know this may be done using XSP and/or actions, but I'd like
to stick to
> XML/XSL as much as I can, hence avoiding XSP and actions, though I'm
open to
> suggestions.
>
>   Regarding the use of the *sitemap parameter* term... I'm
confised, since
> in:
> http://xml.apache.org/cocoon2/userdocs/selectors/selectors.html
>
>   The following sentence is reported: "ParameterSelector: matches
the string
> specified in the "test" parameter against a specified Cocoon internal
(e.g.
> sitemap) parameter;".
>
>   Hence, I supposed the term "sitemap parameter" was widely used.
I guess
> "session parameter" should be used instead, am I right ?

Exactly. Look, there are two steps in the sitemap process:

1. step: evaluation.
2. step: production.

In the 1. step the sitemap assembles the components (generator,
transformer and serializer) to produce the requested resource. This is
done using actions, matchers and selectors. This means that the later
components are activated immediately when encountered during the sitemap
scan whereas the former components are activated when the pipeline is
complete (read has a generator, 0-n transformer and a serializer). This
implies that a selector or matcher or action cannot inspect the SAX
stream the pipeline produces because the production of the SAX stream
is delayed after the evaluation process.

In your case you should probably stick with request/session attribute to
come along what you are trying to solve.

Sitemap parameter are values proposed to be configuration data passed to
the components. These values could be produced by actions or matchers
and passed to pipeline components (generators, transformers or
serializers) but not the other way around.

Hope this makes it clearer.

Cheers

Giacomo

>
>   Thanks for your kind reply,
>
> -
>Luca Morandini
>GIS Consultant
>   [EMAIL PROTECTED]
> http://utenti.tripod.it/lmorandini/index.html
> -
>
>
> > -Original Message-
> > From: giacomo [mailto:[EMAIL PROTECTED]]
> > Sent: Saturday, November 10, 2001 2:12 PM
> > To: Cocoon-users; [EMAIL PROTECTED]
> > Subject: Re: Sitemap parameters set by Transformer
> >
> >
> > On Sat, 10 Nov 2001, Luca Morandini wrote:
> >
> > > Folks,
> > >
> > >   does anyone know how to set a sitemap parameter from within
> > a Transformer ?
> >
> > Why would your Transformer need to set a sitemap parameter (BTW what
do
> > you mean by "sitemap parameter"??) Actually there is no way (and no
> > intention) to set any parameter (except those available from the
> > Environment like Request, Session)
> >
> > >   I'd like to be able to steer the sitemap flow from a
> > Transformer, and the
> > > best way seems to me the ability to set sitemap parameters (to
> > be used in
> > > some subsequent  statements).
> >
> > You should make a sample.
> >
> > Giacomo
> >
>
>
>
>



-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

Re: ClassFormatError

[giacomo]

On Sat, 10 Nov 2001 [EMAIL PROTECTED] wrote:

> This problem is back in cocoon 2 RC2

Why you think "it is back"? Has it ever been gone?

Giacomo

>
> java.lang.ClassFormatError:
> 
>org/apache/cocoon/www/file_/C_/tomcat_3_2_3/webapps/nedss/investigation/web/xsp/investigation_xsp
>
> (Code of a method longer than 65535 bytes)
>
>
>
>
> -
> Please check that your question has not already been answered in the
> FAQ before posting. 
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>
>
>
>


-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>