Re: is this kosher?
Couple of thoughts here. First, if you are suggesting adding an extra parameter to the signature call of the setup method, that won't work. I don't think that is what you are asking, but I'd thought I'd address it anyway. Second, I think there is a slightly different way to go about doing this. Have your HTTPTransformer dump the response code and any other relevant data into an XML structure, and put this structure BOTH in the pipeline and in the session. (You could also just use a simple session attribute like HTTPTransformer-RESPONSE-CODE) This lets users of your HTTPTransformer either use another transformer to deal with the response codes, or use actions,selectors, etc to deal with the response, as they all have access to the session. I am defintely more partial to actions, as they can do all the work of a selector and more. I don't know if it is possible or not, but your HTTPTransformer could also be rewritten as an action, which would let it do it's work and return the response code all in one shot. If all your HTTPTransformer takes in is an href and a method, this wouldn't be a huge deal. Irv David Kavanagh wrote: I've written this HTTPTransformer which takes some simple XML containing link information (href, method) and returns either html (run through JTidy), xml (from the web server), or xml containing the location of the file that was downloaded (if type wasn't text/html* or text/xml*). Now, I'd like to be able to return the HTTP response code in a way that would let a selector decide what to do next. Would it be taboo to add a parameter to those passed in via the setup() method on AbstractSAXTransformer? Would that parameter even become available, or is this one just a private copy? I was thinking I'd also write a simple selector (like the ParameterSelector) which would take a list of strings to be tested (i.e. test=one|two|three|four). That way, I can check for a bunch of return codes. The other option is to write a selector that understands some better expressions like test=param500 param =400. Please tell me if I'm barking up the wrong tree, or of someone has already implemented something like I'm talking about. I do have the HTTPTransformer working, I just need to address the return code issue. I'd prefer to have the sitemap define the action based on result code. Thanks, David - 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: XUpdate
When running this, I get Failed to update resource xmldb-object-id: 1 The sitemap log file says it cannot compile the query. What is the oid supposed to be? I don't have anything that seems to match up, or does that even matter? Irv Josema Alonso wrote: Irv, I remember I built the javadoc that came with the transformer and it was pretty easy to use starting there. I suggest you do the same. Anyway if you want a snippet I can give you this. The transformer is declared in the sitemap this way: map:transformer name=xmldb src=org.apache.cocoon.transformation.XMLDBTransformer driverorg.apache.xindice.client.xmldb.DatabaseImpl/driver basexmldb:xindice:///db/base /map:transformer Then is used on a pipeline like any other transformer. The syntax it uses for XUpdate queries for example is: xindice:query type=update oid=xmldb-object-id xu:modifications version=1.0 xmlns:xu=http://www.xmldb.org/xupdate; xu:remove select=/person/[EMAIL PROTECTED] = 'home']/ xu:update select=/person/[EMAIL PROTECTED] = 'work'] 480-300-3003 /xu:update /xu:modifications /xindice:query As I said is pretty straightforward. Hope it helps. - Original Message - From: Irving Salisbury To: [EMAIL PROTECTED] Sent: Sunday, March 09, 2003 5:38 AM Subject: Re: XUpdate This is great news. I don't suppose there are any preliminary docs on this as far as what type of XML it is looking for, etc? I can go rooting around in the source, but any docs or even any examples that make use of it would be a huge help. Thanks, Irv Josema Alonso wrote: Hey, Irv There's a XMLDBTransformer available. It was in Scratchpad but it was moved to a new xmldb block in the CVS repository. Please, checkout a fresh 2.1 from CVS and you'll foun it there or at its block: http://cvs.apache.org/viewcvs.cgi/xml-cocoon2/src/blocks/xmldb/ I have used it succesfully quite a while ago. Best, Josema. - Original Message - From: Irving Salisbury [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, March 08, 2003 7:54 PM Subject: XUpdate I am interested in using xupdate commands to xindice from within Cocoon. First, is there something like an XUpdateTransformer that would allow me to do this within a pipeline? If not, are there any actions, etc that help out? If anyone has any links that would be helpful, that would be great. Thanks, Irv - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SQLTransformer stored procedure question
I call an existing stored procedure with: sql:execute-query sql:query isstoredprocedure=true begin qChange.R_IMS_CHANGE( 'ALZHEIMERS', '1999 Q3', 'NRX', ?); end; /sql:query sql:out-parameter sql:nr=1 sql:name=resultset sql:type=oracle.jdbc.driver.OracleTypes.CURSOR/ /sql:execute-query However, I get an ORA-08103: object no longer exists error at SQLTransformer:1250. This line looks like it is simply calling getObject on the CallableStatement. Any reason why I might be getting this ? Thanks, Irv - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Xindice question
I thought I had followed the directions at cocooncenter for setting up xindice on my box with cocoon, but I am getting: org.xmldb.api.base.XMLDBException: Collection No IndexManager at org.apache.cocoon.components.source.XMLDBSource.resourceToSAX(XMLDBSource.java:215) at org.apache.cocoon.components.source.XMLDBSource.toSAX(XMLDBSource.java:175) at org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:143) This is really stumping me. I am currently running with JDK1.4 and Cocoon 2.0.4. What is this IndexManager, and why isn't mine working ;-) Irv - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Xindice question
Just solved my own problem. Turns out I simply needed to add a trailing slash to my xmldb URL string. You'd think that this would be a pretty common problem. Irv Irv Salisbury III wrote: I thought I had followed the directions at cocooncenter for setting up xindice on my box with cocoon, but I am getting: org.xmldb.api.base.XMLDBException: Collection No IndexManager at org.apache.cocoon.components.source.XMLDBSource.resourceToSAX(XMLDBSource.java:215) at org.apache.cocoon.components.source.XMLDBSource.toSAX(XMLDBSource.java:175) at org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:143) This is really stumping me. I am currently running with JDK1.4 and Cocoon 2.0.4. What is this IndexManager, and why isn't mine working ;-) Irv - 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]
SQLTransformer modifications
We'd like to use paging in our application from the result sets returned from the SQLTransformer. However, with a number of our queries returning 20,000+ rows, it seems like the current Paginator will not cut it for us. This is mainly because it looks like the Paginator expects all of the data to be there, which we don't want it to be. What we'd like to do is to take advantage of the setFetchSize() stuff in the Statement object, and the fact that the drivers we are using implement this properly. So, in essence, the driver will only go and get the number of rows we want, and when we go past that number of rows, it will go and fetch N number more. To do this, we have to do our paginating by using the ResultSet directly. I have been wrestling with this and looking at the code for SQLTransformer to see if I could extend it to do this. Basically, set the fetch size on the Statement object before querying. I also then need to put the ResultSet object into my session so I can retrieve it with my paginating transformer. Upon looking at this, it doesn't seem like there is a good way to tap into the SQLTransformer to do this. It seems like another alternative would be to just copy the source code for SQLTransformer and tap in where I need to. Seems pretty nasty, but would get me where I want to go. So, I'd love feedback on this, as well as any thoughts from people that might have tackled this before. Irv - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Reporting Engine
I have been tasked to build/find/modify a reporting engine inside cocoon. I have looked at the POI project, and it will not fit, as we don't want Excel to be the client. I am hoping for any information on any engines that people have used inside cocoon, or if anyone knows of any engines that are XML based that could be integrated. Our ideal solution would be: 1. Has an XML based template mechanism to let end users create templates. 2. Uses XSL to translate to HTML/PDF. (We can build these, but if the engine has them already, great) 3. Has a mechanism for plugging in SQL into the pipeline for the data to put in the template. (We can build this as well, but if it is already in there, great) Thanks in advance for any info. Irv - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reporting Engine
Thanks for the info. This looks really good. Any other things I should know about this before digging in? Irv Sean McKaharay wrote: xReporter...I am using xReporter right now. It takes a little time to understand all the stylesheets but I think it works great for reporting. Check it out: http://xreporter.cocoondev.org/index.html -Original Message- From: Irv Salisbury III [mailto:[EMAIL PROTECTED]] Sent: Mon 2/10/2003 1:41 PM To: [EMAIL PROTECTED] Cc: Subject: Reporting Engine I have been tasked to build/find/modify a reporting engine inside cocoon. I have looked at the POI project, and it will not fit, as we don't want Excel to be the client. I am hoping for any information on any engines that people have used inside cocoon, or if anyone knows of any engines that are XML based that could be integrated. Our ideal solution would be: 1. Has an XML based template mechanism to let end users create templates. 2. Uses XSL to translate to HTML/PDF. (We can build these, but if the engine has them already, great) 3. Has a mechanism for plugging in SQL into the pipeline for the data to put in the template. (We can build this as well, but if it is already in there, great) Thanks in advance for any info. Irv - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Training others on Cocoon - suggestions?
Derek, I tried to send a PDF of the training that we used, but it was too large for the list to accept. (It is 288K) Send me an email directly if you want it. Here are the topics in it: 1. Basics a. Directory Structure b. cocoon.xconf c. web.xml d. sitemap e. pipeline basics f. built in generators g. built in transformers h. built in serializers i. protocols (cocoon, context, etc) j. lab 2. Custom components a. Selectors b. actions c. transformers d. generators e. avalon interfaces f. lab 3. XSP a. basics b. advanced c. lab I also have a PDF of our XLST training, but it is too large as well. I can send it to you directly if you want. Irv Derek Hohls wrote: Thanks Bertrand I know I always make the mistake of trying to cover too much! OTOH, when you say your students did not cope with using all the different components involved without understanding any of them in detail (at first). I smile because thats *exactly* the way I do learn; trying things out to see if they work and only worrying about understanding much later - that way I quickly build up a big picture without being bogged down. Derek [EMAIL PROTECTED] 06/02/2003 04:43:39 I am planning on covering XSLT in the first part, as their skills are weak in this field and I believe this is a key topic for effective use of Cocoon. I don't know your public, but what I've found when mentoring or teaching people to use Cocoon is that they are often overwhelmed by the many different technologies and skills involved. IMHO you can do a lot with some XSLT, some sitemap config, some log exploration skills, etc. without having to go deep in any of these at first. What my students/colleagues found distracting was using all the different components involved without understanding any of them in detail (at first). OTOH I think it's a good idea to start with some XSLT, which can be disturbing enough for people to warrant being treated separately from Cocoon. Hope this helps, Bertrand - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner http://www.mailscanner.info/, and is believed to be clean. The CSIR exercises no editorial control over E-mail messages and/or attachments thereto/links referred to therein originating in the organisation and the views in this message/attachments thereto are therefore not necessarily those of the CSIR and/or its employees. The sender of this e-mail is, moreover, in terms of the CSIR's Conditions of Service, subject to compliance with the CSIR's internal E-mail and Internet Policy. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Training others on Cocoon - suggestions?
Our whole training environment here at DOTech is actually based on Cocoon. We write our slides in XML and use Cocoon to transform them while training into HTML. It works great and people love it here. We also use XSL:FO to transform them to PDF for printing. It is a little rough around the edges, but I'll see if I can get the thing hosted on our company's website. As a minimum, I can at least get the PDFs up there later. Irv Steve Homer wrote: Would it be possible to have these two pdf's hosted somewhere? Tutorial material on XSLT and Cocoon would be very useful for me. Thanks Steve -Original Message- From: Irv Salisbury III [mailto:[EMAIL PROTECTED]] Sent: 06 February 2003 15:00 To: [EMAIL PROTECTED] Subject: Re: Training others on Cocoon - suggestions? Derek, I tried to send a PDF of the training that we used, but it was too large for the list to accept. (It is 288K) Send me an email directly if you want it. Here are the topics in it: 1. Basics a. Directory Structure b. cocoon.xconf c. web.xml d. sitemap e. pipeline basics f. built in generators g. built in transformers h. built in serializers i. protocols (cocoon, context, etc) j. lab 2. Custom components a. Selectors b. actions c. transformers d. generators e. avalon interfaces f. lab 3. XSP a. basics b. advanced c. lab I also have a PDF of our XLST training, but it is too large as well. I can send it to you directly if you want. Irv Derek Hohls wrote: Thanks Bertrand I know I always make the mistake of trying to cover too much! OTOH, when you say your students did not cope with using all the different components involved without understanding any of them in detail (at first). I smile because thats *exactly* the way I do learn; trying things out to see if they work and only worrying about understanding much later - that way I quickly build up a big picture without being bogged down. Derek [EMAIL PROTECTED] 06/02/2003 04:43:39 I am planning on covering XSLT in the first part, as their skills are weak in this field and I believe this is a key topic for effective use of Cocoon. I don't know your public, but what I've found when mentoring or teaching people to use Cocoon is that they are often overwhelmed by the many different technologies and skills involved. IMHO you can do a lot with some XSLT, some sitemap config, some log exploration skills, etc. without having to go deep in any of these at first. What my students/colleagues found distracting was using all the different components involved without understanding any of them in detail (at first). OTOH I think it's a good idea to start with some XSLT, which can be disturbing enough for people to warrant being treated separately from Cocoon. Hope this helps, Bertrand - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner http://www.mailscanner.info/, and is believed to be clean. The CSIR exercises no editorial control over E-mail messages and/or attachments thereto/links referred to therein originating in the organisation and the views in this message/attachments thereto are therefore not necessarily those of the CSIR and/or its employees. The sender of this e-mail is, moreover, in terms of the CSIR's Conditions of Service, subject to compliance with the CSIR's internal E-mail and Internet Policy. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
