[magnolia-dev] [JIRA] (BLOSSOM-218) BeanInstantiationException exception when binding javax.jcr.Node request param?

[JIRA (on behalf of Dominika)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dominika created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-218 
 
 
 
  BeanInstantiationException exception when binding javax.jcr.Node request param?  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 3.1 
 
 
 

Assignee:
 
 Tobias Mattsson 
 
 
 

Created:
 

 14/Jul/15 5:39 PM 
 
 
 

Environment:
 

 Magnolia 3.4, Blossom 3.1-SNAPSHOT, Spring Framework 4.1.6.RELEASE 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Dominika 
 
 
 
 
 
 
 
 
 
 
I have encountered this stack trace when starting up Mag 5.4 with new 3.1 Blossom.  

 

2015-07-14 10:47:53,987 ERROR ndering.engine.ModeDependentRenderExceptionHandler: Error while rendering [/test] with template [searchAndSortModule:pages/home] for URI [/test.html?mgnlPreview=falsemgnlChannel=desktop]:
RenderException: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [javax.jcr.Node]: Specified class is an interface
info.magnolia.rendering.engine.RenderException: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [javax.jcr.Node]: Specified class is an interface
	at 

[magnolia-dev] [JIRA] (BLOSSOM-184) Add support for DAM 2.x new package name of DamConfig.java

[JIRA (on behalf of Dominika)]

Dominika
 created  BLOSSOM-184


Add support for DAM 2.x new package name of DamConfig.java















Issue Type:


Improvement



Affects Versions:


3.0.2



Assignee:


Tobias Mattsson



Created:


11/Jul/14 2:09 AM



Description:


Using Magnolia 5.3.1-SNAPSHOT and Blossom 3.0.2.

When using new DAM versions 2.x, the @TabFactory method 'DamConfig' argument can no longer bind.

In the new DAM 'DamConfig' is in the "info.magnolia.dam.app.ui.config" package, while Blossom's ParameterResolver implementation has hardcoded and expecting the class name of "info.magnolia.dam.asset.config.DamConfig"

Stacktrace:
Caused by: java.lang.IllegalStateException: Unable to resolve parameter of type class info.magnolia.dam.app.ui.config.DamConfig

As a quick fix, I created a class in my module using old package structure, pining to DamFieldConfig in new package structure.

package info.magnolia.dam.asset.config;
import info.magnolia.dam.app.ui.config.DamFieldConfig;
public class DamConfig 
{
	public final DamFieldConfig fields = new DamFieldConfig();
}

So far so good. Probably this class should find its way to DAM 2.x magnolia-dam-compatibility project.







Project:


Magnolia Blossom Module



Priority:


Major




Reporter:


Dominika




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com