[jira] [Resolved] (CXF-3740) CXF WSA handler have to throw WebServiceException on client side if addressing is required but not found in the message

2011-08-18 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3740. Resolution: Fixed Fix Version/s: (was: 2.3.7) > CXF WSA handler have to throw WebServiceException on clien

[jira] [Commented] (CXF-3740) CXF WSA handler have to throw WebServiceException on client side if addressing is required but not found in the message

2011-08-18 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087575#comment-13087575 ] jimma commented on CXF-3740: Patch is applied. Thanks Richard! > CXF WSA handler have to throw

[jira] [Assigned] (CXF-3740) CXF WSA handler have to throw WebServiceException on client side if addressing is required but not found in the message

2011-08-18 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma reassigned CXF-3740: -- Assignee: jimma > CXF WSA handler have to throw WebServiceException on client side if > addressing is required b

[jira] [Updated] (CXF-3716) Move get classloader from bus extension to the constructor to imporve the perfomance

2011-08-07 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-3716: --- Affects Version/s: 2.4.1 Fix Version/s: (was: 2.4.1) 2.5 > Move get classloader from

[jira] [Resolved] (CXF-3716) Move get classloader from bus extension to the constructor to imporve the perfomance

2011-08-07 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3716. Resolution: Fixed > Move get classloader from bus extension to the constructor to imporve the > perfomance > ---

[jira] [Created] (CXF-3716) Move get classloader from bus extension to the constructor to imporve the perfomance

2011-08-06 Thread jimma (JIRA)
Move get classloader from bus extension to the constructor to imporve the perfomance Key: CXF-3716 URL: https://issues.apache.org/jira/browse/CXF-3716 Project: CXF

[jira] [Resolved] (CXF-3639) The duplicate soap body is appended when the endpoint is both configured with soap handler and wsse enabled

2011-07-10 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3639. Resolution: Fixed > The duplicate soap body is appended when the endpoint is both configured > with soap handler an

[jira] [Updated] (CXF-3639) The duplicate soap body is appended when the endpoint is both configured with soap handler and wsse enabled

2011-07-10 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-3639: --- Affects Version/s: 2.2.12 Fix Version/s: 2.2.13 > The duplicate soap body is appended when the endpoint is bot

[jira] [Created] (CXF-3639) The duplicate soap body is appended when the endpoint is both configured with soap handler and wsse enabled

2011-07-06 Thread jimma (JIRA)
The duplicate soap body is appended when the endpoint is both configured with soap handler and wsse enabled Key: CXF-3639 URL: https://issues.apache.org/

[jira] [Created] (CXF-3560) wsa wrongly assumes that code using WSA must be employing a request-reply exchange.

2011-05-30 Thread jimma (JIRA)
wsa wrongly assumes that code using WSA must be employing a request-reply exchange. --- Key: CXF-3560 URL: https://issues.apache.org/jira/browse/CXF-3560 Project: CXF

[jira] [Resolved] (CXF-3544) The nested policy reference can not be resolved

2011-05-24 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3544. Resolution: Fixed > The nested policy reference can not be resolved > ---

[jira] [Created] (CXF-3544) The nested policy reference can not be resolved

2011-05-22 Thread jimma (JIRA)
The nested policy reference can not be resolved --- Key: CXF-3544 URL: https://issues.apache.org/jira/browse/CXF-3544 Project: CXF Issue Type: Bug Components: WS-* Components

[jira] [Resolved] (CXF-2193) Allow for WRAPPED style code generation for "wrapper elements" with xsd:extension of a wrapper-compatible type

2011-05-19 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2193. Resolution: Fixed Assignee: jimma > Allow for WRAPPED style code generation for "wrapper elements" with > xsd:

[jira] [Resolved] (CXF-3502) IllegalArgumentException: wrong number of arguments with Dispatch/Provider service

2011-05-09 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3502. Resolution: Fixed > IllegalArgumentException: wrong number of arguments with Dispatch/Provider > service > -

[jira] [Created] (CXF-3502) IllegalArgumentException: wrong number of arguments with Dispatch/Provider service

2011-05-08 Thread jimma (JIRA)
IllegalArgumentException: wrong number of arguments with Dispatch/Provider service -- Key: CXF-3502 URL: https://issues.apache.org/jira/browse/CXF-3502 Project: CXF

[jira] [Resolved] (CXF-3456) WSA implementation does not throw wsa:InvalidCardinality exception when there is a greater than expected number of the specified header

2011-04-19 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3456. Resolution: Fixed > WSA implementation does not throw wsa:InvalidCardinality exception when there > is a greater tha

[jira] [Resolved] (CXF-3458) AddressingFeature required Client should throw exception when the wsa header is missing in the inbound message

2011-04-19 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3458. Resolution: Fixed > AddressingFeature required Client should throw exception when the wsa header > is missing in the

[jira] [Created] (CXF-3458) AddressingFeature required Client should throw exception when the wsa header is missing in the inbound message

2011-04-18 Thread jimma (JIRA)
AddressingFeature required Client should throw exception when the wsa header is missing in the inbound message --- Key: CXF-3458 URL: https://issues.apach

[jira] [Created] (CXF-3456) WSA implementation does not throw wsa:InvalidCardinality exception when there is a greater than expected number of the specified header

2011-04-13 Thread jimma (JIRA)
WSA implementation does not throw wsa:InvalidCardinality exception when there is a greater than expected number of the specified header --- Key: CXF

[jira] Resolved: (CXF-3364) No wsdl elements generated for Exception.class

2011-02-24 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3364. Resolution: Fixed > No wsdl elements generated for Exception.class > -- >

[jira] Created: (CXF-3364) No wsdl elements generated for Exception.class

2011-02-24 Thread jimma (JIRA)
No wsdl elements generated for Exception.class -- Key: CXF-3364 URL: https://issues.apache.org/jira/browse/CXF-3364 Project: CXF Issue Type: Bug Components: Tooling Reporter:

[jira] Reopened: (CXF-3209) Service is builtFromWSDL twice

2011-01-20 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma reopened CXF-3209: This fix introduced another problem . When the ClientProxyFactory is configured with MTOMFeature, the databinding can n

[jira] Created: (CXF-3250) EPR's address is NOT used for invocations on the endpoint when the dispatchImpl is created with EPR

2011-01-16 Thread jimma (JIRA)
EPR's address is NOT used for invocations on the endpoint when the dispatchImpl is created with EPR Key: CXF-3250 URL: https://issues.apache.org/jira/browse/CXF-

[jira] Created: (CXF-3209) Service is builtFromWSDL twice

2010-12-21 Thread jimma (JIRA)
Service is builtFromWSDL twice -- Key: CXF-3209 URL: https://issues.apache.org/jira/browse/CXF-3209 Project: CXF Issue Type: Improvement Components: JAX-WS Runtime Affects Versions: 2.3.1

[jira] Resolved: (CXF-3199) Set the wsa action and remove the not understood soap headers in OneWayDecoupledFaultHandler

2010-12-16 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3199. Resolution: Fixed > Set the wsa action and remove the not understood soap headers in > OneWayDecoupledFaultHandler >

[jira] Created: (CXF-3199) Set the wsa action and remove the not understood soap headers in OneWayDecoupledFaultHandler

2010-12-16 Thread jimma (JIRA)
Set the wsa action and remove the not understood soap headers in OneWayDecoupledFaultHandler Key: CXF-3199 URL: https://issues.apache.org/jira/browse/CXF-3199

[jira] Resolved: (CXF-3188) The response code 500 and soapFault are produced for an one way operation when the soap understand headers can not be processed

2010-12-14 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3188. Resolution: Fixed > The response code 500 and soapFault are produced for an one way operation > when the soap unders

[jira] Updated: (CXF-3188) The response code 500 and soapFault are produced for an one way operation when the soap understand headers can not be processed

2010-12-14 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-3188: --- Description: If there are must understand headers can not be processed/understood , server responds with 500 response

[jira] Created: (CXF-3188) The response code 500 and soapFault are produced for an one way operation when the soap understand headers can not be processed

2010-12-13 Thread jimma (JIRA)
The response code 500 and soapFault are produced for an one way operation when the soap understand headers can not be processed --- Key: CXF-3188

[jira] Resolved: (CXF-3181) MAPCodec cancel the entire interceptor chain and throws exception when the server inboud message with RelatesTo header

2010-12-10 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3181. Resolution: Fixed > MAPCodec cancel the entire interceptor chain and throws exception when the > server inboud mess

[jira] Updated: (CXF-3181) MAPCodec cancel the entire interceptor chain and throws exception when the server inboud message with RelatesTo header

2010-12-10 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-3181: --- Description: Since the uncorrelatedExchanges stores the ReplysTo exchange only in client side , we can remove the corr

[jira] Created: (CXF-3181) MAPCodec cancel the entire interceptor chain and throws exception when the server inboud message with RelatesTo header

2010-12-10 Thread jimma (JIRA)
MAPCodec cancel the entire interceptor chain and throws exception when the server inboud message with RelatesTo header --- Key: CXF-3181 URL: http

[jira] Created: (CXF-3157) @PostConstruct doesn't work with servlet transport

2010-11-30 Thread jimma (JIRA)
@PostConstruct doesn't work with servlet transport --- Key: CXF-3157 URL: https://issues.apache.org/jira/browse/CXF-3157 Project: CXF Issue Type: Bug Components: Transports

[jira] Updated: (CXF-3153) doesn't work when the wsdlLocation is provided

2010-11-25 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-3153: --- Component/s: JAX-WS Runtime Affects Version/s: 2.3.0 Fix Version/s: 2.4 Assignee: jimma

[jira] Created: (CXF-3153) doesn't work when the wsdlLocation is provided

2010-11-25 Thread jimma (JIRA)
doesn't work when the wsdlLocation is provided -- Key: CXF-3153 URL: https://issues.apache.org/jira/browse/CXF-3153 Project: CXF Issue Type: Bug

[jira] Resolved: (CXF-3106) JAXWS2.2: responses in @Addressing and @AddressingFeature does not work

2010-11-03 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3106. Resolution: Fixed > JAXWS2.2: responses in @Addressing and @AddressingFeature does not work > ---

[jira] Created: (CXF-3106) JAXWS2.2: responses in @Addressing and @AddressingFeature does not work

2010-11-01 Thread jimma (JIRA)
JAXWS2.2: responses in @Addressing and @AddressingFeature does not work --- Key: CXF-3106 URL: https://issues.apache.org/jira/browse/CXF-3106 Project: CXF Issue Type: Bug

[jira] Resolved: (CXF-3104) @Mtom and @MTOMFeature threshold configuration does not work

2010-10-31 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3104. Resolution: Fixed > @Mtom and @MTOMFeature threshold configuration does not work > -

[jira] Created: (CXF-3104) @Mtom and @MTOMFeature threshold configuration does not work

2010-10-31 Thread jimma (JIRA)
@Mtom and @MTOMFeature threshold configuration does not work - Key: CXF-3104 URL: https://issues.apache.org/jira/browse/CXF-3104 Project: CXF Issue Type: Bug Components:

[jira] Resolved: (CXF-3060) AddressingFeature(true, true) does not work in client side when the wsa policy is not enforced

2010-10-21 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3060. Resolution: Fixed > AddressingFeature(true, true) does not work in client side when the wsa > policy is not enforced

[jira] Resolved: (CXF-3044) Issue with optional policy alternatives and default policy selector

2010-10-17 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3044. Resolution: Later Setting this to later resolution. And discuss this issue again to see if there is need to implemen

[jira] Commented: (CXF-3044) Issue with optional policy alternatives and default policy selector

2010-10-17 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921980#action_12921980 ] jimma commented on CXF-3044: Setting the MaximalAlternativeSelctor in the sever side can fix this

[jira] Assigned: (CXF-3044) Issue with optional policy alternatives and default policy selector

2010-10-12 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma reassigned CXF-3044: -- Assignee: jimma > Issue with optional policy alternatives and default policy selector > -

[jira] Created: (CXF-3060) AddressingFeature(true, true) does not work in client side when the wsa policy is not enforced

2010-10-12 Thread jimma (JIRA)
AddressingFeature(true, true) does not work in client side when the wsa policy is not enforced -- Key: CXF-3060 URL: https://issues.apache.org/jira/browse/CXF-3060

[jira] Created: (CXF-3011) Configure clientImpl synchronousTimeout through BindingProvider.getRequestContext

2010-09-30 Thread jimma (JIRA)
Configure clientImpl synchronousTimeout through BindingProvider.getRequestContext - Key: CXF-3011 URL: https://issues.apache.org/jira/browse/CXF-3011 Project: CXF

[jira] Resolved: (CXF-2991) Configure the http client connection and receive timeout via BindingProvider.getRequestContext

2010-09-30 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2991. Assignee: jimma Resolution: Fixed > Configure the http client connection and receive timeout via > BindingProv

[jira] Created: (CXF-2991) Configure the http client connection and receive timeout via BindingProvider.getRequestContext

2010-09-14 Thread jimma (JIRA)
Configure the http client connection and receive timeout via BindingProvider.getRequestContext -- Key: CXF-2991 URL: https://issues.apache.org/jira/browse/CXF-2991

[jira] Created: (CXF-2974) Log warning message instead of ServiceConstructionException in ReflectionServiceFactoryBean.initializeClassInfo()

2010-09-06 Thread jimma (JIRA)
Log warning message instead of ServiceConstructionException in ReflectionServiceFactoryBean.initializeClassInfo() Key: CXF-2974 URL: https://is

[jira] Resolved: (CXF-2944) targetNamespace value in @WebResult annotation does not respect the refrence element namespace

2010-08-16 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2944. Resolution: Fixed > targetNamespace value in @WebResult annotation does not respect the refrence > element namespace

[jira] Resolved: (CXF-2941) Response wrapper bean generation does not respect the @WebResult annotation

2010-08-16 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2941. Resolution: Fixed > Response wrapper bean generation does not respect the @WebResult annotation > ---

[jira] Resolved: (CXF-2935) The targentNamespace value in @Webparam generated from a reference element is wrong

2010-08-16 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2935. Resolution: Fixed > The targentNamespace value in @Webparam generated from a reference element is > wrong >

[jira] Resolved: (CXF-2934) The wrong target namespace of filed in response wrapper bean is generated

2010-08-16 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2934. Resolution: Fixed > The wrong target namespace of filed in response wrapper bean is generated >

[jira] Created: (CXF-2944) targetNamespace value in @WebResult annotation does not respect the refrence element namespace

2010-08-16 Thread jimma (JIRA)
targetNamespace value in @WebResult annotation does not respect the refrence element namespace -- Key: CXF-2944 URL: https://issues.apache.org/jira/browse/CXF-2944

[jira] Created: (CXF-2941) Response wrapper bean generation does not respect the @WebResult annotation

2010-08-13 Thread jimma (JIRA)
Response wrapper bean generation does not respect the @WebResult annotation --- Key: CXF-2941 URL: https://issues.apache.org/jira/browse/CXF-2941 Project: CXF Issue Type

[jira] Updated: (CXF-2935) The targentNamespace value in @Webparam generated from a reference element is wrong

2010-08-10 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-2935: --- Summary: The targentNamespace value in @Webparam generated from a reference element is wrong (was: The targent namespa

[jira] Created: (CXF-2935) The targent namespace in @Webparam generated from a reference element in the wrapped operation is wrong

2010-08-10 Thread jimma (JIRA)
The targent namespace in @Webparam generated from a reference element in the wrapped operation is wrong Key: CXF-2935 URL: https://issues.apache.org/jira/bro

[jira] Created: (CXF-2934) The wrong target namespace of filed in response wrapper bean is generated

2010-08-10 Thread jimma (JIRA)
The wrong target namespace of filed in response wrapper bean is generated -- Key: CXF-2934 URL: https://issues.apache.org/jira/browse/CXF-2934 Project: CXF Issue Type:

[jira] Resolved: (CXF-2918) URIParserUtil.getAbsoluteURL() does not return a nomalized url string

2010-08-09 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2918. Resolution: Fixed > URIParserUtil.getAbsoluteURL() does not return a nomalized url string > -

[jira] Created: (CXF-2918) URIParserUtil.getAbsoluteURL() does not return a nomalized url string

2010-07-30 Thread jimma (JIRA)
URIParserUtil.getAbsoluteURL() does not return a nomalized url string - Key: CXF-2918 URL: https://issues.apache.org/jira/browse/CXF-2918 Project: CXF Issue Type: Bug

[jira] Resolved: (CXF-2911) HttpServletRequest.getScheme() returns null in one way webservice method

2010-07-28 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2911. Resolution: Fixed > HttpServletRequest.getScheme() returns null in one way webservice method > -

[jira] Created: (CXF-2911) HttpServletRequest.getScheme() returns null in one way webservice method

2010-07-26 Thread jimma (JIRA)
HttpServletRequest.getScheme() returns null in one way webservice method - Key: CXF-2911 URL: https://issues.apache.org/jira/browse/CXF-2911 Project: CXF Issue Type: Bu

[jira] Resolved: (CXF-2867) Skip wsa policy verification when client proxy is created with AddressingFeature(required=false)

2010-07-12 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2867. Resolution: Fixed > Skip wsa policy verification when client proxy is created with > AddressingFeature(required=fal

[jira] Resolved: (CXF-2868) JAXB unmarshal error when the field of partTypeClass is javax.xml.datatype.XMLGregorianCalendar

2010-07-12 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2868. Resolution: Fixed > JAXB unmarshal error when the field of partTypeClass is > javax.xml.datatype.XMLGregorianCale

[jira] Updated: (CXF-2867) Skip wsa policy verification when client proxy is created with AddressingFeature(required=false)

2010-07-02 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-2867: --- Summary: Skip wsa policy verification when client proxy is created with AddressingFeature(required=false) (was: Not

[jira] Updated: (CXF-2867) Not throw PolicyException when client proxy is created with AddressingFeature(required=false)

2010-07-02 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-2867: --- Summary: Not throw PolicyException when client proxy is created with AddressingFeature(required=false) (was: Do n

[jira] Created: (CXF-2868) JAXB unmarshal error when the field of partTypeClass is javax.xml.datatype.XMLGregorianCalendar

2010-07-02 Thread jimma (JIRA)
JAXB unmarshal error when the field of partTypeClass is javax.xml.datatype.XMLGregorianCalendar -- Key: CXF-2868 URL: https://issues.apache.org/jira/browse/CXF-2868

[jira] Created: (CXF-2867) Do not throw PolicyException when client side uses AddressingFeature(required=false)

2010-07-02 Thread jimma (JIRA)
Do not throw PolicyException when client side uses AddressingFeature(required=false) - Key: CXF-2867 URL: https://issues.apache.org/jira/browse/CXF-2867 Project: CXF

[jira] Updated: (CXF-2867) Do not throw PolicyException when client proxy is created with AddressingFeature(required=false)

2010-07-02 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-2867: --- Summary: Do not throw PolicyException when client proxy is created with AddressingFeature(required=false) (was: Do no

[jira] Resolved: (CXF-2850) Throw correct SOAPFaultException when the wsa addressing header is missing

2010-07-01 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2850. Resolution: Fixed > Throw correct SOAPFaultException when the wsa addressing header is missing > ---

[jira] Resolved: (CXF-2860) Handle the soap fault inbound message in server side

2010-06-27 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2860. Resolution: Fixed > Handle the soap fault inbound message in server side > --

[jira] Updated: (CXF-2860) Handle the soap fault inbound message in server side

2010-06-24 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-2860: --- Description: When using WSA, the service is configured a FaultTo endpoint which is not the same as the From endpoint ,

[jira] Created: (CXF-2860) Handle the soap fault inbound message in server side

2010-06-24 Thread jimma (JIRA)
Handle the soap fault inbound message in server side Key: CXF-2860 URL: https://issues.apache.org/jira/browse/CXF-2860 Project: CXF Issue Type: Improvement Components: Core

[jira] Created: (CXF-2858) TransportURIResolver can not get the import resource file correctly

2010-06-20 Thread jimma (JIRA)
TransportURIResolver can not get the import resource file correctly --- Key: CXF-2858 URL: https://issues.apache.org/jira/browse/CXF-2858 Project: CXF Issue Type: Bug

[jira] Created: (CXF-2850) Throw correct SOAPFaultException when the wsa addressing header is missing

2010-06-16 Thread jimma (JIRA)
Throw correct SOAPFaultException when the wsa addressing header is missing --- Key: CXF-2850 URL: https://issues.apache.org/jira/browse/CXF-2850 Project: CXF Issue Type

[jira] Created: (CXF-2849) Update to jaxws2.2 API

2010-06-16 Thread jimma (JIRA)
Update to jaxws2.2 API -- Key: CXF-2849 URL: https://issues.apache.org/jira/browse/CXF-2849 Project: CXF Issue Type: Task Components: JAX-WS Runtime Reporter: jimma Assignee: jimma

[jira] Created: (CXF-2845) JAXWS2.2: Implement new added apis javax.xml.ws.spi.http.*

2010-06-11 Thread jimma (JIRA)
JAXWS2.2: Implement new added apis javax.xml.ws.spi.http.* --- Key: CXF-2845 URL: https://issues.apache.org/jira/browse/CXF-2845 Project: CXF Issue Type: Task Components: JAX

[jira] Updated: (CXF-2845) JAXWS2.2: Implement new added HTTP SPI APIs

2010-06-11 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-2845: --- Summary: JAXWS2.2: Implement new added HTTP SPI APIs (was: JAXWS2.2: Implement new added apis javax.xml.ws.spi.http.*

[jira] Resolved: (CXF-2842) wsa:action header is missing when the wsam:Action="" in wsdl input

2010-06-11 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2842. Resolution: Fixed > wsa:action header is missing when the wsam:Action="" in wsdl input > --

[jira] Resolved: (CXF-2843) The default wsa:action value computation for response message is not correct.

2010-06-11 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2843. Resolution: Fixed > The default wsa:action value computation for response message is not correct. >

[jira] Resolved: (CXF-2840) JAXWS2.2: Process the EPR in WSDL

2010-06-11 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2840. Resolution: Fixed > JAXWS2.2: Process the EPR in WSDL > - > > Key: CX

[jira] Updated: (CXF-2843) The default wsa:action value computation for response message is not correct.

2010-06-10 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-2843: --- Description: The wsa:action value computation in wsdl1.1 is confused in spec :http://www.w3.org/TR/2006/CR-ws-addr-wsd

[jira] Created: (CXF-2843) The default wsa:action value computation for response message is not correct.

2010-06-10 Thread jimma (JIRA)
The default wsa:action value computation for response message is not correct. -- Key: CXF-2843 URL: https://issues.apache.org/jira/browse/CXF-2843 Project: CXF Issu

[jira] Created: (CXF-2842) Empty wsa:action header when the wsam:Action="" in wsdl input

2010-06-10 Thread jimma (JIRA)
Empty wsa:action header when the wsam:Action="" in wsdl input -- Key: CXF-2842 URL: https://issues.apache.org/jira/browse/CXF-2842 Project: CXF Issue Type: Bug Components

[jira] Updated: (CXF-2842) wsa:action header is missing when the wsam:Action="" in wsdl input

2010-06-10 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-2842: --- Summary: wsa:action header is missing when the wsam:Action="" in wsdl input (was: Empty wsa:action header when the

[jira] Created: (CXF-2840) JAXWS2.2: Process the EPR in WSDL

2010-06-07 Thread jimma (JIRA)
JAXWS2.2: Process the EPR in WSDL - Key: CXF-2840 URL: https://issues.apache.org/jira/browse/CXF-2840 Project: CXF Issue Type: Task Components: JAX-WS Runtime Reporter: jimma

[jira] Resolved: (CXF-2836) JAXWS2.2: Generate proper wsa:action header for dispatch instance when AddressinfFeature is enabled

2010-06-07 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2836. Fix Version/s: 2.3 Resolution: Fixed > JAXWS2.2: Generate proper wsa:action header for dispatch instance when

[jira] Created: (CXF-2836) JAXWS2.2: Generate proper wsa:action header for dispatch instance when AddressinfFeature is enabled

2010-06-01 Thread jimma (JIRA)
JAXWS2.2: Generate proper wsa:action header for dispatch instance when AddressinfFeature is enabled --- Key: CXF-2836 URL: https://issues.apache.org/jira/browse/CXF-28

[jira] Assigned: (CXF-2836) JAXWS2.2: Generate proper wsa:action header for dispatch instance when AddressinfFeature is enabled

2010-06-01 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma reassigned CXF-2836: -- Assignee: jimma > JAXWS2.2: Generate proper wsa:action header for dispatch instance when > AddressinfFeature is

[jira] Resolved: (CXF-2834) JAXWS2.2:MAPCodec.restoreExchange() does not honor the addressingDisabled property

2010-05-31 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2834. Resolution: Fixed > JAXWS2.2:MAPCodec.restoreExchange() does not honor the addressingDisabled > property > -

[jira] Updated: (CXF-2834) JAXWS2.2:MAPCodec.restoreExchange() does not honor the addressingDisabled property

2010-05-30 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-2834: --- Summary: JAXWS2.2:MAPCodec.restoreExchange() does not honor the addressingDisabled property (was: JAXWS2.2:M

[jira] Created: (CXF-2834) JAXWS2.2:MAPCodec.restoreExchange() does not honor the addressingDisabled"

2010-05-30 Thread jimma (JIRA)
JAXWS2.2:MAPCodec.restoreExchange() does not honor the addressingDisabled" -- Key: CXF-2834 URL: https://issues.apache.org/jira/browse/CXF-2834 Project: CXF Issue Type:

[jira] Resolved: (CXF-2831) JAXWS2.2: Compute wsam:action value for SEI method annotated with empty @FaultAction(className=AddNumbersException.class, value=""))

2010-05-28 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2831. Resolution: Fixed > JAXWS2.2: Compute wsam:action value for SEI method annotated with empty > @FaultAction(className

[jira] Created: (CXF-2831) JAXWS2.2: Compute wsam:action value for SEI method annotated with empty @FaultAction(className=AddNumbersException.class, value=""))

2010-05-27 Thread jimma (JIRA)
JAXWS2.2: Compute wsam:action value for SEI method annotated with empty @FaultAction(className=AddNumbersException.class, value="")) Key: CXF-2831

[jira] Resolved: (CXF-2827) JAXWS2.2: wsam:action attribute is not generated in and element when the SEI method is not annotated with @Action

2010-05-27 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2827. Resolution: Fixed > JAXWS2.2: wsam:action attribute is not generated in and > element when the SEI method is not a

[jira] Updated: (CXF-2827) JAXWS2.2: wsam:action attribute is not generated in and element when the SEI method is not annotated with @Action

2010-05-27 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-2827: --- Summary: JAXWS2.2: wsam:action attribute is not generated in and element when the SEI method is not annotated wit

[jira] Updated: (CXF-2827) JAXWS2.2: wsam:action attribute is not generated in and element when the SEI method is not annotated with @Action

2010-05-27 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma updated CXF-2827: --- Component/s: Tooling > JAXWS2.2: wsam:action attribute is not generated in and > element when the SEI method is not

[jira] Created: (CXF-2827) JAXWS2.2: URI is not correct for the SEI method without @Action for input and output

2010-05-26 Thread jimma (JIRA)
JAXWS2.2: URI is not correct for the SEI method without @Action for input and output Key: CXF-2827 URL: https://issues.apache.org/jira/browse/CXF-2827

[jira] Resolved: (CXF-2822) The interceptor is not added to the ClientImpl when create the dispatch to invoke service

2010-05-25 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2822. Resolution: Fixed > The interceptor is not added to the ClientImpl when create the dispatch to > invoke service > --

[jira] Created: (CXF-2822) The interceptor is not added to the ClientImpl when create the dispatch to invoke service

2010-05-24 Thread jimma (JIRA)
The interceptor is not added to the ClientImpl when create the dispatch to invoke service - Key: CXF-2822 URL: https://issues.apache.org/jira/browse/CXF-2822 Proj

[jira] Resolved: (CXF-2819) ##SOAP12_Binding in handler chain is not correctly matched

2010-05-21 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-2819. Resolution: Fixed > ##SOAP12_Binding in handler chain is not > correctly matched > --

  1   2   >