Re: JXTemplates - what's in a name?
Well, a template is normally thought of something where you have a layout and just fill in the holes with data created somewhere else, vs a generator whose assignment it is to do the data generation in the first place I did try to make this distinction clear in the rest of the message (which you have snipped off, below) [EMAIL PROTECTED] 2004/05/03 07:55:51 PM On Mon, 2004-05-03 at 14:22, Derek Hohls wrote: An April 2004 post pointed me to Terence Parr's article on Enforcing Strict MV Separation in Template Engines. (see article link at: http://www.stringtemplate.org ). This is a fascinating read and, to me, a classic in the field. What I learnt (amongst other interesting stuff) is that a true template ONLY provides a view on the data: it should not incorporate ANY logic (apart from the need to understand standard data structures; refer to other templates; and test for the existence of data) and so not be subject to any changes in the underlying model. This definition seems to differ from the rather loose term used in the Cocoon community; for example, Bruno says a template is just an easy way to create a custom generator. (ref: http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=108317864027176w=2). How does that differ exactly? -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: using Cocoon: chinese government agencies
Sorry, I have to smile at this; is it really possible that the Chinese are ardent supporters of the ultimate capitalist monopoly? If so, more proof that suits rule! [http://info.astrian.net/jargon/terms/s/suit.html] [EMAIL PROTECTED] 2004/05/03 04:22:41 PM How can you tell they are using Cocoon? if they truly are using Cocoon this would help me quite a bit. I work for an economic development agency that just participated in a trade mission to China. Our management is somewhat skeptical of using Cocoon because it isn't Microsoft. if I could show them evidence of Chinese government or a Chinese agency using Cocoon it would help my cause greatly. Gary T. Schultz Web Technical Administrator / GIS Coordinator Wisconsin Department of Commerce 6th Floor P.O. Box 7970 Madison, WI 1-608-266-1283 -Original Message- From: manuel moura [mailto:[EMAIL PROTECTED] Sent: Saturday, May 01, 2004 9:02 PM To: [EMAIL PROTECTED] Subject: using Cocoon: chinese government agencies hi , you guys might also be interested to know that the Government of the People's Republic of China is also using Cocoon. They do have a lot of web sites there.For instance the Ministry of Commerce http://english.mofcom.gov.cn. try google using this query cocoon site:mofcom.gov.cn/ http://www.google.com/search?q=site:gov.cn%20cocoon regards , manny __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover - 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] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Doctype declaration missing
Hi, I have XSLT that does XML - XML transformation. I want to include a doctype declaration in the output so my XSLT starts with: xsl:output method=xml doctype-system=http://docbook.org/xml/4.2/docbookx.dtd; doctype-public=-//OASIS//DTD DocBook XML//EN omit-xml-declaration=no/ However output that cocoon produces does not include the DocType Declaration. Any ideas and/or suggestions? Thank you. Sarah __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Doctype declaration missing
Sarah Haff wrote: I have XSLT that does XML - XML transformation. I want to include a doctype declaration in the output so my XSLT starts with: xsl:output method=xml doctype-system=http://docbook.org/xml/4.2/docbookx.dtd; doctype-public=-//OASIS//DTD DocBook XML//EN omit-xml-declaration=no/ However output that cocoon produces does not include the DocType Declaration. Any ideas and/or suggestions? Yes ... I suggest you check your email and read my reply to your earlier question :-) As far as I know you just can't do this with XSLT in Cocoon - you must configure a serializer in your Cocoon sitemap - take a look. If you use xsl:output in your XSLT it will be ignored. Cheers Con - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JXT or XSP?
Nacho How about putting to togetehr a brief guide for developing components under Avalon and posting it to the Wiki; best practice develops when people can clearly see alternative and better ways of doing things! Thanks Derek [EMAIL PROTECTED] 2004/05/03 06:28:55 PM beyaNet Consultancy wrote: Hi, as I started this whole kettle of fish discussion, I fully support and use the sitemap, flowscript, jxt combination. in my opinion trying to use the sitemap to determine the flow of a site can become too complicated produce and maintain in a very short time! And as for the use of Avalon/Actions, that itself can be too complex a solution to most problems I have had to deal with... I just wanted to add my 0.02. These are my 0.02.. (we are reaching the 500 bill mark any moment now :) ) I' ve been developing with cocoon for a couple of years now, and still find new ways of doing things from time to time. Cocoon is **huge**, and that is both a pro and a con for a framework. The first time I came into cocoon I was having a sabatic half-year between start-ups and had some time to tinker and toy arround with the samples to get used to cocoon's feeling. If I discovered cocoon now, I don't think I could have the time to learn how to use it and make my customers profit from my experience. It happened me with struts before.. It looked great, but I just didn't have the time to pause and refractor my (then) current project into struts, so I kept working with jsp and ignored a tecnology that could have improved the results. Cocoon is so horizontally spread, that it makes the first step very hard for begginners.. I remember doing the Web Application HOWTO and then, a week later, learning that that was not the way to do it, that there were far more efficient ways. Even now, when I finish a cocoon project and deploy it, I keep on thinking that maybe is not the correct way to do it, maybe there is a more efficient/quicker/higher performance way to implement the kind of project I've just finished. I refractored my first project 4 times until i settled down on the (XSP+Actions+Sitemap) combination. For the next one, I jumped to the (Flowscript+Woody+XSP) combo, and I thought I had settled in the (Flow + Avalon component +Woody + XSP) until I started refractoring to JXTemplates my last project. IMHO, Cocoon needs to slim down and clean up (the blocks effort points the right way, but is not enough) and lead the way for beginners. I think that's the weakest link in cocoon. The samples are great to get used to the different tecnologies you can use, the wiki is fantastic for people already developing, but a list of best behaviours for common cases would really make newbies more confortable. An example of what I mean... Right now there's a pet shop example in the distibution. The same pet shop is implemented in several ways. That's great for me, because I do want to learn all about cocoon, but most of the potential users that come across cocoon and install it for the first time will only get more and more confused by looking at several ways of doing the same thing. For them, it'd be easier to find five different examples (typical webapps) and the 'best' way to implement them, and a small guide to their probable needs. Most of the people want to be lead, not many want to be a pathfinder. It's undoubtedly true that you can abuse flowscript and implement too much business logic in it. At my company, we are probably guilty of this, in a sense. We tend to implement things with Javascript because the roundtrip time between editing and testing is so short: no need to recompile and restart the container to test results. Our policy is that putting business logic in the flowscript is to be considered OK in a prototyping stage. Once the prototype is tested, you should reimplement it in a Java method or class. Of course, this takes discipline and sometimes the move-to-Java stage can be postponed (or forgotten) due to deadline pressure, as always. Is the debbuging improvement worth the effort of translation? I do my bussiness logic as an Avalon Component, and I call the component from the sitemap when needed.. I find it a little bit hard to debug, but keeps the code clean and concerns as separate as I need them. One more thing: you mentioned editing cocoon.xconf as a typical step when you're defining a new business object. Well, I see cocoon.xconf as something that should be hidden from view as much as possible. I don't want less-experienced developers touch it and risk breaking the build because of a misconfigured component. I don't even want myself being subjected to the pain of dealing with it. That's one of my complains.. I have to restart cocoon 5 times a minute when developing components and touch the cocoon.xconf file. That's not very clean.. There should be a way of dynamically loading components into
Re: JXTemplates - what's in a name?
Terence Yes, I think your situation is true for a lot of Cocooners; I have tended to use XSP because my use cases do not require specialised data generation (as yours seems to) - its mostly just pulling data from a DB (see the other thread on this topic). If I can avoid handcoded Java for this type of application, I will do so. I agree XSLT works (I use and I like it) - but the point I picked from the article was the difficulty of working with a page designer who may know HTML and now wants to incorporate dynamic elements in the page - the argument goes that giving that person a whole language (be it XSLT or a full-blown JXT) is really overkill (and leads to mixing of view with model). I do think its good to bring in opinions from people outside of the Cocoon bubble - certainly Cocoon has always espoused SOC and we need to look at insights that suggest where there are gaps in the approach; not because we are academics [remember the article was written by someone with very solid experience in website design and maintenance ] but because we have an inherent drive to make things better! My 2c, anyway. [EMAIL PROTECTED] 2004/05/04 03:02:54 AM I'm new to cocoon and JXTs so what I know is only what I have read on the website and what I've done so far with a cocoon app I've taken over development of. I will make some general comments on the ideas you've raised. I wouldn't get bogged down in the whole purity thing with whether or not a template is a true template. For me, the important thing is separation of concerns. As you point out, XSLT provides enough facilities in the specification to create the necessary contracts for separation of concerns. For me, it's the only templating system I need and I choose it because it is a widespread cross-technology standard. Being a cocoon newbie, I'm questioning the need to use XSPs because I see them as a way to loose many of the bonuses that come with OO in terms of using popular industrial tools like JavaDoc and Junit. Although I started my web development career with ColdFusion, I'm not a big fan of the tags and code mixture when it comes to creating a controller (in the MVC sense) or writing business logic. I'm thinking I'm probably gonna write all my apps using custom generator classes and just ignore XSPs. But that's just me. Some would argue that XSPs are easier and more rapid but I think they just create an extra layer of maintenance in your java application. I've just taken over development of an existing cocoon app here at work so it looks like I'll be writing XSPs in the short term, but they are not for me. Generally, as far as your discussion goes, I don't like using text-based templates anywhere near my business logic - ie, I don't like using the templating facilities of JSP, XSP, ASP, PHP, or ColdFusion. My experience is mainly with PHP, and I tend to write in an OO way - using the standards based DOM API to build up my content, and then I use an XSLT processor to orchestrate the view (with XSLT stylesheets). I think this concept in general is very simple but it is a scalable one with easy maintenance. (I've written a PHP framework (XML Application Objects) which is on hold while I learn cocoon http://xao-php.sf.net ). Maybe when I get more experience with cocoon, I will port XAO as a set of cocoon generators. As it stands, it's already easy for me to integrate XAO applications into coocoon as it is easy to pull untransformed content into the sitemap -- especially in the contenxt of aggregation. Same is true the other way around. XAO can easily consume XML from a cocoon app with one line. So yeah, all I need is the DOM standard for content generation, and the XSLT standard for formatting. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: a working version of 2.1.5?
I will disable the doc generation for blocks until we have a working solution :( Thanks Carsten -Original Message- From: Joerg Heinicke [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 04, 2004 2:04 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: a working version of 2.1.5? On 04.05.2004 01:35, Lars Huttar wrote: Hi all, I downloaded the most recent (at the time) Cocoon 2.1 snapshot this afternoon, but it turned out not to be buildable. The version I downloaded was http://cvs.apache.org/snapshots/cocoon-2.1/cocoon-2.1_20040503161326.t ar.gz Does anybody know of a recent 2.1.5-dev snapshot that does build? My purpose is to be able to develop using CForms as CForms instead of Woody. My understanding is that CForms don't exist in any release version. Of course I can wait till May 14 if necessary but... Or, does anyone know how to fix this build? The end of the build.sh output was: cocoon-block-html-patch: Processing: C:\temp\cocoon-2.1.5-dev\src\blocks\html\conf\tidy.xmap Writing: C:\temp\cocoon-2.1.5-dev\build\webapp\sitemap.xmap Processing: C:\temp\cocoon-2.1.5-dev\src\blocks\html\conf\tidy.xconf Writing: C:\temp\cocoon-2.1.5-dev\build\webapp\WEB-INF\cocoon.xconf Collection sitemap components info BUILD FAILED C:\temp\cocoon-2.1.5-dev\tools\targets\webapp-build.xml:93: Following error occu red while executing this line C:\temp\cocoon-2.1.5-dev\build\cocoon-2.1.5-dev\temp\blocks-build.xml: 4073: Site map component HTMLGenerator does not implement a sitemap component interface. Total time: 6 minutes 9 seconds export: Files\apache-ant-1.6.0: bad variable name export: Files\Saxon653\saxon.jar;C:\Program: bad variable name If you run the build in verbose mode (-v) you will see the real reason: D:\cocoon-2.1\tools\targets\webapp-build.xml:93: Following error occured while executing this line D:\cocoon-2.1\build\cocoon-2.1.5-dev\temp\blocks-build.xml:4075: IOException: java.io.FileNotFoundException: D:\cocoon-2.1\build\cocoon-2.1.5-dev\documentation\ xdocs\userdocs\generators\book.xml The patching happens to early, before this file is copied to that place. This feature was added recently and generates documentation and sitemap component declaration in a XDoclet-like way. Unfortunately it does not work that perfect until now. To work around the problem, exclude html block if you don't need it. If you need it build your Cocoon once including documentation and excluding html block. In the second run (the file is now there) you can include the html block successfully. Joerg - 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]
Re: AW: JXTemplates - what's in a name?
This sounds great - exactly what I had in mind - perhaps JXStringTemplate (in deference to the original concept) ?? [EMAIL PROTECTED] 2004/05/03 06:31:38 PM hi derek, I alse read that paper and agree that it was revealing. it also made me rethink view generation (the bad symtpoms had of course already occurred to me). my current idea (pretty blurry ATM) is to create a stripped down version of the JXT generator (remove the 'power features') and provide it with 'view contexts'. there would be a 'facility' (kind of factory) which would return a 'view context' for a specified view identifier. now the simple JXT generator would have all it needs to 'fill the holes'. -Ursprungliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von Derek Hohls Gesendet: Montag, 3. Mai 2004 14:23 An: [EMAIL PROTECTED] Betreff: JXTemplates - what's in a name? An April 2004 post pointed me to Terence Parr's article on Enforcing Strict MV Separation in Template Engines. (see article link at: http://www.stringtemplate.org ). This is a fascinating read and, to me, a classic in the field. snip what=almost everything;-)/snip - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Business Logic in Cocoon Applications?
Well, I did say good practice, not best practice! (I think the latter is a myth, anyway, and is so case- specific as to be of little use). If there are two (or three, or more?!) equally good approaches, clearly laid out, with suggested areas of application, and pros and cons highlighted, this is a major step up from and uh, just do what seems right, you know [with hands waving in the air]. People are competent enough to make their own choices once you give them sufficient starting material [EMAIL PROTECTED] 2004/05/03 07:56:07 PM David Leangen wrote: Well said! I don't mind volunteering myself to draft a Wiki during my spare time. However, as I mentioned before, I think that we need some type of consensus on these issues... even if that means agreeing to disagree. So, first reach consensus and I'll sum in all up in a Wiki with pleasure. :-) Dave -Original Message- From: Derek Hohls [mailto:[EMAIL PROTECTED] Sent: May 3, 2004 21:31 To: [EMAIL PROTECTED] Subject: Business Logic in Cocoon Applications? There have been a number of threads on the mailing list (April 2004) on the issue of where to locate the Business Logic; with Cocoon Flow, for example, coming under criticism (and defence) for its potential to act (correctly or incorrectly?!) in this respect. It would be very helpful to set up a good practice guide for Cocoon users that identifies (a) what types of logic one encounters [what do we actually mean by 'Business Logic', and there are any other types??] and (b) how and where to go about implementing these in the various layers. As always, clear examples would help new users. I do not think it matters if the application is small or large, simple or complex, the principles and approaches need to be consistent so that one can transition from between projects knowing that the same things will be in the same places. Any takers to draft a Wiki Page on this topic? Mine! Mine! The thing is.. who's so cocky as to say that he (she? any cocoon-girls arround?) is using the best approach? I think we should run a debate on which is the best way to do something and once we clarify which way is it, then we can do the wiki. But we have to try to keep it in practical terms, or the dabate will take on forever. Sometimes the theoreticaly-best way is not the best way due to performance, ease of use, etc.. We could have several different scenarios and the best way to implement each one.. and maybe as a final page, a guide with some interesting alternatives that branch from each case... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Better alternative to ESQL?
Leon I agree that if what works for you is OK, then you are doing fine. My concern is that there are better ways evolving and, if they are easy and clean, I am prepared to learn them but, and this is my case in a number of threads (and you have effectively said the same thing here), if this approach is a limited to a few in the know and there is not sufficient info for others to get in the know, how can we evolve as a community of developers with a *potentially* really good product? See Point 6 of: http://www.hibernate.org/38.html Derek [EMAIL PROTECTED] 2004/05/03 06:50:10 PM Hi Christopher, the better combination seems to be flowscript + woody + O/R with O/R to be either Hibernate or OJB. There are some examples in the Wiki. Unfortunately, I find the combination neither very clean nor easy to learn, though experienced users vouch it is both easy and clean. I think you could look at the JXT or XSP thread, or to the flowscript thread on the devel group. There was a discussion on this subject not too long ago (http://marc.theaimsgroup.com/?l=xml-cocoon-devm=108236425519235w=2) On the other hand, I fully agree with you that you do not need to change a winning team; being aware (and knowing what it does) of the winning team to be is I think sufficient. Leon Christopher Painter-Wakefield wrote: FWIW, that conversation did not include everyone using Cocoon and/or reading the list. It may be that the folks joining in the conversation were those with similar approaches. My attitude is the best tool for the job is the one that meets your needs. Since many of the tools recently mentioned were not available 1-2 years ago, we developed a lot of our own designs to tackle the same sorts of problems in our environment. We make heavy use of XSP, logicsheets, and ESQL. At this point our designs are pretty mature and, of course, are a custom fit for our needs. If you have established software that is working, you probably have a good idea where the most pain is - where the code is difficult to modify and extend, where you spend the most time, etc. Or you may be adding new features with very different requirements than before. In these cases, it is probably worth examining the new tools to see if they offer a solution to your particular problems. Otherwise, if it ain't broke In our case, I am interested in some of the tools that help with forms and form validation, which is an area we are very weak on, so I may examine these in the future. However, on site navigation, layouting, etc., I feel our designs are working very well, so I probably won't look for something else. Here's my vote for XSP: it is general-purpose, powerful, flexible, and extensible (with all of Java available to you). It doesn't solve a specific problem, but it can be used to solve almost any problem. -Christopher |-+ | | Derek Hohls| | | [EMAIL PROTECTED]| | | a | | || | | 05/03/2004 07:28 | | | AM | | | Please respond to| | | users| | || |-+ --| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Better alternative to ESQL? | --| There seems to be a very a strong current of opinion on the list at present (April 2004) saying that XSP is not really a suitable component of a well archictectured Cocoon application. My major use of it has been in the development of complex database reporting systems; using ESQL for the bulk of the work and adding in Java code to do any necessary non-SQL calculations. If the use of XSP (and, therefore, I assume, ESQL) is not espoused any longer, what is the equivalent but better methodology for tackling this type of work, and where is/are the corresponding examples/docs on the Cocoon sites? Thanks Derek PS Yes, I have looked at XReporter... - 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] -- This
Why ${this.Project} is successful?
How are we doing in comparison to our peers - see: http://www.hibernate.org/38.html Think about how Cocoon is doing on these points which are, I think, valid for pretty much any OS project - but even more so as the scope gets wider, new features are added and the community grows in both size and range (from newbies to veterans, with a bias towards the former...) Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Better alternative to ESQL?
Derek Hohls dijo: Leon I agree that if what works for you is OK, then you are doing fine. My concern is that there are better ways evolving and, if they are easy and clean, I am prepared to learn them but, and this is my case in a number of threads (and you have effectively said the same thing here), if this approach is a limited to a few in the know and there is not sufficient info for others to get in the know, how can we evolve as a community of developers with a *potentially* really good product? Hi Derek: I really appreciate your effort. I think it is a must. The reality is all this is too new stuff and we need time to write some docs. Also get some experience before write it is a good idea. Often, we use our spare time to make Cocoon and the lack of time is what brakes us to give more info. It is not we cannot want to share knowledges at all. :-D In my own case, I stoped my little contributions on the list, because I have a big pressure on work. This is really a big one. I promise to write some docs when I will have time to do that and no one else did it. We can talk around about this lack of docos forever and no docs will be done. I think someone can start the doc and then others will add new stuff or rewrite the doc if needed. If you have now the time to do that, please start it. :-D WDYT? Best Regards, Antonio Gallardo. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Vote: to unify, or not to unify (Was RE: Business Logic in Cocoon Applications?)
[I don't want to barge in on things here or step on anybody's toes. My intention is only to get some direction so I can help contribute to the Cocoon documentation. Although I am a relative newbie any my Cocoon skills are 1/1000th of the vets lingering around on this list, I think that's exactly what qualifies me to help contribute to the user documentation.] The first thing that we need to decide on is: do we aim for a unified approach, or should the platform continue to be a testing ground? Or rather, what is the face of Cocoon that we want to show to its users? There are good arguments for either case, but until we decide on which path to take, it is difficult to get started with any useful tutorial or other that explains how to program biz logic in Cocoon. In my view, regardless of what's happening internally, the user doc should show a simple and unified approach to using Cocoon. Otherwise, it's just too long and difficult to get a real project up and running, especially for the non-seasoned developer. Anything else can (and should) be reserved for more advanced users. If there's anything I learned in the commercial world, it's that the message must be simple and easily understood, even if it's not perfect from a theoretical standpoint. I therefore strongly suggest orienting user documentation with simplicity and user centricity in mind. However, we still need to reach consensus on what such a unified approach(es) should be. I would like to take a poll (probably the first of many): *** [ ] A. I think that we should show users the best way to get up and running with Cocoon. [ ] B. I think that we should show users all the options possible and let them decide the best approach. [ ] C. Yeah, whatever. Either way is good for me. Peace, man! Poll results so far: A. - 1 B. - 0 C. - 0 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Wierd error in Tomcat 5.0.21
Guys, My freaky setup: -MacOSX Client 10.3.3 with Java 1.4.2 -Jonas 4.0.0. with Tomcat 5.0.21 -Cocoon 2.1.4 The error is as follows below: The two communities together, keep me on the treadmill all the time. First Jonas upgrades then Cocoon does, then Jonas again and then Cocoon again, ad infinitum! And when everything works, Apple decides to upgrade!! Open Source is the opposite of Shampoos: one promises nice long hair and with the other, you just simply tear them off your head in frustration ;-) Ciao! Dp HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: tried to access method org.apache.log.Hierarchy.getRootLogger()Lorg/apache/log/Logger; from class org.apache.avalon.excalibur.logger.LogKitLoggerManager org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java: 281) org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.ja va:157) org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.ja va:110) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.jav a:117) org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java: 160) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java: 793) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process Connection(Http11Protocol.java:702) org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java: 571) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.java:644) java.lang.Thread.run(Thread.java:552) root cause java.lang.IllegalAccessError: tried to access method org.apache.log.Hierarchy.getRootLogger()Lorg/apache/log/Logger; from class org.apache.avalon.excalibur.logger.LogKitLoggerManager org.apache.avalon.excalibur.logger.LogKitLoggerManager.init(LogKitLog gerManager.java:131) org.apache.avalon.excalibur.logger.LogKitLoggerManager.init(LogKitLog gerManager.java:113) org.apache.cocoon.servlet.CocoonServlet.initLogger(CocoonServlet.java: 820) org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:338) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja va:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl.java:25) java.lang.reflect.Method.invoke(Method.java:324) org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:241) java.security.AccessController.doPrivileged(Native Method) javax.security.auth.Subject.doAsPrivileged(Subject.java:500) org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java: 263) org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.ja va:157) org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.ja va:110) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.jav a:117) org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java: 160) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java: 793) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process Connection(Http11Protocol.java:702) org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java: 571) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.java:644) java.lang.Thread.run(Thread.java:552) note The full stack trace of the root cause is available in the Apache Tomcat/5.0.21 logs. Apache Tomcat/5.0.21 -- Deepak 'Dp' Mehta E-mail: [EMAIL PROTECTED] URL: http://www.dp.com/ PGP Fingerprint: 837E B8E6 6AF4 6675 2730 0848 7731 09F5 3445 00A5 It is easier to get forgiveness than permission. smime.p7s Description: S/MIME cryptographic signature
Re: document() in xsl:variable - low performance
On 04.05.2004 03:37, Corin Moss wrote:
Hi There,
I've not been following this thread as closely as I might, so someone might have already mentioned this:
If you use a string() function on your document value as below:
xsl:variable name=langxsl:value-of select=string(document('cocoon:/getxml')/context/lang)//xsl:variable
Then you will forevermore be accessing only the value, not the entire document :)
Some might say it's a little hacky, but it is a simple fix which works.
No, it's absolutely a good fix/work around. The explicite cast to string
avoids the overhead of the RTF, especially because a RTF can only be
used as string, not as node set:
http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=108360536625037w=4
Joerg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Vote: to unify, or not to unify (Was RE: Business Logic in Cocoon Applications?)
My Vote is for A; with a comment text that says: - if there are any best approaches that are case-specific these must be clearly pointed out to the users ... ... bear in mind that even though some users may be Cocoon newbies they may be experienced developers in other frameworks and want to know how to handle case x - user tracks based on needs and experiences would be extremely powerful if we can get that far! [EMAIL PROTECTED] 2004/05/04 09:56:29 AM [I don't want to barge in on things here or step on anybody's toes. My intention is only to get some direction so I can help contribute to the Cocoon documentation. Although I am a relative newbie any my Cocoon skills are 1/1000th of the vets lingering around on this list, I think that's exactly what qualifies me to help contribute to the user documentation.] The first thing that we need to decide on is: do we aim for a unified approach, or should the platform continue to be a testing ground? Or rather, what is the face of Cocoon that we want to show to its users? There are good arguments for either case, but until we decide on which path to take, it is difficult to get started with any useful tutorial or other that explains how to program biz logic in Cocoon. In my view, regardless of what's happening internally, the user doc should show a simple and unified approach to using Cocoon. Otherwise, it's just too long and difficult to get a real project up and running, especially for the non-seasoned developer. Anything else can (and should) be reserved for more advanced users. If there's anything I learned in the commercial world, it's that the message must be simple and easily understood, even if it's not perfect from a theoretical standpoint. I therefore strongly suggest orienting user documentation with simplicity and user centricity in mind. However, we still need to reach consensus on what such a unified approach(es) should be. I would like to take a poll (probably the first of many): *** [ ] A. I think that we should show users the best way to get up and running with Cocoon. [ ] B. I think that we should show users all the options possible and let them decide the best approach. [ ] C. Yeah, whatever. Either way is good for me. Peace, man! Poll results so far: A. - 1 B. - 0 C. - 0 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JXTemplates - what's in a name?
On Tue, 2004-05-04 at 08:20, Derek Hohls wrote: Well, a template is normally thought of something where you have a layout and just fill in the holes with data created somewhere else, vs a generator whose assignment it is to do the data generation in the first place The result of processing a template is also data. A template-based generator provides an easy alternative to writing a custom generator that would do the equivalent of the template (which would be the only option if there weren't template-based generators). I don't see how in this context the definition of the word template would differ from the definition you have given. It's no big deal, but you suggested that I was putting another meaning in the word template then your definition (layout with filling in holes), but that wasn't the case or certainly not my intention. In fact now that I reread my message I was exactly defending that a template shouldn't do more then that. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cocoon freeze: nullpointer exception during moderate load testing
and another exception that happens *sometimes* :(
Can anyone shed light on this ??
Original exception : java.lang.NullPointerException
at org.apache.xml.dtm.ref.sax2dtm.SAX2DTM.comment(SAX2DTM.java:2486)
at
org.apache.xalan.transformer.TransformerHandlerImpl.comment(TransformerHandlerImpl.java:933)
at org.apache.cocoon.xml.AbstractXMLPipe.comment(AbstractXMLPipe.java:265)
at org.apache.cocoon.xml.AbstractXMLPipe.comment(AbstractXMLPipe.java:265)
at
org.apache.cocoon.components.profiler.ProfilingSAXConnector.comment(ProfilingSAXConnector.java:226)
at
org.apache.cocoon.xml.ContentHandlerWrapper.comment(ContentHandlerWrapper.java:304)
at org.apache.xerces.parsers.AbstractSAXParser.comment(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanComment(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
Jorg Heymans wrote:
I just got a NPE at another place :
org.apache.cocoon.ProcessingException: Exception during processing of
file:/opt/jakarta-tomcat-5.0.19/webapps/cocoon/app/gfx/sitemap.xmap:
java.lang.NullPointerException
at
org.apache.cocoon.components.source.AbstractStreamSource.toSAX(AbstractStreamSource.java:205)
at
Looking at this method
public void toSAX(ContentHandler handler)
throws SAXException, ProcessingException {
SAXParser parser = null;
try {
parser = (SAXParser)this.manager.lookup(SAXParser.ROLE);
Under which circumstances can the lookup *sometimes* return null here?
This is my xml parser config
xml-parser class=org.apache.excalibur.xml.impl.JaxpParser
logger=core.xml-parser pool-grow=4 pool-max=32 pool-minj=8
parameter name=validate value=false/
parameter name=namespace-prefixes value=false/
parameter name=stop-on-warning value=true/
parameter name=stop-on-recoverable-error value=true/
parameter name=reuse-parsers value=true/
/xml-parser
If it's a pool issue why is my jmeter script not getting similar errors
returned?
Thoughts?
Jorg
Jorg Heymans wrote:
Hi,
I have a jmeter script with 3 threads firing off requests to cocoon.
After a while, when I try to access the cocoon instance through my
browser and loading the simplest of pages (read file, xslt, serialize
html) i get a nullpointerexception during XSLT transformation. The
funny thing is that this only happens *sometimes*. The only constant
thing is that when a request fails it always fails during the xslt
transformation with a nullpointerexception.
I first thought that this was due to undersized pools, but i've set a
pool-size of 200 with pool-min 20 and pool-grow 10 on all sitemap
components and it still happens. The pool seems to be managing
component instances correctly because from debugging statements, the
number of components received from and returned to the pool are
identical.
Thoughts?
Example stacktrace:
org.apache.cocoon.ProcessingException: Exception during processing of
file:/opt/jakarta-tomcat-5.0.19/webapps/cocoon/app/common/stylesheets/remove_namespaces.xsl:
java.lang.NullPointerException
at
org.apache.cocoon.components.source.AbstractStreamSource.toSAX(AbstractStreamSource.java:205)
at
org.apache.cocoon.components.xslt.XSLTProcessorImpl.getTransformerHandler(XSLTProcessorImpl.java:275)
at
org.apache.cocoon.components.xslt.XSLTProcessorImpl.getTransformerHandler(XSLTProcessorImpl.java:240)
at
org.apache.cocoon.transformation.TraxTransformer.setup(TraxTransformer.java:313)
at
org.apache.cocoon.components.pipeline.AbstractEventPipeline.setupPipeline(AbstractEventPipeline.java:204)
at
org.apache.cocoon.components.pipeline.CachingEventPipeline.setup(CachingEventPipeline.java:290)
at
org.apache.cocoon.components.pipeline.CachingEventPipeline.process(CachingEventPipeline.java:180)
at
org.apache.cocoon.components.profiler.ProfilingCachingEventPipeline.process(ProfilingCachingEventPipeline.java:122)
at
org.apache.cocoon.components.pipeline.CachingStreamPipeline.process(CachingStreamPipeline.java:412)
at
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:148)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vote: to unify, or not to unify (Was RE: Business Logic in Cocoon Applications?)
David Leangen wrote: [ ] A. I think that we should show users the best way to get up and running with Cocoon. [X ] B. I think that we should show users all the options possible and let them decide the best approach. [ ] C. Yeah, whatever. Either way is good for me. Peace, man! Ugo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vote: to unify, or not to unify (Was RE: Business Logic in Cocoon Applications?)
However, we still need to reach consensus on what such a unified approach(es) should be. I would like to take a poll (probably the first of many): *** [ ] A. I think that we should show users the best way to get up and running with Cocoon. [X ] B. I think that we should show users all the options possible and let them decide the best approach. [ ] C. Yeah, whatever. Either way is good for me. Peace, man! Poll results so far: A. - 1 B. - 0 C. - 0 *** i think that there in NO BEST way. every aproach is releated with what the needs are.so the end-user can choose the right for him/her. --stavros - 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]
Re: LDAP and ActiveDirectory
Ivo Limmen wrote: Hi, I haven't tried it but I did has some experience in using AD's LDAP interface. I works perfectly. Simply connect to the AD on port 389 using the credentials of someone that has access rights. what did you use as LDAP client? Thanks Michi Michael Wechner wrote: Is anyone using M$ ActiveDirectory together with Cocoon's LDAP integration successfully? Thanks Michi -- Michael Wechner Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://cocoon.apache.org/lenya/ [EMAIL PROTECTED][EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JISP problems solved within 2.1.5-dev?
Is it possible that the JISP problems http://archives.real-time.com/pipermail/cocoon-devel/2004-April/030844.html of 2.1.4 have been solved within 2.1.5-dev? Thanks Michi -- Michael Wechner Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://cocoon.apache.org/lenya/ [EMAIL PROTECTED][EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
XSLT: Session-Content in Variables
Some weeks ago I comlained about not getting session content in variables in xslt. I read much about others who had the same problem. Now I found out, why it doesn't work. It's not a bug, it's a feature. What I tried: - Some.xsl: - ... xsl:variable name=langsession:getxml context=bct path=/context/lang//xsl:variable ... - My sitemap looked like this: - map:pipeline type=noncaching map:match pattern=rmd_list map:generate src=content/foo.xml/ map:transform src=style/xsl/some.xsl/ (1) map:transform type=session/(2) map:serialize type=html/ /map:match /map:pipeline - The simple reason, why there will never be something in the variable while processing the xsl is, that alle the xsl-stuff (1) (including the usage of the variable) is done before the session-tags are processed by the session-transformer (2). For example: If I have a xsl:value-of select=$lang/ somewhere in some.xsl, cocoon would first replace this with nothing (1) and afterwards care about the session-tags (2). So, using session-content in variables will never work using the session-transformer. Any comments? Regards, Nils - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LDAP and ActiveDirectory
Michael Wechner wrote: Ivo Limmen wrote: Hi, I haven't tried it but I did has some experience in using AD's LDAP interface. I works perfectly. Simply connect to the AD on port 389 using the credentials of someone that has access rights. what did you use as LDAP client? We didn't use an LDAP client (?). We had a webserver where users could log into and we used an LDAP connection to MS AD to verify their passwords. Is was simply a few Java statements to connect to the LDAP (AD). But if you need an (Java) LDAP client: Fast and good: http://www.iit.edu/~gawojar/ldap/ Feature rich and uses schema's: http://www.pegacat.com/jxplorer/ Thanks Michi Michael Wechner wrote: Is anyone using M$ ActiveDirectory together with Cocoon's LDAP integration successfully? Thanks Michi -- Ivo Limmen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LDAP and ActiveDirectory
Ivo Limmen wrote: what did you use as LDAP client? We didn't use an LDAP client (?). We had a webserver where users could log into and we used an LDAP connection to MS AD to verify their passwords. Is was simply a few Java statements to connect to the LDAP (AD). that's answering my question ;-) But if you need an (Java) LDAP client: Fast and good: http://www.iit.edu/~gawojar/ldap/ Feature rich and uses schema's: http://www.pegacat.com/jxplorer/ thanks for the links Michi Thanks Michi Michael Wechner wrote: Is anyone using M$ ActiveDirectory together with Cocoon's LDAP integration successfully? Thanks Michi -- Michael Wechner Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://cocoon.apache.org/lenya/ [EMAIL PROTECTED][EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LDAP and ActiveDirectory
But if you need an (Java) LDAP client: Fast and good: http://www.iit.edu/~gawojar/ldap/ That project seems to be dead. The latest news are from April 25th, 2001 Feature rich and uses schema's: http://www.pegacat.com/jxplorer/ That is better. Version 3.0 was released Nov 10, '03. Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JXTemplates - what's in a name?
Bruno I apologise then, if I misunderstood what you said. I still do not think that we should use the term template generator in this context. There are generators and there are templates and I don't think their roles should be mixed. That's why I was arguing for two different takes on the current situation - the JXGenerator which sits in the same place that other generators do (eg XSP) and allows access to, and manipulation of, the underlying data; and JXTemplate which is only about the layout and filling in the data. If you are also saying this then we are in agreement! Thanks Derek [EMAIL PROTECTED] 2004/05/04 10:21:47 AM On Tue, 2004-05-04 at 08:20, Derek Hohls wrote: Well, a template is normally thought of something where you have a layout and just fill in the holes with data created somewhere else, vs a generator whose assignment it is to do the data generation in the first place The result of processing a template is also data. A template-based generator provides an easy alternative to writing a custom generator that would do the equivalent of the template (which would be the only option if there weren't template-based generators). I don't see how in this context the definition of the word template would differ from the definition you have given. It's no big deal, but you suggested that I was putting another meaning in the word template then your definition (layout with filling in holes), but that wasn't the case or certainly not my intention. In fact now that I reread my message I was exactly defending that a template shouldn't do more then that. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JISP problems solved within 2.1.5-dev?
On 04.05.2004 11:26, Michael Wechner wrote: Is it possible that the JISP problems http://archives.real-time.com/pipermail/cocoon-devel/2004-April/030844.html of 2.1.4 have been solved within 2.1.5-dev? Not directly, you only have now two alternatives delivered with Cocoon: ehcache and jcs. Both must be configured somewhere in cocoon.xconf, jisp is still the default AFAIK. Joerg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LDAP and ActiveDirectory
Andreas Kuckartz wrote: But if you need an (Java) LDAP client: Fast and good: http://www.iit.edu/~gawojar/ldap/ That project seems to be dead. The latest news are from April 25th, 2001 Not really weird since it is as complete (and bug free) as it can be. I use this LDAP client the most. Feature rich and uses schema's: http://www.pegacat.com/jxplorer/ That is better. Version 3.0 was released Nov 10, '03. Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ivo Limmen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XSLT: Session-Content in Variables
On 04.05.2004 11:30, Nils Köster wrote: Some weeks ago I comlained about not getting session content in variables in xslt. I read much about others who had the same problem. Now I found out, why it doesn't work. It's not a bug, it's a feature. What I tried: - Some.xsl: - ... xsl:variable name=langsession:getxml context=bct path=/context/lang//xsl:variable ... - My sitemap looked like this: - map:pipeline type=noncaching map:match pattern=rmd_list map:generate src=content/foo.xml/ map:transform src=style/xsl/some.xsl/ (1) map:transform type=session/(2) map:serialize type=html/ /map:match /map:pipeline - The simple reason, why there will never be something in the variable while processing the xsl is, that alle the xsl-stuff (1) (including the usage of the variable) is done before the session-tags are processed by the session-transformer (2). For example: If I have a xsl:value-of select=$lang/ somewhere in some.xsl, cocoon would first replace this with nothing (1) and afterwards care about the session-tags (2). So, using session-content in variables will never work using the session-transformer. Any comments? Hello Nils, it seems you mix some things a bit. Though your observation is correct - it can not work in that way - IMO your pipeline setup seems to be just insufficient. I never used the session transformer but I guess it expects elements in the session namespace as you provided it with session:getxml/. The problem is that this XML snippet never reaches the session as it never gets to see the stylesheet. And you do not add this snippet to the XML SAX stream (it's just a result tree fragment in $lang), which the session transformer would get to read. I can imagine two solutions for a working pipeline: map:match map:generate src=content.xml/ map:transform src=addSessionMarkupToXMLStream.xsl/ map:transform type=session/ map:transform src=needsSessionInfoStyling.xsl/ map:serialize/ /map:match or map:match map:aggregate map:part src=content.xml/ map:part src=cocoon:/sessioninfo/ /map:aggregate map:transform src=needsSessionInfoStyling.xsl/ map:serialize/ /map:match map:match pattern=sessioninfo/ map:generate src=sessionMarkup.xml/ map:transform type=session/ map:serialize/ /map:match If you have further questions on this feel free to ask. If it is irrelevant because you wanted to express the same, just ignore it :) Joerg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wierd error in Tomcat 5.0.21
On 03.05.2004 21:53, Deepak Mehta wrote: The two communities together, keep me on the treadmill all the time. First Jonas upgrades then Cocoon does, then Jonas again and then Cocoon again, ad infinitum! And when everything works, Apple decides to upgrade!! Open Source is the opposite of Shampoos: one promises nice long hair and with the other, you just simply tear them off your head in frustration ;-) But isn't that with all software product, not only open source. As soon as you use products of more than one producer you will have these problems. And I guess the same can be true if you use different products of only one producer. And: nobody forces you to upgrade from working combination if it's really that difficult ;-) Joerg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: XSLT: Session-Content in Variables
Hi Joerg, You're right. In my pipeline i solved it this way: map:pipeline type=noncaching map:match pattern=impressum map:generate src=content/texts.xml type=serverpages/ map:transform type=session/ map:transform src=style/xsl/general_content_template.xsl/ map:serialize type=html/ /map:match /map:pipeline I put in the session-tags and some xsp-code in the source-xml to care about the session-stuff and to access it in the xsl-template with some xpath-expressions. Your suggestion with: map:aggregate map:part src=content.xml/ map:part src=cocoon:/sessioninfo/ /map:aggregate Looks very interesting, i'll try that as well. Thanks and bye! Nils - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OJB performance in Cocoon webapp
Hi, I'd like to ask people who are using OJB as a data layer in cocoon web apps. Is the performance good, comparable to plain jdbc? I know that plain jdbc could be faster but OJB (or other implementations) has mechanisms to improve performance (caching, reading db fields on demand). I'd like to build medium sized webapp usig OJB and Cocoon but I'm worried about performance that OJB would kill it and it would be my app's bottle neck. Regards, mirko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JISP problems solved within 2.1.5-dev?
Joerg Heinicke dijo: On 04.05.2004 11:26, Michael Wechner wrote: Is it possible that the JISP problems http://archives.real-time.com/pipermail/cocoon-devel/2004-April/030844.html of 2.1.4 have been solved within 2.1.5-dev? Not directly, you only have now two alternatives delivered with Cocoon: ehcache and jcs. Both must be configured somewhere in cocoon.xconf, jisp is still the default AFAIK. Hi: Would be fine to switch the default to JCS in the 2.1.5 release. WDYT? Best Regards, Antonio Gallardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Sendmail Action HTML-Mail Attachment
Since it's important for me and nobody answered yet, i repost my question:
Hi there,
I'm trying to send mail via the sendmail action with html-body and
pdf-attachment, my sitemap looks like this:
map:act type=sendmail
map:parameter name=smtphost value=some.smtp.de/
map:parameter name=from value=[EMAIL PROTECTED]/
map:parameter name=to value=[EMAIL PROTECTED]/
map:parameter name=subject value={request-param:subject}/
!--map:parameter name=body value={request-param:message}/--
map:parameter name=src value=context://mailer/test.html/
map:parameter name=srcMimeType value=text/html/
map:parameter name=cc value=/
map:parameter name=bcc value=[EMAIL PROTECTED]/
map:parameter name=attachments value={request-param:attachment}/
map:parameter name=charset value=ISO-8859-1/
/map:act
In request-param:attachment i have something like:
context:/nkpm/resources/documents/some.pdf
But it doesn't send the mail when I have both in it: attachment and
html-src. With one of them it works.
Does anybody have a clue?
Regards,
Nils
In the error.log I get:
---
ERROR (2004-05-02) 22:25.32:156 [sitemap.action.sendmail] (/mailer/mail)
http8080-Processor25/Sendmail: SendmailAction: An exception was thrown while
sending email. java.lang.NullPointerException
at
org.apache.cocoon.mail.MailMessageSender.send(MailMessageSender.java:323)
at org.apache.cocoon.acting.Sendmail.act(Sendmail.java:253)
at
org.apache.cocoon.components.treeprocessor.sitemap.ActTypeNode.invoke(ActTyp
eNode.java:154)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:84)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invok
e(PreparableMatchNode.java:165)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:107)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(Pipel
ineNode.java:162)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:107)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(Pipe
linesNode.java:136)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcess
or.java:371)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcess
or.java:312)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNod
e.java:133)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:84)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invok
e(PreparableMatchNode.java:165)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:107)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(Pipel
ineNode.java:162)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:107)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(Pipe
linesNode.java:136)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcess
or.java:371)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcess
or.java:312)
at org.apache.cocoon.Cocoon.process(Cocoon.java:656)
at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1112)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:284)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:204)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:257)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:151)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContext
Valve.java:245)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:199)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:151)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:184
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:151)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:164
)
at
Re: OJB performance in Cocoon webapp
mirko wrote: Hi, I'd like to ask people who are using OJB as a data layer in cocoon web apps. Is the performance good, comparable to plain jdbc? I know that plain jdbc could be faster but OJB (or other implementations) has mechanisms to improve performance (caching, reading db fields on demand). I'd like to build medium sized webapp usig OJB and Cocoon but I'm worried about performance that OJB would kill it and it would be my app's bottle neck. Regards, mirko OJB has a performance test suite. Robert posted results here: http://marc.theaimsgroup.com/?l=ojb-devm=108208175512540w=2 HTH -- Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wierd error in Tomcat 5.0.21
Joerg Heinicke dijo: On 03.05.2004 21:53, Deepak Mehta wrote: The two communities together, keep me on the treadmill all the time. First Jonas upgrades then Cocoon does, then Jonas again and then Cocoon again, ad infinitum! And when everything works, Apple decides to upgrade!! Open Source is the opposite of Shampoos: one promises nice long hair and with the other, you just simply tear them off your head in frustration ;-) But isn't that with all software product, not only open source. As soon as you use products of more than one producer you will have these problems. And I guess the same can be true if you use different products of only one producer. And: nobody forces you to upgrade from working combination if it's really that difficult ;-) Hi: Please make sure you are using STABLE releases. rant Why are you using Tomcat 5.0.21? AFAIK the lastest STABLE tomcat release is 5.0.19. If you are willing to work with non-stable versions, then why are you ranting? /rant Best Regards, Antonio Gallardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Better alternative to ESQL?
Antonio Thanks for the honest (and heartfelt!?) response. Please do not take my remarks as any kind of criticism for the developers; I think they are (and have been) doing a great job. I understand too that they are doing what they love and enjoy, as and when they can. Nonetheless, I think that, at the end, what counts is people out there using and, hopefully, appreciating! your code. The big step is then to tell people what you have done, and why, and - most important - how they can use it! It seems, from what you say, that the time is now for getting this done. Again, at the risk of being very boring, I will quote from the Hibernate website where they say ( http://www.hibernate.org/38.html ) There's no such thing as an undocumented feature. If your users don't know about a feature, its a nonfeature. Get rid of it; it's just complicating the sourcecode. A harsh standard to use, but probably a fair one. If we are heading for the next milestone date, then perhaps that's a good point to take time out and see: * what docs are currently outdated (deprecated features); * what docs refer to old practices and ways of doing things (eg. XSP) * which features are not documented at all * which features are documented poorly and/or in a very fragmented fashion. Looking through the archives will allow us to spot thorny issues (esp. reoccurring ones) that can be pulled into FAQs or just made part of the docs. Ideally, in future, as questions get asked, it would be great to say oh yes, thats explained in this doc, or this FAQ. This would help cut down on repeating the same answers to same question. Also ideally, much of the wisdom that is provided here on the list by those in the know needs to be distilled into relevant areas in a structured way. A big task, perhaps, but one that would add significantly to the documentation. As for a role I could play; at the moment I am just getting started with trying to learn the whole flow/forms/template, plus the add ons such as Hibernate and Java logic classes, technology, with any docs that are available - I am not sure this qualifies me to write anything yet! Having said that, I (and others I am sure - some of whom have already volunteered to write stuff ) would be happy to start perhaps trying to highlight specific areas of work - in fact, there a number of emails on the list that have done this already. I do think there are some very good writers out there - for example, Tony Collen's Gentle Tutorial on flow is really great - if we could get to this standard for some of the other areas at a both introductory and advanced level we would have a system that is comparable with the best anywhere... My 1c Derek [EMAIL PROTECTED] 2004/05/04 09:56:14 AM Derek Hohls dijo: Leon I agree that if what works for you is OK, then you are doing fine. My concern is that there are better ways evolving and, if they are easy and clean, I am prepared to learn them but, and this is my case in a number of threads (and you have effectively said the same thing here), if this approach is a limited to a few in the know and there is not sufficient info for others to get in the know, how can we evolve as a community of developers with a *potentially* really good product? Hi Derek: I really appreciate your effort. I think it is a must. The reality is all this is too new stuff and we need time to write some docs. Also get some experience before write it is a good idea. Often, we use our spare time to make Cocoon and the lack of time is what brakes us to give more info. It is not we cannot want to share knowledges at all. :-D In my own case, I stoped my little contributions on the list, because I have a big pressure on work. This is really a big one. I promise to write some docs when I will have time to do that and no one else did it. We can talk around about this lack of docos forever and no docs will be done. I think someone can start the doc and then others will add new stuff or rewrite the doc if needed. If you have now the time to do that, please start it. :-D WDYT? Best Regards, Antonio Gallardo. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OJB performance in Cocoon webapp
Reinhard Poetz wrote: OJB has a performance test suite. Robert posted results here: http://marc.theaimsgroup.com/?l=ojb-devm=108208175512540w=2 Thanks. I'd like to use JDO api but it wasn't in the test results. If its performance is like the PB's I could accept it. Regards, mirko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JISP problems solved within 2.1.5-dev?
Joerg Heinicke wrote: On 04.05.2004 11:26, Michael Wechner wrote: Is it possible that the JISP problems http://archives.real-time.com/pipermail/cocoon-devel/2004-April/030844.html of 2.1.4 have been solved within 2.1.5-dev? Not directly, you only have now two alternatives delivered with Cocoon: ehcache and jcs. Both must be configured somewhere in cocoon.xconf, jisp is still the default AFAIK. thanks, I will take a look at them Michi Joerg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michael Wechner Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://cocoon.apache.org/lenya/ [EMAIL PROTECTED][EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem with the SessionAttributeSelector
Hi! Has anyone find an answer to this question? I want to do the same: Test a session attribute (ID = not sessionID, but userID) in sitemap. If sessionis equals a defined value, it should refer to pageA, else refer to pageB. What is the correct syntax of the SessionAttributeSelector? Found no document about it. Regards, Christian From: bremerj Subject: Problem with the SessionAttributeSelector Date: Sat, 24 Apr 2004 12:25:11 -0700 I have problems using the SessionAttributeSelector. I have tried basically any syntax I have found in the various documents, but none worked. The when test is never successful. Has anybody managed to use this selector successfully? And what do I have to do to make the selector work? Thanks for your help. Joseph BREMER
Question about JSP generator
Title: Question about JSP generator Hi, As far as I understand, the JSPGenerator calls the Jasper JSPServlet to compile a JSP file. The Jasper servlet has some init parameters that I would like to set when used inside Cocoon. Is it possible to set these parameters in the web.xml file of the webapp ? Thanks, Eddy
Re: Vote: to unify, or not to unify (Was RE: Business Logic in Cocoon Applications?)
David Leangen wrote: [X ] A. I think that we should show users the best way to get up and running with Cocoon. [X ] B. I think that we should show users all the options possible and let them decide the best approach. [ ] C. Yeah, whatever. Either way is good for me. Peace, man! Have a track that shows the best way(s) depending on the context where they are used, but also link to docs for all the other options. This way we give clear guidance while also documenting everything we have. Remember that a new context could develop where what is best changes to one of the other options. --Tim Larson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OJB performance in Cocoon webapp
The JDO implementation presently in OJB is a big fat special case. It relies on the JDO reference implementation, which breaks proxies. It works, is compliant, and is performant if you don't want any proxies, but this usually leads to some nasty memory issues. On a performance note, the PB has the highest performance numbers as it doesn't do things like automatic dirtying. if you go to ODMG or OTM you get a bit larger performance hit. On the other hand, if you always use OJB, or something else that can participate in the cache -- allowing you to cache aggressively, you will typically see a massive performance boost as OJB makes caching much easier than using raw jdbc. My favorite example of this is an app we have which presently makes an obscene number of calls to the database for a couple of page loads. If we swap out to OJB using the default cache we can reduce it to 0 database hits per typical page load as it is frequently used and infrequently modified data -- prime for caching but from so many different tables that JDBC caching is really had to do for it. -Brian On May 4, 2004, at 7:29 AM, mirko wrote: Reinhard Poetz wrote: OJB has a performance test suite. Robert posted results here: http://marc.theaimsgroup.com/?l=ojb-devm=108208175512540w=2 Thanks. I'd like to use JDO api but it wasn't in the test results. If its performance is like the PB's I could accept it. Regards, mirko - 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]
Re: Problem with the SessionAttributeSelector
Forgot to say, that I am using the authentication framework, so the session information is stored as XML. With SessionModule/SessionAttributeModule I get no access to these session vars. Any ideas? Christian - Original Message - From: Christian Rosenberger To: [EMAIL PROTECTED] Sent: Tuesday, May 04, 2004 2:45 PM Subject: RE: Problem with the SessionAttributeSelector Hi! Has anyone find an answer to this question? I want to do the same: Test a session attribute (ID = not sessionID, but userID) in sitemap. If sessionis equals a defined value, it should refer to pageA, else refer to pageB. What is the correct syntax of the SessionAttributeSelector? Found no document about it. Regards, Christian From: bremerj Subject: Problem with the SessionAttributeSelector Date: Sat, 24 Apr 2004 12:25:11 -0700 I have problems using the SessionAttributeSelector. I have tried basically any syntax I have found in the various documents, but none worked. The when test is never successful. Has anybody managed to use this selector successfully? And what do I have to do to make the selector work? Thanks for your help. Joseph BREMER
Hotspot Virtual Machine Error
Anyone who encounters the same problem?? ...OLE_Obj... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Virtual Machine Error (sorry, i didn't include error)
ErrorVirtualMachine.gif Anyone who encounters the same problem?? Kind regards, Robby Pelssers attachment: ErrorVirtualMachine.gif- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Virtual Machine Error (sorry, i didn't include error)
I had loads of these when I was doing JNI but they can be caused by all sorts of things actually. Can you give us a bit more information about your install and what you're doing that causes this problem. I doubt that it's cocoon related but maybe some of us can help you a bit further anyway. regards Jorg [EMAIL PROTECTED] wrote: ErrorVirtualMachine.gif Anyone who encounters the same problem?? Kind regards, Robby Pelssers - 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]
RE: Vote: to unify, or not to unify (Was RE: Business Logic in C ocoon Applications?)
Personally, I don't think there CAN be a single best way. Most of the folks here seem to be writing their whole application in the web container and using all the cool Cocoon provided stuff that does JDBC, etc. In my world, I'm not even allowed to make JDBC calls from the web container. We use EJBs and do all the business stuff in the EJB container. So for me, most of the cool things like ESQL, OJB, etc. I simply can't use. Ralph -Original Message- From: David Leangen [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 04, 2004 12:56 AM To: [EMAIL PROTECTED] Subject: Vote: to unify, or not to unify (Was RE: Business Logic in Cocoon Applications?) *** [ ] A. I think that we should show users the best way to get up and running with Cocoon. [X ] B. I think that we should show users all the options possible and let them decide the best approach. [ ] C. Yeah, whatever. Either way is good for me. Peace, man! Poll results so far: A. - 1 B. - 0 C. - 0 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Passing an input form value to the sitemap
OK. I have done this before, but am confused as to the simplest way to accomplish a fairly trivial task: Passing a request attribute to the sitemap. Yes, I have read the docs. And I remain somewhat confused. What I want to do: Select a db record (MySQL db, Cocoon 2.1) based on a value submitted by a form. The documentation on the SQLTransformer suggests the following: page xmlns:sql=http://apache.org/cocoon/SQL/2.0; execute-query xmlns=http://apache.org/cocoon/SQL/2.0; query select id,name from employee_table where name = 'sql:substitute-value sql:name=username/' /query /execute-query /page However, the example for a dynamic pipeline is not much help: map:transform type=sql map:parameter name=use-connection value=personnel/ map:parameter name=show-nr-of-rows value=true/ map:parameter name=username value=Stefano Mazzocchi/ /map:transform Now, this example demonstrates that the SQLTransformer is capable of using a parameter, but what is the simplest way to get the value of username to the sitemap from a form? Note: This can be accomplished by creating a dummy XML file... content dynamic-query/ /content ...and an XSL stylesheet to prepare the query BEFORE passing it to the SQL transformer: ?xml version=1.0? xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:sql=http://apache.org/cocoon/SQL/2.0; xsl:param name=name/ xsl:template match=/ page titleHello xsl:value-of select=$name//title content xsl:apply-templates/ /content /page /xsl:template xsl:template match=dynamic-query execute-query xmlns=http://apache.org/cocoon/SQL/2.0; queryselect * from portalusers where name= 'xsl:value-of select=$name/'/query /execute-query /xsl:template /xsl:stylesheet This is the method Lajos Moczar describes in Cocoon Developer's Handbook to achieve a truly dynamic query, and takes advantage of params in the first XSL. However, this was before the tag, sql:substitute-value became available in Cocoon 2.1, so I would think this is easily implemented in some way... But, how? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Goovy's News
Does someone own some news about Groovy integration in cocoon ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vote: to unify, or not to unify (Was RE: Business Logic in C ocoon Applications?)
hmm tough decision.. One the one hand, when newer users get stuck, it will be simpler to have unified solutions. On the other hand, we may end up with avalon components signing guestbooks. ( A little overkill ) What I would love to see is all of the examples and ideas that are in place now, but maybe with a *best practice* flag. Having said that, my vote has to go on A. I just spend too much time figuring out how to do something rather than doing it :) -Original Message- From: David Leangen [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 04, 2004 12:56 AM To: [EMAIL PROTECTED] Subject: Vote: to unify, or not to unify (Was RE: Business Logic in Cocoon Applications?) *** [ X ] A. I think that we should show users the best way to get up and running with Cocoon. [ ] B. I think that we should show users all the options possible and let them decide the best approach. [ ] C. Yeah, whatever. Either way is good for me. Peace, man! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Doctype declaration missing
Con, Thanks for the reply. In my sitemap, I do have: map:serializer name=docbook mime-type=text/xml; charset=iso-8859-1 src=org.apache.cocoon.serialization.XMLSerializer doctype-public//OASIS//DTD DocBook XML V4.2//EN/doctype-public doctype-systemhttp://docbook.org/xml/4.2/docbookx.dtd/doctype-system encodingiso-8859-1/encoding /map:serializer and map:serialize type=docbook/ in the pipeline section. But the output has not Doctype Declaration. Any ideas? Thanks. Sarah --- Conal Tuohy [EMAIL PROTECTED] wrote: Hi Sarah In Cocoon, serialization is done in a separate step from transformation. So xsl:output is ignored. To change your serialization, configure the serializer component. e.g. you can configure the XML serializer as a docbook serializer, and use map:serialize type=docbook/ in your pipelines. Cheers Con -Original Message- From: Sarah Haff [mailto:[EMAIL PROTECTED] Sent: Tuesday, 4 May 2004 2:22 p.m. To: [EMAIL PROTECTED] Subject: Doctype declaration missing Hi, I have XSLT that does XML - XML transformation. I want to include a doctype declaration in the output so my XSLT starts with: xsl:output method=xml doctype-system=http://docbook.org/xml/4.2/docbookx.dtd; doctype-public=-//OASIS//DTD DocBook XML//EN omit-xml-declaration=no/ However output that cocoon produces does not include the DocType Declaration. Any ideas and/or suggestions? Thank you. Sarah Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
is xreporter alive?
Title: Message Hello please, excuse my ignorance, I've been looking at xreporter for a few days. I don't see much activity there. Is this project alive? thanks, Argyn
Re: Vote: to unify, or not to unify (Was RE: Business Logic in Cocoon Applications?)
Tim Larson wrote: David Leangen wrote: [X ] A. I think that we should show users the best way to get up and running with Cocoon. [X ] B. I think that we should show users all the options possible and let them decide the best approach. [ ] C. Yeah, whatever. Either way is good for me. Peace, man! Have a track that shows the best way(s) depending on the context where they are used, but also link to docs for all the other options. This way we give clear guidance while also documenting everything we have. Remember that a new context could develop where what is best changes to one of the other options. If you really want cocoon to catch up on usage numbers, then you ***have*** to keep it simple for begginers, and simple means not a myriad of options: Right now, starting with our beloved framework is a a big headache . Both the wiki and the userdocs are tecnology oriented, not user oriented. It's quite normal, because they are written by developes for developers, but we have to try an place a red carpet on the door so unexperienced java and web developers, and people who just don't have the time can learn what a great technology this is. Some people, those who need it or simply like tinkering arround, will want to keep on learning new tricks and ways once they understand the basics, and they should have the docs and samples available, just as they are now.. but that would be a second phase of the learning curve.. Right now is so steep I think we should break it in two parts. I just don't want cocoon to suffer the betamax curse. I owned a Sony Betamax, an Amiga, an Apple.. maybe It's just that I want to be on the winners side for once. :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Vote: to unify, or not to unify (Was RE: Business Logic in Cocoon Applications?)
[XX] A. I think that we should show users the best way to get up and running with Cocoon. [ ] B. I think that we should show users all the options possible and let them decide the best approach. [ ] C. Yeah, whatever. Either way is good for me. Peace, man! Joel McConaughy Managing Partner Displayware LLC 800 Fifth Ave., #101-316 Seattle, WA 98104-3191 206-300-4732 Direct 206-382-2188 Fax [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: is xreporter alive?
On Tue, May 04, 2004 at 11:11:20AM -0400, Kuketayev, Argyn wrote: please, excuse my ignorance, I've been looking at xreporter for a few days. I don't see much activity there. Is this project alive? Yes it is alive, but it has it's own developer and cvs-commit-log mailing lists. There have been a good bit of messages and commits lately on these lists. Please see: http://xreporter.cocoondev.org/getting-involved.html for more info about the lists, message archives, and cvs repo. --Tim Larson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: is xreporter alive?
Thanks, I didn't see there's a separate list. -Original Message- From: Tim Larson [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 04, 2004 12:08 PM To: [EMAIL PROTECTED] Subject: Re: is xreporter alive? On Tue, May 04, 2004 at 11:11:20AM -0400, Kuketayev, Argyn wrote: please, excuse my ignorance, I've been looking at xreporter for a few days. I don't see much activity there. Is this project alive? Yes it is alive, but it has it's own developer and cvs-commit-log mailing lists. There have been a good bit of messages and commits lately on these lists. Please see: http://xreporter.cocoondev.org/getting-involved.html for more info about the lists, message archives, and cvs repo. --Tim Larson - 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]
RE: Vote: to unify, or not to unify - results
Thank you for your input! Some excellent comments have been made and all are noted. So far, the poll results show that there is no unanimity (see below). I think that it would be pretty unscientific to reach any firm conclusions based on such a small sample, but I think that some trends can be established. First, I think it is clear, not only from this poll but from the many messages that have been posted lately, that the general opinion is that work needs to be done on the user docs to be more user-centric, use case oriented, and less confusing. However, there is some fear (for lack of a better word) that we will be taking freedom away from more experienced developers who may resent being forced down a certain path. There is also the concern that whatever we cite as the preferred approach may not be the best choice for a particular use case, or that the best practice may change. Generally, based on your comments, it appears that a good approach may be to choose a currently preferred approach. This recognises that what is often called best practices may change over time. This makes sense to me. So the CPA method allows for future changes (without loss of face), while still allowing us to focus on one particular approach for beginners. Other than the CPA, we would show other options. For example, if a newbie were reading up on JXTemplates, rather than saying that you can use Jexl or JXPath, we would choose our CPA (for example, JXPath), but have a link to a homologous page that explains the same things, but for Jexl. This would reduce one more variable, and thus one more possible source of delay or confusion to a newbie. So new users will be able to get up and running much faster, and once they have more experience, will be able to go over the alternative approaches. This seems to me a good compromise and, hopefully, a means of reaching consenus. Questions? Comments? Insults? It's not too late to chime in if you still want to vote or have other comments to add. The above is not a conclusion, just a proposition. *** [ ] A. I think that we should show users the best way to get up and running with Cocoon. [ ] B. I think that we should show users all the options possible and let them decide the best approach. [ ] C. Yeah, whatever. Either way is good for me. Peace, man! Poll results so far: A. - 6 B. - 3 C. - 0 A Dave L. Derek H. Tim L. JDD Nacho J. Joel M. B Ugo C. Stavros K. Ralph G. *** Dave L. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vote: to unify, or not to unify
[I don't want to barge in on things here or step on anybody's toes. My intention is only to get some direction so I can help contribute to the Cocoon documentation. Although I am a relative newbie any my Cocoon skills are 1/1000th of the vets lingering around on this list, I think that's exactly what qualifies me to help contribute to the user documentation.] I agree. I wrote docs when I was relatively new to Cocoon, which helped me learn more about Cocoon and the topics I was documenting, and let me write docs from the point of view of someone who didn't already understand all of the internals. We should encourage this! In the absence of a fourth choice, I'll vote for C. My suggestion is, if you want to help out by writing documentation, write it on the topics that confuse(d) you. If enough folks did this, we'd have all the bases covered, and the consensus approach would emerge automatically. In an ideal world -Christopher
Re: document() in xsl:variable - low performance
Thanks for all the input. Now to find a way to rework my code
-Christopher
Joerg Heinicke [EMAIL PROTECTED]
05/04/2004 04:04 AM
Please respond to users
To:[EMAIL PROTECTED]
cc:
Subject:Re: document() in xsl:variable - low performance
On 04.05.2004 03:37, Corin Moss wrote:
Hi There,
I've not been following this thread as closely as I might, so someone might have already mentioned this:
If you use a string() function on your document value as below:
xsl:variable name=langxsl:value-of select=string(document('cocoon:/getxml')/context/lang)//xsl:variable
Then you will forevermore be accessing only the value, not the entire document :)
Some might say it's a little hacky, but it is a simple fix which works.
No, it's absolutely a good fix/work around. The explicite cast to string
avoids the overhead of the RTF, especially because a RTF can only be
used as string, not as node set:
http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=108360536625037w=4
Joerg
Re: Vote: to unify, or not to unify - results
Other than the CPA, we would show other options. For example, if a newbie were reading up on JXTemplates, rather than saying that you can use Jexl or JXPath, we would choose our CPA (for example, JXPath), but have a link to a homologous page that explains the same things, but for Jexl. This would reduce one more variable, and thus one more possible source of delay or confusion to a newbie. So new users will be able to get up and running much faster, and once they have more experience, will be able to go over the alternative approaches. This is just an example of what I think we should avoid... The average user does not give a shiling about JXTemplates, JXPath, JEXL or whatever load of letters we decide to acronymize today. The user wants to know how can he set up his ubercool website accessing XML documents and SQL data with the mimimum of fuss, and hence, the document he is looking for is a step by step guide to do that. In one of those steps, he's shown how to get a needed parameter from the context, using our recommended method (JXTemplateTransformer, through a JXPath expression). There, on a side note, you can have an overview on what JXTemplateTranformer is, why is it our preferred method to access the parameter he needs and wich alternatives he could use, and pointers to the wikiPages of the related tecnologies for a deeper study if he needs it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Vote: to unify, or not to unify - results
I would suggest that if you want to write best/good practices that they be done under classifications, i.e - what kind of website you have. I think it would be quite useful to have a guideline for how to write a simple site (although you could get a lot of that from the sample site), as well as one for a larger site, and one that uses EJBs. I have seen the petstore implemented in many ways to illustrate whatever technology was being discussed - I believe Sun even has multiple versions of it. To be honest, I've never looked at Cocoon's petstore. Mostly, I guess, because I knew it didn't use EJBs. However, it would be cool to be able to go to the Cocoon site, read descriptions about various implementations of the petstore, and then download the one(s) that sound relevant to the project being developed. Just a thought. Ralph -Original Message- From: David Leangen [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 04, 2004 9:17 AM To: [EMAIL PROTECTED] Subject: RE: Vote: to unify, or not to unify - results Generally, based on your comments, it appears that a good approach may be to choose a currently preferred approach. This recognises that what is often called best practices may change over time. This makes sense to me. So the CPA method allows for future changes (without loss of face), while still allowing us to focus on one particular approach for beginners. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Supersonic block has landed (Power Trio tutorial/example app)
I've just committed the new supersonic block, a tutorial/example app called Supersonic Tour of Apache Cocoon, focused on Pipelines, Flow, Forms (aka the Power Trio). It is accessible from the blocks with samples page if you run the current Cocoon CVS version. The tutorial is meant to be studied independently of other docs, and give a quick overview of the most important components of Cocoon. There are probably a few typos here and there, and I'm no Forms guru (yet..) so enhancements are certainly possible (for example: why does this Calendar link show up next to the date entry fields ;-) Enjoy, and as always feedback and contributions are very welcome! -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: wb:delete-bean?
I'm using hibernate/cforms to build simple CRUD pages. These take the results from a query and create an ArrayList of beans, display a page worth of rows in a repeater, allow in place editting, and persist the results back to the database. Hibernate handles row updates automatically. Insertions are handled in the flow by explicitly calling a hibernate save operation on any row with a null ID. Deletions are the problem. Hibernate requires that I explicitly call a delete method for each deleted row. Cforms doesn't keep track of deleted rows within a repeater so I believe that I need to do this as each delete event is fired. However, I don't know how to access the row inside the wb:on-delete tag or how to call some external Java from there. May be there's an easier way to accomplish this? Thanks for the response. joel Joel McConaughy Managing Partner Displayware LLC 800 Fifth Ave., #101-316 Seattle, WA 98104-3191 206-300-4732 Direct 206-382-2188 Fax [EMAIL PROTECTED] -Original Message- From: Marc Portier [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 3:46 PM To: [EMAIL PROTECTED] Subject: Re: wb:delete-bean? Joel McConaughy wrote: Is there a delete equivalent to wb:insert-bean? I'd like to pick up wb:delete-node works for beans and xml files the delete event and do some app-specific processing on the row before what do you mean with 'pickup the delete event?' execution of the binding (load/save) is not triggering any events of this kind it is removed from the repeater with wb:delete-node/ but don't know how to access the row. Thanks. maybe you can explain a bit more off what you try to achieve -marc= -- Marc Portierhttp://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center Read my weblog athttp://blogs.cocoondev.org/mpo/ [EMAIL PROTECTED] [EMAIL PROTECTED] - 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]
RE: Vote: to unify, or not to unify - results
David Leangen dijo: *** [ ] A. I think that we should show users the best way to get up and running with Cocoon. [ X ] B. I think that we should show users all the options possible and let them decide the best approach. [ ] C. Yeah, whatever. Either way is good for me. Peace, man! Because we cannot have a one size shirt for all people ie: If someone need Cocoon as: 1- a publisher framework + 1 feedback form + 1 host book (or whatever). 2- a webapp framework for a small-medium size company 3- a webapp framework for a medium-large (enterprise) size company etc. Then you can make diferents configurations and the best practices are diferent for each one. Some questions are in place before choosing the right tools: What if the user already have implemented or want to use J2EE? What if there is already some work on PHP? Will be the application scalable or not? How easy the scalability will be? Will be deployed on an Application server or just on a Servlet container? And we can continue puting question on the list. From a 1 server bundle all to a full distributed system using J2EE. Then the question is: What is the best practices at all? I prefer to see Cocoon as is on the Website: web glue for your web application development needs That is Cocoon and every one can use it as he need. Best Regards, Antonio Gallardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Passing an input form value to the sitemap
Joe D. Williams wrote: OK. I have done this before, but am confused as to the simplest way to accomplish a fairly trivial task: Passing a request attribute to the sitemap. [snip] The documentation on the SQLTransformer suggests the following: [snip] When I first struggled with this example (not so very long ago), someone off list pointed out that the key was the Request generator feeding an XSL transformation which is passed to the SQL transformer. Warning: The following example was cut and edited from live code but hasn't actually been fully tested. Assuming a URL like this http://my.cocoon.server.ca/search?SearchTerms=Help map:match pattern=*/search map:generate type=request/ map:transform src=Search/Search.xsl / map:transform type=sql map:parameter name=use-connection value=ConnectionName / map:parameter name=show-nr-of-rows value=true/ /map:transform map:transform src=/xsl/SearchtoHTML.xsl map:parameter name=use-request-parameters value=true/ /map:transform map:serialize type=html/ /map:match The Request generator does not get a lot of play but it will hand off an xml representation of the HTML header to the transformer. In the XSLT transformation that follows might look something like: ?xml version=1.0 ? xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform; version=1.0 xmlns:h=http://apache.org/cocoon/request/2.0; xsl:param name=SearchTermsxsl:value-of select=//h:[EMAIL PROTECTED]'SearchTerms']/h:value//xsl:param xsl:template match=/ document sql:execute-query xmlns:sql=http://apache.org/cocoon/SQL/2.0; sql:query name=Main [Your SQL statement with the search parameters xsl:value-of select=$SearchTerms/ substituted in the appropriate place] /sql:query /sql:execute-query !-- and at this point you can include additional queries or XIncludes or other good stuff not in the example -- /document /xsl:template /xsl:stylesheet Presumably there are Good Things one could do in the XSL Transformation to validate the parameters from the URL and to ensure Unpleasant Things didn't come along for the ride. I would *love* to see some examples of the kinds of things people actually do. The XML coming out of this should be ready for the SQLTransformer to act on it. I haven't been following along for long enough to know if the SQLTransformer is considered Due For Deprecation. If it isn't, a use case with URL submitted parameters would be a useful enhancement to the documentation. Walter Lewis virtual Cocoon newbie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
PDF Display Problem with IE
Title: PDF Display Problem with IE I am getting a problem where IE sometimes receives a pdf document from cocoon, but either displays nothing, or displays the content of the pdf document as text (encoded at that). Has anybody else come across this problem? If so, how does one get around it. I've not seen it when loading pdf files from other websites. Closing all IE windows and trying again appears to rectify the problem, but I'd rather not have to tell our users to do that. Regards, John Grange Software Team Leader Tel: +44 (0) 1749 834922 Email: [EMAIL PROTECTED] BlueFinger Limited Underwood Business Park, Wookey Hole Road, Wells, Somerset, BA5 1AF, UK Tel: +44 (0) 1749 834900 Fax: +44 (0) 1749 834902 Mobile: +44 (0) 7876 038058 web: www.bluefinger.com http://www.bluefinger.com Company Reg No: 4209395 Registered Office: 2 Temple Back East, Temple Quay, BRISTOL. BS1 6EG. *** This E-mail contains confidential information for the addressee only. If you are not the intended recipient, please notify us immediately. You should not use, disclose, distribute or copy this communication if received in error. No binding contract will result from this e-mail until such time as a written document is signed on behalf of the company. BlueFinger Limited cannot accept responsibility for the completeness or accuracy of this message as it has been transmitted over public networks.***
Re: Vote: to unify, or not to unify - results
Le 4 mai 04, à 18:39, Nacho Jimenez a écrit : ... The average user does not give a shiling about JXTemplates, JXPath, JEXL or whatever load of letters we decide to acronymize today. The user wants to know how can he set up his ubercool website accessing XML documents and SQL data with the mimimum of fuss, and hence, the document he is looking for is a step by step guide to do that What you're describing is only one of the many use-cases of Cocoon. The beauty of this framework (which is also what can make it difficult to grasp) is that there are so many different ways to use it. Ask five people what Cocoon is, you might well get six answers ;-) -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vote: to unify, or not to unify - results
Nacho Jimenez wrote:
Other than the CPA, we would show other options. For example, if a
newbie
were reading up on JXTemplates, rather than saying that you can use
Jexl or
JXPath, we would choose our CPA (for example, JXPath), but have a
link to a
homologous page that explains the same things, but for Jexl. This would
reduce one more variable, and thus one more possible source of delay or
confusion to a newbie. So new users will be able to get up and
running much
faster, and once they have more experience, will be able to go over the
alternative approaches.
This is just an example of what I think we should avoid... The
average user does not give a shiling about JXTemplates, JXPath, JEXL
or whatever load of letters we decide to acronymize today.
The user wants to know how can he set up his ubercool website
accessing XML documents and SQL data with the mimimum of fuss, and
hence, the document he is looking for is a step by step guide to do that.
In one of those steps, he's shown how to get a needed parameter
from the context, using our recommended method (JXTemplateTransformer,
through a JXPath expression). There, on a side note, you can have an
overview on what JXTemplateTranformer is, why is it our preferred
method to access the parameter he needs and wich alternatives he could
use, and pointers to the wikiPages of the related tecnologies for a
deeper study if he needs it.
I have to disagree a bit here
When I started with cocoon, I wanted to load a simple result set from a
database into an xml file and transform it. simple enough. I wanted to
use jxtemplate .. it was what everyone suggested. but no one it seemed,
could tell me why both ${var} and #{var} both worked.. and in fact in my
use case, one didn't. So I was faced with learning 2 expression
syntaxes, with a deadline facing me. This was a week long agony for me
and I ended up using xsp because there was a n00b tutorial up and I
could make it work. Now, most of my stuff is based on xsp for the
datbase queries. I have moved into other advancements since then like
woody and flow, but now I have to look at refactoring from xsp if I want
to keep up with cocoon develpment. ( Don't get me wrong here, basically
xsp exists to use esql in my mind.. the rumblings of change there are a
good idea )
JD
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vote: to unify, or not to unify - results
Bertrand Delacretaz wrote: Le 4 mai 04, à 18:39, Nacho Jimenez a écrit : ... The average user does not give a shiling about JXTemplates, JXPath, JEXL or whatever load of letters we decide to acronymize today. The user wants to know how can he set up his ubercool website accessing XML documents and SQL data with the mimimum of fuss, and hence, the document he is looking for is a step by step guide to do that What you're describing is only one of the many use-cases of Cocoon. The beauty of this framework (which is also what can make it difficult to grasp) is that there are so many different ways to use it. Ask five people what Cocoon is, you might well get six answers ;-) I know that, of course, but for new users to learn about cocoon, a guided tour of a bunch of common cases would make life a lot easier. Once they learn their way arround they can use all the flexibility of this framework, but I think many people finds too step a learning curve and leaves before even trying. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vote: to unify, or not to unify - results
On Tue, 2004-05-04 at 18:39, Nacho Jimenez wrote: Other than the CPA, we would show other options. For example, if a newbie were reading up on JXTemplates, rather than saying that you can use Jexl or JXPath, we would choose our CPA (for example, JXPath), but have a link to a homologous page that explains the same things, but for Jexl. This would reduce one more variable, and thus one more possible source of delay or confusion to a newbie. So new users will be able to get up and running much faster, and once they have more experience, will be able to go over the alternative approaches. This is just an example of what I think we should avoid... The average user does not give a shiling about JXTemplates, JXPath, JEXL or whatever load of letters we decide to acronymize today. The user wants to know how can he set up his ubercool website accessing XML documents and SQL data with the mimimum of fuss, and hence, the document he is looking for is a step by step guide to do that. In one of those steps, he's shown how to get a needed parameter from the context, using our recommended method (JXTemplateTransformer, through a JXPath expression). (unrelated to the main topic, but couldn't resist) I wouldn't recommend to use the JXTemplateTransformer (unless you have good reasons to), as it is a fake generator, which has the disadvantage that templates can't be cached but need to be compiled on each use. There, on a side note, you can have an overview on what JXTemplateTranformer is, why is it our preferred method to access the parameter he needs and wich alternatives he could use, and pointers to the wikiPages of the related tecnologies for a deeper study if he needs it. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RT] The Bootable Cocoon Demo CD
Has anyone had any luck (or even tried) to create a bootable CD with a working Cocoon/Jetty installed? I've played a little with Knoppix [1], and I was impressed with what they can cram into a single CD. There's even docs about remastering Knoppix to suit your needs [2]. Things to think about: o No writable disk. This means there would be nowhere to put logs and other stuff. Does Knoppix have a ramdisk? o Speed. Not sure if this would be a factor. o Distributing other software. I'm not sure what Sun has to say about distributing their JRE. I think it would be fine. Acrobat Reader would be another must to show off the FOP. SVG viewers are good as well. It would be really cool to pop in a CD, and have the system boot to a web browser with a running instance of Cocoon. I'm not totally sure how useful it would be, but it might be worth at least checking out. WDYT? Tony [1] http://www.knoppix.net/ [2] http://www.knoppix.net/docs/index.php/KnoppixRemasteringHowto - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JXTemplates - what's in a name?
On Tue, 2004-05-04 at 10:39, Derek Hohls wrote: Bruno I apologise then, if I misunderstood what you said. I still do not think that we should use the term template generator in this context. There are generators and there are templates and I don't think their roles should be mixed. That's why I was arguing for two different takes on the current situation - the JXGenerator which sits in the same place that other generators do (eg XSP) and allows access to, and manipulation of, the underlying data; and JXTemplate which is only about the layout and filling in the data. If you are also saying this then we are in agreement! yep, we agree on the goal, though I still notice you persist on the fact that generators would do manipulation of the underlying data. I don't think this has ever been the purpose of generators and thus also XSP. Of course, things can always be misused. If I want I can start an HTTP server or send mail in the toString() mehod of an object. But that's hardly the intended use of toString(). Likewise, if someone implements the business logic and flow control of his/her site in XSP, we can't stop them. With JXTemplate the same: it is meant to use the data available from a few supplied contexts: most importantly the viewData from flowscript, and possibly environment data like the request and session objects. If used in that way, is it still different from the 'real templates'? (Just curious, I haven't found time yet to read the paper) -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RT] The Bootable Cocoon Demo CD
New user here, but i've seen knoppix. comments inline... -kz Tony Collen wrote: Has anyone had any luck (or even tried) to create a bootable CD with a working Cocoon/Jetty installed? I've played a little with Knoppix [1], and I was impressed with what they can cram into a single CD. There's even docs about remastering Knoppix to suit your needs [2]. Things to think about: o No writable disk. This means there would be nowhere to put logs and other stuff. Does Knoppix have a ramdisk? very much so. the memory requirements are fairly large. o Speed. Not sure if this would be a factor. shouldn't be. the initial load might be a bit more, but once loaded, i'm thinking all *should* be well. o Distributing other software. I'm not sure what Sun has to say about distributing their JRE. I think it would be fine. Acrobat Reader would be another must to show off the FOP. SVG viewers are good as well. this i don't know about It would be really cool to pop in a CD, and have the system boot to a web browser with a running instance of Cocoon. I'm not totally sure how useful it would be, but it might be worth at least checking out. WDYT? quite cool indeed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Goovy's News
Consider, also, using the StreamingMarkupBuilder as an XSLT alternative for transforms =) -Brian On May 4, 2004, at 3:15 PM, Bertrand Delacretaz wrote: Le 4 mai 04, à 16:33, olivier demah a écrit : Does someone own some news about Groovy integration in cocoon ? The ScriptGenerator (BSF block) can run Groovy scripts. I've given some pointers [1] about how to integrate the GroovySQL stuff, but haven't heard news about it. I won't have time to work more on this in the near future, unfortunately. -Bertrand [1] http://marc.theaimsgroup.com/?l=xml-cocoon-devm=108327543609640w=2 - 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]
Re: Supersonic block has landed (Power Trio tutorial/example app)
i know that we must not use this list for just for say thank you but this tutorial is great A big thank you from all to Bertrand! Absolute work Just fine!!! lets translate this tutorial to several languages -- stavros On Tue, 4 May 2004, Bertrand Delacretaz wrote: I've just committed the new supersonic block, a tutorial/example app called Supersonic Tour of Apache Cocoon, focused on Pipelines, Flow, Forms (aka the Power Trio). It is accessible from the blocks with samples page if you run the current Cocoon CVS version. The tutorial is meant to be studied independently of other docs, and give a quick overview of the most important components of Cocoon. There are probably a few typos here and there, and I'm no Forms guru (yet..) so enhancements are certainly possible (for example: why does this Calendar link show up next to the date entry fields ;-) Enjoy, and as always feedback and contributions are very welcome! -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Goovy's News
Le 4 mai 04, à 22:07, Brian McCallister a écrit : Consider, also, using the StreamingMarkupBuilder as an XSLT alternative for transforms =) hehe. I've had this fuzzy feeling for a while, that a combination of the EffectPipe (as used to create the EffectWidgetReplacingPipe in the forms block) with scriptable (Groovy) element handlers could be a nice way to write transformers. But unfortunately our days still have no more than 24 hours around here ;-) -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
upcoming Cocoon events?
Hi all, Are there plans for another Cocoon GetTogether in 2004? Or something similar? Lars - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vote: to unify, or not to unify - results
On Tue, 4 May 2004, JD Daniels wrote:
Nacho Jimenez wrote:
Other than the CPA, we would show other options. For example, if a
newbie
were reading up on JXTemplates, rather than saying that you can use
Jexl or
JXPath, we would choose our CPA (for example, JXPath), but have a
link to a
homologous page that explains the same things, but for Jexl. This would
reduce one more variable, and thus one more possible source of delay or
confusion to a newbie. So new users will be able to get up and
running much
faster, and once they have more experience, will be able to go over the
alternative approaches.
This is just an example of what I think we should avoid... The
average user does not give a shiling about JXTemplates, JXPath, JEXL
or whatever load of letters we decide to acronymize today.
The user wants to know how can he set up his ubercool website
accessing XML documents and SQL data with the mimimum of fuss, and
hence, the document he is looking for is a step by step guide to do that.
In one of those steps, he's shown how to get a needed parameter
from the context, using our recommended method (JXTemplateTransformer,
through a JXPath expression). There, on a side note, you can have an
overview on what JXTemplateTranformer is, why is it our preferred
method to access the parameter he needs and wich alternatives he could
use, and pointers to the wikiPages of the related tecnologies for a
deeper study if he needs it.
I have to disagree a bit here
When I started with cocoon, I wanted to load a simple result set from a
database into an xml file and transform it. simple enough. I wanted to
use jxtemplate .. it was what everyone suggested. but no one it seemed,
could tell me why both ${var} and #{var} both worked.. and in fact in my
use case, one didn't. So I was faced with learning 2 expression
syntaxes, with a deadline facing me. This was a week long agony for me
and I ended up using xsp because there was a n00b tutorial up and I
could make it work. Now, most of my stuff is based on xsp for the
datbase queries. I have moved into other advancements since then like
woody and flow, but now I have to look at refactoring from xsp if I want
to keep up with cocoon develpment. ( Don't get me wrong here, basically
xsp exists to use esql in my mind.. the rumblings of change there are a
good idea )
JD
let me put here my two cents
for select queries xsp/esql is great and the perfect _in_most_cases_ way
in most cases we create pipelines that make select queries and return the
content in xml format. then we call this pipelines in most cases internal.
--stavros
-
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]
RE: Vote: to unify, or not to unify - results
I'm confused by your statement. Did you mean that xsp/esql is perfect in most cases for you (and your product website), or that you feel it is the best way to perform an SQL query and that it should be recommended to everyone? Ralph -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 04, 2004 2:14 PM To: [EMAIL PROTECTED] Subject: Re: Vote: to unify, or not to unify - results let me put here my two cents for select queries xsp/esql is great and the perfect _in_most_cases_ way in most cases we create pipelines that make select queries and return the content in xml format. then we call this pipelines in most cases internal. --stavros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Vote: to unify, or not to unify - results
i recommend the use of xsp/esql --- xml when the needs are select only queries it very simple/clean and cover the needs in most cases i dont recommend this approach for update queries. --stavros On Tue, 4 May 2004, Ralph Goers wrote: I'm confused by your statement. Did you mean that xsp/esql is perfect in most cases for you (and your product website), or that you feel it is the best way to perform an SQL query and that it should be recommended to everyone? Ralph -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 04, 2004 2:14 PM To: [EMAIL PROTECTED] Subject: Re: Vote: to unify, or not to unify - results let me put here my two cents for select queries xsp/esql is great and the perfect _in_most_cases_ way in most cases we create pipelines that make select queries and return the content in xml format. then we call this pipelines in most cases internal. --stavros - 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]
design questions/need ideas
I have been starting to use cocoon for my personal web site, and I am becoming quite fond of it... Congrats go out to all devs. I have a few apps i'd like to build, and either I am too new to cocoon to understand all that i should, or what I want to do is stupid. In any case, here we go. I would like to write an application to create a local cache of certain websites i like to monitor. The flow of the application is that the first time a user requests a certain resource, the server goes out and queries the web for it. It uses xslt, etc, etc to transform the source, and then stores it locally for future use. The locally stored copy is then sent out to the users. The local copy is never updated once it is successfully aquired one time. So, with that in mind, the questions... 1. Is the best way to do the download and save step to create an action, and run this action conditionally in a resource-exists selector? Is there a better way, or preferably one that I could do (being my lazy self) without writing java/perl code, but just add stuff to the sitemap? 2. I have a list of resources available. I want the user to be able to view them all on one page (all as in all for the day), or each individually. Ideally, I would store these resources in an xml file, and generate the list with xslt. But my sitemap also needs an entry for each of these. I tried to do this: map:match pattern=resourses.xmap ... map:serialize type=xml/ /map:match map:mount uri-prefix= check-reload=yes src=cocoon:/resourses.xmap/ but it failed. Interestingly enough it knew if a resource was available or not, but simply returned a blank page. I am assuming from reading archives of the list that this is not supported, but I was wondering what is the best way to do this? The resource list needs to store various properties like a name, an originating url, etc. I thought about saving this all in the sitemap, and then using xslt to parse the sitemap file to create the list that contains them all, but couldn't think where to store the url and things like that. So, any assistance would be kindly appreciated, and once again I love the app. thanks, -kz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Vote: to unify, or not to unify - results
If you aren't familiar with these already, please take the time to read some of these. While any application that uses SQL can be vulnerable to this, using SQL in the Web container typically will increase your risk (not simply because you are in the web container, but because multi-tiered systems typically (or should) have more parameter validation). http://www.4guysfromrolla.com/webtech/061902-1.shtml http://www.securiteam.com/securityreviews/5DP0N1P76E.html http://www.spidynamics.com/papers/SQLInjectionWhitePaper.pdf http://www.ebcvg.com/articles.php?id=210 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 04, 2004 2:40 PM To: '[EMAIL PROTECTED]' Subject: RE: Vote: to unify, or not to unify - results i recommend the use of xsp/esql --- xml when the needs are select only queries it very simple/clean and cover the needs in most cases i dont recommend this approach for update queries. --stavros On Tue, 4 May 2004, Ralph Goers wrote: I'm confused by your statement. Did you mean that xsp/esql is perfect in most cases for you (and your product website), or that you feel it is the best way to perform an SQL query and that it should be recommended to everyone? Ralph -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 04, 2004 2:14 PM To: [EMAIL PROTECTED] Subject: Re: Vote: to unify, or not to unify - results let me put here my two cents for select queries xsp/esql is great and the perfect _in_most_cases_ way in most cases we create pipelines that make select queries and return the content in xml format. then we call this pipelines in most cases internal. --stavros - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Supersonic block has landed (Power Trio tutorial/example app)
On 04 May 2004, at 19:35, Bertrand Delacretaz wrote: I've just committed the new supersonic block, a tutorial/example app called Supersonic Tour of Apache Cocoon, focused on Pipelines, Flow, Forms (aka the Power Trio). Thanks a lot for this, Bertrand. I like the name and of course the Power Trio term. :-) /Steven -- Steven Noelshttp://outerthought.org/ Outerthought - Open Source Java XMLAn Orixo Member Read my weblog athttp://blogs.cocoondev.org/stevenn/ stevenn at outerthought.orgstevenn at apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Doctype declaration missing
Hi Sarah. That looks correct to me. So I don't know what's going wrong now, sorry. Have you changed the source document? Cocoon may still be serving a previously-serialized file from its cache, so it may be an idea to clear or invalidate the cache, if you haven't already. -Original Message- From: Sarah Haff [mailto:[EMAIL PROTECTED] Sent: Wednesday, 5 May 2004 3:00 a.m. To: [EMAIL PROTECTED] Subject: RE: Doctype declaration missing Con, Thanks for the reply. In my sitemap, I do have: map:serializer name=docbook mime-type=text/xml; charset=iso-8859-1 src=org.apache.cocoon.serialization.XMLSerializer doctype-public//OASIS//DTD DocBook XML V4.2//EN/doctype-public doctype-systemhttp://docbook.org/xml/4.2/docbookx.dtd/docty pe-system encodingiso-8859-1/encoding /map:serializer and map:serialize type=docbook/ in the pipeline section. But the output has not Doctype Declaration. Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wb:delete-bean?
On May 4, 2004, at 10:54 AM, Joel McConaughy wrote: I'm using hibernate/cforms to build simple CRUD pages. Have you seen the alternative acronymn?: Create/Read/Amend/Purge :-) These take the results from a query and create an ArrayList of beans, display a page worth of rows in a repeater, allow in place editting, and persist the results back to the database. Hibernate handles row updates automatically. Insertions are handled in the flow by explicitly calling a hibernate save operation on any row with a null ID. Deletions are the problem. Hibernate requires that I explicitly call a delete method for each deleted row. Cforms doesn't keep track of deleted rows within a repeater so I believe that I need to do this as each delete event is fired. However, I don't know how to access the row inside the wb:on-delete tag or how to call some external Java from there. May be there's an easier way to accomplish this? I know you can do it with the v2 forms/flow API... see the flowscript in the v2 samples directory. There might be a way to do it with the wb:on-delete way, but I'll let somebody else answer that 'cause I don't know! :-) ~mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RT] The Bootable Cocoon Demo CD
Tony, this works quite good. One year ago we remastered Knoppix to put the http://www.mobiharz.de site within knoppix. Things to think about: o No writable disk. This means there would be nowhere to put logs and other stuff. Does Knoppix have a ramdisk? It has, as the other posts already mentioned. I wrote some startup scripts which put all the writeable things into ramdisk. As the mobiharz system needed a postgres database we even took the database into ram disk! o Speed. Not sure if this would be a factor. Of course it is slower but satisfied our needs for demonstration issues. o Distributing other software. I'm not sure what Sun has to say about distributing their JRE. I think it would be fine. Acrobat Reader would be another must to show off the FOP. SVG viewers are good as well. Thats a problem to my mind. You carefully have to study the licensing agreements about that. Have you considered other software like JRE from http://www.blackdown.org or xpdf? -- Harald Wehr Institut für Tourismus- und Geo-Informationssysteme GmbH Sitz: Friedrichstrasse 57-59 38855 Wernigerode Büro: Gießerweg 5 38855 WernigerodeWeb: http://www.itgis.com Tel: 03943/557807 Fax: 03943/557808 Das Internet-Lexikon Knowlex - Ein Service der ITGIS GmbH http://www.knowlex.org Privat: http://www.harald-wehr.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
