Aegis per-service options painful to configure
----------------------------------------------
Key: CXF-1338
URL: https://issues.apache.org/jira/browse/CXF-1338
Project: CXF
Issue Type: Bug
Components: Aegis Databinding
Affects Versions: 2.0.3
Reporter: Benson Margulies
Assignee: Dan Diephouse
I'd like to improve on the XML here. I see some possibilties. One is to
propagate properties from the server to the service factory. Currently, the
RFSB copies its properties onto the Service, where Aegis can see them. But
properties on the server (<simple:properties>) don't go. If they were copied,
the overrideTypes and friends could be there. While here, these props should
get 'aegis' in their names, no?
Anyway, Dan, if you will offer an editorial opinion, you can send it back to me
to do something about.
<simple:server id="aegis-service"
serviceClass="org.apache.cxf.javascript.fortest.AegisService"
address="http://localhost:8808/aegis";>
<simple:serviceBean>
<bean
class="org.apache.cxf.javascript.fortest.AegisServiceImpl" />
</simple:serviceBean>
<simple:dataBinding>
<bean
class="org.apache.cxf.aegis.databinding.AegisDatabinding">
</bean>
</simple:dataBinding>
<simple:serviceFactory>
<bean
class='org.apache.cxf.service.factory.ReflectionServiceFactoryBean'>
<property name="properties">
<map>
<entry key="overrideTypesList">
<list>
<value>org.apache.cxf.javascript.fortest.aegis.Mammal</value>
</list>
</entry>
</map>
</property>
</bean>
</simple:serviceFactory>
</simple:server>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
