[#XFIRE-466] XFire 1.1.1 SAAJ dependencies are not resolved transitively

XFire

XFire 1.1.1 SAAJ dependencies are not resolved transitively

Created: 19/Jun/06 11:36 AM Updated: 20/Jul/06 12:54 PM

Component/s:

None

Affects Version/s:

1.1.1

Fix Version/s:

1.2-RC

Time Tracking:

Not Specified

Description

« Hide

I noticed XFire 1.1.1 switched to using xfire:saaj-api-1.3 and xfire:saaj-imp-1.3 instead of using Sun's SAAJ Early Access 2.0 jars in XFire 1.1

The problem is those dependencies are unresolvable with clean build. Just try deleting xfire/saaj-impl and xfire/saaj-api folders from your local m2 repo to reproduce it. It must have been downloaded by previous versions, but really has to be published in an accessible repo.

For now our XFire tests in Mule do not depend on SOAP with attachments, and I resorted to excluding them from the graph, but it could be a small time bomb.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Andrew Perepelytsya - 19/Jun/06 01:03 PM

Just found the xfire:jaxws-api-2.0 has the same problem, but this one is one of those falling under Sun license. Anyway, I found it published at https://maven-repository.dev.java.net/repository/javax.xml.ws/ (note the different groupId). Mule is using this repo (with <layout>legacy</layout>, but it is of no help if the groupId is incorrect (pom needs to be fixed?)

[ Permlink | « Hide ]

Dan Diephouse - 20/Jun/06 10:09 AM

The problem with the dev.java.net repository is that it always times out. So I put them on the dist.codehaus.org site. If you add that to your repositories list you should be OK. But we need to get the JAX-WS jars uploaded to ibiblio.

[ Permlink | « Hide ]

Andrew Perepelytsya - 20/Jun/06 10:21 AM

Dan, as always, everything is relative

. The java.net repo is blazing fast if accessed from US, just to keep that in mind. As for the dist.codehaus.org, I checked it before, and rechecked just now. Neither xfire nor org.codehaus.xfire groups contain the aforementioned jars. Neither did I find any 1.1.1-related releases there. So did you only plan to do it, or is it a bug?

[ Permlink | « Hide ]

Dan Diephouse - 20/Jun/06 10:29 AM

I'm confused, I see them there:

http://dist.codehaus.org/xfire/jars/jaxws-api-2.0.jar
http://dist.codehaus.org/xfire/jars/saaj-impl-1.3.jar
http://dist.codehaus.org/xfire/jars/saaj-api-1.3.jar

[ Permlink | « Hide ]

Andrew Perepelytsya - 20/Jun/06 10:36 AM

I must have missed something on my side. Ok, thanks. I'll add the xfire repo and close the issue if it works out.

[ Permlink | « Hide ]

Andrew Perepelytsya - 20/Jun/06 01:01 PM

Dan,

I have added XFire dependencies repo for the XFire provider, but those have to published on ibiblio eventually:

<repositories>
        <repository>
            <id>xfire</id>
            <name>XFire Dependencies</name>
            <url>http://dist.codehaus.org</url>
            <snapshots>
                <enabled>false</enabled>
            </snapshots>
            <layout>legacy</layout>
        </repository>
    </repositories>

[ Permlink | « Hide ]

Dan Diephouse - 25/Jun/06 10:06 PM

One other note, the only reason you need these is because you are depending on xfire-jaxws. You are probably just depending on xfire-all - instead of using this, I would depend on xfire-spring.

[ Permlink | « Hide ]

Dan Diephouse - 20/Jul/06 12:54 PM

Finally got this resolved. Now we only use jars on ibiblio.