Samples as tools for learning and development (Was: Giving up!Cocoon too big, slow and confusing)
Argyn Kuketayev wrote: I don't think that Cocoon is complex. I blame the very poor documentation. When you know how it works, it's simple. So, you have to get very familiar with the source codes to use Cocoon. I don't like it. I'd rather look under the hood only when I have non-trivial problems. Unfortunately, with Cocoon you have to do it all the time. E.g., Cocoon's samples are just to say hey, we have samples!. Not so. They are there as a learning tool for you. Yet they more than that. They provide the basis for you to create your own applications (copy-and-extend). Please read the following snippet from http://xml.apache.org/cocoon/overview.html#samples It will greatly assist your understanding of Cocoon to investigate behind-the-scenes, to find out how each sample is processed. Do this by looking at the actual XML documents provided in the distribution at webapp/docs/samples/ and by consulting the sitemap to see the processing steps that are defined. Please contribute other new samples as you see fit. I am interested to know how you propose to build a reliable finely-tuned publishing system using Cocoon without looking under the hood. I did not realise that we had reached that stage of automation yet. We certainly are aiming for that. In HEAD branch, the Samples are being re-organised into a set of clean, reliable, informative, individually-packaged samples. This makes it easy to use them as template apps. Eventually, high-level tools can utilise them. I hear that sitemap editing tools are starting to emerge too. For the moment you must look under the hood. Anyway, i find that getting my hands dirty is the best way to learn. Please follow the samples that others have tried to provide. You say that you need to get familiar with the source code in order to understand. Well, i do not touch any java code. I just copy and tweak the samples' xml/xsl files and sitemaps. --David - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Elephants and Mavericks (Re: Giving up! Cocoon too big, slow and confusing)
Thanks for the honest words, instead of silence. I am reminded of the following definition: second-system effect n. When one is designing the successor to a relatively small, elegant, and successful system, there is a tendency to become grandiose in one's success and design an elephantine feature-laden monstrosity. The term was first used by Fred Brooks in his classic The Mythical Man-Month: Essays on Software Engineering. It described the jump from a set of nice, simple operating systems on the IBM 70xx series to OS/360 on the 360 series. A similar effect can also happen in an evolving system; see Brooks's Law, creeping elegance, creeping featurism. http://www.tuxedo.org/~esr/jargon/html/entry/second-system-effect.html The choice is to stick around and help fix things (if indeed they are broken), or jump to a lighter alternative like Maverick: Maverick is a minimalist web publishing framework which combines the best features of Struts and Cocoon and yet is far simpler than either. http://marc.theaimsgroup.com/?l=velocity-userm=102387923624439w=2 --Jeff On Wed, Jun 26, 2002 at 10:41:14PM -0400, John Austin wrote: I'm back from a short vacation in beautiful Chicago (it really is much nicer than Toronto or Montreal) and have waded back in to Cocoon for a couple of days. After just a few hours of poking around I have decided that it will be much simpler for me to simply hand-code a whole hat-full of servlets than to try and pull any meaning out of Cocoon and it's documentation. Fifteen hours on the Interstate wasn't as challenging as trying to figure out how one should check a Web Form this month but I didn't have that feeling of travelling backwards half of the time. I was also able to predict and achieve forward progress (for a change). Thanks guys, but no thanks. Maybe I'm getting old, but I really don't understand the need for all of the complexity and the lack of documentation in this product. On the other hand, I used to feel the same way about the mind-numbing complexity of a certain thirty-year-old mainframe operating system (MVS) produced by IBM back in the sixties and it's patching system (SMP4). So it can't just be my age. Anyway, Cocoon has cost me far morte (a typo that's better than the original word) time than it was worth. The chief problems appear to have been endlessly re-invented terminology for an overwhelming number of 'new concepts' and a complete lack of consistency between different components (i.e. functional code, non-functional examples, unbuildable documentation and a website that doesn't match up with any single released version of the project). I have a lot of respect for the ability of the people who have built this project, but I want them to know that their project appears to be out-of-control and could become very difficult to manage. If experienced developers (like myself) can't figure out how to use enough features in the product to make it worth using, then penetration will be limited and all of your efforts will be wasted. There is more to this business than stuffing in features at the expense of documentation and testing. You have a lot of very good ideas, but the execution of the project as a whole seems to be suffering. I know that I will often look at my JSP and servlet code and think 'XSP and Cocoon were sooo much better!' until I remember that I wasn't ever able to use enough of Cocoon to make a profit. Oh, well, at least all of my test systems have bags of memory now! - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Giving up! Cocoon too big, slow and confusing
To be fair, the documentation has greatly improved since I started with Cocoon (almost a year ago). I sent out an email earlier with specific comments (thank you Nicola for noticing:)), both the good and the bad.. and while I was looking through the existing documentation, I noticed a few things I hadn't noticed before. Here are the best answers for the specific questions that I've been able to come up with, hopefully they're helpful. Ricardo Trindade wrote: Ok. Where is the documentation for Pipeline Components ? Where is an in-depth description of each type of G enerator ? By pipeline components, do you mean sitemap components? You can find that (as well as in-depth descriptions of most Generators) at http://xml.apache.org/cocoon/userdocs/index.html. From the front page, you can just click on User Guide on the left and you'll get there. You might want to take a look at the Internal Pipeline snippet http://xml.apache.org/cocoon/snippet/snippet-internal-pipeline.html from the Snippets section, or the Sitemap documentation http://xml.apache.org/cocoon/userdocs/concepts/sitemap.html located in the Concepts section of the User's guide. (I think because the sitemap is so central, you might want to think about taking it outside of the concepts section and moving it into the main User Docs section? I don't intuitively look in the Concepts section for the sitemap documentation, that might just be me, though.) There is no depth to the documentation. One doesn't have to go very far to run out of documentation. In my mind, that's what this process is for; to find out the trouble areas and fix them. And as you've pointed out, depth is one of those trouble areas. One of my problems was the consistency; some docs really explained both the problem and the solution extremely well, while others just gave me a fully qualified classname, a one-sentence description, and whether or not it's cacheable (sometimes with a number of ?'s instead). But in the near future, if I can fully wrap my mind around some of these concepts enough to consider myself worthy of doc writing, I'll do so. The Tutorial. How do I write a simple data-base backed application ? One of the problems in the doc that I just noticed now is how hard it can be find something that you're looking for. I was just 12 hours ago that I had looked over the entire site, and I saw a really nice cocoon-specific database article. But now I can't remember if it was a how-to, a faq, or a tutorial. I think that's a problem... and my only suggestion on how to fix that is to either change the wording or make it really clear what goes in each, as well as edit gray areas. Taking a quick look through the site, however, I found the following: Dev Guide - Using Databases in Apache Cocoon (I thought the Dev Guide was for those who were developing Cocoon, not developing with Cocoon? the line seems blurry to me.. I find the javadoc from the Dev Guide useful, however I find the docs in the Users Guide useful as well.. I don't see the need for a seperation, and I find the seperation both confusing and time-consuming to repeatedly move from one section to the other.) http://xml.apache.org/cocoon/developing/datasources.html Users Guide - Concepts - Database Access (This one's a bit hard to find, I think; I ended up looking three times in the How-To, FAQ, Tutorial or Performance section. The concepts section doesn't stick out so well in my mind.) http://xml.apache.org/cocoon/userdocs/concepts/databases.html I can't promise that these are what you're looking for, but hopefully it's a start. And hopefully, if they're not what you're looking for, the questions that get raised will become questions posed to the list. all the best, Liam Morley - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Q] SunSpot Portal Demo Error(NullPointerException) in Cocoon 2.0.2 and 2.1-dev
Hi, I'm currently trying to run cocoon, actually I'm very interested in sunspot portal. But I've got problem when I run login to the portal demo with guest/guest. It emits NullPointerException and after searching mailing lists I've found the same question but no answer. I'm running JDK 1.4.0_02 and Tomcat 4.0.4 with cocoon 2.0.2 and cocoon 2.1-dev. Can anyone help me?
Re: Giving up! Cocoon too big, slow and confusing
Robert S. Koberg wrote: I (and probably many other XSLT-heavy folk) would very interested to know the best practices for cocoon shown in way that takes an XSLT based site and produces a best-practices cocoon based app. (I would love to see how Jorge Pietschman builds cocoon apps) It's interesting, because most of my work with cocoon has been java-based.. giving an object layer above a database schema, and assigning a transformer to look for certain xml elements, which then hands off the element and any sub-elements/attributes to another class, which takes care of spitting out the database-specific SAX elements into the stream. Are we violating best practice, or is this just another approach? We kind of like it:) For example: - why is xsl:include and xsl:import bad - how should it be done this is bad? hrm. There was another thread about how included/imported stylesheets don't get refreshed right away, but that bug has been fixed by Carsten apparently in the 2.0.3 code (or so says a recent thread). Are there other reasons this is bad? Are there other more desired solutions (other than sticking everything in the same XSL doc, or making multiple entries in the sitemap)? I'm interested. I've always used XML as a template of sorts (I'm currently trying to minimize the number of XML docs so that there are less changes to be made in updating them, and from what I read, I don't think aggregates will do it for me, nor am I sure I agree with the philosophy). Liam Morley - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Samples as tools for learning and development (Was: Giving up! Cocoon too big, slow and confusing)
-Original Message- From: David Crossley [mailto:[EMAIL PROTECTED]] Sent: Saturday, June 29, 2002 2:50 AM To: [EMAIL PROTECTED] Subject: Samples as tools for learning and development (Was: Giving up! Cocoon too big, slow and confusing) For the moment you must look under the hood. Anyway, i find that getting my hands dirty is the best way to learn. Please follow the samples that others have tried to provide. I always look at samples and docs. The issue is that there's not enough of them. And some people deny the very existance of this issue. However the docs are improving, and the message of this topic has been gotten, at least by few developers. Others are still in denial mode, but it's Ok. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Samples as tools for learning and development (Was: Giving up! Cocoon too big, slow and confusing)
I always look at samples and docs. The issue is that there's not enough of them. And some people deny the very existance of this issue. I have never heard anyone deny that. However the docs are improving, and the message of this topic has been gotten, at least by few developers. Others are still in denial mode, but it's Ok. No, the bulk of the message I tried to deliver is: everyone is aware of it, people are working on it, if it truely bothers you, pay for your opensource software and be one of those people. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html 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. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Samples as tools for learning and development (Was: Giving up ! Cocoon too big, slow and confusing)
-Original Message- From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]] Sent: Saturday, June 29, 2002 9:11 AM To: [EMAIL PROTECTED] Subject: Re: Samples as tools for learning and development (Was: Giving up ! Cocoon too big, slow and confusing) However the docs are improving, and the message of this topic has been gotten, at least by few developers. Others are still in denial mode, but it's Ok. No, the bulk of the message I tried to deliver is: everyone is aware of it, people are working on it, if it truely bothers you, pay for your opensource software and be one of those people. Andrew, that message was hidden in the noise. Trolling references, cathedral and bazaar mentions and other off-topic subjects did not help you, guys, to deliver the message. I'm left with the mixed feeling. At the end, I see that people recognize the issue and think of solutions, but at the same time the first reaction (He's giving up? Let him go.) is shocking. Also, repeating theme from many developers is MONEY, every other message advises me to pay MONEY. It's all off-topic. I'm amazed how experienced USENET, FIDO people were lost in off-topic. Forget Cathedral..., there's an issue. Solve it. We are not Free Software Prophets, we are programmers. Let's be pragmatic. I'm not complaining, it's just my poor English :) - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Samples as tools for learning and development (Was: Giving up ! Cocoon too big, slow and confusing)
On Saturday, June 29, 2002, at 10:04 AM, Argyn Kuketayev wrote: Also, repeating theme from many developers is MONEY, every other message advises me to pay MONEY. It's all off-topic. I'm amazed how experienced USENET, FIDO people were lost in off-topic. Forget Cathedral..., there's an issue. Solve it. We are not Free Software Prophets, we are programmers. Let's be pragmatic. I didn't interpret Andrew's message that way. I think he was suggesting you should pay (figuratively speaking) by helping (in *pragmatic* ways) to improve the docs. As for Free Software Prophets, we should be careful not to generalize or make broad assumptions about what motivates the people who participate on this list. People are here for different reasons, and IMHO that's a Good Thing. The beauty of it all is that in spite of our differences we can still work together and help to produce something truly amazing. -- Diana - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: null pointer passed as base exception
From: Leona Slepetis [mailto:[EMAIL PROTECTED]]
Hi All,
I have part of a pipeline that looks like this:
map:match pattern=matrix
map:generate src=gs.xml/
map:transform src=gs.xsl
map:parameter name=pagename value=matrix/
map:parameter name=dealID value={1}/
map:parameter name=playerID value=123/
map:parameter name=matrixfile value={3}/
map:parameter name=projectname value={4}/
/map:transform
map:transform src=default-html.xsl/
map:serialize type=html/
/map:match
In gs.xml I have:
application
page name=matrix/
!-- some other stuff that doesn't matter in this example --
/application
In gs.xsl I have:
xsl:template match=application
xsl:if test=not($pagename)
xsl:apply-templates select=page[@name='default']/
/xsl:if
xsl:if test=$pagename
xsl:apply-templates select=page[@name=$pagename]/
/xsl:if
/xsl:template
And default-html.xsl has:
xsl:template match=page
html
head
titletitle/title
/head
body
xsl:apply-templates/
/body
/html
/xsl:template
I get to it by calling
http://localhost:8080/GS/matrix?dealID=1001playerID=matrixfile=file://
/D:/
matrix.xmlprojectname=new
When I run it, the following error occurs:
Could not read resource file:/D:/tomcat/webapps/GS/gs.xml
org.apache.cocoon.ProcessingException: Could not read resource
file:/D:/tomcat/webapps/GorillaStation/gs.xml:
java.lang.RuntimeException:
java.lang.IllegalArgumentException: Null pointer passed as base
What's the stacktrace?
Vadim
One thing I notice is that playerID is not set to the value '123'. Why
is
this?
The other thing is that if I take outmap:parameter
name=pagename
value=matrix/ from the pipeline it works
according to the default logic in xsl:application.
There doesn't appear to be anything wrong with gs.xml; it was working
under
C1.
Other pipeline segments using the parameter pagename work just fine,
such
as:
map:match pattern=summary
map:generate src=gs.xml/
map:transform src=gs.xsl
map:parameter name=pagename value=summary/
/map:transform
map:transform src=default-html.xsl/
map:serialize type=html/
/map:match
Can anyone give me a clue as to what is wrong?
Thanks very much,
Leona
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
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. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Form Validator
I've been trying to get the form validator and DB Validator working for about a week now. I decided to try and just got the form stuff working first but I can't even get that. I'm running Cocoon 2.0.2-dev and Tomcat 4.1.3. In my sitemap.xmap I have the following: !-- | The page do_login does not actually exist this is just a dummy | target for the login auth to take place at. -- map:match pattern=do_login.xsp map:act type=form-validator map:parameter name=descriptor value=context://house_bills/descriptors/params.xml/ map:parameter name=validate-set value=user-pass/ map:redirect-to uri=index.xsp/ /map:act map:redirect-to uri=login.xsp/ /map:match login.xsp has a form that posts to do_login.xsp and has two inputs named user_name and user_password. Here is my params.xml ?xml version=1.0? root parameter name=user_name type=string nullable=no/ parameter name=user_password type=string nullable=no/ constraint-set name=name-pass validate name=user_name/ validate name=user_password/ /constraint-set /root I've checked through the logs and there aren't any context errors so Cocoon seems to be finding the params.xml file OK. Everytime I submit the form I get bounced back to the login.xsp page instead of getting sent to index.xsp. It doesn't matter if I don't put anything in the inputs or have valid data in both. I would also like to be able to validate the user_name password_fields against a MySQL database and setting the value in the corresponding user_id column in a session variable. I played with it a little and cocoon was connection to the DB but not authenticating, I don't have my descriptor file for that any more. Here is my DDL for the table I want to auth against. CREATE TABLE `users` ( `user_id` int(11) unsigned NOT NULL auto_increment, `user_name` varchar(255) NOT NULL default '', `user_password` varchar(16) NOT NULL default '', `user_first_name` varchar(255) NOT NULL default '', `user_last_name` varchar(255) NOT NULL default '', `user_email` varchar(255) NOT NULL default '', `user_status` tinyint(4) unsigned NOT NULL default '1', PRIMARY KEY (`user_id`), UNIQUE KEY `user_login` (`user_name`,`user_password`), UNIQUE KEY `user_id` (`user_id`) ) TYPE=MyISAM My other question with the DBAuth stuff is can cocoon run the submitted password through MySQLs PASSWORD() function? I would really like to be able to keep the password column in the table encrypted and still be able to use the DBAuth stuff. I hope someone can give me a hand with this. After a week of searching the mailing lists, coocon site and web in general I'm stuck! -Eric Dalquist - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Q] SunSpot Portal Demo Error(NullPointerException) in Cocoon 2.0.2 and 2.1-dev
[Please use plain text] Hi there, your problem should be due to using jdk1.4. I suggest 1.3 instead, which is what I run with tomcat 404 and cocoon2.1-dev. This combination works fine. --- [EMAIL PROTECTED] wrote: HR BODY style=FONT-SIZE: 10pt; FONT-FAMILY: ±¼¸²P style=margin-top:3px; margin-bottom:3px;Hi,/P P style=margin-top:3px; margin-bottom:3px;I'm currently trying to run cocoon, actually I'm very interested in sunspot portal. But I've got/P P style=margin-top:3px; margin-bottom:3px;problem when I run login to the portal demo with guest/guest. It emits NullPointerException/P P style=margin-top:3px; margin-bottom:3px;and after searching mailing lists I've found the same question but no answer. I'm running/P P style=margin-top:3px; margin-bottom:3px;JDK 1.4.0_02 and Tomcat 4.0.4 with cocoon 2.0.2 and cocoon 2.1-dev./P P style=margin-top:3px; margin-bottom:3px;nbsp;/P P style=margin-top:3px; margin-bottom:3px;Can anyone help me?/P P style=margin-top:3px; margin-bottom:3px;nbsp;/P/BODY __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Sitemap diagram documentation
Hi, It would be nice if you also had a 8 1/2 by 11 paged PDF for us Americans! :) Thanks, Ryan Hoegg ISIS Networks Steven Noels wrote: Dear all, We have created a diagram representation of the Cocoon sitemap that you might consider being helpful. It is available in PDF format at http://outerthought.net/sitemap/ for now, since we are redesigning our website and plan to move it over to outerthought.org 'v2' when that is ready. Please enjoy and comment. Warm regards, /Steven - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [PATCH QUEUE] Summary June 30 2002
--- This mail is generated automatically using Jakarta Ant. Contents are automatically downloaded from Apache's Bugzilla. --- Please do not reply to this mail. --- *** COCOON PATCH QUEUE UPDATE patches in queue: 8 *** --- 8614:[PATCH] configurable component manager --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8614 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 9075:[PATCH] Contribution of SAP R/3(r) connectivity components --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9075 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 9521:[PATCH] Mozilla script support for simple-xml2html.xsl --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9521 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 9728:[PATCH] CocoonServlet getClassPath() enhancements Tomcat4 --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9728 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 10208:[PATCH]/[RT] Aggregation and Error Conditions (file not foun --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10208 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 10281:[PATCH] nested cocoon: source spanning multiple sitemaps --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10281 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 10284:[PATCH] CachingPoint caching algorithm --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10284 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW --- 6879:[PATCH] Cache improvement using ESI invalidation protocol --- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6879 REVIEWER:[EMAIL PROTECTED] RESOLUTION: STATUS: NEW *that's it! patch HOWTO Send patches to http://nagoya.apache.org/bugzilla/ specifying [PATCH] in the summary. Bugzilla sends a mail automatically to this list. Reviewers will mark it FIXED there when applied. Patches not sent to Bugzilla will not be reviewed. --- This file is scheduled to be generated every Tuesday and Friday 1:00 CET for the cocoon-dev mailing list, on Sundays 1:00 CET for the cocoon-users mailing list. For any problem, question or suggestion, please notify [EMAIL PROTECTED] --- There is a HEAD branch and sometimes a previous-version branch that are maintained. Where will the patch go? 1. If it is a bug fix it should go to both branches 2. If something is totally new it goes into HEAD scratchpad. 3. Something in between, but does not break backward compatibility _may_ go into both (and may not) 4. For everything else, a vote is required so first it may go into HEAD, and then be VOTEd in order to sync this into branch. Please note that structural changes have to be VOTEd first. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [HELP]
From: Mellado, Rafael [mailto:[EMAIL PROTECTED]]
I got the following exception in my sitemap I have the following:
map:generator name=xsp
src=org.apache.cocoon.generation.ServerPagesGenerator/
and
map:match pattern=tutorial/*.xml
map:generate type=xsp src=tutorial/{1}.xsp/
map:serialize type=xml/
/map:match
I am using version 2.1-dev
Description:org.apache.cocoon.ProcessingException:
java.lang.NullPointerException
full exception chain stacktrace
Original exception : java.lang.NullPointerException
at
net.sf.pizzacompiler.compiler.Namer.findMethod(C:\pizza\main\src\net\sf\
pizz
acompiler\compiler\Namer.pizza:306)
Seems that pizza compiler really does not like your XSP. You could try
javac instead of pizza.
Easiest way to do this is get Cocoon source distribution, remove file
lib/optional/pizza-1.1.jar, remove everything in build directory, and
rebuild Cocoon.
Also, you could try to compile Java file generated from the XSP to
compile from the command line using pizza and if it fails in similar
way, contact pizza developers (project hosted at sourceforge).
Vadim
at
net.sf.pizzacompiler.compiler.Namer.resolveSelectFromType(C:\pizza\main\
src\
net\sf\pizzacompiler\compiler\Namer.pizza:648)
at
net.sf.pizzacompiler.compiler.Attr.attribSelect(C:\pizza\main\src\net\sf
\piz
zacompiler\compiler\Attr.pizza:1572)
at
net.sf.pizzacompiler.compiler.Attr.attribExpr(C:\pizza\main\src\net\sf\p
izza
compiler\compiler\Attr.pizza:1359)
at
net.sf.pizzacompiler.compiler.Attr.attribExpr(C:\pizza\main\src\net\sf\p
izza
compiler\compiler\Attr.pizza:1113)
at
net.sf.pizzacompiler.compiler.Attr.attribStat(C:\pizza\main\src\net\sf\p
izza
compiler\compiler\Attr.pizza:692)
at
net.sf.pizzacompiler.compiler.Attr.attribStats(C:\pizza\main\src\net\sf\
pizz
acompiler\compiler\Attr.pizza:750)
at
net.sf.pizzacompiler.compiler.Attr.attribDef(C:\pizza\main\src\net\sf\pi
zzac
ompiler\compiler\Attr.pizza:472)
at
net.sf.pizzacompiler.compiler.Attr.attribDef(C:\pizza\main\src\net\sf\pi
zzac
ompiler\compiler\Attr.pizza:424)
at
net.sf.pizzacompiler.compiler.Attr.attribute(C:\pizza\main\src\net\sf\pi
zzac
ompiler\compiler\Attr.pizza:355)
at
net.sf.pizzacompiler.compiler.Main.process(C:\pizza\main\src\net\sf\pizz
acom
piler\compiler\Main.pizza:228)
at
net.sf.pizzacompiler.compiler.Main.compile(C:\pizza\main\src\net\sf\pizz
acom
piler\compiler\Main.pizza:309)
at
org.apache.cocoon.components.language.programming.java.Pizza.compile(Piz
za.j
ava:114)
at
org.apache.cocoon.components.language.programming.java.JavaLanguage.comp
ile(
JavaLanguage.java:225)
at
org.apache.cocoon.components.language.programming.CompiledProgrammingLan
guag
e.load(CompiledProgrammingLanguage.java:207)
at
org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.loa
dPro
gram(ProgramGeneratorImpl.java:398)
at
org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.loa
d(Pr
ogramGeneratorImpl.java:287)
at
org.apache.cocoon.generation.ServerPagesGenerator.setup(ServerPagesGener
ator
.java:203)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupPi
peli
ne(AbstractProcessingPipeline.java:370)
at
org.apache.cocoon.components.pipeline.impl.CachingProcessingPipeline.set
upPi
peline(CachingProcessingPipeline.java:287)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process
(Abs
tractProcessingPipeline.java:493)
at
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(
Seri
alizeNode.java:142)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invo
keNodes(AbstractParentProcessingNode.java:83)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.i
nvok
e(PreparableMatchNode.java:157)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invo
keNodes(AbstractParentProcessingNode.java:107)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P
ipel
ineNode.java:158)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invo
keNodes(AbstractParentProcessingNode.java:107)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P
ipel
ineNode.java:158)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invo
keNodes(AbstractParentProcessingNode.java:107)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(
Pipe
linesNode.java:152)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro
cess
or.java:327)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro
cess
or.java:309)
at org.apache.cocoon.Cocoon.process(Cocoon.java:587)
at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:999)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
