Java version

Hi everybody, I noticed, that my compiled block has always java version 1.5. I need it with 1.4. What should I do? I build my block by mvn install. cheers Johannes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional

RE: Java version

In the pom, You can define a the plugin below and just set the source and target to your needs. Cheers, Robby Pelssers build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.0/version

Re: Java version

Hi Robby, thank you for your quick reply, but It doesn't work. I added: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.0/version configuration source1.4/source target1.4/target

Re: Java version

I did it. I changed my environment variable JAVA_HOME to 1.4. Nevertheless I would be happy if some one knows another solution how to configure the maven build. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional

Re: Java version

Well, you can't say that it is solved. When I want to build my webapp, I have to switch to 1.5 again. Otherwise I get fatal errors. What I am wondering is, that cocoon hasn't a maven-compiler-plugin by default, so it doesn't need this, or? Robby Pelssers schrieb: Strange that the

Re: Java version

;) Yes, and you can't say that it is solved twice because tomcat 5.0 with 1.4 doesn't want to start the application... cheers Johannes Hoechstaedter schrieb: Well, you can't say that it is solved. When I want to build my webapp, I have to switch to 1.5 again. Otherwise I get fatal errors.

How to access configuration files and properties after packaging

Hi everybody, in my cocoon block I have some configuration files in the resource/external directory, which I want to be accessible by the admin of the application even when I compiled the block, and put it as webapp into my Tomcat. Till now these files are packed correctly into the block jar

Re: Java version

Hi, now here is a solution I can live with: I have edited: the maven-jar-plugin and simply added Build-Jdk1.4/Build-Jdk to the manifest. That works for me. bye - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional

Re: Java version

End of thred is, that I have Error creating bean with name 'de.memocomp.myBlock1.service' running my webapp on Tomcat 5.0 with java 1.4. Everything was fine with Tomact 5.5 and java 1.5. Johannes Hoechstaedter schrieb: Hi, now here is a solution I can live with: I have edited: the

Re: Passing a node-set from XSLT to Java

Hi Luca/All, Sorry. On further testing, we're still not getting through the full tree fragment to Java. I've adapted the java method to give details of what it receives: public String addGML(org.w3c.dom.Node myNode) { System.out.println(Class = +node.getClass().getName());

RE: How to access configuration files and properties after packaging

Here is one way that seems to work. Make a separate set of configuration for development and the default for production. \src\main\resources\META-INF\cocoon\properties\config.properties \src\main\resources\META-INF\cocoon\dev\properties\config.properties and run during development with mvn

Re: How to access configuration files and properties after packaging

2008/7/3 Robin Rigby [EMAIL PROTECTED]: Here is one way that seems to work. Make a separate set of configuration for development and the default for production. \src\main\resources\META-INF\cocoon\properties\config.properties

Re: How to access configuration files and properties after packaging

Robin Rigby schrieb: Here is one way that seems to work. Make a separate set of configuration for development and the default for production. \src\main\resources\META-INF\cocoon\properties\config.properties \src\main\resources\META-INF\cocoon\dev\properties\config.properties and run during

RE: How to access configuration files and properties after packaging

ok. Depends what the config does. In my case, there would be an ugly crash before any damage could be done. btw. I think that should have been \src\main\resources\META-INF\cocoon\properties\config.properties \src\main\resources\META-INF\cocoon\properties\dev\config.properties Robin

RE: How to access configuration files and properties after packaging

Try a third set of resources, that are not packaged in the war file, in addition to internal and external. The path to them can be configured as I described. The sitemap does something like: map:pipeline id=non-war-resource map:match pattern=resource/nonwar/** map:read

Re: How to access configuration files and properties after packaging

Your right. I don't want to configure important properties during runtime. My aim is an application which is easy configurable by the sysadmin without the need for compilation. For example when the system is down some properties or some some resources (table decriptors for example) should be

Re: How to access configuration files and properties after packaging

How can I access the web-inf folder? Robin Rigby schrieb: Try a third set of resources, that are not packaged in the war file, in addition to internal and external. The path to them can be configured as I described. The sitemap does something like: map:pipeline id=non-war-resource

XSLT Version?

Hi All, Simple question, I hope. How do I find out which version of XSLT I've got? My version of Cocoon is: 2.1.10, if it's related to that. Ultimately, I'd like to be using XSLT 2.0. Thanks, Andy - To unsubscribe,

Re: How to access configuration files and properties after packaging

I use properties to define my database connection. I my development environment I add my properties into block rcl.properties and I can test blocks individually with jetty. rcl.properties file is not included in block jar file. In my application I created cocoon/

Re: XSLT Version?

2008/7/3 Andrew Chamberlain [EMAIL PROTECTED]: Hi All, Simple question, I hope. How do I find out which version of XSLT I've got? Try using some XSLT 2-only features in a pipeline and see if you get a stack trace instead? ;-) My version of Cocoon is: 2.1.10, if it's related to that.

Access Cocoon User-Object from outside Cocoon?

Hi, I am currently optimizing an application I have developed and am currently trying to create a Servlet, that bypasses Cocoons Pipeline-Stuff. The reason for this is that my application has an instant messenger component, that checks for new messages every 6 seconds. With 100 Users online,

Re: XSLT Version?

Hi Andy, Thanks for that. Yes - I'm using Xalan as provided with the sample webapp. I think your suggestion of setting up Saxon in parallel to Xalan is probably the best option, as I don't want to affect the other pipelines we have running. Thanks again, Andy Andy Stevens wrote:

Re: How to access configuration files and properties after packaging

Hi, that mechanism with the property file works. Thumbsup :) For a strange reason I have the porty file in my jar file and in the expected folder, although I have deleted it from my block. My second question is still, how I can access some folders outside of my jar by the pointed out

Re: Passing a node-set from XSLT to Java

Andrew Chamberlain wrote: Hi Luca/All, Sorry. On further testing, we're still not getting through the full tree fragment to Java. I've adapted the java method to give details of what it receives: public String addGML(org.w3c.dom.Node myNode) { System.out.println(Class =

Re: Passing a node-set from XSLT to Java

Andrew Chamberlain wrote: The last line (which uses the getTextContent() method) throws the following exception: javax.xml.transform.TransformerException: java.lang.AbstractMethodError: org.apache.xml.dtm.ref.DTMNodeProxy.getTextContent()Ljava/lang/String; at

Re: XSLT Version?

Andrew Chamberlain wrote: Hi All, Simple question, I hope. How do I find out which version of XSLT I've got? My version of Cocoon is: 2.1.10, if it's related to that. Ultimately, I'd like to be using XSLT 2.0. Thanks, Andy Insert something like the following into a stylesheet: