[
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
[
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
[
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
[
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
[
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
> ---
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
[
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
[
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
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/
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
[
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
> ---
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
[
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:
[
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
> -
IllegalArgumentException: wrong number of arguments with Dispatch/Provider
service
--
Key: CXF-3502
URL: https://issues.apache.org/jira/browse/CXF-3502
Project: CXF
[
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
[
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
AddressingFeature required Client should throw exception when the wsa header is
missing in the inbound message
---
Key: CXF-3458
URL: https://issues.apach
WSA implementation does not throw wsa:InvalidCardinality exception when there
is a greater than expected number of the specified header
---
Key: CXF
[
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
> --
>
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:
[
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
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-
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
[
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
>
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
[
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
[
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
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
[
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
[
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
MAPCodec cancel the entire interceptor chain and throws exception when the
server inboud message with RelatesTo header
---
Key: CXF-3181
URL: http
@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
[
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
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
[
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
> ---
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
[
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
> -
@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:
[
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
[
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
[
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
[
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
> -
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
Configure clientImpl synchronousTimeout through
BindingProvider.getRequestContext
-
Key: CXF-3011
URL: https://issues.apache.org/jira/browse/CXF-3011
Project: CXF
[
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
Configure the http client connection and receive timeout via
BindingProvider.getRequestContext
--
Key: CXF-2991
URL: https://issues.apache.org/jira/browse/CXF-2991
Log warning message instead of ServiceConstructionException in
ReflectionServiceFactoryBean.initializeClassInfo()
Key: CXF-2974
URL: https://is
[
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
[
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
> ---
[
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
>
[
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
>
targetNamespace value in @WebResult annotation does not respect the refrence
element namespace
--
Key: CXF-2944
URL: https://issues.apache.org/jira/browse/CXF-2944
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
[
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
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
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:
[
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
> -
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
[
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
> -
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
[
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
[
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
[
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
[
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
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
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
[
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
[
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
> ---
[
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
> --
[
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 ,
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
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
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
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
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
[
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.*
[
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
> --
[
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.
>
[
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
[
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
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
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
[
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
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
[
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
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
[
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
[
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
> -
[
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
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:
[
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
JAXWS2.2: Compute wsam:action value for SEI method annotated with empty
@FaultAction(className=AddNumbersException.class, value=""))
Key: CXF-2831
[
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
[
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
[
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
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
[
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
> --
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
[
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 - 100 of 106 matches
Mail list logo