Hi Shriniwas,
When I need to find this sort of information out, I
normally use the maven repository to figure it out:
http://repo1.maven.org/maven2/org/codehaus/xfire/xfire-jaxb2/1.2.6/xfire
-jaxb2-1.2.6.pom
As you can see in the above file, xfire-jaxb2 component uses the
following dependency:
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-xjc</artifactId>
<version>2.0.1</version>
<exclusions>
<exclusion>
<artifactId>jsr173</artifactId>
<groupId>javax.xml</groupId>
</exclusion>
</exclusions>
</dependency>
So, it follows it's highly likely that xfire 1.2.6 uses jaxb 2.0.1.
As for upgrading, it is possible, you just need to know how to configure
maven to exclude jaxb version 2.0.1 (i.e. see the example I just gave in
this email, which excludes jsr173), and include the new version of jaxb
you require.
Best,
Conor
________________________________
From: Wagle, Shriniwas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 18 July 2007 6:48 AM
To: [email protected]
Subject: [xfire-user] XFire 1.2.6 & JAXB 2.0 version
Which specific JAXB 2.0 version is being used with XFire 1.2.6? E.g.
JAXB 2.0.1 or 2.0.2 or 2.0.3?
Is there some easy way for me to determine that?
Can I upgrade the JAXB version to 2.1.4 by getting the reference
implementation from https://jaxb.dev.java.net/? If yes, how can I do
that and then is there a way to validate that the upgrade has been
successful?
Thank you.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This email (including any attached files) is for the intended
recipient(s) only. If you received this email by mistake, please,
as a courtesy, tell the sender, then delete this email.
The views and opinions are the originator's and do not necessarily
reflect those of the Queensland Studies Authority. All reasonable
precautions have been taken to ensure that this email contained no
viruses at the time it was sent.
