The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc) that do not relate to the official business of this company shall be understood as neither given nor endorsed by it. IG Group Holdings plc is a company registered in England and Wales under number 04677092. VAT registration number 761 2978 07. Registered Office: Cannon Bridge House, 25 Dowgate Hill, London EC4R 2YA. Listed on the London Stock Exchange. Its subsidiaries IG Markets Limited and IG Index Limited are authorised and regulated by the Financial Services Authority (IG Markets Limited FSA registration number 195355 and IG Index Limited FSA registration number 114059).

On 02/10/2012 10:13 AM, Barbara Rosi-Schwartz wrote:

Hello everyone.

 

I want to use the Spring Configurator to configure access ports for my JMX MBeans, with ports changing for the different development environments.

 

The spring configuration file contains the following:

 

<bean id="featureLauncherMBean"

            class="com.iggroup.wb.core.featurelauncher.internal.DefaultFeatureLauncher"

            init-method="init" destroy-method="dismissAllFeatures">

</bean>

 

<util:map id="exposedMBeans">

      <entry key="bean:type=featureLauncherMBean,name=remoteJMX"

            value-ref="featureLauncherMBean" />

</util:map>

 

<bean id="mBeanExporter" class="org.springframework.jmx.export.MBeanExporter"

      p:beans-ref="exposedMBeans" p:assembler-ref="assembler" />

 

<util:list id="manageableInterfaces">

      <value>com.iggroup.wb.core.featurelauncher.api.FeatureLauncherMBean</value>

</util:list>

 

<bean id="assembler"

      class="org.springframework.jmx.export.assembler.InterfaceBasedMBeanInfoAssembler"

      p:managedInterfaces-ref="manageableInterfaces" />

 

<bean id="registry" class="org.springframework.remoting.rmi.RmiRegistryFactoryBean"

      p:port="1099" />

 

<bean id="serverConnector"

      class="org.springframework.jmx.support.ConnectorServerFactoryBean"

      depends-on="registry" p:objectName="connector:name=rmi"

      p:serviceUrl="service:jmx:rmi://localhost/jndi/rmi://localhost:1099/jmxrmi" />

 

The first bean, featureLauncherMBean,  is the one I work with directly but the ones that contain the environment dependent properties are registry (port property) and serverConnector (serviceUrl property).These beans are just part of the wiring and  I cannot access them directly.

 

How would I go about using the Configurator to get port and serviceUrl to point to the right port values depending upon the environment?

Use running modes to store the properties
http://cocoon.apache.org/subprojects/configuration/1.0/spring-configurator/2.0/1309_1_1.html
http://cocoon.apache.org/subprojects/configuration/1.0/spring-configurator/2.0/1310_1_1.html

so you have something like
src/main/resources/META-INF/cocoon/properties/
and in there a prod.properties (1) file and in a dev (RUNNING_MODE) folder the same file (2) with another url.

put in (1) serviceUrl=service:jmx:rmi://localhost/jndi/rmi://localhost:1099/jmxrmi
and in (2) e.g. serviceUrl=service:jmx:rmi://myhost/jndi/rmi://localhost:666/jmxrmi

and then simply p:serviceUrl="${serviceUrl}"  in your spring file.

HTH

salu2

 

TIA,

B.

 

BARBARA ROSI-SCHWARTZ

Senior Developer

 

IG Group|Cannon Bridge House

25 Dowgate Hill|London|EC4R ZYA

 

t: +44(0)20 7573 0208 (Direct)

t: +44(0)20 7896 0011 (Switchboard)

w: www.iggroup.com

 

The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc) that do not relate to the official business of this company shall be understood as neither given nor endorsed by it. IG Group Holdings plc is a company registered in England and Wales under number 04677092. VAT registration number 761 2978 07. Registered Office: Cannon Bridge House, 25 Dowgate Hill, London EC4R 2YA. Listed on the London Stock Exchange. Its subsidiaries IG Markets Limited and IG Index Limited are authorised and regulated by the Financial Services Authority (IG Markets Limited FSA registration number 195355 and IG Index Limited FSA registration number 114059).

-- Thorsten Scherler <scherler.at.gmail.com> codeBusters S.L. - web based systems <consulting, training and solutions> http://www.codebusters.es/

The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc) that do not relate to the official business of this company shall be understood as neither given nor endorsed by it. IG Group Holdings plc is a company registered in England and Wales under number 04677092. VAT registration number 761 2978 07. Registered Office: Cannon Bridge House, 25 Dowgate Hill, London EC4R 2YA. Listed on the London Stock Exchange. Its subsidiaries IG Markets Limited and IG Index Limited are authorised and regulated by the Financial Services Authority (IG Markets Limited FSA registration number 195355 and IG Index Limited FSA registration number 114059).

On 02/10/2012 12:27 PM, Barbara Rosi-Schwartz wrote:

Hi.

 

I know the Spring Configurator can be used to transparently handle properties that are environment dependent. Is it possible to use it also to choose a specific spring config file depending upon the environment?

http://cocoon.apache.org/subprojects/configuration/1.0/spring-configurator/2.0/1312_1_1.html

HTH

salu2

 

TIA,

B.

 

BARBARA ROSI-SCHWARTZ

Senior Developer

 

IG Group|Cannon Bridge House

25 Dowgate Hill|London|EC4R ZYA

 

t: +44(0)20 7573 0208 (Direct)

t: +44(0)20 7896 0011 (Switchboard)

w: www.iggroup.com

 

The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc) that do not relate to the official business of this company shall be understood as neither given nor endorsed by it. IG Group Holdings plc is a company registered in England and Wales under number 04677092. VAT registration number 761 2978 07. Registered Office: Cannon Bridge House, 25 Dowgate Hill, London EC4R 2YA. Listed on the London Stock Exchange. Its subsidiaries IG Markets Limited and IG Index Limited are authorised and regulated by the Financial Services Authority (IG Markets Limited FSA registration number 195355 and IG Index Limited FSA registration number 114059).

-- Thorsten Scherler <scherler.at.gmail.com> codeBusters S.L. - web based systems <consulting, training and solutions> http://www.codebusters.es/

Hello,

We've been Cocoon 2.1.* users for years. We're now trying to shift to the Cocoon 3 way of doing things.
I barely understand Maven, but I'm willing to learn.

I've installed Cocoon 3, and can run a sample.

But now I'm having trouble figuring out how to build my own "hello world" web application.

What I did so far:

     cd c3
I can then access the running databases sample at
    http://localhost:8888/
in the browser.

I've generated the four Maven 2 archetypes as instructed at http://cocoon.apache.org/3.0/download.html
(sample, block, webapp, parent).
I don't understand, though, what each one is for.

For archetype-block, the instruction says "Create an empty Cocoon 3 block in order to create your own Cocoon 3 web application."
But once I've done that, what do I do in the generated block in order to create a web application?

For archetype-webapp, it says "Create an empty Java web application project. After that add your Cocoon block as dependency." I guess Cocoon block refers to the previous thing I generated. How do I add it as a dependency? I guess I should edit cocoon-archetype-webapp/pom.xml and add this before </project>:
  <dependencies>
    <dependency>
      <groupId>org.apache.cocoon.archetype-block</groupId>
      <artifactId>cocoon-archetype-block</artifactId>
    </dependency>
  </dependencies>

For archetype-parent, the instruction says "Create a parent module for your Cocoon project." Is a project the same as a web application? Does this mean I should edit the contents of <parent> in archetype-webapp/pom.xml to point correctly to archetype-parent? (The <parent> element is present already, but its groupId, artifactId, and relativePath are a bit off from what would match the parent archetype generated by the instructions.)


**The main thing I want to know, though,** is where do I start building a sitemap?
In the working databases sample that I mentioned above, the only place I find a sitemap is under target/samples/COB-INF.
But the generated archetype-webapp/ folder doesn't have a target subfolder structure. Is that something I generate using a maven command?

Thanks!
I look forward to using C3, and I feel like if I can get past this point, I'll be able to start cooking.

Lars

Hi Lars,

The instructions on the site are obscure because they presuppose a good deal of Maven knowledge.
Maven helps you to build the project: it puts all the files you need together and at first it feels metaphysical
(hey, will you let me control my own build?).

But here's what I do:

ThingToKnow1:  the elements you want to expose, and your sitemap are in the "block". Your "cocoon webapp"
is going to "mount" (my word choice) the blocks on a virtual path.
ThingToKnow2:  You control Mavens behaviour through editing pom.xml. Add your Cocoon block as dependency means that you are going to edit the pom.xml.

1.   create the webapp from the archetype. The webapp contains close to nothing.
      It will contain close to nothing. It should contain the "canonical structure" of a web project:
          pom.xml
          main
          main/resources
          main/webapp
          main/webapp/WEB-INF
          main/webapp/WEB-INF/applicationContext.xml
          main/webapp/WEB-INF/log4j.xml
          main/webapp/WEB-INF/web.xml 

Edit pom.xml, you will see the section "dependencies". Add the dependency for the block you want to add (I said "mount",
but I guess that is old fashioned).

<dependencies>
     <dependency>
      <groupId>org.tiaterra</groupId>
      <artifactId>myCocoonBlock</artifactId>
      <version>1.0.0-SNAPSHOT</version>
    </dependency>
  </dependencies>

2.  create your block from the archetype
     
     This will create a structure like: 
src
src/test
src/test/resources
src/test/java
src/main
src/main/resources
src/main/resources/COB-INF
src/main/resources/COB-INF/javascript
src/main/resources/COB-INF/xslt
src/main/resources/COB-INF/images
src/main/resources/COB-INF/style
src/main/resources/COB-INF/style/images
src/main/resources/COB-INF/static-content
src/main/resources/META-INF
src/main/resources/META-INF/cocoon
src/main/resources/META-INF/cocoon/spring
src/main/java
src/main/java/org
src/main/java/org/tanteterra

Your site map is at:
 
src/main/resources/COB-INF/sitemap.xmap

And true, the documentation on the site does not make it easy enough to step
up the threshold and upgrade.
[ <at> group: shouldn't we do something about that. Cocoon is losing its user base,
it will end up getting adopted only by a few old people out there. It is gaining momentum on the planet Zork but that's not
going to help us on Earth, is it?]

I hope this helps you on the way. It would make me very happy to know that I am not one of the sole developers
on this planet who chose cocoon 3 as a development platform, for the few times in your life that you are in the
position to make this choice for your customer! I chose for cocoon 3 because I liked the new architecture.
[ <at> group: this can be the start for a tutorial for newbies, someone interested? I feel that the maven integration and
the spring part deserve better explanation, they are way too arcane for starters. A tutorial could explain how to get things
done without first studying two other frameworks.]

Kind regards,
Jos Snellings


On 03/01/2012 11:59 PM, Lars Huttar wrote:

Hello,

We've been Cocoon 2.1.* users for years. We're now trying to shift to the Cocoon 3 way of doing things.
I barely understand Maven, but I'm willing to learn.

I've installed Cocoon 3, and can run a sample.

But now I'm having trouble figuring out how to build my own "hello world" web application.

What I did so far:

   svn checkout http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk c3

     cd c3

   mvn clean install
   cd cocoon-databases-sample
   mvn jetty:run

I can then access the running databases sample at
    http://localhost:8888/
in the browser.

I've generated the four Maven 2 archetypes as instructed at http://cocoon.apache.org/3.0/download.html
(sample, block, webapp, parent).
I don't understand, though, what each one is for.

For archetype-block, the instruction says "Create an empty Cocoon 3 block in order to create your own Cocoon 3 web application."
But once I've done that, what do I do in the generated block in order to create a web application?

For archetype-webapp, it says "Create an empty Java web application project. After that add your Cocoon block as dependency." I guess Cocoon block refers to the previous thing I generated. How do I add it as a dependency? I guess I should edit cocoon-archetype-webapp/pom.xml and add this before </project>:
  <dependencies>
    <dependency>
      <groupId>org.apache.cocoon.archetype-block</groupId>
      <artifactId>cocoon-archetype-block</artifactId>
    </dependency>
  </dependencies>

For archetype-parent, the instruction says "Create a parent module for your Cocoon project." Is a project the same as a web application? Does this mean I should edit the contents of <parent> in archetype-webapp/pom.xml to point correctly to archetype-parent? (The <parent> element is present already, but its groupId, artifactId, and relativePath are a bit off from what would match the parent archetype generated by the instructions.)


**The main thing I want to know, though,** is where do I start building a sitemap?
In the working databases sample that I mentioned above, the only place I find a sitemap is under target/samples/COB-INF.
But the generated archetype-webapp/ folder doesn't have a target subfolder structure. Is that something I generate using a maven command?

Thanks!
I look forward to using C3, and I feel like if I can get past this point, I'll be able to start cooking.

Lars

On 02/03/2012 07:47, Jos Snellings wrote:

[...]

And true, the documentation on the site does not make it easy enough to step up the threshold and upgrade.
[ <at> group: shouldn't we do something about that. Cocoon is losing its user base, it will end up getting adopted only by a few old people out there. It is gaining momentum on the planet Zork but that's not going to help us on Earth, is it?]

I agree: should we move to dev ML and discuss this "getting started / documentation" topic?

I hope this helps you on the way. It would make me very happy to know that I am not one of the sole developers
on this planet who chose cocoon 3 as a development platform, for the few times in your life that you are in the
position to make this choice for your customer! I chose for cocoon 3 because I liked the new architecture.

You're not alone, Jos! We are trying to push a C3-based front-end framework for Hippo CMS [1]: we've been quiet for a while, but things should start rolling again soon...

[ <at> group: this can be the start for a tutorial for newbies, someone interested? I feel that the maven integration and
the spring part deserve better explanation, they are way too arcane for starters. A tutorial could explain how to get things
done without first studying two other frameworks.]

Agreed: see my comment above.

I hope that Lars will keep trying with C3, and maybe discover what's new behind traditional sitemap way to pipelines!

Cheers.

[1] https://forge.onehippo.org/gf/project/hct/
-- Francesco Chicchiriccò Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/