XFire SOAP Framework Developer List

http://www.w3.org/2001/04/xmlenc#}EncryptedData

ERROR - org.apache.ws.security.WSSecurityException: WSHandler: Encryption: no crypto property file
OR Invalid operation: {http://www.w3.org/2001/04/xmlenc#}EncryptedData
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: XFIRE-1155
                 URL: https://jira.codehaus.org/browse/XFIRE-1155
             Project: XFire
          Issue Type: Bug
         Environment: win xp  jdk1.6  spring
            Reporter: Jeffrey
            Assignee: Dan Diephouse
             Fix For: 1.2.6

Exception in thread "main" org.codehaus.xfire.XFireRuntimeException: Could not invoke service..
Nested exception is org.codehaus.xfire.fault.XFireFault: Invalid operation: {http://www.w3.org/2001/04/xmlenc#}EncryptedData
org.codehaus.xfire.fault.XFireFault: Invalid operation: {http://www.w3.org/2001/04/xmlenc#}EncryptedData
	at org.codehaus.xfire.fault.Soap11FaultSerializer.readMessage(Soap11FaultSerializer.java:31)
	at org.codehaus.xfire.fault.SoapFaultSerializer.readMessage(SoapFaultSerializer.java:28)
	at org.codehaus.xfire.soap.handler.ReadHeadersHandler.checkForFault(ReadHeadersHandler.java:111)
	at org.codehaus.xfire.soap.handler.ReadHeadersHandler.invoke(ReadHeadersHandler.java:67)
	at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
	at org.codehaus.xfire.client.Client.onReceive(Client.java:406)
	at org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(HttpChannel.java:139)
	at org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48)
	at org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
	at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
	at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79)
	at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114)
	at org.codehaus.xfire.client.Client.invoke(Client.java:336)
	at org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77)

(Continue reading)

headers

Jeffrey (JIRA | 1 Nov 03:31

http://www.w3.org/2001/04/xmlenc#}EncryptedData

ERROR - org.apache.ws.security.WSSecurityException: WSHandler: Encryption: no crypto property file
OR Invalid operation: {http://www.w3.org/2001/04/xmlenc#}EncryptedData
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: XFIRE-1155
                 URL: https://jira.codehaus.org/browse/XFIRE-1155
             Project: XFire
          Issue Type: Bug
         Environment: win xp  jdk1.6  spring
            Reporter: Jeffrey
            Assignee: Dan Diephouse
             Fix For: 1.2.6

Exception in thread "main" org.codehaus.xfire.XFireRuntimeException: Could not invoke service..
Nested exception is org.codehaus.xfire.fault.XFireFault: Invalid operation: {http://www.w3.org/2001/04/xmlenc#}EncryptedData
org.codehaus.xfire.fault.XFireFault: Invalid operation: {http://www.w3.org/2001/04/xmlenc#}EncryptedData
	at org.codehaus.xfire.fault.Soap11FaultSerializer.readMessage(Soap11FaultSerializer.java:31)
	at org.codehaus.xfire.fault.SoapFaultSerializer.readMessage(SoapFaultSerializer.java:28)
	at org.codehaus.xfire.soap.handler.ReadHeadersHandler.checkForFault(ReadHeadersHandler.java:111)
	at org.codehaus.xfire.soap.handler.ReadHeadersHandler.invoke(ReadHeadersHandler.java:67)
	at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
	at org.codehaus.xfire.client.Client.onReceive(Client.java:406)
	at org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(HttpChannel.java:139)
	at org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48)
	at org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
	at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
	at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79)
	at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114)
	at org.codehaus.xfire.client.Client.invoke(Client.java:336)
	at org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77)

(Continue reading)

headers

ST (JIRA | 21 Jul 09:50

[jira] Created: (XFIRE-1154) Xfire-all module's pom.xml contains bad dependency scope (compile) of xfire modules (xfire-aegis, xfire-core,...)

Xfire-all module's pom.xml contains bad dependency scope (compile) of xfire modules (xfire-aegis, xfire-core,...)
-----------------------------------------------------------------------------------------------------------------

                 Key: XFIRE-1154
                 URL: https://jira.codehaus.org/browse/XFIRE-1154
             Project: XFire
          Issue Type: Bug
    Affects Versions: 1.2.4
         Environment: All
            Reporter: ST
            Assignee: Dan Diephouse
             Fix For: 1.2.7

Xfire-all module's pom.xml contains bad dependency scope (compile) of xfire modules (xfire-aegis,
xfire-core,...). If you create dependency on xfire-all then you get xfire-all.jar and xfire-core.jar,
xfire-aegis.jar,... It means You have duplicated all classes - one in xfire-all.jar a

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

headers

ST (JIRA | 21 Jul 09:50

[jira] Created: (XFIRE-1154) Xfire-all module's pom.xml contains bad dependency scope (compile) of xfire modules (xfire-aegis, xfire-core,...)

Xfire-all module's pom.xml contains bad dependency scope (compile) of xfire modules (xfire-aegis, xfire-core,...)
-----------------------------------------------------------------------------------------------------------------

                 Key: XFIRE-1154
                 URL: https://jira.codehaus.org/browse/XFIRE-1154
             Project: XFire
          Issue Type: Bug
    Affects Versions: 1.2.4
         Environment: All
            Reporter: ST
            Assignee: Dan Diephouse
             Fix For: 1.2.7

Xfire-all module's pom.xml contains bad dependency scope (compile) of xfire modules (xfire-aegis,
xfire-core,...). If you create dependency on xfire-all then you get xfire-all.jar and xfire-core.jar,
xfire-aegis.jar,... It means You have duplicated all classes - one in xfire-all.jar a

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

headers

Christian Htiman (JIRA | 12 Apr 18:07

[jira] Created: (XFIRE-1153) problem with parameter namespace ; xfire client generated from a cxf server wsdl

problem with parameter namespace ; xfire client generated from a cxf server wsdl
--------------------------------------------------------------------------------

                 Key: XFIRE-1153
                 URL: http://jira.codehaus.org/browse/XFIRE-1153
             Project: XFire
          Issue Type: Bug
    Affects Versions: 1.2.6
            Reporter: Christian Htiman
            Assignee: Dan Diephouse

Hello all!

first, sorry for my bad english...

I need to dialog with a CXF/OpenEJB web service from a XFire wsdl generated client.

People managing the server tell me all the parameter are null. The reason I have found is the soap adds "ns1:"
prefix to the parameter names :

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body>
<ns1:verification xmlns:ns1="myNamespace">
<ns1:systemIdent>SYSID</ns1:systemIdent>
<ns1:sessionToken>1231445569844</ns1:sessionToken>
</ns1:verification >
</soap:Body>
</soap:Envelope>

(Continue reading)

headers

Christian Htiman (JIRA | 12 Apr 18:07

[jira] Created: (XFIRE-1153) problem with parameter namespace ; xfire client generated from a cxf server wsdl

problem with parameter namespace ; xfire client generated from a cxf server wsdl
--------------------------------------------------------------------------------

                 Key: XFIRE-1153
                 URL: http://jira.codehaus.org/browse/XFIRE-1153
             Project: XFire
          Issue Type: Bug
    Affects Versions: 1.2.6
            Reporter: Christian Htiman
            Assignee: Dan Diephouse

Hello all!

first, sorry for my bad english...

I need to dialog with a CXF/OpenEJB web service from a XFire wsdl generated client.

People managing the server tell me all the parameter are null. The reason I have found is the soap adds "ns1:"
prefix to the parameter names :

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body>
<ns1:verification xmlns:ns1="myNamespace">
<ns1:systemIdent>SYSID</ns1:systemIdent>
<ns1:sessionToken>1231445569844</ns1:sessionToken>
</ns1:verification >
</soap:Body>
</soap:Envelope>

(Continue reading)

headers

James Snell (JIRA | 25 Nov 21:30

[jira] Created: (XFIRE-1152) MTOM/XOP Interoperability - cid href URLEncode/URLDecode

MTOM/XOP Interoperability - cid href URLEncode/URLDecode
--------------------------------------------------------

                 Key: XFIRE-1152
                 URL: http://jira.codehaus.org/browse/XFIRE-1152
             Project: XFire
          Issue Type: Bug
    Affects Versions: 1.2.4
            Reporter: James Snell
            Assignee: Dan Diephouse

WCF uses a URL Encoded href cid for xopInclude. However, the Content-Id for the attachment is not URL
Encoded. As such, XFire is unable to find the attachment.

Example:

Request
<xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750" xmlns:xop="http://www.w3.org/2004/08/xop/include"/>

--uuid:357c6d9d-d6cf-42e3-bca5-75c8f3761934+id=1
Content-ID: <http://tempuri.org/1/633631227250468750>

Response
Attachment cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750 was not found.

XFire log:

java.lang.IllegalArgumentException: Attachment
cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750 was not found.
 at org.codehaus.xfire.jaxb2.AttachmentUnmarshaller.getAttachmentAsDataHandler(AttachmentUnmarshaller.java:70)

(Continue reading)

headers

James Snell (JIRA | 25 Nov 21:30

[jira] Created: (XFIRE-1152) MTOM/XOP Interoperability - cid href URLEncode/URLDecode

MTOM/XOP Interoperability - cid href URLEncode/URLDecode
--------------------------------------------------------

                 Key: XFIRE-1152
                 URL: http://jira.codehaus.org/browse/XFIRE-1152
             Project: XFire
          Issue Type: Bug
    Affects Versions: 1.2.4
            Reporter: James Snell
            Assignee: Dan Diephouse

WCF uses a URL Encoded href cid for xopInclude. However, the Content-Id for the attachment is not URL
Encoded. As such, XFire is unable to find the attachment.

Example:

Request
<xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750" xmlns:xop="http://www.w3.org/2004/08/xop/include"/>

--uuid:357c6d9d-d6cf-42e3-bca5-75c8f3761934+id=1
Content-ID: <http://tempuri.org/1/633631227250468750>

Response
Attachment cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750 was not found.

XFire log:

java.lang.IllegalArgumentException: Attachment
cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750 was not found.
 at org.codehaus.xfire.jaxb2.AttachmentUnmarshaller.getAttachmentAsDataHandler(AttachmentUnmarshaller.java:70)

(Continue reading)

headers

Trupti Parakh (JIRA | 19 Oct 05:38

[jira] Commented: (XFIRE-480) aegis NullPointerException


    [
http://jira.codehaus.org/browse/XFIRE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=240044#action_240044
] 

Trupti Parakh commented on XFIRE-480:
-------------------------------------

Has this issue been resolved.??? I am still getting this error for the same example and I am using
xfire-all-1.2.6.jar for the deployment of the service. As stated by eureka , I get a "java.lang.NullPointerException
	at org.codehaus.xfire.aegis.type.basic.HolderType.readObject(HolderType.java:54)" when the
service is invoked.

I would really appreciate any input on how to get this resolved or guidelines on implementing INOUT PARAMS
using XFIRE.

> aegis NullPointerException
> --------------------------
>
>                 Key: XFIRE-480
>                 URL: http://jira.codehaus.org/browse/XFIRE-480
>             Project: XFire
>          Issue Type: Bug
>          Components: Aegis Module
>    Affects Versions: 1.1.1
>         Environment: Windows2003, JDK 1.5.0_07, Resin 3.0.19, XFire 1.1.1, Spring 2.0 m5
>            Reporter: eureka
>            Assignee: Tomasz Sztelak
>             Fix For: 1.2.6
>

(Continue reading)

headers

Trupti Parakh (JIRA | 19 Oct 05:38

[jira] Commented: (XFIRE-480) aegis NullPointerException


    [
http://jira.codehaus.org/browse/XFIRE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=240044#action_240044
] 

Trupti Parakh commented on XFIRE-480:
-------------------------------------

Has this issue been resolved.??? I am still getting this error for the same example and I am using
xfire-all-1.2.6.jar for the deployment of the service. As stated by eureka , I get a "java.lang.NullPointerException
	at org.codehaus.xfire.aegis.type.basic.HolderType.readObject(HolderType.java:54)" when the
service is invoked.

I would really appreciate any input on how to get this resolved or guidelines on implementing INOUT PARAMS
using XFIRE.

> aegis NullPointerException
> --------------------------
>
>                 Key: XFIRE-480
>                 URL: http://jira.codehaus.org/browse/XFIRE-480
>             Project: XFire
>          Issue Type: Bug
>          Components: Aegis Module
>    Affects Versions: 1.1.1
>         Environment: Windows2003, JDK 1.5.0_07, Resin 3.0.19, XFire 1.1.1, Spring 2.0 m5
>            Reporter: eureka
>            Assignee: Tomasz Sztelak
>             Fix For: 1.2.6
>

(Continue reading)

headers

Jeff Liu (JIRA | 30 Jun 15:04

[jira] Created: (XFIRE-1151) The pom file of xfire-jsr181-api is not a valid POM version 4

The pom file of xfire-jsr181-api is not a valid POM version 4
-------------------------------------------------------------

                 Key: XFIRE-1151
                 URL: http://jira.codehaus.org/browse/XFIRE-1151
             Project: XFire
          Issue Type: Bug
          Components: Annotations
    Affects Versions: 1.2.6, 1.2.5, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2, 1.2-RC, 1.1.2, 1.1.1, 1.1, 1.1-RC1,
1.1-beta-1, 1.0
         Environment: Apache Maven 2.2.1 Java version: 1.6.0_18 OS name: "windows 7" version: "6.1" arch: "x86"
Family: "windows"
            Reporter: Jeff Liu
            Assignee: Dan Diephouse
            Priority: Trivial
             Fix For: 1.2.7

My project is depend on xfire 1.2.6. when I build it with maven 2.2.1, the warning message below is always
printed in the console.

///////////////////////////////////////////////////////////////////////////////////////
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building AppFuse Struts 2 Application
[INFO]    task-segment: [compile]
[INFO] ------------------------------------------------------------------------
[WARNING] POM for 'xfire:xfire-jsr181-api:pom:1.0-M1:compile' is invalid.

Its dependencies (if any) will NOT be available to the current build.

(Continue reading)

2	November 2011
2	July 2011
2	April 2011
2	March 2011
3	November 2010
2	October 2010
2	September 2010
9	August 2010
2	July 2010
9	June 2010
1	April 2010
2	March 2010
4	February 2010
6	January 2010
10	December 2009
1	November 2009
6	October 2009
4	September 2009
18	July 2009
11	May 2009
6	April 2009
4	March 2009
24	February 2009
8	January 2009
5	December 2008
16	November 2008
3	October 2008
10	September 2008
11	August 2008
6	July 2008
10	June 2008
12	May 2008
32	April 2008
24	March 2008
22	February 2008
9	January 2008
13	December 2007
35	November 2007
33	October 2007
38	September 2007
92	August 2007
78	July 2007
194	June 2007
328	May 2007
337	April 2007
315	March 2007
317	February 2007
178	January 2007
150	December 2006
220	November 2006
87	October 2006
1	August 2006
33	June 2006
180	May 2006
266	April 2006
7	March 2006

Mon	Tue	Wed	Thu	Fri	Sat	Sun

		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29