It looks like it's 2.0.0-beta. Here is the POM file:

<project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance";
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
 <modelVersion>4.0.0</modelVersion>

 <groupId>org.integration</groupId>
 <artifactId>client-3.0.0</artifactId>
 <version>0.0.1-SNAPSHOT</version>
 <packaging>jar</packaging>

 <name>stubs</name>
 <url>http://maven.apache.org</url>

 <properties>
  <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
  <cxf.version>3.0.0-milestone1</cxf.version>
  <bouncycastle.version>1.40</bouncycastle.version>
  <junit.version>4.1</junit.version>
 </properties>

 <build>
  <plugins>
   <plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <configuration>
     <source>1.6</source>
     <target>1.6</target>
    </configuration>
   </plugin>
  </plugins>
 </build>

 <dependencies>
  <dependency>
   <groupId>org.apache.cxf</groupId>
   <artifactId>cxf-rt-frontend-jaxws</artifactId>
   <version>${cxf.version}</version>
  </dependency>
  <dependency>
   <groupId>org.apache.cxf</groupId>
   <artifactId>cxf-rt-transports-http</artifactId>
   <version>${cxf.version}</version>
  </dependency>
  <dependency>
   <groupId>org.apache.cxf</groupId>
   <artifactId>cxf-rt-ws-security</artifactId>
   <version>${cxf.version}</version>
  </dependency>
  <dependency>
   <groupId>org.apache.cxf</groupId>
   <artifactId>cxf-rt-ws-policy</artifactId>
   <version>${cxf.version}</version>
  </dependency>
  <dependency>
   <groupId>com.sun.xml.messaging.saaj</groupId>
   <artifactId>saaj-impl</artifactId>
   <version>1.3.18</version>
  </dependency>
  <dependency>
   <groupId>commons-codec</groupId>
   <artifactId>commons-codec</artifactId>
   <version>1.4</version>
  </dependency>
  <dependency>
   <groupId>org.bouncycastle</groupId>
   <artifactId>bcprov-jdk16</artifactId>
   <version>${bouncycastle.version}</version>
   <exclusions>
    <exclusion>
     <groupId>commons-logging</groupId>
     <artifactId>commons-logging</artifactId>
    </exclusion>
   </exclusions>
  </dependency>
  <dependency>
   <groupId>junit</groupId>
   <artifactId>junit</artifactId>
   <version>${junit.version}</version>
   <scope>test</scope>
  </dependency>
  <dependency>
   <groupId>log4j</groupId>
   <artifactId>log4j</artifactId>
   <version>1.2.17</version>
  </dependency>
 </dependencies>
</project>




On Mon, Feb 17, 2014 at 5:12 AM, Colm O hEigeartaigh <[email protected]>wrote:

>
> Could you verify what version of CXF you are using (in particular, what
> are the versions of XML Security (Santuario) + WSS4J in your classpath)?
> What does your client configuration look like?
>
> Colm.
>
>
> On Sun, Feb 16, 2014 at 4:28 PM, Wabi Sabi <[email protected]> wrote:
>
>> This is great, thanks so much Colm for all your help! I disabled the BSP
>> compliance, and it kind of worked with the initial, non SwA call, but it
>> keeps on failing with the call that includes the attachments:
>>
>>
>> Caused by: *org.apache.xml.security.transforms.InvalidTransformException*:
>> Unknown transformation. No handler installed for URI
>> http://docs.oasis-open.org/wss/oasis-wss-SwAProfile-1.1#Attachment-Ciphertext-Transform
>>
>> at org.apache.xml.security.transforms.Transform.<init>(
>> *Transform.java:155*)
>>
>> at org.apache.xml.security.transforms.Transforms.item(
>> *Transforms.java:321*)
>>
>>  ... 54 more
>>
>>
>> This is the error I ran into previously even with CXF 2.7, after adding
>> custom resolvers. I wonder if that requires a custom transformation? Any
>> pointers are greatly appreciated.
>>
>> Thank you once again, Colm. I greatly appreciate you looking into this
>> problem.
>>
>> On Thu, Feb 13, 2014 at 8:42 AM, Colm O hEigeartaigh <[email protected]
>> > wrote:
>>
>>
>>> The error message is fairly self-explanatory here, the Signature does not
>>> contain a PrefixList Attribute as required by the Basic Security Profile.
>>> To get around this, you can disable Basic Security Profile compliance on
>>> the inbound side by setting the property "ws-security.is-bsp-compliant"
>>> to
>>> "false".
>>>
>>> Colm.
>>>
>>>
>>>
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>

Reply via email to