Re: some thoughts that I wanted to post, in regards to RP, CRI, Exceptions, and a class scanner

Hi Ryan On Tue, May 24, 2011 at 6:28 AM, Ryan Zoerner wrote: > I have some thoughts that I wanted to post to the dev list. > > Here they are: > > The RP will need to choose between lifecylces, possibly just selecting which > existing cxf > resourceProvider to choose, based upon annotation. The an

Re: Custom Reuqest Param Name for Bean Request Object

Hi On Fri, May 20, 2011 at 11:23 PM, Biju Nair wrote: > Updated the JIRA with DIFF file. > > May I know whether that worked. > I have problems applying the patch, as it seems like InjectionUtils has been completely changed, I can't spot, by looking at the diff file, what the actual changes are. I

Re: Custom Reuqest Param Name for Bean Request Object

Actually, I can see you modifying the code for explicit Maps be supported as well. That is not a bad idea but I'd prefer for one issue (to do with parameter beans containing Map fileds) addressed first. Explicit Maps can be supported right now (a bit of work is needed to register ParameterHandler

Re: Jenkins build became unstable: CXF-Trunk-JDK15 #2088

I am looking at these failures. Thanks Jim On Tue, May 24, 2011 at 5:20 PM, Apache Jenkins Server wrote: > See > > >

Re: CXF And minOccurs="1" on operation parameters

The second form below will work, but you need to endorse the jaxb-api 2.2 jar to get the version of XmlElement that is allowed on the parameter. Dan On Sunday, May 22, 2011 2:20:19 AM marcin.kasin...@gmail.com wrote: > Hello. > > I searched forum, but I couldn't find anwser for my question. >

Re: problems using WSDL with web service CXF endpoint configuration

You would need to check the WSDL to see what the names of the services and ports that are defined in there. The error of: > [gsc][1/10456] javax.xml.ws.WebServiceException: > org.apache.cxf.service.factory.ServiceConstructionException: Could not > find definition for service {com.X.Y}DPAPolli

Re: some thoughts that I wanted to post, in regards to RP, CRI, Exceptions, and a class scanner

This is what I had in mind for an RP constructor: Incidentally, EJB annotations show up in the cri. under ClassResourceInfo.elementData[i].resourceClass.declaredAnnotations.table[j]. h.type.name and ClassResourceInfo.elementData[i].resourceClass.declaredAnnotations.table[j].h.memberValues.table[k]

Re: some thoughts that I wanted to post, in regards to RP, CRI, Exceptions, and a class scanner

Of course, resourceInstance should probably be resoureceProvider. Then you can just call the variable provider from methods where necessary. Ryan

Re: some thoughts that I wanted to post, in regards to RP, CRI, Exceptions, and a class scanner

Also, I suppose that you could just use AnnotationUtils on "o" in the formal params and then find out isEJB() and ejbLifecycle from that. Ryan

Re: Custom Reuqest Param Name for Bean Request Object

That was my mistake. I was using Eclipse IDE and I formatted the java file, so the whole file got messed up. I revereted the changes and made support only for bean with nested Map interface (FormParam(""),QueryParam("")..) Attaching the changed file with this mail. --

Re: Custom Reuqest Param Name for Bean Request Object

I gave the Explict Map Support, becuase CXF was supporting Explict List support. The code which i send you have only support for beans with nested Map interface. On Tue, May 24, 2011 at 8:28 PM, Biju Nair wrote: > That was my mistake. I was using Eclipse IDE and I formatted the java file, > so

Re: some thoughts that I wanted to post, in regards to RP, CRI, Exceptions, and a class scanner

and btw, I didn't intend any pun on your initials. Ryan

Re: some thoughts that I wanted to post, in regards to RP, CRI, Exceptions, and a class scanner

you will note that nabble mangled the ); in my email, which is what caused me to think of this. Ryan