[continuum] BUILD ERROR: core-samples-main Block Implementation

[[EMAIL PROTECTED]]

Online report : 
http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/182/buildId/1575
Build statistics:
  State: Error
  Previous State: Ok
  Started at: Fri, 30 Jun 2006 03:27:40 +
  Finished at: Fri, 30 Jun 2006 03:27:43 +
  Total time: 2s
  Build Trigger: Schedule
  Exit code: 0
  Building machine hostname: cocoon.zones.apache.org
  Operating system : SunOS(unknown)
  Java version : 1.4.2_06(Sun Microsystems Inc.)

Changes
  No files changed
  

Build Error:

Provider message: The svn command failed.
Command output: 
---
svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
svn: 
Cannot replace a directory from within
---

Re: XMLDBTransformer blows up Saxon

[Don Grodecki]

1-What said the xml specification about null?
The API being called is the SAX org.xml.sax.ContentHandler.createElement().
>From the Interface definition at 
http://www.saxproject.org/apidoc/index.html:
"Parameters:
uri - the Namespace URI, or the empty string if the element has no Namespace 
URI or if Namespace processing is not being performed
..."

Note that a null value is not specified as one of the options:

2-Which saxon version blows up with null?
Both the versions that I have, which are saxon8 (jar contents dated 
4/7/2005) and saxonB-8.7.3 (the latest), blow out with a 
NullPointerException.

I have used Saxon quite a bit, for XSLT 2.0, and the only calls to Saxon 
with null URIs have been from the XMLDBTransformer.

- Don

- Original Message - 
From: "Antonio Gallardo" <[EMAIL PROTECTED]>
To: 
Sent: Wednesday, June 28, 2006 7:08 PM
Subject: Re: XMLDBTransformer blows up Saxon


Don Grodecki escribió:
> The XMLDBTransformer blows up Saxon, which does not like null URIs. The
> following fix seems to work, replacing null in the first parameter to
> addAttribute with "". - Don
>
> // Report result
> AttributesImpl attrs = new AttributesImpl();
> attrs.addAttribute("", XMLDB_QUERY_OID_ATTRIBUTE,
> XMLDB_QUERY_OID_ATTRIBUTE, "CDATA", this.key);
> attrs.addAttribute("", XMLDB_QUERY_TYPE_ATTRIBUTE,
> XMLDB_QUERY_TYPE_ATTRIBUTE, "CDATA",
> this.operation);
> attrs.addAttribute("", XMLDB_QUERY_RESULT_ATTRIBUTE,
> XMLDB_QUERY_RESULT_ATTRIBUTE, "CDATA", result);
>
>
Hi Don,

Thanks for the patch, would you responds this questions:

1-What said the xml specificationa about null?
2-Wich saxon version blows up with null?

Best Regards,

Antonio Gallardo.

Re: Daisy password and contributing documentation

[Steven Noels]

On 29 Jun 2006, at 18:15, Gavin Carothers wrote:


Is it possible to change ones daisy password?

Going to UserSettings gives me:

You do not have access to this function.

Also, how should one contribute documentation? My impression from the 
list was to use Daisy and not the wiki. However I don't think the 
guest roll has the right to create documents.


http://cocoon.zones.apache.org/daisy/passwordReminder if you forgot 
your password.


I've added you to the doc-editors role. LMK if that doesn't work out.


--
Steven Noelshttp://outerthought.org/
Outerthought  Open Source Java & XML
stevenn at outerthought.orgstevenn at apache.org

Re: svn commit: r417871 - /cocoon/trunk/blocks/cocoon-auth/cocoon-auth-impl/pom.xml

[Jorg Heymans]

Carsten Ziegeler wrote:

> It *should* be passed on transitively, but interestingly in some cases
> it is not! (One of the unpredictable things of maven) While it is passed
> on on my laptop (W2K) it is not on my home computer (WXP) - both using
> the same JDK and the same m2 version (2.0.4). So that's why I had to add
> it to the auth pom.
>
> I'll try this out next week again when I have access to my home computer
> to see if it now works...
>

yep that would be great. I thought you had forgotten to remove it or
something, if it doesn't work for you just add it again.

On a related note, auth-impl has a dependency on cocoon-portal-impl. Is
this temporary? (just curious)


Regards
Jorg

Re: Build error in 2.2

[Jorg Heymans]

Carsten Ziegeler wrote:

>> While building the ajax block in 2.2 I get the following error:
>>
>> [INFO] The plugin 'org.apache.maven.plugins:maven-antrun-plugin' does
>> not exist
>> or no valid version could be found
>>
>> Shouldn't maven automatically download the plugin?
>>
>> Carsten
>>
> I fixed this by adding a version to the plugin info in the ajax impl
> pom. Don't know if that is the correct solution?
> 

My guess is that you hadn't used the maven-antrun-plugin before. Maven
then needs the version number in order to retrieve it. If you have
installed it locally it defaults to the latest version available in the
local repository.

Specifying plugin versions is always good, if nothing else it will
prevent maven from using any other plugin version when the users forces
plugin updates.


Jorg

Daisy password and contributing documentation

[Gavin Carothers]

Is it possible to change ones daisy password?

Going to UserSettings gives me:

You do not have access to this function.

Also, how should one contribute documentation? My impression from the  
list was to use Daisy and not the wiki. However I don't think the  
guest roll has the right to create documents.


Cheers,
Gavin

Re: Making a Block Run in Trunk, or Using Cocoon 2.2 Part II

[Reinhard Poetz]

Gavin Carothers wrote:

Questions and Answers from Part I:

"looking in the docs"

http://cocoon.zones.apache.org/daisy/documentation/g1/1159.html
refers to creating a block, but uses the cocoon-22-archetype-webapp

http://cocoon.zones.apache.org/daisy/documentation/g1/756.html
refers to a very strange archetype that happily no longer seems to exist

http://svn.apache.org/repos/asf/cocoon/whiteboard/example-apps/bricks- 
archetype/

SEEMS to be based on the "webapp" archetype.

http://cocoon.zones.apache.org/daisy/documentation/863/g1/796.html
refers to creating a block, and as it's under the block deployer this  
makes sense. The reason I ended up using the block archetype rather  
then webapp was simply that it seemed to be working.



Gavin,

correcting the docs is on the top of my todo list and I should find some time 
this evening/tommorrow to make all the referred docs consistent.


--
Reinhard Pötz   Independent Consultant, Trainer & (IT)-Coach 


{Software Engineering, Open Source, Web Applications, Apache Cocoon}

   web(log): http://www.poetz.cc






___ 
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

Making a Block Run in Trunk, or Using Cocoon 2.2 Part II

[Gavin Carothers]

Questions and Answers from Part I:

"looking in the docs"

http://cocoon.zones.apache.org/daisy/documentation/g1/1159.html
refers to creating a block, but uses the cocoon-22-archetype-webapp

http://cocoon.zones.apache.org/daisy/documentation/g1/756.html
refers to a very strange archetype that happily no longer seems to exist

http://svn.apache.org/repos/asf/cocoon/whiteboard/example-apps/bricks- 
archetype/

SEEMS to be based on the "webapp" archetype.

http://cocoon.zones.apache.org/daisy/documentation/863/g1/796.html
refers to creating a block, and as it's under the block deployer this  
makes sense. The reason I ended up using the block archetype rather  
then webapp was simply that it seemed to be working.



Thursday, June 29th:

Based on messages from the mailing list, this morning begin with:

svn up
mvn install

Oops, org.apache.cocoon.template.jxtg.JXTemplateGeneratorTestCase and  
org.apache.cocoon.environment.FOMTestCase still fail.


mvn install -Dmaven.test.skip=true

Starting back were we ended yesterday. We have the archetype block  
created and want to see if the pipeline it deploys works.


mvn cocoon:deploy
mvn jetty6:run

Opening up Firefox and trying http://localhost:/toc-manager/ No  
luck.


No default type exists for 'map:pipeline' at file:/Users/gcarothers/ 
Documents/Programing/toc-manager/target/toc-manager/sitemap.xmap:26:19


Okay, so some part of the configuration is likely screwed up. Lets go  
back to February when I last remember seeing this issue mentioned on  
the mailing list.


Ben Popes comment on adding dependencies causing the error gives us  
the best chance for fixing this quickly.

http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=114082894919896&w=2

removing

  org.apache.cocoon
  cocoon-template-impl
  1.0.0-SNAPSHOT

from the pom.xml, finding no blocks.xml or other place where  
dependencies are referenced in COB-INF we will try cleaning and  
deploying again.


mvn clean cocoon:deploy
mvn jetty6:run

Opening up Firefox and trying http://localhost:/toc-manager/ No  
luck.


No default type exists for 'map:pipeline' at file:/Users/gcarothers/ 
Documents/Programing/toc-manager/target/toc-manager/sitemap.xmap:23:19


There is another  file in cocoon-core-applicationContext.xml  
lets see what removing it's license header does.


Nope.

Okay, lets look into the issues from February a bit more deeply.  
Well, http://marc.theaimsgroup.com/?l=xml-cocoon- 
dev&m=114089107113280&w=2 seems to mean that this got solved for  
cocoon-webapp, that's good. So lets take a look at that application  
since it works.


First thing we notice is this application has a META-INF directory  
which upon first inspection mentions spring, closer examination  
revels that this is used by OSGi and not the normal cocoon-block- 
deployer, so we can move on from here.


There seems to be a lot of stuff in here for the samples, being a  
demo application. We don't really want to deal with getting the  
samples to work at the moment we want to know why this webapp works  
and toc-manager doesn't. So going to remove the dependencies on the  
sample blocks. Simplify what we're building, and hope it still works.  
Upon removing those we find one other dependency left:



  org.apache.cocoon
  cocoon-deployer-plugin-demo
  1.0.0-SNAPSHOT


mvn clean cocoon:deploy jetty6:run

Well now, we have a running application without all the samples, in  
fact without much of anything. Excellent, lets see what's going on in  
the target/cocoon-webapp/ directory and compare that to our target/ 
toc-manager. Well, there we go. toc-manager's target webapp does not  
have a cocoon-core-sitemap.xmap, so no pipelines nor any of the other  
main components are every configured. In fact our block has no WEB- 
INF at all... hrm. Now clearly some of the items from COB-INF end up - 
in- the deployed WEB-INF but as I don't yet understand how that  
process works nor have I found documentation on it we are going to  
cheat. As this comes from the src/ directory and not from any  
dependency we will simply copy over the whole of WEB-INF into the  
src/ tree of toc-manager and see what happens.


cd toc-manager
mvn -o clean cocoon:deploy jetty6:run

Heh, as one might guess this did nothing. In fact none of the  
contents of WEB-INF was copied into target at all. Manually coping  
the cocoon-core-sitemap.xmap into target/ causes everything to work!  
We are running code!


minimac:~ gcarothers$ curl http://localhost:/toc-manager/


  com.amesondemand.bookbuild:toc-manager
  This is a message coming from a Spring bean.


So, now how do we get cocoon-core-sitemap.xmap into our block? We  
could keep copying it by hand, but that's not much fun. We could add  
it to our block and then to the block archetype as well, or we can  
add it too cocoon-core. I've taken that last of these options locally.


cocoon-2.2-dev/core/cocoon-core/src/main/resources/META-INF/legacy/ 
sitemap-additions/cocoon-core-sitemap.xmap has bee

Re: XMLDBTransformer blows up Saxon

[Antonio Gallardo]

Don Grodecki escribió:
The XMLDBTransformer blows up Saxon, which does not like null URIs. The 
following fix seems to work, replacing null in the first parameter to 
addAttribute with "". - Don


// Report result
AttributesImpl attrs = new AttributesImpl();
attrs.addAttribute("", XMLDB_QUERY_OID_ATTRIBUTE,
XMLDB_QUERY_OID_ATTRIBUTE, "CDATA", this.key);
attrs.addAttribute("", XMLDB_QUERY_TYPE_ATTRIBUTE,
XMLDB_QUERY_TYPE_ATTRIBUTE, "CDATA", 
this.operation);

attrs.addAttribute("", XMLDB_QUERY_RESULT_ATTRIBUTE,
XMLDB_QUERY_RESULT_ATTRIBUTE, "CDATA", result); 

  

Hi Don,

Thanks for the patch, would you responds this questions:

1-What said the xml specificationa about null?
2-Wich saxon version blows up with null?

Best Regards,

Antonio Gallardo.

Patch for PDE support submitted to JIRA

[Reinhard Pötz]

Hi Fabrizio,

I've just submitted a patch (http://jira.codehaus.org/browse/MECLIPSE-92) that 
adds PDE support to the Eclipse plugin. It would be really great for the Cocoon 
community if it got applied very soon  ;-)


If you have any questions or concerns, don't hesitate to raise them.

Best regards,
Reinhard

[jira] Commented: (COCOON-1874) Bricks example app archetype

[Bertrand Delacretaz (JIRA)]

[ 
http://issues.apache.org/jira/browse/COCOON-1874?page=comments#action_12418472 
] 

Bertrand Delacretaz commented on COCOON-1874:
-

At revision 418046, moving from a Cocoon application to a 2.2 block

> Bricks example app archetype
> 
>
>  Key: COCOON-1874
>  URL: http://issues.apache.org/jira/browse/COCOON-1874
>  Project: Cocoon
> Type: New Feature

>   Components: - Samples
> Versions: 2.2-dev (Current SVN)
> Reporter: Bertrand Delacretaz

>
> Create a Maven archetype for a simple example app, using CForms to edit data 
> in an embedded database (an improved port of the Bricks example, see 
> http://wiki.apache.org/cocoon/BricksCms).
> See also http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=115141627713015&w=2

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

DO NOT REPLY [Bug 36810] - source that declares namespace fails JXPath/Linkrewriter/Input Modules

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36810


Bug 36810 depends on bug 32360, which changed state.

Bug 32360 Summary: [jxpath] Default Namespace not handled correctly
http://issues.apache.org/bugzilla/show_bug.cgi?id=32360

   What|Old Value   |New Value

 Status|REOPENED|RESOLVED
 Resolution||INVALID



-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

[jira] Closed: (COCOON-1730) [Link] Computer Science Department 2 - University of Erlangen-Nuremberg

[Helma van der Linden (JIRA)]

 [ http://issues.apache.org/jira/browse/COCOON-1730?page=all ]
 
Helma van der Linden closed COCOON-1730:


Resolution: Fixed

Information is added to the Live Sites pages.

> [Link] Computer Science Department 2 - University of Erlangen-Nuremberg
> ---
>
>  Key: COCOON-1730
>  URL: http://issues.apache.org/jira/browse/COCOON-1730
>  Project: Cocoon
> Type: Wish

>   Components: - Documentation
> Versions: 2.1.8
> Reporter: Thorsten Meinl
> Assignee: Helma van der Linden

>
> URL of the website: http://www2.informatik.uni-erlangen.de/
> Title of the website: Computer Science Department 2
> Cocoon version used: 2.1.8
> Short summary: Webpages of the programming systems group at the 
> Friedrich-Alexander University Erlangen-Nuremberg
> How can we verify this site is actually built with Cocoon? 
> http://www2.informatik.uni-erlangen.de/cocoon-status.xml
> - How much time did it take to build the site from design to publication?
> 2 months
> - How much traffic does the site handle?
>  ~300MB/day, ~15,000 hits/day
> - What made you choose Cocoon to build the site?
> Our university-wide information system (UnivIS, 
> http://univis.uni-erlangen.de/) offers an XML export of all data (lecture, 
> publications, person, projects, ...) To avoid maintaining the data at 
> multiple places we import these data and use Cocoon to produce our webpages 
> more or less automatically
> - What other information do you want to disclose (e.g. how does it work, how 
> didyou build it, what parts of Cocoon did you use)?
> Most importantly, we use eXist as XML database to store the imported data and 
> use the XMLDBTransformer to include it into the pipeline.
> - Can you provide a contact email address if people want further information?
> [EMAIL PROTECTED]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Assigned: (COCOON-1730) [Link] Computer Science Department 2 - University of Erlangen-Nuremberg

[Helma van der Linden (JIRA)]

 [ http://issues.apache.org/jira/browse/COCOON-1730?page=all ]

Helma van der Linden reassigned COCOON-1730:


Assign To: Helma van der Linden

> [Link] Computer Science Department 2 - University of Erlangen-Nuremberg
> ---
>
>  Key: COCOON-1730
>  URL: http://issues.apache.org/jira/browse/COCOON-1730
>  Project: Cocoon
> Type: Wish

>   Components: - Documentation
> Versions: 2.1.8
> Reporter: Thorsten Meinl
> Assignee: Helma van der Linden

>
> URL of the website: http://www2.informatik.uni-erlangen.de/
> Title of the website: Computer Science Department 2
> Cocoon version used: 2.1.8
> Short summary: Webpages of the programming systems group at the 
> Friedrich-Alexander University Erlangen-Nuremberg
> How can we verify this site is actually built with Cocoon? 
> http://www2.informatik.uni-erlangen.de/cocoon-status.xml
> - How much time did it take to build the site from design to publication?
> 2 months
> - How much traffic does the site handle?
>  ~300MB/day, ~15,000 hits/day
> - What made you choose Cocoon to build the site?
> Our university-wide information system (UnivIS, 
> http://univis.uni-erlangen.de/) offers an XML export of all data (lecture, 
> publications, person, projects, ...) To avoid maintaining the data at 
> multiple places we import these data and use Cocoon to produce our webpages 
> more or less automatically
> - What other information do you want to disclose (e.g. how does it work, how 
> didyou build it, what parts of Cocoon did you use)?
> Most importantly, we use eXist as XML database to store the imported data and 
> use the XMLDBTransformer to include it into the pipeline.
> - Can you provide a contact email address if people want further information?
> [EMAIL PROTECTED]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Closed: (COCOON-1856) [Link] www.pyxx.org

[Helma van der Linden (JIRA)]

 [ http://issues.apache.org/jira/browse/COCOON-1856?page=all ]
 
Helma van der Linden closed COCOON-1856:


Resolution: Fixed

The information is added to Live Sites.

> [Link] www.pyxx.org
> ---
>
>  Key: COCOON-1856
>  URL: http://issues.apache.org/jira/browse/COCOON-1856
>  Project: Cocoon
> Type: Improvement

>   Components: - Documentation
> Versions: 2.1.8
> Reporter: Sasha Philippov
> Assignee: Helma van der Linden
> Priority: Minor

>
> "Pyxx.org" - live site on XML-related authoring and publishing for web and 
> on-line learning.
> URL: http://www.pyxx.org
> Cocoon version used: 2.1.8 
> It took five days for one programmer to develop and set up the site.
> You can see the description of the hosting solution (Apache, Tomcat, Cocoon) 
> here: http://www.pyxx.org/cocoon/vhosting/howto.html
> The site full sources are available for download here: 
> http://www.pyxx.org/cocoon/thesite/sitemap.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Assigned: (COCOON-1856) [Link] www.pyxx.org

[Helma van der Linden (JIRA)]

 [ http://issues.apache.org/jira/browse/COCOON-1856?page=all ]

Helma van der Linden reassigned COCOON-1856:


Assign To: Helma van der Linden

> [Link] www.pyxx.org
> ---
>
>  Key: COCOON-1856
>  URL: http://issues.apache.org/jira/browse/COCOON-1856
>  Project: Cocoon
> Type: Improvement

>   Components: - Documentation
> Versions: 2.1.8
> Reporter: Sasha Philippov
> Assignee: Helma van der Linden
> Priority: Minor

>
> "Pyxx.org" - live site on XML-related authoring and publishing for web and 
> on-line learning.
> URL: http://www.pyxx.org
> Cocoon version used: 2.1.8 
> It took five days for one programmer to develop and set up the site.
> You can see the description of the hosting solution (Apache, Tomcat, Cocoon) 
> here: http://www.pyxx.org/cocoon/vhosting/howto.html
> The site full sources are available for download here: 
> http://www.pyxx.org/cocoon/thesite/sitemap.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Closed: (COCOON-1659) Finish the sitemap internals document in Daisy

[Helma van der Linden (JIRA)]

 [ http://issues.apache.org/jira/browse/COCOON-1659?page=all ]
 
Helma van der Linden closed COCOON-1659:


Resolution: Fixed

No feedback in 4 months so I assume that the text is ok.

> Finish the sitemap internals document in Daisy
> --
>
>  Key: COCOON-1659
>  URL: http://issues.apache.org/jira/browse/COCOON-1659
>  Project: Cocoon
> Type: Task

>   Components: - Documentation
> Versions: 2.2-dev (Current SVN)
> Reporter: Helma van der Linden
> Assignee: Helma van der Linden
> Priority: Minor
>  Attachments: svgs-of-article.zip
>
> Text and images of the description of the sitemap processing should be 
> enhanced and reviewed.
> http://cocoon.zones.apache.org/daisy/documentation/732.html
> - integrate related wiki pages:
> http://wiki.apache.org/cocoon/InterpretedSitemapInternals
> http://wiki.apache.org/cocoon/GT2005HackatonDay1Notes
> - Review of the content by sitemap experts (Sylvain?)
> - Create better images (see also pages on wiki page)
> - add links to appropriate classes into apidocs

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Closed: (COCOON-1660) [Link] Warsztat

[Helma van der Linden (JIRA)]

 [ http://issues.apache.org/jira/browse/COCOON-1660?page=all ]
 
Helma van der Linden closed COCOON-1660:


Resolution: Fixed

Added to the list of Live Sites built with Cocoon 2.1.7

> [Link] Warsztat
> ---
>
>  Key: COCOON-1660
>  URL: http://issues.apache.org/jira/browse/COCOON-1660
>  Project: Cocoon
> Type: Improvement

>   Components: - Documentation
> Versions: 2.1.7
> Reporter: Grzegorz Kossakowski (aka g[R]eK)
> Assignee: Helma van der Linden
> Priority: Minor

>
> URL of the website: http://www.gamedev.pl
> Title of the website: Warsztat
> Cocoon version used: 2.1.7
> Short summary: Polish site in early stage of development that aims at keeping 
> polish game programming community together and provide some useful resources.
> How can we verify this site is actually built with Cocoon?
> Check HTTP headers.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Assigned: (COCOON-1660) [Link] Warsztat

[Helma van der Linden (JIRA)]

 [ http://issues.apache.org/jira/browse/COCOON-1660?page=all ]

Helma van der Linden reassigned COCOON-1660:


Assign To: Helma van der Linden  (was: Cocoon Developers Team)

> [Link] Warsztat
> ---
>
>  Key: COCOON-1660
>  URL: http://issues.apache.org/jira/browse/COCOON-1660
>  Project: Cocoon
> Type: Improvement

>   Components: - Documentation
> Versions: 2.1.7
> Reporter: Grzegorz Kossakowski (aka g[R]eK)
> Assignee: Helma van der Linden
> Priority: Minor

>
> URL of the website: http://www.gamedev.pl
> Title of the website: Warsztat
> Cocoon version used: 2.1.7
> Short summary: Polish site in early stage of development that aims at keeping 
> polish game programming community together and provide some useful resources.
> How can we verify this site is actually built with Cocoon?
> Check HTTP headers.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Closed: (COCOON-1850) [Link] Dutch Ministry of Finance - www.minfin.nl

[Helma van der Linden (JIRA)]

 [ http://issues.apache.org/jira/browse/COCOON-1850?page=all ]
 
Helma van der Linden closed COCOON-1850:


Resolution: Fixed

I am closing this issue. If Arje would like to add additional information to 
the Daisy entry, he can do so on his own.

> [Link] Dutch Ministry of Finance - www.minfin.nl
> 
>
>  Key: COCOON-1850
>  URL: http://issues.apache.org/jira/browse/COCOON-1850
>  Project: Cocoon
> Type: Task

>   Components: - Documentation
> Versions: 2.1.8
> Reporter: Arjé Cahn
> Assignee: Helma van der Linden
> Priority: Trivial

>
> URL of the website: www.minfin.nl
> Title of the website: Dutch Ministry of Finance
> Cocoon version used: 2.1.8
> Short summary: The main website of the Dutch Ministry of Finance 
> (www.minfin.nl). Built entirely in Cocoon 2.1.8 and launched in April, 2006. 
> Total development time took around 4 months.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Assigned: (COCOON-1713) [LINK] www.mw-import.de

[Helma van der Linden (JIRA)]

 [ http://issues.apache.org/jira/browse/COCOON-1713?page=all ]

Helma van der Linden reassigned COCOON-1713:


Assign To: Helma van der Linden

> [LINK] www.mw-import.de
> ---
>
>  Key: COCOON-1713
>  URL: http://issues.apache.org/jira/browse/COCOON-1713
>  Project: Cocoon
> Type: Task

>   Components: - Documentation
> Reporter: Jianyu Wang
> Assignee: Helma van der Linden
> Priority: Trivial

>
> -URL of the website: 
> http://www.mw-import.de
> -Title of the website: 
> MW-Import Werkzeuge.
> -Cocoon version used:  
> 2.1.7
> - Short summary of your site:
>  A German Web shop selling measurement tools imported from Asia.
> - How can we verify this site is actually built with Cocoon?: 
> view response header.
> How much time did it take to build the site from design to publication?
> 6 month 
> - How many people were involved in the project?
> one Java Developer and one Designer
> -How much traffic does the site handle?
> 100 User a day / 1500 Pages
> -What made you choose Cocoon to build the site?
> The main reason to that cocoon let us follow the MVC pattern and  separate 
> concerns. The Web designer was able to develop the style sheet totally 
> independent of the application logic. All business logic could be 
> encapsulated in services and tested with Junit outside the web container. At 
> least the flow provide as facility to bind the web application together. As a 
> bonus we easily can create Order documents in pdf.
> Beside the fact that cocoon is cool framework one of our partners used cocoon 
> in former project.
> -What other information do you want to disclose-  
> Main Parts used: Cocoon Form, Flow with Continuation, and FOP 
> -   Can you provide a contact email address if people want further 
> information? 
> I'm happy to share cocoon experience:  [EMAIL PROTECTED]
> I hope i commited this task correctly bcause is the first time i use jira. 
> Jianyu

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Closed: (COCOON-1713) [LINK] www.mw-import.de

[Helma van der Linden (JIRA)]

 [ http://issues.apache.org/jira/browse/COCOON-1713?page=all ]
 
Helma van der Linden closed COCOON-1713:


Resolution: Fixed

> [LINK] www.mw-import.de
> ---
>
>  Key: COCOON-1713
>  URL: http://issues.apache.org/jira/browse/COCOON-1713
>  Project: Cocoon
> Type: Task

>   Components: - Documentation
> Reporter: Jianyu Wang
> Priority: Trivial

>
> -URL of the website: 
> http://www.mw-import.de
> -Title of the website: 
> MW-Import Werkzeuge.
> -Cocoon version used:  
> 2.1.7
> - Short summary of your site:
>  A German Web shop selling measurement tools imported from Asia.
> - How can we verify this site is actually built with Cocoon?: 
> view response header.
> How much time did it take to build the site from design to publication?
> 6 month 
> - How many people were involved in the project?
> one Java Developer and one Designer
> -How much traffic does the site handle?
> 100 User a day / 1500 Pages
> -What made you choose Cocoon to build the site?
> The main reason to that cocoon let us follow the MVC pattern and  separate 
> concerns. The Web designer was able to develop the style sheet totally 
> independent of the application logic. All business logic could be 
> encapsulated in services and tested with Junit outside the web container. At 
> least the flow provide as facility to bind the web application together. As a 
> bonus we easily can create Order documents in pdf.
> Beside the fact that cocoon is cool framework one of our partners used cocoon 
> in former project.
> -What other information do you want to disclose-  
> Main Parts used: Cocoon Form, Flow with Continuation, and FOP 
> -   Can you provide a contact email address if people want further 
> information? 
> I'm happy to share cocoon experience:  [EMAIL PROTECTED]
> I hope i commited this task correctly bcause is the first time i use jira. 
> Jianyu

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Commented: (COCOON-1713) [LINK] www.mw-import.de

[Helma van der Linden (JIRA)]

[ 
http://issues.apache.org/jira/browse/COCOON-1713?page=comments#action_12418429 
] 

Helma van der Linden commented on COCOON-1713:
--

The information is added to the Live Sites and will be displayed on the main 
documentation site after the next doc updates.

> [LINK] www.mw-import.de
> ---
>
>  Key: COCOON-1713
>  URL: http://issues.apache.org/jira/browse/COCOON-1713
>  Project: Cocoon
> Type: Task

>   Components: - Documentation
> Reporter: Jianyu Wang
> Priority: Trivial

>
> -URL of the website: 
> http://www.mw-import.de
> -Title of the website: 
> MW-Import Werkzeuge.
> -Cocoon version used:  
> 2.1.7
> - Short summary of your site:
>  A German Web shop selling measurement tools imported from Asia.
> - How can we verify this site is actually built with Cocoon?: 
> view response header.
> How much time did it take to build the site from design to publication?
> 6 month 
> - How many people were involved in the project?
> one Java Developer and one Designer
> -How much traffic does the site handle?
> 100 User a day / 1500 Pages
> -What made you choose Cocoon to build the site?
> The main reason to that cocoon let us follow the MVC pattern and  separate 
> concerns. The Web designer was able to develop the style sheet totally 
> independent of the application logic. All business logic could be 
> encapsulated in services and tested with Junit outside the web container. At 
> least the flow provide as facility to bind the web application together. As a 
> bonus we easily can create Order documents in pdf.
> Beside the fact that cocoon is cool framework one of our partners used cocoon 
> in former project.
> -What other information do you want to disclose-  
> Main Parts used: Cocoon Form, Flow with Continuation, and FOP 
> -   Can you provide a contact email address if people want further 
> information? 
> I'm happy to share cocoon experience:  [EMAIL PROTECTED]
> I hope i commited this task correctly bcause is the first time i use jira. 
> Jianyu

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Re: Build error in 2.2

[Carsten Ziegeler]

Carsten Ziegeler wrote:
> While building the ajax block in 2.2 I get the following error:
> 
> [INFO] The plugin 'org.apache.maven.plugins:maven-antrun-plugin' does
> not exist
> or no valid version could be found
> 
> Shouldn't maven automatically download the plugin?
> 
> Carsten
> 
I fixed this by adding a version to the plugin info in the ajax impl
pom. Don't know if that is the correct solution?

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/

Re: Creating a Block in Trunk, or Using Cocoon 2.2 Part I

[Andrew Savory]

Hi Gavin,

Gavin Carothers wrote:


Shall I keep up the blow by blow over the next few days or not?


This is excellent! Please do keep it up.


result of quick non exhaustive test:
AJAX samples don't work so good


Maurizio fixed this yesterday and Simone committed it, the samples 
should now work properly.



Thanks,

Andrew.
--
Andrew Savory, Managing Director, Luminas Limited
Tel: +44 (0)870 741 6658  Fax: +44 (0)700 598 1135
Web: http://www.luminas.co.uk/
Orixo alliance: http://www.orixo.com/

Build error in 2.2

[Carsten Ziegeler]

While building the ajax block in 2.2 I get the following error:

[INFO] The plugin 'org.apache.maven.plugins:maven-antrun-plugin' does
not exist
or no valid version could be found

Shouldn't maven automatically download the plugin?

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/

[jira] Closed: (COCOON-1872) ajax not working in 2.2

[Andrew Savory (JIRA)]

 [ http://issues.apache.org/jira/browse/COCOON-1872?page=all ]
 
Andrew Savory closed COCOON-1872:
-

Resolution: Fixed

Patch committed by Simone. Thanks, Maurizio!

> ajax not working in 2.2
> ---
>
>  Key: COCOON-1872
>  URL: http://issues.apache.org/jira/browse/COCOON-1872
>  Project: Cocoon
> Type: Bug

>   Components: Blocks: Ajax
> Versions: 2.2-dev (Current SVN)
> Reporter: Simone Gianni
> Assignee: Simone Gianni
> Priority: Critical
>  Attachments: build.xml, cocoon-ajax-impl-pom.diff
>
> In current 2.2 the Dojo stuff is not there. This is because (Sylvain told me) 
> the dojo.js we are using is a reduced version of dojo, and in 2.1 there is an 
> ant build file that takes only the parts we need from the complete unzipped 
> dojo stuff and builds a custom .jar file for it.
> The problem is how to incorporate this in Maven for 2.2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Re: Creating a Block in Trunk, or Using Cocoon 2.2 Part I

[Carsten Ziegeler]

Bertrand Delacretaz wrote:
> On 6/28/06, Gavin Carothers <[EMAIL PROTECTED]> wrote:
> 
>> ...At the end of this process I hope to come up with
>> something a bit more organized as well
> 
> Thanks for sharing your experiences!
> 
> Note that we have started a similar effort in the whiteboard, an
> improved port of the Bricks example, currently at
> http://svn.apache.org/repos/asf/cocoon/whiteboard/example-apps/bricks-archetype/
> 
> Once this works, the idea is to convert it to a Maven archetype so
> that people can quickly see how to build apps on 2.2.
> 
> I have just created http://issues.apache.org/jira/browse/COCOON-1874
> to follow this.
> 
> Anyone willing to join in is welcome, of course!
> 
> And alternate "getting to grips with 2.2" stories are welcome of course.
> 
I started to document some of the new features in Daisy. There is a new
document about configuration and so on. These docs do not cover
everything yet, but it's a good starting point.

I think we should do some marketing when we do a release next week -
those of us who where yesterday at Sally's session will know what I mean :)

Carsten
-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/

[jira] Commented: (COCOON-1713) [LINK] www.mw-import.de

[Jianyu Wang (JIRA)]

[ 
http://issues.apache.org/jira/browse/COCOON-1713?page=comments#action_12418420 
] 

Jianyu Wang commented on COCOON-1713:
-

Thx for the notifcation. Now the site is avaible again. The site should be 
always online of coruse 

> [LINK] www.mw-import.de
> ---
>
>  Key: COCOON-1713
>  URL: http://issues.apache.org/jira/browse/COCOON-1713
>  Project: Cocoon
> Type: Task

>   Components: - Documentation
> Reporter: Jianyu Wang
> Priority: Trivial

>
> -URL of the website: 
> http://www.mw-import.de
> -Title of the website: 
> MW-Import Werkzeuge.
> -Cocoon version used:  
> 2.1.7
> - Short summary of your site:
>  A German Web shop selling measurement tools imported from Asia.
> - How can we verify this site is actually built with Cocoon?: 
> view response header.
> How much time did it take to build the site from design to publication?
> 6 month 
> - How many people were involved in the project?
> one Java Developer and one Designer
> -How much traffic does the site handle?
> 100 User a day / 1500 Pages
> -What made you choose Cocoon to build the site?
> The main reason to that cocoon let us follow the MVC pattern and  separate 
> concerns. The Web designer was able to develop the style sheet totally 
> independent of the application logic. All business logic could be 
> encapsulated in services and tested with Junit outside the web container. At 
> least the flow provide as facility to bind the web application together. As a 
> bonus we easily can create Order documents in pdf.
> Beside the fact that cocoon is cool framework one of our partners used cocoon 
> in former project.
> -What other information do you want to disclose-  
> Main Parts used: Cocoon Form, Flow with Continuation, and FOP 
> -   Can you provide a contact email address if people want further 
> information? 
> I'm happy to share cocoon experience:  [EMAIL PROTECTED]
> I hope i commited this task correctly bcause is the first time i use jira. 
> Jianyu

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Commented: (COCOON-1874) Bricks example app archetype

[Bertrand Delacretaz (JIRA)]

[ 
http://issues.apache.org/jira/browse/COCOON-1874?page=comments#action_12418414 
] 

Bertrand Delacretaz commented on COCOON-1874:
-

The current status of the example is at 
http://svn.apache.org/repos/asf/cocoon/whiteboard/example-apps/bricks-archetype/STATUS.txt
 - the idea is to first get the app working, and then to turn it into a Maven 
archetype.

> Bricks example app archetype
> 
>
>  Key: COCOON-1874
>  URL: http://issues.apache.org/jira/browse/COCOON-1874
>  Project: Cocoon
> Type: New Feature

>   Components: - Samples
> Versions: 2.2-dev (Current SVN)
> Reporter: Bertrand Delacretaz

>
> Create a Maven archetype for a simple example app, using CForms to edit data 
> in an embedded database (an improved port of the Bricks example, see 
> http://wiki.apache.org/cocoon/BricksCms).
> See also http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=115141627713015&w=2

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Re: Creating a Block in Trunk, or Using Cocoon 2.2 Part I

[Bertrand Delacretaz]

On 6/28/06, Gavin Carothers <[EMAIL PROTECTED]> wrote:


...At the end of this process I hope to come up with
something a bit more organized as well


Thanks for sharing your experiences!

Note that we have started a similar effort in the whiteboard, an
improved port of the Bricks example, currently at
http://svn.apache.org/repos/asf/cocoon/whiteboard/example-apps/bricks-archetype/

Once this works, the idea is to convert it to a Maven archetype so
that people can quickly see how to build apps on 2.2.

I have just created http://issues.apache.org/jira/browse/COCOON-1874
to follow this.

Anyone willing to join in is welcome, of course!

And alternate "getting to grips with 2.2" stories are welcome of course.

-Bertrand

[jira] Created: (COCOON-1874) Bricks example app archetype

[Bertrand Delacretaz (JIRA)]

Bricks example app archetype


 Key: COCOON-1874
 URL: http://issues.apache.org/jira/browse/COCOON-1874
 Project: Cocoon
Type: New Feature

  Components: - Samples  
Versions: 2.2-dev (Current SVN)
Reporter: Bertrand Delacretaz


Create a Maven archetype for a simple example app, using CForms to edit data in 
an embedded database (an improved port of the Bricks example, see 
http://wiki.apache.org/cocoon/BricksCms).

See also http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=115141627713015&w=2

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Re: svn commit: r417871 - /cocoon/trunk/blocks/cocoon-auth/cocoon-auth-impl/pom.xml

[Carsten Ziegeler]

[EMAIL PROTECTED] schrieb:
> Author: jheymans
> Date: Wed Jun 28 13:54:51 2006
> New Revision: 417871
> 
> URL: http://svn.apache.org/viewvc?rev=417871&view=rev
> Log:
> servlet api is passed on transitively from core
> 
It *should* be passed on transitively, but interestingly in some cases
it is not! (One of the unpredictable things of maven) While it is passed
on on my laptop (W2K) it is not on my home computer (WXP) - both using
the same JDK and the same m2 version (2.0.4). So that's why I had to add
it to the auth pom.

I'll try this out next week again when I have access to my home computer
to see if it now works...

Carsten
-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/

Re: Creating a Block in Trunk, or Using Cocoon 2.2 Part I

[hepabolu]

Gavin Carothers said the following on 28/6/06 23:18:

To the Community:

Shall I keep up the blow by blow over the next few days or not? It seems 
to be me that people have been questioning if they can adopt 2.2 for use 
in their applications or not. Personally I just want to try and see what 
happens and I thought others might want to see what it's like. At the 
end of this process I hope to come up with something a bit more 
organized as well.


Hi Gavin,

this is great stuff. Thanks for the effort, I'm looking forward to the 
next posts.


I'd like to put this somewhere more in focus, daisy docs e.g. It 
provides an excellent stepwise intro for 2.2 beginners.


If you agree, I could put your "installments" in Daisy, but it would be 
nice if you could do a bit more explicit referencing. Examples:

- "looking in the docs", please add a link
- "docs are somewhat outdated", I know 2.2 is moving target, but if you 
could point more specifically to the outdated parts, they can be fixed 
or marked with a warning.


Bye, Helma

[jira] Commented: (COCOON-1713) [LINK] www.mw-import.de

[Helma van der Linden (JIRA)]

[ 
http://issues.apache.org/jira/browse/COCOON-1713?page=comments#action_12418400 
] 

Helma van der Linden commented on COCOON-1713:
--

The url times out with a proxy error. I'll check later. If it stays 
unavailable, I'll close this issue.
The author can reopen it, if necessary.

> [LINK] www.mw-import.de
> ---
>
>  Key: COCOON-1713
>  URL: http://issues.apache.org/jira/browse/COCOON-1713
>  Project: Cocoon
> Type: Task

>   Components: - Documentation
> Reporter: Jianyu Wang
> Priority: Trivial

>
> -URL of the website: 
> http://www.mw-import.de
> -Title of the website: 
> MW-Import Werkzeuge.
> -Cocoon version used:  
> 2.1.7
> - Short summary of your site:
>  A German Web shop selling measurement tools imported from Asia.
> - How can we verify this site is actually built with Cocoon?: 
> view response header.
> How much time did it take to build the site from design to publication?
> 6 month 
> - How many people were involved in the project?
> one Java Developer and one Designer
> -How much traffic does the site handle?
> 100 User a day / 1500 Pages
> -What made you choose Cocoon to build the site?
> The main reason to that cocoon let us follow the MVC pattern and  separate 
> concerns. The Web designer was able to develop the style sheet totally 
> independent of the application logic. All business logic could be 
> encapsulated in services and tested with Junit outside the web container. At 
> least the flow provide as facility to bind the web application together. As a 
> bonus we easily can create Order documents in pdf.
> Beside the fact that cocoon is cool framework one of our partners used cocoon 
> in former project.
> -What other information do you want to disclose-  
> Main Parts used: Cocoon Form, Flow with Continuation, and FOP 
> -   Can you provide a contact email address if people want further 
> information? 
> I'm happy to share cocoon experience:  [EMAIL PROTECTED]
> I hope i commited this task correctly bcause is the first time i use jira. 
> Jianyu

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira