[
https://issues.apache.org/jira/browse/CXF-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611255#action_12611255
]
dkulp edited comment on CXF-1355 at 7/7/08 10:47 AM:
-----------------------------------------------------------
One "issue" with this is should the default databinding be JAXB or Aegis? In
general, with CXF, we definitely prefer going the JAXB route.
It might make sense to parameterize the service configurations and databinding
stuff somehow.
was (Author: dkulp):
On "issue" with this is should the default databinding be JAXB or Aegis? In
general, with CXF, we definitely prefer going the JAXB route.
It might make sense to parameterize the service configurations and databinding
stuff somehow.
> Port Jsr181HandlerMapping from Xfire
> ------------------------------------
>
> Key: CXF-1355
> URL: https://issues.apache.org/jira/browse/CXF-1355
> Project: CXF
> Issue Type: New Feature
> Components: Integration
> Environment: Spring 1.x, 2.x
> Reporter: Jara Cesnek
> Attachments: Jsr181HandlerMapping.java
>
>
> In Xfire was support for automatic scans for @WebService annotated beans in
> Spring servlet context and publish them as endpoints.
> In CXF this feature is missing.
> In attachment I provide my own implementation same functionality on CXF.
> (Spring code is fine, about CXF code I am not sure, but anyway this works)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
