[
https://issues.apache.org/jira/browse/CXF-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528224
]
willem Jiang commented on CXF-1029:
-----------------------------------
I suppose the runtime need to create a object instance from the service class,
if the service bean is not been set.
I am also trying to fix it , so we do not need to change the wiki :)
But I think it not only need to change the ServerFactoryBean code , but also
need to fix dozens of tests.
> The given example is not correct!
> ---------------------------------
>
> Key: CXF-1029
> URL: https://issues.apache.org/jira/browse/CXF-1029
> Project: CXF
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 2.0.1
> Environment: JDK6 + Eclipse 3.3
> Reporter: Hubert zhang
> Assignee: willem Jiang
> Priority: Minor
>
> Please check the web link
> :http://cwiki.apache.org/CXF20DOC/xfire-migration-guide.html
> There are some examples for how to use service factories, but in "Example
> JAXWSServiceFactory Migration" part , the given example is not correct:
> JaxWsServerFactoryBean sf = new JaxWsServerFactoryBean();
> sf.setServiceClass(MyServiceImpl.class);
> sf.setAddress("http://localhost:8080/myservice";);
> sf.create();
> It must use SEI or interface class to call setServiceClass, not the
> implementation class! Should be changed like this:
> JaxWsServerFactoryBean sf = new JaxWsServerFactoryBean();
> sf.setServiceBean(new MyServiceImpl());
> sf.setServiceClass(MyServiceInterface.class);
> sf.setAddress("http://localhost:8080/myservice";);
> sf.create();
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
