Hi TLN,
This deprecation was made in error and was reverted in 2.0.11 and 2.1.1.
See https://jira.magnolia-cms.com/browse/MGNLDAM-602
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=ab0eb91b-51fe-47b3-9ede-0a96b3832226
Hi,
It is not possible to use JSP files stored in the resources app.
This use case requires freemarker templates.
The reason JSP files can't be used lies in limitations in the Servlet API Spec.
It does not define any way to instruct the servlet container from where to load
JSP files. It only
Hi Brad,
In the documentation on configuring instances you'll find all you need about
setting up subscribers to publish to public instances.
https://documentation.magnolia-cms.com/display/DOCS/Subscribers
Publishing to more than one public instance is an EE feature though.
// Tobias
--
Hi Brad,
The getting started guide shows how to use the archetypes and when completing
it you will have an empty project that you can start working on.
There's also a rich sample with a page template and a bunch of components
showing how to use both JSP and Freemarker views.
Hi David,
Magnolia and its modules are bundled as a war, that includes the Blossom module
and your own modules. At startup it will install if that hasn't been done
before. When you deploy a new version it will update if necessary. When you
restart it will just start up. You can automate the
Hi David,
You can simply add the Jersey servlet to your Magnolia webapp. The recommended
way is having a module install it to the filter chain although adding it
directly in web.xml also works, just remember to exclude its path from being
processed by the Magnolia filter chain.
You'll find
Hi Hafiz,
The basic upload field uploads the image and stores it in the page itself.
To upload to the DAM use the DAM upload field. See
http://documentation.magnolia-cms.com/display/DOCS/Blossom+module#Blossommodule-UsingDAMfields
--
Context is everything:
Hi Young Lee,
I've reviewed the source and can't find anything that would cause this problem.
At this point I'd suspect something is wrong with the IDE and project setup.
Do you have the same problem running the blossom sample ?
--
Context is everything:
Would it be okay for you to zip the project and share it with me? Including the
pom files. You don't need to include the xplan packages.
One thing that would cause this is if an older blossom jar is present in
tomcat, possibly due to eclipse publishing issues. Versions prior to 3.0.2
don't see
Hi Young,
The only mistake I see is the id in the @Template annotation. But that wouldn't
prevent it from being registered.
This bit @Template(id = acmeModule:components/main, title = Main) should be
@Template(id = acmeModule:pages/main, title = Main)
Could you share your project with me so I
Hi Chris,
The problem is the Dialog parameter, if you check the logs you should see this
error: Caused by: java.lang.IllegalStateException: Unable to resolve parameter
of type [class info.magnolia.ui.dialog.Dialog].
The parameters you can use on tab factories are TabBuilder, DialogDefinition,
Hi Karthik,
This question is better to ask on the 'Get help with Magnolia' forum, there's a
larger audience there especially since its synced with the user mailing list.
We have a complete sample project for Blossom with a number of java classes and
jsps. Follow the instructions in the Blossom
Hi Dean,
You have several options, which best suits your needs depends on what the
listener does. ServletContextListeners usually initializes things that servlets
and filters later depend on.
The most straightforward solution would be to simply copy the web.xml that
Magnolia uses and add the
You appear to be missing the groovy jar file.
How are you managing the dependencies in your project, use maven or by copying
in the jars themselves? Using maven is strongly recommended since Magnolia
pulls in a large number of open source libraries and as you add modules to
Magnolia these will
Hi Paolo,
What happens here is that both forms target the same page, they're using
pre-execution and returning redirects so everything is fine until you add
validation and instead of returning a redirect return a view with validation
errors. Then the page is rendered in its entirety including
Hi Dominik,
Blossom does not require a specific DAM version. In fact it doesn't require it
to be present at all. The blossom sample app does depend on DAM 1.1. If you've
based your project on the sample and upgraded it to 5.2 you can safely update
the dependency to use DAM 1.2.
Hope that
You're welcome, this code is indeed not in the sample.
I added it now as a child page of
http://wiki.magnolia-cms.com/display/WIKI/Magnolia+Blossom where you can find
other tips that might be helpful.
// Tobias
--
Context is everything:
Hi Ralf,
At the moment apps can only be configured in the repository. Going forward
having a blossom-style programmatic way of creating apps is a priority for us.
Stay tuned, it is coming. =)
// Tobias
--
Context is everything:
Hi Paolo,
Could it be that you need aop:aspectj-autoproxy / in applicationContext.xml ?
// Tobias
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=e11b2879-68fc-4998-9173-06c8cbe6d355
For list
In your project you can mix STK and Blossom, on the same page you can have some
components implemented using STK and some using Blossom.
Extending an STK template using Blossom is not easily done because they use
different programming models. The RenderingModel implementation used by STK
Hi Nirmal,
This is usually done in your modules version handler. When the module is
installed it will then add this extra node. The version handler is free to make
any changes it needs. The default version handler used unless you specify your
own will import xml files placed in
Hi Ralf,
Place jsps in
/src/main/resources/mgnl-files/templates/acmeModule/pages
/src/main/resources/mgnl-files/templates/acmeModule/areas
/src/main/resources/mgnl-files/templates/acmeModule/components
And ftls in
/src/main/resources/acmeModule/templates/pages
Hi Nirmal,
The stkFooterLinkList is configured to allow stkFooterInternalLink and
stkFooterExternalLink being added to its area. To make another component
available you need to configure it at
/modules/standard-templating-kit/templates/components/stkFooterLinkList/areas/linkList/,
there's
Hi Francisco,
Do you have errors in the log while starting up?
This is usually caused by the module not starting up properly or not being
correctly configured. You did have it working before, what has changes? Package
names maybe?
// Tobias
--
Context is everything:
Hi Francisco,
Could you provide the full maven log, perhaps using pastie.org or pastebin.com ?
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=3f466009-9d53-4b7d-96cf-e3ecad87be97
For list
It looks like
/home/javi/.m2/repository/info/magnolia/magnolia-empty-webapp/5.1-rc1/magnolia-empty-webapp-5.1-rc1.war
is corrupt. Try deleting it from your local drive and build again to have it
downloaded again.
--
Context is everything:
Hi Francisco,
Blossom 3.0 supports Magnolia 5.1. Both are currently in release candidate
stage. The final release is only days away.
Use 5.1-rc1 of Magnolia and 3.0-rc1 of Blossom.
Here's the maven dependency you'd use in your project, note that the groupId is
now info.magnolia.blossom:
Hi Fabrizio,
I can't reproduce this problem. I've used the same xml snippet, although a
different replacement implementation and I get the init() call from
ConfigLoader.
Could you file a ticket for this with the exact version where you're seeing the
problem?
// Tobias
--
Context is
Hi Luca,
You can override the MessagesManager in your module descriptor like this:
components
idsystem/id
component
typeinfo.magnolia.cms.i18n.MessagesManager/type
implementationmy.package.MyMessagesManager/implementation
/component
/components
// Tobias
--
Context
29 matches
Mail list logo
