[jira] [Created] (CXF-5274) WS-RM should provide application access to acknowledgments

2013-09-11 Thread Dennis Sosnoski (JIRA)
Dennis Sosnoski created CXF-5274: Summary: WS-RM should provide application access to acknowledgments Key: CXF-5274 URL: https://issues.apache.org/jira/browse/CXF-5274 Project: CXF Issue Type

[jira] [Resolved] (CXF-5272) NPE will cause the camel-cxf endpoint start error in blueprint

2013-09-11 Thread Willem Jiang (JIRA)
[ https://issues.apache.org/jira/browse/CXF-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CXF-5272. --- Resolution: Fixed Applied patch into trunk, 2.7.x-fixes, and 2.6.x-fixes. > NPE will c

[jira] [Created] (CXF-5273) Filter the interceptor according to Phase instead of class name in WSDLGetInterceptor

2013-09-11 Thread Willem Jiang (JIRA)
Willem Jiang created CXF-5273: - Summary: Filter the interceptor according to Phase instead of class name in WSDLGetInterceptor Key: CXF-5273 URL: https://issues.apache.org/jira/browse/CXF-5273 Project: CX

[jira] [Updated] (CXF-5272) NPE will cause the camel-cxf endpoint start error in blueprint

2013-09-11 Thread Willem Jiang (JIRA)
[ https://issues.apache.org/jira/browse/CXF-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CXF-5272: -- Fix Version/s: 2.6.10 > NPE will cause the camel-cxf endpoint start error in blueprint >

[jira] [Created] (CXF-5272) NPE will cause the camel-cxf endpoint start error in blueprint

2013-09-11 Thread Willem Jiang (JIRA)
Willem Jiang created CXF-5272: - Summary: NPE will cause the camel-cxf endpoint start error in blueprint Key: CXF-5272 URL: https://issues.apache.org/jira/browse/CXF-5272 Project: CXF Issue Type:

[jira] [Resolved] (CXF-5265) Netty Http transport can handler ?wsdl request rightly

2013-09-11 Thread Willem Jiang (JIRA)
[ https://issues.apache.org/jira/browse/CXF-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CXF-5265. --- Resolution: Fixed Applied the patch into trunk. > Netty Http transport can handler ?ws

[jira] [Commented] (CXF-5267) WebClient using POST with chunking enabled (the default) can't read 401 error response stream

2013-09-11 Thread Jesse Pangburn (JIRA)
[ https://issues.apache.org/jira/browse/CXF-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764784#comment-13764784 ] Jesse Pangburn commented on CXF-5267: - Do you mean write a similar test using Apache Htt

[jira] [Commented] (CXF-5267) WebClient using POST with chunking enabled (the default) can't read 401 error response stream

2013-09-11 Thread Sergey Beryozkin (JIRA)
[ https://issues.apache.org/jira/browse/CXF-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764710#comment-13764710 ] Sergey Beryozkin commented on CXF-5267: --- Hi, thanks for doing a quick test - it does c

[jira] [Created] (CXF-5271) Event.CLIENT_CREATED fired too soon

2013-09-11 Thread Daniel Kulp (JIRA)
Daniel Kulp created CXF-5271: Summary: Event.CLIENT_CREATED fired too soon Key: CXF-5271 URL: https://issues.apache.org/jira/browse/CXF-5271 Project: CXF Issue Type: Bug Components: Cor

[jira] [Resolved] (CXF-5271) Event.CLIENT_CREATED fired too soon

2013-09-11 Thread Daniel Kulp (JIRA)
[ https://issues.apache.org/jira/browse/CXF-5271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-5271. -- Resolution: Fixed > Event.CLIENT_CREATED fired too soon > --- > >

[jira] [Commented] (CXF-5268) Automatic WS-Policy computation should be possible on Dispatch clients without setting operation manually

2013-09-11 Thread Jesse Pangburn (JIRA)
[ https://issues.apache.org/jira/browse/CXF-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764476#comment-13764476 ] Jesse Pangburn commented on CXF-5268: - Awesome! From the first time I looked at this co

[jira] [Commented] (CXF-5267) WebClient using POST with chunking enabled (the default) can't read 401 error response stream

2013-09-11 Thread Jesse Pangburn (JIRA)
[ https://issues.apache.org/jira/browse/CXF-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764565#comment-13764565 ] Jesse Pangburn commented on CXF-5267: - Hi Sergey, well I can say I'm completely surprise

[jira] [Commented] (CXF-5267) WebClient using POST with chunking enabled (the default) can't read 401 error response stream

2013-09-11 Thread Sergey Beryozkin (JIRA)
[ https://issues.apache.org/jira/browse/CXF-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764502#comment-13764502 ] Sergey Beryozkin commented on CXF-5267: --- Hi Jesse, can you give me a favor and confirm

[jira] [Resolved] (CXF-5268) Automatic WS-Policy computation should be possible on Dispatch clients without setting operation manually

2013-09-11 Thread Daniel Kulp (JIRA)
[ https://issues.apache.org/jira/browse/CXF-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-5268. -- Resolution: Fixed Fix Version/s: 2.7.7 Assignee: Daniel Kulp This also allows removal of

[jira] [Commented] (CXF-5268) Automatic WS-Policy computation should be possible on Dispatch clients without setting operation manually

2013-09-11 Thread Daniel Kulp (JIRA)
[ https://issues.apache.org/jira/browse/CXF-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764389#comment-13764389 ] Daniel Kulp commented on CXF-5268: -- Arg looking at this code, the whole stuff around t

[jira] [Updated] (CXF-4878) Avoid trying to register Jetty MBean if already registered to avoid very ugly WARN with stacktrace

2013-09-11 Thread Daniel Kulp (JIRA)
[ https://issues.apache.org/jira/browse/CXF-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated CXF-4878: - CXF Fields: Blocked on External > Avoid trying to register Jetty MBean if already registered to avoid v

[jira] [Commented] (FEDIZ-8) Add support for OAuth

2013-09-11 Thread Sergey Beryozkin (JIRA)
[ https://issues.apache.org/jira/browse/FEDIZ-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764199#comment-13764199 ] Sergey Beryozkin commented on FEDIZ-8: -- I think it can be interesting to consider gettin

[jira] [Resolved] (CXF-5270) XKMS Crypto Client does not check local keystore for "locate" if the alias is actually a Subject DN

2013-09-11 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/CXF-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CXF-5270. -- Resolution: Fixed > XKMS Crypto Client does not check local keystore for "locate" if

[jira] [Commented] (CXF-4878) Avoid trying to register Jetty MBean if already registered to avoid very ugly WARN with stacktrace

2013-09-11 Thread Freeman Fang (JIRA)
[ https://issues.apache.org/jira/browse/CXF-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764182#comment-13764182 ] Freeman Fang commented on CXF-4878: --- Found that we can't workaround on CXF side, as some j

[jira] [Created] (CXF-5270) XKMS Crypto Client does not check local keystore for "locate" if the alias is actually a Subject DN

2013-09-11 Thread Colm O hEigeartaigh (JIRA)
Colm O hEigeartaigh created CXF-5270: Summary: XKMS Crypto Client does not check local keystore for "locate" if the alias is actually a Subject DN Key: CXF-5270 URL: https://issues.apache.org/jira/browse/CXF-5

[jira] [Commented] (CXF-4878) Avoid trying to register Jetty MBean if already registered to avoid very ugly WARN with stacktrace

2013-09-11 Thread Freeman Fang (JIRA)
[ https://issues.apache.org/jira/browse/CXF-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764163#comment-13764163 ] Freeman Fang commented on CXF-4878: --- Another way is workaround it on CXF side, add a org.

[jira] [Commented] (CXF-4878) Avoid trying to register Jetty MBean if already registered to avoid very ugly WARN with stacktrace

2013-09-11 Thread Freeman Fang (JIRA)
[ https://issues.apache.org/jira/browse/CXF-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764162#comment-13764162 ] Freeman Fang commented on CXF-4878: --- The id=0 is generated in jetty code. We can run into

[jira] [Resolved] (CXF-5230) Message element is not generated for Exception class

2013-09-11 Thread Jim Ma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Ma resolved CXF-5230. - Resolution: Fixed > Message element is not generated for Exception class >

[jira] [Assigned] (CXF-4878) Avoid trying to register Jetty MBean if already registered to avoid very ugly WARN with stacktrace

2013-09-11 Thread Freeman Fang (JIRA)
[ https://issues.apache.org/jira/browse/CXF-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-4878: - Assignee: Freeman Fang (was: Willem Jiang) > Avoid trying to register Jetty MBean if already r

[jira] [Updated] (CXF-5269) the ws-security.encryption.username property not been taken into account when using XKMS service on CXF client

2013-09-11 Thread Xilai Dai (JIRA)
[ https://issues.apache.org/jira/browse/CXF-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xilai Dai updated CXF-5269: --- Description: the properties configured with spring for CXF client looks like: ..

[jira] [Created] (CXF-5269) the ws-security.encryption.username property not been taken into account when using XKMS service on CXF client

2013-09-11 Thread Xilai Dai (JIRA)
Xilai Dai created CXF-5269: -- Summary: the ws-security.encryption.username property not been taken into account when using XKMS service on CXF client Key: CXF-5269 URL: https://issues.apache.org/jira/browse/CXF-5269