[ANN]: Fins 1.0.0 released

2008-04-29 Thread Luca Morandini


http://www.cocoondev.org/main/117-cd/29-cd.html


   Luca Morandini
www.lucamorandini.it



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



Re: Protocols in Cocoon

2008-04-29 Thread dynnamitt

Question:
 - How do I specify the cocoon-view param when using the cocoon:// or
cocoon:// protocol ?

just adding '?coccon-view=content' into the url doesn't seem to help much...
(2.1.11)

mvh,
dynnamitt.



Alexander Daniel wrote:
> 
> On 24.02.2008, at 06:30, Mansour wrote:
> 
>> Is there a full documentation about all the protocols available in  
>> Cocoon. I couldn't find any document on the Cocoon web site about  
>> this subject. Protocols I am aware of:
>>
>> implicit.
>> block:
>> blockcontext:
>> context:
>> resource:
>> servlet:
>> cocoon:
>>
>> I don't know what is the difference between each of them. Where can  
>> I get this info?
> 
> Unfortunately I am not aware of any full documentation of all the  
> protocols. Some information can be found in the Cocoon Wiki [1].
> 
> The Cocoon 2.1.11 samples configure following protocols in  
> cocoon.xconf: all JDK standard protocols (e.g. http), blob, cached,  
> cocoon, context, coplet, empty, file, module, qdox, repository,  
> resource, slide, upload, webdav, xmldb, xmodule, zip. Javadocs for  
> most of these can be found at [2].
> 
> I assume that block, blockcontext and servlet were introduced with  
> Cocoon 2.2.
> 
> Alex
> 
> [1] http://wiki.apache.org/cocoon/Protocols
> [2]
> http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/components/source/impl/package-summary.html
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Protocols-in-Cocoon-tp15661166p16976573.html
Sent from the Cocoon - Users mailing list archive at Nabble.com.


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



Re: problem with JSTL import tag on weblogic 9.2

2008-04-29 Thread Andy Stevens
On 28/04/2008, John Lung <[EMAIL PROTECTED]> wrote:
> Hi:
>
> We're trying to use JSTL 1.1 c:import tag on weblogic 9.2 in an JSP page to
> import the Cocoon page (Cocoon 2.1.11) under a different context (a
> different webapp in the same weblogic domain).
>
> 
>
> cocoon throws a 404 error and saying no match in the sitemap.  But when I
> directly access this page:
>
> http://localhost:port/Cocoon/MyCocoonPage
>
> the page displays fine.  I tested on Tomcat5.5 and it worked fine.  I tested
> to c:import a different JSP on weblogic and it worked fine too.  Any
> suggestions?

If I remember rightly, c:import works much like jsp:include in that it
looks up the relevant RequestDispatcher (in this case, for the Cocoon
servlet) and does a .include() on it.  There's some added trickery to
allow for the included resource calling getOutputStream when the jsp
containing the tag will have already called getWriter, which would
otherwise throw an IllegalStateException.  The thing that's catching
you out is that the .include() call gets passed the original request &
(wrapper around the) response objects, so if your Cocoon pipeline uses
the wildcard or regex URI matchers the URI they see will be for the
originally requested JSP rather than the path & context mapped to the
Cocoon servlet.  That's why it's failing to match and you get the
404s.

We had the same problem on a project I worked on a few years back -
the Content Management System generated JSPs from its data structures,
and we needed to embed some stuff generated by Cocoon.  The first
workaround we used was to change the CMS's templates to generate
c:import tags along the lines of

and in our root sitemap.xmap change the default matcher to the request
parameter one instead of the URI one.  That way we didn't have to
change any of the map:match entries except where one pipeline called
another via cocoon:/

The second version workaround we used was to create our own version of
the c:import tag.  This passed a request wrapper to the dispatcher's
include method that behaved as if it was a new request for the
included resource, so the various getServletPath/URI/etc. methods
would return the appropriate values for /Cocoon/MyCocoonPage and no
need to mess around with the extra request parameter.

The third version sent all requests through Cocoon, and anything
asking for a JSP matches a pipeline that uses the JSP reader to call
it.  The rest was down to configuring the jsp-engine entries in
cocoon.xconf so that things got dispatched correctly (not initialising
a new copy of the JSP with every call, and not attempting to forward
the request back through the Cocoon servlet again as that led to a
blown stack and/or Out Of Memory errors).  I'm not entirely sure we
had any JSPs doing further jsp:include or c:import calls, though, as
by this stage we were doing most of the page inclusion on the Cocoon
side via the cinclude transformer.

Hope that gives you some ideas to be going on with.


Andy.
-- 
http://pseudoq.sourceforge.net/  Open source java Sudoku application.

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



Auth block

2008-04-29 Thread Andre Juffer

Hi All,

I experience a problem with the Cocoon authentication block, when 
updating from authentication-fw. The following exception is thrown:



..
Caused by: org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 
'org.springframework.beans.factory.config.CustomScopeConfigurer#0' 
defined in URL 
[jar:file:/home/juffer/TriBC/projects/maven/repository/org/apache/cocoon/cocoon-pipeline-impl/1.0.0/cocoon-pipeline-impl-1.0.0.jar!/META-INF/cocoon/spring/PipelineComponentScope.xml]: 
Cannot create inner bean 
'org.apache.cocoon.components.pipeline.spring.PipelineComponentScope#442b7fc2' 
of type 
[org.apache.cocoon.components.pipeline.spring.PipelineComponentScope] 
while setting bean property 'scopes' with key [TypedStringValue: value 
[pipelineComponent], target type [null]]; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating 
bean with name 
'org.apache.cocoon.components.pipeline.spring.PipelineComponentScope#442b7fc2' 
defined in URL 
[jar:file:/home/juffer/TriBC/projects/maven/repository/org/apache/cocoon/cocoon-pipeline-impl/1.0.0/cocoon-pipeline-impl-1.0.0.jar!/META-INF/cocoon/spring/PipelineComponentScope.xml]: 
Initialization of bean failed; nested exception is 
java.lang.IllegalStateException: No Scope registered for scope 'call'



The pom.xml includes the following dependencies for cocoon-auth-api, 
cocoon-pipeline-api, cocoon-pipeline-impl, and cocoon-pipeline-components.


I also have the following in a xml file located in META-INF/cocoon/spring/


http://www.springframework.org/schema/beans";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="http://www.springframework.org/schema/beans 
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd";>


  class="org.apache.cocoon.auth.impl.PipelineSecurityHandler" 
scope="singleton">
value="cocoon:raw:/subscriptions/authenticate"/>
ref="org.apache.excalibur.source.SourceResolver"/>

  
  class="org.apache.cocoon.auth.StandardApplication" scope="singleton">
ref="org.apache.cocoon.auth.SecurityHandler/handler"/>

  



Do I miss something?

Thanks,
--
Andre H. Juffer  | Email: [EMAIL PROTECTED]
The Biocenter and| WWW: www.biochem.oulu.fi/Biocomputing/
the Dep. of Biochemistry | Fax: +358-8-553-1141
University of Oulu, Finland  | Phone: +358-8-553 1161
Triacle Biocomputing | WWW: www.triacle-bc.com

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



Re: Output, more than one file?

2008-04-29 Thread solprovider
On 4/29/08, Carlos Tejo Alonso <[EMAIL PROTECTED]> wrote:
>  Is it possible that a pipe output could be more than one file?
>  Carlos Tejo Alonso

Q. Can Cocoon send information to multiple outputs?
A. Yes, a Transformer can write to multiple Sources before a
Serializer handles the primary response:
http://cocoon.apache.org/2.1/userdocs/sourcewriting-transformer.html

Q. Can the output of one pipeline be used in multiple pipelines?
A. Yes, multiple pipelines can call the same pipeline.  Cache may
prevent the pipeline from being processed multiple times during the
request.

For more assistance, please tell us what your requirements.

solprovider

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



Re: Output, more than one file?

2008-04-29 Thread Antonio Gallardo

Hi Carlos,

Would you explain the use case? Perhaps we can find another way to solve 
it. :)


Best Regards,

Antonio Gallardo.

Carlos Tejo Alonso escribió:

Hello,

Is it possible that a pipe output could be more than one file?

Best regards,

Carlos Tejo Alonso
R&D Deparment - CTIC Foundation [Asturias, Spain]
www.fundacionctic.org


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



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



Output, more than one file?

2008-04-29 Thread Carlos Tejo Alonso
Hello,

Is it possible that a pipe output could be more than one file?

Best regards,

Carlos Tejo Alonso
R&D Deparment - CTIC Foundation [Asturias, Spain]
www.fundacionctic.org


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