Hi, Yes the @Paragraph annotation is what makes Blossom detect it and expose it in Magnolia.
I tried it and I was unable to reproduce your problems. Here's what i did: Downloaded the source code from the article. Compiled and installed it to my local maven repository > mvn install Exported the magnolia-empty-webapp (this is what the magnolia bundles are based on) > svn export > http://svn.magnolia-cms.com/svn/community/magnolia/tags/magnolia-4.3.8/magnolia-empty-webapp/ Added the dependency to the example module to the pom.xml for empty-webapp <dependency> <groupId>info.magnolia</groupId> <artifactId>magnolia-module-example</artifactId> <version>1.0.0</version> </dependency> Added ServletContextExposingContextListener to web.xml <listener> <listener-class>info.magnolia.module.blossom.support.ServletContextExposingContextListener</listener-class> </listener> Started the empty-webapp using jetty >mvn jetty:run-war After installing the modules I looked in /modules/blossom/paragraphs/autodetected and pizzaForm is there. Are you seeing any indication of problems in your logs? Do you see Spring starting up? Have you tried increasing the log levels in log4j.xml? // Tobias On Dec 22, 2010, at 2:42 AM, medikgt wrote: > > > I was following > http://www.developer.com/java/web/spring-framework-and-magnolia-cms-creating-complex-java-based-websites.html > this tutorial on how to create a module with Blossom, which I found linked > from the Magnolia documentation page. > > I was able to download the source code, compile it and Magnolia was able to > detect it and install it fine. When I go to AdminCentral>Config, I see the > new "example" module there fine with the right version number. However, when > I click on "/module/Blossom/" I do not see my paragraphs autodetected like > it mentioned in the tutorial. > > Here are the exact steps you can do to reproduce my problem (shoudn't take > more a couple minutes): > - download the tutorial's source code > http://www.developer.com/imagesvr_ce/5592/Magnolia-Spring_src.zip here > - compile it with Maven (mvn tomcat:deploy, also tried mvn clean install, > both successful) > - copy the newly created module to WEB-INF/lib, also copy the > http://sourceforge.net/projects/magnoliablossom/ blossom jar and the > http://wiki.magnolia-cms.com/display/WIKI/Blossom+-+Fully+working+example#Blossom-Fullyworkingexample-Installationofdependencies > other spring jars > - in web.xml, add > "<listener-class>info.magnolia.module.blossom.support.ServletContextExposingContextListener</listener-class>" > before the MgnlServletContextListener > - startup Magnolia, install the modules > - go to AdminCentral>config>module>blossom>paragraph and see if there's an > autodetected folder like figure 6 > http://www.developer.com/java/web/deploying-and-testing-magnolia-module-code.html > here > > In the source, there is a pizzaForm.java file with annotated with > @Controller and @Paragraph. Is this what triggers Blossom to add paragraphs > to Magnolia programmatically? I am sure the module is working because I was > able to log some debug messages when the module was initiated. > -- > View this message in context: > http://old.nabble.com/Blossom---not-autodetecting-%40Paragraph-tp30511221p30511221.html > Sent from the Magnolia - User mailing list archive at Nabble.com. > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
