The attachments were there, but I'm not in a position to examine them this instant.
There are JAX-WS constraints on parameter bindings. I may need to defer to Dan. On Tue, Jul 1, 2008 at 2:09 PM, Stopp, Bryan <[EMAIL PROTECTED]> wrote: > It's used as a parameter of the service. No offense meant, but did the > attachments come through with the original message? This is the first > time I've ever used a mailing list, so I don't know if the xml files > were sent with my original email. > > If not, here's the XML for my Aegis binding: > > <?xml version="1.0"?> > <mappings> > <mapping> > <method name="sayHello"> > <parameter index="0" mappedName="user" nillable="false" > minOccurs='1' maxOccurs='1'/> > </method> > </mapping> > </mappings> > > > And Here's my spring file: > > <?xml version="1.0" encoding="UTF-8"?> > <beans xmlns="http://www.springframework.org/schema/beans"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:p="http://www.springframework.org/schema/p"; > xmlns:simple="http://cxf.apache.org/simple"; > xmlns:jaxws="http://cxf.apache.org/jaxws"; > xsi:schemaLocation="http://www.springframework.org/schema/beans > > http://www.springframework.org/schema/beans/spring-beans-2.5.xsd > http://cxf.apache.org/jaxws > http://cxf.apache.org/schemas/jaxws.xsd > http://cxf.apache.org/simple > http://cxf.apache.org/schemas/simple.xsd";> > > <import resource="classpath:META-INF/cxf/cxf.xml" /> > <import resource="classpath:META-INF/cxf/cxf-extension-soap.xml" /> > <import resource="classpath:META-INF/cxf/cxf-servlet.xml" /> > > <bean id="sayHelloBean" class="com.mycompany.test.impl.SayHelloImpl" > /> > <simple:server id="sayHelloService" > serviceClass="com.mycompany.test.SayHello" > address="/sayHello" > > <simple:serviceBean > > <ref bean="sayHelloBean" /> > </simple:serviceBean> > <simple:dataBinding> > <bean > class="org.apache.cxf.aegis.databinding.AegisDatabinding" /> > </simple:dataBinding> > </simple:server> > </beans> > > > I have a valid Web.xml as the WSDL shows up, but as I said, it's not > honoring my specs. > > I'm still trying to figure out why this isn't working correctly. I also > created the same project and used the example from the CXF website on > how to a configure JAS-WS endpoint with spring. It is even worse than > the simple:server configuration. > > -Bryan Stopp > > -----Original Message----- > From: Benson Margulies [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 01, 2008 1:00 PM > To: [email protected] > Subject: Re: Aegis Bindings > > So much for the easy answer. Is this type used as a parameter of a > service, > or is it 'down' a level? > > On Tue, Jul 1, 2008 at 4:16 AM, Stopp, Bryan > <[EMAIL PROTECTED]> > wrote: > > > > > Yes, it is. I turned on debug for the "org.apache.cxf" package tree, > and > > I always see "found file: /com/mycompany/test/SayHello.aegis.xml" > > > > -Bryan Stopp > > > > -----Original Message----- > > From: Benson Margulies [mailto:[EMAIL PROTECTED] > > Sent: Monday, June 30, 2008 5:32 PM > > To: [email protected] > > Subject: Re: Aegis Bindings > > > > Is the .aegis.xml file sitting on the classpath next to the .class > that > > it > > modifies? > > > > On Mon, Jun 30, 2008 at 3:29 PM, Stopp, Bryan > > <[EMAIL PROTECTED]> > > wrote: > > > > > Hello! > > > > > > I'm sure this is going to be a fault on my part. But I can't seem > to > > get > > > Aegis bindings to work with the "simple:server" binding definitions. > > > > > > I have attached an example aegis.xml, web.xml, spring.xml and source > > code. > > > The minOccurs specification on the aegis mapping is not being > honored > > when > > > the WSDL gets generated. I really get the impression I'm missing > some > > > configuration on my "simple:server" binding definition, but I don't > > know > > > what.** > > > > > > It *does* honor the name of the parameter, just not any other > > attributes > > > in the bindings. > > > > > > Can anyone identify what I'm doing wrong, or if I've forgotten > > something? > > > Assistance is needed, and thank you all for it! > > > > > > -Bryan Stopp > > > > > > > PRIVILEGED AND CONFIDENTIAL > > This email transmission contains privileged and confidential > information > > intended only for the use of the individual or entity named above. If > the > > reader of the email is not the intended recipient or the employee or > agent > > responsible for delivering it to the intended recipient, you are > hereby > > notified that any use, dissemination or copying of this email > transmission > > is strictly prohibited by the sender. If you have received this > > transmission in error, please delete the email and immediately notify > the > > sender via the email return address or > mailto:[EMAIL PROTECTED] > > Thank you. > > > > > > > > > > > > PRIVILEGED AND CONFIDENTIAL > This email transmission contains privileged and confidential information > intended only for the use of the individual or entity named above. If the > reader of the email is not the intended recipient or the employee or agent > responsible for delivering it to the intended recipient, you are hereby > notified that any use, dissemination or copying of this email transmission > is strictly prohibited by the sender. If you have received this > transmission in error, please delete the email and immediately notify the > sender via the email return address or mailto:[EMAIL PROTECTED] > Thank you. > > > > >
