[jira] [Commented] (CXF-7571) Revamp of the CXF injection implementation

2017-12-29 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CXF-7571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306434#comment-16306434
 ] 

ASF GitHub Bot commented on CXF-7571:
-

reta commented on a change in pull request #351: [CXF-7571] Adding support for 
CDI injection of @Context objects.
URL: https://github.com/apache/cxf/pull/351#discussion_r159089178
 
 

 ##
 File path: 
systests/cdi/base/src/main/java/org/apache/cxf/systests/cdi/base/BookStoreVersion.java
 ##
 @@ -22,20 +22,25 @@
 import javax.enterprise.context.RequestScoped;
 import javax.inject.Inject;
 import javax.ws.rs.GET;
-import javax.ws.rs.core.Context;
 import javax.ws.rs.core.HttpHeaders;
 import javax.ws.rs.core.MediaType;
 import javax.ws.rs.core.Response;
 
+import org.apache.cxf.systests.cdi.base.context.CustomContext;
+
 @RequestScoped
 public class BookStoreVersion {
 @Inject
 private String version;
-@Context
+@Inject
 private HttpHeaders httpHeaders;
+@Inject
 
 Review comment:
   @johnament Not sure I understood the exact nature of the problem, but with 
`@Context` annotation the `CustomContext` is being processed by 
`DelegateContextAnnotatedType` which injects into it the proxy value (CDI 
managed one), and later on the instance is created by `ContextProducerBean` on 
first invocation.  Is it something along this lines or absolutely different 
flow?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


>  Revamp of the CXF injection implementation
> ---
>
> Key: CXF-7571
> URL: https://issues.apache.org/jira/browse/CXF-7571
> Project: CXF
>  Issue Type: Improvement
>Reporter: Andriy Redko
>Assignee: John D. Ament
>
> As more deep integration with CDI revealed, there are complexities in 
> bringing together {{@Context}}- and {{@Inject}}-based injections. 
> Encapsulating CXF injection implementation and than delegating the hard work 
> to appropriate strategy (CDI, Spring, ...) would be the right solution to 
> address the problem at its roots.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (CXF-7200) wadl2java does not see generated classes with jaxb:nameXmlTransform

2017-12-29 Thread Sergey Beryozkin (JIRA)

 [ 
https://issues.apache.org/jira/browse/CXF-7200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Beryozkin resolved CXF-7200.
---
   Resolution: Fixed
Fix Version/s: 3.2.2
   3.1.15

I've added this option, test the snapshots please

> wadl2java does not see generated classes with jaxb:nameXmlTransform 
> 
>
> Key: CXF-7200
> URL: https://issues.apache.org/jira/browse/CXF-7200
> Project: CXF
>  Issue Type: Improvement
>  Components: JAXB Databinding
>Affects Versions: 3.1.9
>Reporter: Vjacheslav Borisov
>Assignee: Sergey Beryozkin
>Priority: Minor
> Fix For: 3.1.15, 3.2.2
>
>
> wadl2java does not see generated classes with jaxb:nameXmlTransform enabled 
> E.g. If i want to add suffix DTO to all generated classes, wadl2java stops 
> finding them
> Example config 
> 
> 
> 
> 
> 
> 
> 
> Without this setting i see generated  method
> ...
> Test list();
> ...
> With this setting expected to see 
> TestDTO  list();
> but I see 
> Response list();
> This is example project 
> https://github.com/slavb18/namexmltransform
> schemas here  
> https://github.com/slavb18/namexmltransform/tree/master/src/main/resources/schemas/test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Reopened] (CXF-7200) wadl2java does not see generated classes with jaxb:nameXmlTransform

2017-12-29 Thread Sergey Beryozkin (JIRA)

 [ 
https://issues.apache.org/jira/browse/CXF-7200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Beryozkin reopened CXF-7200:
---
  Assignee: Sergey Beryozkin  (was: Freeman Fang)

> wadl2java does not see generated classes with jaxb:nameXmlTransform 
> 
>
> Key: CXF-7200
> URL: https://issues.apache.org/jira/browse/CXF-7200
> Project: CXF
>  Issue Type: Improvement
>  Components: JAXB Databinding
>Affects Versions: 3.1.9
>Reporter: Vjacheslav Borisov
>Assignee: Sergey Beryozkin
>Priority: Minor
>
> wadl2java does not see generated classes with jaxb:nameXmlTransform enabled 
> E.g. If i want to add suffix DTO to all generated classes, wadl2java stops 
> finding them
> Example config 
> 
> 
> 
> 
> 
> 
> 
> Without this setting i see generated  method
> ...
> Test list();
> ...
> With this setting expected to see 
> TestDTO  list();
> but I see 
> Response list();
> This is example project 
> https://github.com/slavb18/namexmltransform
> schemas here  
> https://github.com/slavb18/namexmltransform/tree/master/src/main/resources/schemas/test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)