On 12/10/12 10:56, Jim Talbut wrote:
On 12/10/2012 10:44, Sergey Beryozkin wrote:
Hi
what does dependency:tree show ?
[INFO]
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @
esb.cxf.tracking ---
[INFO] com.groupgti.soa:esb.cxf.tracking:bundle:1.6.0
[INFO] +- com.groupgti:utilities:jar:1.0:provided
[INFO] +- mysql:mysql-connector-java:jar:5.1.19:provided
[INFO] +- org.apache.cxf:cxf-rt-frontend-jaxws:jar:2.6.0:provided
[INFO] | +- xml-resolver:xml-resolver:jar:1.2:provided
[INFO] | +- asm:asm:jar:3.3.1:provided
[INFO] | +- org.apache.cxf:cxf-api:jar:2.6.0:provided
[INFO] | | +- org.codehaus.woodstox:woodstox-core-asl:jar:4.1.2:provided
[INFO] | | | \- org.codehaus.woodstox:stax2-api:jar:3.1.1:provided
[INFO] | | +- org.apache.ws.xmlschema:xmlschema-core:jar:2.0.2:provided
[INFO] | | +-
org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.7.1:provided
[INFO] | | \- wsdl4j:wsdl4j:jar:1.6.2:provided
[INFO] | +- org.apache.cxf:cxf-rt-core:jar:2.6.0:provided
[INFO] | | \- com.sun.xml.bind:jaxb-impl:jar:2.1.13:provided
[INFO] | +- org.apache.cxf:cxf-rt-bindings-soap:jar:2.6.0:provided
[INFO] | | \- org.apache.cxf:cxf-rt-databinding-jaxb:jar:2.6.0:provided
[INFO] | +- org.apache.cxf:cxf-rt-bindings-xml:jar:2.6.0:provided
[INFO] | +- org.apache.cxf:cxf-rt-frontend-simple:jar:2.6.0:provided
[INFO] | \- org.apache.cxf:cxf-rt-ws-addr:jar:2.6.0:provided
[INFO] | \- org.apache.cxf:cxf-rt-ws-policy:jar:2.6.0:provided
[INFO] | \- org.apache.neethi:neethi:jar:3.0.2:provided
[INFO] +- org.apache.cxf:cxf-rt-transports-http:jar:2.6.0:provided
[INFO] +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.6.0:provided
[INFO] | \- javax.ws.rs:jsr311-api:jar:1.1.1:provided
[INFO] +- org.apache.cxf:cxf-rt-transports-http-jetty:jar:2.6.0:provided
[INFO] | +- org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024:provided
[INFO] | | +-
org.eclipse.jetty:jetty-continuation:jar:7.5.4.v20111024:provided
[INFO] | | \- org.eclipse.jetty:jetty-http:jar:7.5.4.v20111024:provided
[INFO] | | \- org.eclipse.jetty:jetty-io:jar:7.5.4.v20111024:provided
[INFO] | | \- org.eclipse.jetty:jetty-util:jar:7.5.4.v20111024:provided
[INFO] | +- org.eclipse.jetty:jetty-security:jar:7.5.4.v20111024:provided
[INFO] | +- org.slf4j:slf4j-api:jar:1.6.2:provided
[INFO] | \-
org.apache.geronimo.specs:geronimo-servlet_2.5_spec:jar:1.1.2:provided
[INFO] +- org.apache.abdera:abdera-parser:jar:1.2-SNAPSHOT:provided
[INFO] | +- org.apache.abdera:abdera-core:jar:1.2-SNAPSHOT:provided
[INFO] | | +- org.apache.abdera:abdera-i18n:jar:1.2-SNAPSHOT:provided
[INFO] | | +-
org.apache.geronimo.specs:geronimo-activation_1.0.2_spec:jar:1.1:provided
[INFO] | | \- commons-codec:commons-codec:jar:1.4:provided
[INFO] | +- org.apache.ws.commons.axiom:axiom-impl:jar:1.2.10:provided
[INFO] | | +- org.apache.ws.commons.axiom:axiom-api:jar:1.2.10:provided
[INFO] | | \-
org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0.2:provided
[INFO] | +-
org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1:provided
[INFO] | +- org.codehaus.woodstox:wstx-asl:jar:3.2.6:provided
[INFO] | \- jaxen:jaxen:jar:1.1.1:provided
[INFO] | +- xml-apis:xml-apis:jar:1.3.02:provided
[INFO] | \- xerces:xercesImpl:jar:2.6.2:provided
[INFO] +- org.springframework:spring-jdbc:jar:3.0.7.RELEASE:provided
[INFO] | \- org.springframework:spring-beans:jar:3.0.7.RELEASE:provided
[INFO] +- org.springframework:spring-core:jar:3.0.7.RELEASE:provided
[INFO] | \- org.springframework:spring-asm:jar:3.0.7.RELEASE:provided
[INFO] +- org.springframework:spring-tx:jar:3.0.7.RELEASE:provided
[INFO] | +- aopalliance:aopalliance:jar:1.0:provided
[INFO] | +- org.springframework:spring-aop:jar:3.0.7.RELEASE:provided
[INFO] | \- org.springframework:spring-context:jar:3.0.7.RELEASE:provided
[INFO] | \-
org.springframework:spring-expression:jar:3.0.7.RELEASE:provided
[INFO] +- org.springframework:spring-orm:jar:3.0.7.RELEASE:provided
[INFO] +- org.springframework:spring-test:jar:3.0.7.RELEASE:provided
[INFO] +- commons-logging:commons-logging:jar:1.1.1:provided
[INFO] +- ch.qos.logback:logback-core:jar:1.0.0:provided
[INFO] +- ch.qos.logback:logback-classic:jar:1.0.0:provided
[INFO] +- org.slf4j:jcl-over-slf4j:jar:1.6.4:provided
[INFO] +- org.apache.openjpa:openjpa:jar:2.2.0:provided
[INFO] | +- commons-lang:commons-lang:jar:2.4:provided
[INFO] | +- commons-collections:commons-collections:jar:3.2.1:provided
[INFO] | +- net.sourceforge.serp:serp:jar:1.13.1:provided
[INFO] | +-
org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.1.1:provided
[INFO] | +-
org.apache.geronimo.specs:geronimo-jta_1.1_spec:jar:1.1.1:provided
[INFO] | +- commons-pool:commons-pool:jar:1.5.4:provided
[INFO] | \-
org.apache.geronimo.specs:geronimo-jpa_2.0_spec:jar:1.1:provided
[INFO] +- com.groupgti.esb:esb.purge:jar:1.0.0:provided
[INFO] +- org.osgi:org.osgi.core:jar:4.2.0:compile
[INFO] +- org.apache.derby:derby:jar:10.8.2.2:test
[INFO] +- cglib:cglib:jar:2.2:test
[INFO] +- com.groupgti:utilities:test-jar:tests:1.1:test
[INFO] \- junit:junit:jar:4.10:test
[INFO] \- org.hamcrest:hamcrest-core:jar:1.1:test
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 9.280s
[INFO] Finished at: Fri Oct 12 10:52:57 BST 2012
[INFO] Final Memory: 18M/219M
[INFO]
------------------------------------------------------------------------
The reason abdera-parser embeds those
libraries is that this is how they approached the integration of Abdera
with OSGI - and in fact, ServiceMix bundle is now available to get
axiom-api embedded there too, but I'm not sure it is those 3/4 embedded
jars that are interfering.
Any other ideas what it could be?
I guess it could be axiom-api or axiom-impl dependencies - may you can
exclude whatever they are bringing in ? I was just saying that it is not
their embedded duplicates which were causing this issue
I'm not at all attached to Abdera if there is another way to generate
the Atom feed (though I'm a fan of doing as little as possible and don't
know the Atom standard well).
Another option is to build it manually using DOM. How complex are your
Atom representations ? Even JAXB can be used but I guess the general
issue is that Atom is generic enough and hence it is difficult to
capture it with JAXB, still some work has to be done on managing the way
the entity content gets marshalled and it can become tricky if the
content is meant to be marshalled as Atom feed or entry extensions (i.e,
as immediate children of entries or feeds)
The Atom representations are going to be pretty simple, but I've got a
few systems that are going to want them, so I was hoping to avoid doing
too much stuff that was specific to my structures.
Maybe I can't.
Whichever way you do it it will still be Atom representations to be
understood by most consumers, the question is how to render the actual
content for the generic consumers to make any sense of it. I guess one
option is to embed an HTML formatted content within entry/content,
another one is to completely break the content into entries linking to
each other with links, yet another option is not to expect the generic
consumers to understand everything given that they are supposed to
ignore the unrecognized content
Cheers, Sergey
Jim
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
