Re: Woody textareas?

[Marc Portier]

Nathaniel Alfred wrote:
-Original Message-
From: Simon Price [mailto:[EMAIL PROTECTED]
Sent: Montag, 30. Juni 2003 20:04
...

Cocoon's form handling is (imho) it's weakest area at present 
although 
it is rapidly improving with the interplay between flow and xmlform.
...

Simon

Luke Penca wrote:

Are textareas implemented in Woody yet?  I cannot find 
anything in the (oh so sparse) documentation.

Furthermore, has anyone used Woody extensively yet?  (I 
know, I know, it's alpha at this point but I need some 
serious forms handling.)  Should I be considering Xforms 
instead?  Who got some experience getting their hands 
bloodied with forms in Cocoon?  I'm ever anxious to find out.
...

Luke.


I've just started prototyping with Woody and I think it is a
diamond in the raw.  Finally a form handling package that does
not require you to write a bean class or Cocoon action for
every little form!
I think it can even get better: just made a posting on cocoon-dev 
on how we could have it working for binding to a bean class as 
well :-)

Coming to the original question:  There is no special textarea widget
but you can emulate it easily by a field widget with styling:

  

yep.

which is then transformed into HTML as:


  


  

  
  

  

  

HTH, ALfred.
nice angle of attack,
(you might want to add a call-template to add the 'wi:validation' 
section to the show)

care to share this as a patch?
(it's the surest way to start cutting the diamond out of the raw 
stone :-))

regards,
-marc=
--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Logging in cocoon.

[Marc Portier]

Irina,

some wild guesses from a distance
(maybe including the relevant parts of the code, the logkit.xconf 
and cocoon.xconf could help us narrowing that distance)

- mismatch in the debugging level?
- some of this logging is through buffered outputstreams, not 
untill those get flushed you will see the info in the log

HTH
-marc=
Kogan Irina wrote:
Hello everybody,

I am using getLogger() function in my action for debugging purposes.
However, for some reason the file to which the logging should go is always
empty (this file has been created after I specified it in the logkit.xconf).
I tried enableLogging(getLogger()) but it did not help.  Does anybody know
how I can get it to work?
Thanks a lot!

Irina.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Error message when starting cocoon

[Marc Portier]

at org.apache.cocoon.servlet.CocoonServlet.initLogger(CocoonServlet.java:813)
at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:269)
at 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935)
at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:668)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at 
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:536)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: bug Pdf Serialiser

[Marc Portier]

Carletta,

there is very little in your message that gives me any clue 
towards the solution.

Are there any stacktraces in the cocoon logs or the tomcat logs?

Some other tests you might want to do:
- can you let the browser-user do a right-click on the 
**PDFO*.jsp and then choose to

- have you tried with other browsers? Can you make the matcher 
work on **PDFO*.pdf just out of curiosity?

- can you maybe slide in an HTTP tunnel to check the HTTP request 
and response?  (I use http://www.pocketsoap.com/tcpTrace/, Apache 
Axis and MS SOAP Toolkit have something similar) and register the 
differences between both cases?

-marc=



CARLETTA ANGELO wrote:
--- Reçu de   INFETUDE.G145193 02/250.96.71  01-04-03 14.22

Hi,

I have a application whith cocoon 2.04 and tomcat 4.1.12
When i start whithout user defined in tomcat (web.xml of application)


the serialize fo2pdf run fine (the acrobat reader run)
   

  
  
  

   
But
When i start whith user defined in tomcat (and the user enter loggin)
the serialize fo2pdf not run (the acrobat reader not start) but if
serialize xml, it'is ok
   

  
  
  

   
Many thanks for your reply!

Carletta

 01-04-03 14.22  Envoyé à  
  -> [EMAIL PROTECTED]
**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
[EMAIL PROTECTED]
This footnote also confirms that this email message has been swept 
 for the presence of computer viruses.

www.pv.be
**
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Can I do this?

[Marc Portier]

you might want to look into the RequestParameterAction

http://xml.apache.org/cocoon/apidocs/org/apache/cocoon/matching/RequestParameterMatcher.html
http://cvs.apache.org/viewcvs.cgi/cocoon-2.0/src/java/org/apache/cocoon/matching/RequestParameterMatcher.java?rev=1.1&content-type=text/vnd.viewcvs-markup

  http://whatever/andsome?term={1}"; />

if you need more then one request parameter it might be easier to 
use the RequestParameterAction:
http://xml.apache.org/cocoon/apidocs/org/apache/cocoon/acting/RequestParamAction.html

-marc=

[EMAIL PROTECTED] wrote:
Can I (?) do anything like this:
 

http://blablabla?term={1}/>



 
I've found that if I do (...) pattern="*.search"> (...)  it works, and i 
can do for example "search phrase".search in the address bar and it 
matches with the generate prototype.. but i want to use that notation to 
match a GET form.
 
Thanks
 
João César
[EMAIL PROTECTED]
 
--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Orcale-XML-Parser in Coccon2

[Marc Portier]

Uwe Gerger wrote:
it is the standard xml-parser in our company; so we have to use it
instead of xerces!
That's the only reason!
uh!
must feel great though :-p
maybe jdk 1.4 is also a standard in whoch case you have a serious 
conflict :-)

in coocon.xconf I found some parameter options for the XML-parser,
namely sax-parser-factory and document-builder-factory. Have I have to
specify them? In the original state they are comment out?
aha. you made me have a look myself now.
it's even better then I suggested (I should 've known though)
yes, use those and replace the ??? values with the factories 
provided by the oracle implementation.
It will need to be full qualified classnames you put in there.

For inspiration on the values open the 
oracle-jaxp-implementation-whatevername.jar (eg with winzip)
and copy the contents of the files in 
META-INF/services/javax.xml.parsers.* into the respective elements.

(if oracle parser is jaxp compliant those files should be in the 
jar, otherwise you'll need to go into the documentation)



for interest in 2 words the theory:
JAXP is an insulation layer for having xml docs parsed using the 
SAX or DOM API (forgetting about the XSLT support for ease of 
argument)

Rather then doing the parsing itself this layer just specifies 
how JAXP compliant parsers should work AND offers a transparent 
dynamic loading of the implementation class through the 
AbstractFactory pattern.

Which boils down to:
This last technique requires you to specify which is the full 
qualified class name of the implementation-factory to be used.

- cocoon lets you do that in the elms you mention there, and I 
would use that option in this case (since you want to hardwire 
the inhouse STANDARD) the bad thing about this approach is that 
newer versions might (unlikely) place their factories elsewhere

- jaxp itself 'detects' (see the directory /META-INF/services in 
the jar file of xerces and (should be oracle) parsers)  which 
implementation to use by probing for the files 
/META-INF/services/javax.xml.parsers.(SAXParserFactory or 
DocumentBuilderFactory) in its classpath... therefor the 'first' 
jaxp implementation jar in the classpath will get used.

since jdk 1.4 however this means you also have to outsmart the 
jre-classpath (since it already holds xerces) using the endorsed 
mechanism
(you will need to check out docos from your webcontainer I guess)

in this latter case I would very much opt for removing xercesImpl.jar



Thanks
Uwe
[EMAIL PROTECTED] schrieb:

Uwe,

have no experience with it, however if it is fully JAXP compliant
it _should_ be as easy as putting the jar in the classpath up
front of (better yet: and removing) the xerces impl jar.
for more detail and explanation: check the  elm in
your WEB-INF/cocoon.xconf (loads of comments there taking you by
the hand)
any particular reason why you like to switch it though?

-marc=

Uwe Gerger wrote:

Hello,
I would like to use the Oracle - XML-Parser (version xdk-9_2_0_1_0) in
Cocoon 2. Has anybody some experience in doing this!?
What I have to do?
Thanks in advance
 Uwe
--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Orcale-XML-Parser in Coccon2

[Marc Portier]

Uwe,

have no experience with it, however if it is fully JAXP compliant 
it _should_ be as easy as putting the jar in the classpath up 
front of (better yet: and removing) the xerces impl jar.

for more detail and explanation: check the  elm in 
your WEB-INF/cocoon.xconf (loads of comments there taking you by 
the hand)

any particular reason why you like to switch it though?

-marc=

Uwe Gerger wrote:
Hello,
I would like to use the Oracle - XML-Parser (version xdk-9_2_0_1_0) in
Cocoon 2. Has anybody some experience in doing this!?
What I have to do?
Thanks in advance
Uwe
--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem in converting umlaut characters..

[Marc Portier]

jaya wrote:
Hello,

I am using Cocoon latest version. When I am generating a text file from
text or html file?
on-line or off-line?
XML document using XSL, I got the following problem in Cocoon.

"Müller" is shown as "Müller"

where do you see this come up? ('in cocoon' is a bit vague)
your browser?
can you check on which encoding the view-app (assuming browser) 
is using to render the text?

currently thinking setting content encoding on your serializer 
should do it (in html you could hack some meta tag in there, for 
txt you'll really need to change the latter)

how to do it is in the first part of this:
http://wiki.cocoondev.org/Wiki.jsp?page=RequestParameterEncoding
HTH
-marc=
I have given the encoding in XML and XSL file properly and I have
generated the same text file in the Command line using Xalan XSLT
processor. I got the text "Müller" properly.  I am not getting this
while I am using Cocoon.
Could U please tell me whether I have to give any settings in Cocoon for

this Umlaut characters ?

Expecting reply,

Thanks a lot,

Jaya

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: How to get HTML (not XHTML) from the HTMLSerializer (C2.0.1)

[Marc Portier]

Hi,

[1]
I thought  was the classic tric for all elder browsers?
as in:
  less_then letter_b letter_r [[[SPACE]]] slash biggert_then

those elder browsers consider /-es appended to the tagname to be part of the
tagname,
and the br/ tag is as meaninless as your own invention to it (and thus
ignored)

[2]
as for you remark to 'easier' I guess the serializer idea comes from the
separation of concerns philosophy... the one that writes an XSLT can not be
sure that it will (at all times) be the last step in the show, not even if
it's output is XHTML

(think about post-processing with another XSLT step that e.g. would change
all
 background color attributes?)

Should check the code, but I expect the output property 'method' of the xsl
to be
overriden to 'xml' anyway when used in a transformer...

[3]
in every case I do live under the impression that the html serializer will
create  for you instead of  did you check your sitemap?

And for this I did check the code: as expected the html serializer is
precisely
an empty TRaX transformer that gets an output property method="html"

handler = getTransformerFactory().newTransformerHandler();
format.put(OutputKeys.METHOD,"html");
handler.setResult(new StreamResult(this.output));
handler.getTransformer().setOutputProperties(format);


which boils down to checking your sitemap again?

-marc=

> -Original Message-
> From: Peter Robins [mailto:[EMAIL PROTECTED]]
> Sent: vrijdag 12 april 2002 12:38
> To: [EMAIL PROTECTED]
> Subject: Re: How to get HTML (not XHTML) from the HTMLSerializer
> (C2.0.1)
>
>
> excuse me if I'm missing the point but, if the objective is to get 
> instead of , wouldn't it be far easier to use the html
> output method in
> the xslt script directly, and not use the HTML serializer?
>
>
> On Friday 12 Apr 2002 7:59, Nicola Ken Barozzi wrote:
> > From: "Yuri Gadow" <[EMAIL PROTECTED]>
> >
> > > > Try with 
> > >
> > > If you mean an XSLT using that syntax (otherwise, I guess I'm missing
> > > something), I'm afraid that doesn't help.
> >
> > It's a hack to get Netscape 4 to use that tag.
> >
> > If I write:
> >
> >   
> >
> >ciao
> >ciao
> >   
> >
> > in Netscape 4.7 I get:
> >
> > ciaociao
> >
> > but if I write this:
> >
> >   
> >
> >ciao
> >ciao
> >   
> >
> > I get:
> >
> > ciao
> > ciao
> >
> > I can also write  and it's the same, the
> > trick is putting in an attribute.
> >
> > In this way Netscape 4 can show valid XHTML, which is IMHO
> better anyways
> > than .
> >
> > Just write a stylesheet that converts adds an attribute to s and
> > copies all other stuff, and you're done.
>
> -
> 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]>