RE: bean stalks

[Benson Margulies]

Willem,

Thanks, Can you tell me, in passing, why jaxws:serviceFactory is a
nested element and not (even optionally) an attribute pointing to a
top-level bean?

I've currently written the following, on the theory that my parser could
insist that a conventionally named service factory would be defined in
an included spring file, and so all I'd have to organize in Java is the
EndpointImpl corresponding to the endpoint decl. I still get this
sinking feeling that I'm capturing a lot of CXF internals into my Java
code, and I should be able to think of a way to tell my users to
interact with a simple XML file without that.

At the end of the day, I want to hand a user a webapp that they can
easily configure to specify (1) the address of the endpoint and (2) a
list of items like <x:index pathname='some real pathname'
writable='true'>
         <description>some verbose description</description>
     </x:index>

I don't want my users to have to edit into the middle of a minefield of
CXF details that, if disturbed, result in a disaster.

I've already done a spring parser for the x:index thing. I could do one
for my service implementation class in two shakes. It's the
jaxws:endpoint that has me going around in circles.

<!-- begin stuff to put in an import file -->
<bean id='aegis-service-factory'
class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean"> 
               <property name="dataBinding" ref="aegisBean"/>
                 <property name="serviceConfigurations">
                     <list>
                       <bean
class="org.apache.cxf.jaxws.support.JaxWsServiceConfiguration"/>
                       <bean
class="org.apache.cxf.aegis.databinding.AegisServiceConfiguration"/>
                       <bean
class="org.apache.cxf.service.factory.DefaultServiceConfiguration"/> 
                    </list>
                </property>
        </bean>
<bean id="aegisBean"
class="org.apache.cxf.aegis.databinding.AegisDatabinding"/>

<!-- end stuff for the import file -->

<!-- begin stuff to produce in a Parser -->

<jaxws:endpoint
          id="index_service_endpoint"
          implementor="#index_service"
          address="/NameIndex"
          > 
          <jaxws:serviceFactory> 
          <ref bean='aegis-service-factory'/>
          </jaxws:serviceFactory>
    </jaxws:endpoint>
<!-- end -->

> -----Original Message-----
> From: Willem Jiang [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 01, 2007 9:29 PM
> To: cxf-user@incubator.apache.org
> Subject: Re: bean stalks
> 
> Hi Benson,
> 
> You can find the jaxws.xsd from this url [1]
> Here is the code [2] which deals with the jaxws:endpoint parsing.
> 
>
[1]http://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/frontend/jaxws
/s
> rc/main/resources/schemas/jaxws.xsd
>
[2]http://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/frontend/jaxws
/s
> rc/main/java/org/apache/cxf/jaxws/spring/EndpointDefinitionParser.java
> 
> 
> Willem.
> 
> Benson Margulies wrote:
> > I'd like to build my own spring XML extension that wraps up the
complex
> > specification of an Aegis service endpoint.
> >
> >
> >
> > Can someone tell me what the fully expanded spring XML would be for
> > jaxws:endpoint, or should I just start reading the source?
> >
> >
> >
> >
> >