[jira] [Updated] (CXF-5772) CXF codegen plugin: Expose original wsdl through wsdlLocation generates a duplicate option exception

[ https://issues.apache.org/jira/browse/CXF-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel C updated CXF-5772: - Priority: Major (was: Minor) > CXF codegen plugin: Expose original wsdl through wsdlLocation generates a > duplic

[jira] [Created] (CXF-5782) Lower logging level of generated class names

Tom Dunstan created CXF-5782: Summary: Lower logging level of generated class names Key: CXF-5782 URL: https://issues.apache.org/jira/browse/CXF-5782 Project: CXF Issue Type: Improvement

[jira] [Created] (CXF-5781) Port ou of Range: -1

Guilherme Veloso Neves Oliveira created CXF-5781: Summary: Port ou of Range: -1 Key: CXF-5781 URL: https://issues.apache.org/jira/browse/CXF-5781 Project: CXF Issue Type: Bug

[jira] [Commented] (CXF-5761) InInterceptor throws exception with PrettyLogging and big message size

[ https://issues.apache.org/jira/browse/CXF-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016869#comment-14016869 ] Przemysław Ołtarzewski commented on CXF-5761: - Hello, I have encountered a simi

[jira] [Commented] (CXF-5776) @PathParam not works inside @BeanParam

[ https://issues.apache.org/jira/browse/CXF-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016860#comment-14016860 ] MIchail Nikolaev commented on CXF-5776: --- same behavior in 2.7.12-SNAPSHOT (it is expec

[jira] [Commented] (CXF-5776) @PathParam not works inside @BeanParam

[ https://issues.apache.org/jira/browse/CXF-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016854#comment-14016854 ] MIchail Nikolaev commented on CXF-5776: --- You mean 2.7.12-SNAPSHOT? > @PathParam not w

[jira] [Commented] (CXF-5776) @PathParam not works inside @BeanParam

[ https://issues.apache.org/jira/browse/CXF-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016841#comment-14016841 ] Sergey Beryozkin commented on CXF-5776: --- Indeed, the original issue description did no

[jira] [Comment Edited] (CXF-5776) @PathParam not works inside @BeanParam

[ https://issues.apache.org/jira/browse/CXF-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016816#comment-14016816 ] MIchail Nikolaev edited comment on CXF-5776 at 6/3/14 3:57 PM: ---

[jira] [Reopened] (CXF-5776) @PathParam not works inside @BeanParam

[ https://issues.apache.org/jira/browse/CXF-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MIchail Nikolaev reopened CXF-5776: --- > @PathParam not works inside @BeanParam > -- > >

[jira] [Commented] (CXF-5776) @PathParam not works inside @BeanParam

[ https://issues.apache.org/jira/browse/CXF-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016816#comment-14016816 ] MIchail Nikolaev commented on CXF-5776: --- [~sergeyb] looks like I not clearly explained

[jira] [Commented] (CXF-5776) @PathParam not works inside @BeanParam

[ https://issues.apache.org/jira/browse/CXF-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016574#comment-14016574 ] Sergey Beryozkin commented on CXF-5776: --- m.getParameterAnnotations()[0] returns all an

[jira] [Resolved] (CXF-5776) @PathParam not works inside @BeanParam

[ https://issues.apache.org/jira/browse/CXF-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-5776. --- Resolution: Invalid Assignee: Sergey Beryozkin > @PathParam not works inside @BeanParam >

[jira] [Commented] (CXF-5771) Limitation of handling bean params inside ClientProxyImpl

[ https://issues.apache.org/jira/browse/CXF-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016563#comment-14016563 ] Sergey Beryozkin commented on CXF-5771: --- Never mind, BeanParam API docs list an exampl

[jira] [Resolved] (CXF-5775) Constraint Validation Exceptions Logging at Warn logging.LogUtils

[ https://issues.apache.org/jira/browse/CXF-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-5775. --- Resolution: Fixed Fix Version/s: 3.0.1 Assignee: Sergey Beryozkin > Constraint

[jira] [Commented] (CXF-5775) Constraint Validation Exceptions Logging at Warn logging.LogUtils

[ https://issues.apache.org/jira/browse/CXF-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016488#comment-14016488 ] Sergey Beryozkin commented on CXF-5775: --- Hi I've updated JAXRSBeanValidationInInterce

[jira] [Commented] (CXF-5740) CXF-5610 is preventing applications from using the same endpoint url for multiple hadlers

[ https://issues.apache.org/jira/browse/CXF-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016447#comment-14016447 ] Sergey Beryozkin commented on CXF-5740: --- Hi, thanks for attaching the example code. I'

[jira] [Resolved] (CXF-5779) Setting custom status loses the Reason Phrase

[ https://issues.apache.org/jira/browse/CXF-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-5779. --- Resolution: Duplicate Assignee: Sergey Beryozkin This is a JAX-RS level issue, see https:

[jira] [Commented] (CXF-5779) Setting custom status loses the Reason Phrase

[ https://issues.apache.org/jira/browse/CXF-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016389#comment-14016389 ] Sergey Beryozkin commented on CXF-5779: --- This is a JAX-RS API level issue, see https:/

[jira] [Commented] (CXF-5771) Limitation of handling bean params inside ClientProxyImpl

[ https://issues.apache.org/jira/browse/CXF-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016376#comment-14016376 ] Sergey Beryozkin commented on CXF-5771: --- Hi, is there a good technical reason why a ne