[ 
https://issues.apache.org/jira/browse/CXF-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967159#action_12967159
 ] 

Sergey Beryozkin commented on CXF-3160:
---------------------------------------

Hi Christian

I was involved a bit awhile back into the discussions surrounding query 
handlers. Example, CXF offers a default WSDLQueryHandler and someone can write 
a custom one and which will be used instead of it.
But generally, the query handlers are for handling HTTP queries, those starting 
with '?' and thus it would make sense IMHO to keep them dealing with HTTP 
queries only. I would not 'overload' them.

As far as service listings are concerned - please note that it is possible to 
configure CXFServlet to use alternative path segments for service listings, ex, 
"/listings" instead of '/services'. There could be a jaxrs system test 
verifying it, but mentioning it just in case. 
It would be nice to make it easy for users to customize the way the service 
listings are presented, such that a user
handler or custom servlet extending CXFServlet can be presented with all the 
information needed to build a view. 


cheers, Sergey





> Reduce Code duplication between http transport variants
> -------------------------------------------------------
>
>                 Key: CXF-3160
>                 URL: https://issues.apache.org/jira/browse/CXF-3160
>             Project: CXF
>          Issue Type: Improvement
>          Components: Transports
>    Affects Versions: 2.3.0
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>         Attachments: CXF-3160-1.patch, CXF-3160-2.patch
>
>
> We still have to much duplicated or very similar code in the http transports. 
> Moving header code from AbstractHttpDestination to Headers
> Moving invokeDestination from ServletController to AbstractServletController 
> to share this code with http-osgi
> Moving invoke from ServletDestination to AbstractHttpDestination  to share 
> this code with http-osgi
> Removing doMessage from OsgiDestination
> Removing invokeDestination from OsgiServletcontroller
> Ignoring some mock based tests that do not work anymore. Will have to do some 
> work on them
> There are some small changes in the behaviour for http-osgi as we are now 
> using the servlet code here. It would be great if Sergey or Dan could review 
> this. IdonĀ“t think the differences are important but I am not sure.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to