You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Dmitry Buzdin (JIRA)" <ji...@apache.org> on 2010/10/12 21:51:40 UTC

[jira] Created: (CAMEL-3228) Upgrade to dozer 5.3.0

Upgrade to dozer 5.3.0
----------------------

                 Key: CAMEL-3228
                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
             Project: Apache Camel
          Issue Type: Improvement
            Reporter: Dmitry Buzdin
             Fix For: 2.6.0


Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62762#action_62762 ] 

Claus Ibsen commented on CAMEL-3228:
------------------------------------

There are a zillion options and tweaks you can do in the maven bundle plugin, so maybe Willem can help you to improve that in your pom.xml.
I assume you have used that to generate the osgi metadata.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-3228:
-------------------------------

    Fix Version/s:     (was: 2.5.0)
                   2.6.0

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63570#action_63570 ] 

Claus Ibsen commented on CAMEL-3228:
------------------------------------

Yeah the last time I looked at it the DozerBeanMapper lacks an API to let 3rd party better control class loading.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62760#action_62760 ] 

Willem Jiang commented on CAMEL-3228:
-------------------------------------

There is two issues of the dozer MANIFEST.MF,
1. The export packages don't specify the version.
2. It imports the same packages which it exports.

If there are two doze bundles installed, the OSGi platform will be confused as it don't know which package which right version should be exported or imported.

To fix this issue we could create a OSGi wrap bundle in ServiceMix, as Camel 2.5.0 is cutting today, I doubt we can do it on time.
Maybe we can put it as a known issue in the release note and let user use the bundle of ServiceMix.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Dmitry Buzdin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63354#action_63354 ] 

Dmitry Buzdin commented on CAMEL-3228:
--------------------------------------

Claus, Dozer release is ready and will be published to Maven repository tonight. SPI interface for resource loading has also been added. 
The problem with itest you posted is related to the fact Dozer is initialized by Spring without Camel-Dozer infrastructure thus the standard resource loading policy is invoked instead of the one provided by extension module.
I will *not* put <DynamicImport-Package>*</DynamicImport-Package> for now. Lets try to solve it differently.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62599#action_62599 ] 

Claus Ibsen commented on CAMEL-3228:
------------------------------------

Yeah we love patches. So please contribute a patch so we can upgrade to use Dozer 5.3

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>             Fix For: 2.6.0
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62810#action_62810 ] 

Claus Ibsen commented on CAMEL-3228:
------------------------------------

Looks like the new JAR can be loaded in OSGi now.

Just that loading the mapping file from classpath now fails. Yeah OSGi influence this as well
{code}
        at org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:138)
        at org.apache.camel.core.osgi.OsgiTypeConverter.mandatoryConvertTo(OsgiTypeConverter.java:94)
        at org.apache.camel.impl.MessageSupport.getMandatoryBody(MessageSupport.java:100)
        ... 58 more
Caused by: org.dozer.MappingException: Unable to locate dozer mapping file [org/apache/camel/itest/osgi/dozer/dozer-mapping.xml] in the classpath!
        at org.dozer.util.MappingUtils.throwMappingException(MappingUtils.java:93)
        at org.dozer.util.MappingValidator.validateURL(MappingValidator.java:61)
        at org.dozer.loader.CustomMappingsLoader.loadFromFiles(CustomMappingsLoader.java:101)
        at org.dozer.loader.CustomMappingsLoader.load(CustomMappingsLoader.java:56)
        at org.dozer.DozerBeanMapper.loadCustomMappings(DozerBeanMapper.java:159)
        at org.dozer.DozerBeanMapper.getMappingProcessor(DozerBeanMapper.java:142)
        at org.dozer.DozerBeanMapper.map(DozerBeanMapper.java:98)
        at org.apache.camel.converter.dozer.DozerTypeConverter.convertTo(DozerTypeConverter.java:46)
        at org.apache.camel.converter.dozer.DozerTypeConverter.convertTo(DozerTypeConverter.java:50)
        at org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:181)
        at org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:136)
        ... 60 more
{code}

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63550#action_63550 ] 

Willem Jiang commented on CAMEL-3228:
-------------------------------------

@Dmitry

I just ran a test with the latest dozer-osgi 5.3.1,  and got the same error as claus got.
It looks like the classloader for the MappingValidator  is not set rightly.

{code}
Caused by: org.apache.camel.NoTypeConversionAvailableException: No type converter available to convert from type: org.apache.camel.itest.osgi.dozer.service.Customer to the required type: org.apache.camel.itest.osgi.dozer.model.Customer with value org.apache.camel.itest.osgi.dozer.service.Customer@5e149a
	at org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:138)
	at org.apache.camel.core.osgi.OsgiTypeConverter.mandatoryConvertTo(OsgiTypeConverter.java:94)
	at org.apache.camel.impl.MessageSupport.getMandatoryBody(MessageSupport.java:100)
	... 55 more
Caused by: org.dozer.MappingException: Unable to locate dozer mapping file [org/apache/camel/itest/osgi/dozer/dozer-mapping.xml] in the classpath!
	at org.dozer.util.MappingUtils.throwMappingException(MappingUtils.java:93)
	at org.dozer.util.MappingValidator.validateURL(MappingValidator.java:63)
	at org.dozer.loader.CustomMappingsLoader.loadFromFiles(CustomMappingsLoader.java:101)
	at org.dozer.loader.CustomMappingsLoader.load(CustomMappingsLoader.java:56)
	at org.dozer.DozerBeanMapper.loadCustomMappings(DozerBeanMapper.java:210)
	at org.dozer.DozerBeanMapper.getMappingProcessor(DozerBeanMapper.java:185)
	at org.dozer.DozerBeanMapper.map(DozerBeanMapper.java:111)
	at org.apache.camel.converter.dozer.DozerTypeConverter.convertTo(DozerTypeConverter.java:46)
	at org.apache.camel.converter.dozer.DozerTypeConverter.convertTo(DozerTypeConverter.java:50)
	at org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:181)
	at org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:136)
	... 57 more

{code}

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62754#action_62754 ] 

Claus Ibsen commented on CAMEL-3228:
------------------------------------

I pulled out the MANIFEST.MF from the JAR
{code}

Manifest-Version: 1.0
Export-Package: org.dozer.factory;uses:="org.dozer.config,org.dozer,or
 g.slf4j,org.dozer.util,javax.xml.datatype",org.dozer.converters;uses:
 ="org.apache.commons.beanutils,javax.xml.datatype,org.apache.commons.
 lang,org.apache.commons.beanutils.converters,org.apache.commons.lang.
 builder,org.dozer,org.dozer.cache",org.dozer.spring;uses:="org.spring
 framework.core.io,org.dozer,org.springframework.beans.factory",org.do
 zer.propertydescriptor;uses:="org.dozer.factory,org.dozer.fieldmap,or
 g.dozer,org.dozer.classmap,org.dozer.util",org.dozer.loader;uses:="or
 g.dozer.loader.xml,org.dozer.fieldmap,org.dozer.converters,org.dozer.
 classmap,org.slf4j,org.dozer.util,org.apache.commons.lang",org.dozer.
 classmap;uses:="org.dozer.fieldmap,org.dozer.converters,org.apache.co
 mmons.lang.builder,org.dozer.util,org.apache.commons.lang",org.dozer.
 util;uses:="org.apache.commons.beanutils,org.dozer.factory,org.dozer.
 converters,org.dozer.propertydescriptor,org.dozer.classmap,org.slf4j,
 org.apache.commons.lang,org.hibernate.proxy,org.dozer.config,org.doze
 r.fieldmap,org.apache.commons.lang.builder,org.dozer,org.dozer.cache"
 ,org.dozer.loader.xml;uses:="javax.el,org.dozer.loader,javax.xml.pars
 ers,org.dozer.classmap,org.dozer.util,org.slf4j,org.w3c.dom,org.apach
 e.commons.lang,org.xml.sax,org.dozer.config,org.dozer,org.xml.sax.hel
 pers",org.dozer.config;uses:="org.dozer.loader.xml,org.slf4j,org.doze
 r.util",org.dozer.fieldmap;uses:="org.dozer.factory,org.dozer.propert
 ydescriptor,org.apache.commons.lang.builder,org.dozer.classmap,org.sl
 f4j,org.dozer.util",org.dozer.event;uses:="org.dozer.fieldmap,org.doz
 er,org.dozer.classmap,org.dozer.util",org.dozer.stats;uses:="org.doze
 r.config,org.apache.commons.lang.builder,org.slf4j,org.dozer.util",or
 g.dozer.loader.api;uses:="org.dozer.loader,org.dozer.classmap,org.apa
 che.commons.lang",org.dozer;uses:="org.dozer.factory,org.dozer.conver
 ters,org.dozer.loader,javax.management,org.dozer.classmap,org.dozer.u
 til,org.slf4j,org.apache.commons.lang,org.dozer.loader.xml,org.dozer.
 config,org.dozer.fieldmap,org.dozer.event,org.dozer.stats,org.dozer.l
 oader.api,org.dozer.jmx,org.dozer.cache",org.dozer.cache;uses:="org.d
 ozer.stats,org.apache.commons.lang.builder,org.dozer.util,org.slf4j",
 org.dozer.jmx;uses:="org.dozer.config,org.dozer.stats,javax.managemen
 t,org.slf4j"
Private-Package: !*
Built-By: buzdin
Tool: Bnd-0.0.227
Bundle-Name: dozer-osgi
Created-By: Apache Maven Bundle Plugin
Build-Jdk: 1.6.0_15
Bundle-Version: 5.3.0
Bnd-LastModified: 1286913037471
Bundle-ManifestVersion: 2
Bundle-Description: dozer.osgi
Bundle-SymbolicName: net.sf.dozer.dozer-osgi
Embed-Dependency: *;scope=provided;type=!pom;inline=true
Import-Package: javax.el,javax.management,javax.xml.datatype,javax.xml
 .parsers,org.apache.commons.beanutils,org.apache.commons.beanutils.co
 nverters,org.apache.commons.lang,org.apache.commons.lang.builder,org.
 dozer,org.dozer.cache,org.dozer.classmap,org.dozer.config,org.dozer.c
 onverters,org.dozer.event,org.dozer.factory,org.dozer.fieldmap,org.do
 zer.jmx,org.dozer.loader,org.dozer.loader.api,org.dozer.loader.xml,or
 g.dozer.propertydescriptor,org.dozer.spring,org.dozer.stats,org.dozer
 .util,org.hibernate.proxy,org.slf4j,org.springframework.beans.factory
 ,org.springframework.core.io,org.w3c.dom,org.xml.sax,org.xml.sax.help
 ers
Originally-Created-By: Apache Maven
Archiver-Version: Plexus Archiver
{code}



> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62887#action_62887 ] 

Claus Ibsen commented on CAMEL-3228:
------------------------------------

It wont make it in Camel 2.5. But sure for Camel 2.6 it will.

And this is only an issue when using OSGi. So people with Camel 2.5 can use Dozer.
And people in OSGi can upgrade to Dozer 5.3.1 to get a bit further ahead. Only the last piece of classloading their mapping files may require a bit of OSGi configuration trouble to get working.

If Dozer offers the SPI for Camel to leverage later one then it should work out of the box for the end user when using Camel and Dozer.

If you look at, and see the method - loadMappings
https://svn.apache.org/repos/asf/camel/trunk/components/camel-dozer/src/main/java/org/apache/camel/converter/dozer/DozerTypeConverterLoader.java

You can see we use the Camel ClassResolver.

Its just that I think {{DozerBeanMapper}} is not having such a SPI for 3rd party to leverage for classloading pain


> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Dmitry Buzdin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63538#action_63538 ] 

Dmitry Buzdin commented on CAMEL-3228:
--------------------------------------

dozer 5.3.1 is already in Maven. Let me know if you need any additional changes.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Dmitry Buzdin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Buzdin updated CAMEL-3228:
---------------------------------

    Attachment: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch

Here you go.
Should be working fine. Now it is possible to define mappings in programmatic way using builders. This is a second supported format in Dozer since version 5.3.0.

I can update documentation page as well if you could give me access to the Wiki.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62750#action_62750 ] 

Claus Ibsen commented on CAMEL-3228:
------------------------------------

In the OSGi test I get this constraint error
{code}
ERROR: Error starting file:bundles/net.sf.dozer.dozer-osgi_5.3.0.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle net.sf.dozer.dozer-osgi [33]: package; (package=org.hibernate.proxy))
org.osgi.framework.BundleException: Unresolved constraint in bundle net.sf.dozer.dozer-osgi [33]: package; (package=org.hibernate.proxy)
        at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
        at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
        at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
        at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
        at java.lang.Thread.run(Thread.java:637)
{code}

What Hibernate JAR are you using?

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62761#action_62761 ] 

Claus Ibsen commented on CAMEL-3228:
------------------------------------

Yeah we should help Dmitry to have the Dozer project being able to generate a better OSGi MANIFEST.MF.

We will put this on known issue for Camel 2.5, and then in Camel 2.6 we could have this fixed when the next release of Dozer is out and have the OSGi stuff improved.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Dmitry Buzdin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62752#action_62752 ] 

Dmitry Buzdin commented on CAMEL-3228:
--------------------------------------

We use hibernate-core 3.5.0. This is optional runtime dependency. Dozer works without that, only one implementation of SPI interface depends on Hibernate.
dozer-osgi is simply osgified version of dozer with help of Felix maven plugin. How do we deal with this issue?

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Dmitry Buzdin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63203#action_63203 ] 

Dmitry Buzdin commented on CAMEL-3228:
--------------------------------------

I am publishing 5.3.1 release this week. Fixed a couple of bugs together with OSGi stuff.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62751#action_62751 ] 

Claus Ibsen commented on CAMEL-3228:
------------------------------------

trunk: 1026271.

Thanks for the patch. I have applied it.
However the OSGi feature for camel-dozer fails to be installed in Karaf as shown above.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang updated CAMEL-3228:
--------------------------------

    Attachment: pom.xml

@Dmitry,
Here is the osgi pom, that I just changed.

Can dozer run with commons-lang 2.4 ?
If not you can specify the version rang of commons-lang as you need.
As the package of javax*, and org.xml* are export default by OSGi, we don't need to specify the version.

For the hibernate, spring and sl4j packages you may also need to specify the version number.



> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Dmitry Buzdin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62764#action_62764 ] 

Dmitry Buzdin commented on CAMEL-3228:
--------------------------------------

Would gladly accept help. I am not an OSGi expert (or even a user). Here is the pom.xml of the dozer-osgi. 
http://dozer.svn.sourceforge.net/viewvc/dozer/trunk/osgi/pom.xml?revision=1084&view=markup

And pom.xml of dozer itself. Just in case.
http://dozer.svn.sourceforge.net/viewvc/dozer/trunk/core/pom.xml?revision=1084&view=markup

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62765#action_62765 ] 

Willem Jiang commented on CAMEL-3228:
-------------------------------------

@ Dmitry
I just created a JIRA in SMX4-613, maybe you can take a look at the patch and publish a new Dozer-OSGI bundle.
In this way we don't need to update the camel feature for it.


> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Dmitry Buzdin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Buzdin updated CAMEL-3228:
---------------------------------

    Attachment: dozer-osgi-5.3.0.jar

Did OSGi tricks you suggested. Thanks!
commons-lang 2.4 is not a problem.
Hibernate and Spring are optional dependencies. Also put some version ranges.
Please test the attached Jar and if it works I will put it to Maven repo.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63569#action_63569 ] 

Willem Jiang commented on CAMEL-3228:
-------------------------------------

@Dmitry,

I dig the code of the DozerTypeConverterLoader, it works as I expected which can load the customer mapper file from OSGi bundle.
But when the DozerTypeConverter tries convert the objects , it will use the DozerBeanMapper which is not injected with right class loader.

I'm trying to set the ClassMap into the DozerBeanMapper, but I can't do it without changing the code of DozerBeanMapper.
Can you double check the DozerBeanMapper ?

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Dmitry Buzdin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Buzdin updated CAMEL-3228:
---------------------------------

    Fix Version/s:     (was: 2.6.0)
                   2.5.0

Changed fix version to 2.5.0 as this is the one in pom.xml right now.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>             Fix For: 2.5.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Dmitry Buzdin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62767#action_62767 ] 

Dmitry Buzdin commented on CAMEL-3228:
--------------------------------------

I could do this over the weekend and release 5.3.1.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62830#action_62830 ] 

Claus Ibsen commented on CAMEL-3228:
------------------------------------

Dmitry

Yeah the new JAR is much better than the old one. So I think you should go ahead and do a 5.3.1 release.

In terms of classloading. I would suggest to provide a SPI for end users so they can provide URL or InputStream or something to load the resources.
This allows them to use Dozer in various servers which otherwise would have difficulty otherwise. For example JBoss, WebSphere may have issues loading on classpath.
BEA WebLogic as well. etc.

In the camel-dozer component it allows us from Camel to use the SPI to ensure the resources can be loaded using the Camel ClassResolver SPI
which we have adapters for OSGi, JBoss, WebSphere etc.

If you want to let OSGi be able to load from classpath and the end user can in fact put the mapping files in any classpath they like.
So to remedy that you may have to enable the dynamic imports. 

In the pom.xml you can do:
<DynamicImport-Package>*</DynamicImport-Package>

This may give some other problems in the longer run.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62755#action_62755 ] 

Claus Ibsen commented on CAMEL-3228:
------------------------------------

I will let the Maven OSGi experts have a go at this.

I think you can specify that hibernate stuff as being optional.
Also I think there is a rule of thumb to *not* import the same packages you export. But will leave it up to the OSGi maven experts to tell.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Dmitry Buzdin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63552#action_63552 ] 

Dmitry Buzdin commented on CAMEL-3228:
--------------------------------------

@Willem the problem is that integration test creates Dozer instance via Spring directly, but not with help of dozer-camel component.
If you do create a raw instance of dozer then it is not osgi compatible out of the box. Take a look at tests in camel-dozer module to see the proper initialization code.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62749#action_62749 ] 

Claus Ibsen commented on CAMEL-3228:
------------------------------------

Whats the difference between dozer and dozer-osgi artifacts?

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Dmitry Buzdin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62868#action_62868 ] 

Dmitry Buzdin commented on CAMEL-3228:
--------------------------------------

We already have SPI for classloading. What is left is implementation of Resource loading. I will do that and release 5.3.1.
Hope this does not impact your release schedule. If you need that by specific data please tell, otherwise it will be prepared at end of this week.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen reassigned CAMEL-3228:
----------------------------------

    Assignee: Claus Ibsen

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63201#action_63201 ] 

Claus Ibsen commented on CAMEL-3228:
------------------------------------

Dmitry how is it going with Dozer and OSGi?

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63355#action_63355 ] 

Willem Jiang commented on CAMEL-3228:
-------------------------------------

@Dmitry

I will update the Dozer version once the artifacts appears in the Maven repository.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Dmitry Buzdin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Buzdin updated CAMEL-3228:
---------------------------------

    Patch Info: [Patch Available]

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>             Fix For: 2.5.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-3228) Upgrade to dozer 5.3.0

Posted by "Dmitry Buzdin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62826#action_62826 ] 

Dmitry Buzdin commented on CAMEL-3228:
--------------------------------------

Dozer test wants to load Xml resource from classpath. I am not sure that this is Dozer bundle responsibility to restrict or allow such operations or am I wrong?
Is it possible to tell that Dozer is eligible to load any classpath resources somehow? This also is actual for classes, because some custom features could be implemented in application and then plugged in into Dozer mappings, which requires access to these classes in runtime.

> Upgrade to dozer 5.3.0
> ----------------------
>
>                 Key: CAMEL-3228
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3228
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Dmitry Buzdin
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>         Attachments: CAMEL-3228_-_Upgrade_to_Dozer_5_3_0_.patch, dozer-osgi-5.3.0.jar, pom.xml
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Dozer 5.3.0 has been released. It has changes in internal API, which make usage of dozer-camel impossible with the most recent version.
> As Dozer maintainer I could contribute a patch upgrading camel-dozer module to use 5.3.0. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.