I was getting java.beans.IntrospectionException. I ended up patching the code in the intake service to handle this correctly.
I think that it was inside XmlField or Field that if mapToProperty != null AND mapToProperty.length() != 0, then it would set the mapToProperty attribute. Because of this the call to Field.getMapToProperty always returned the name of the field. In the Field constructor, the code tries to map the setter and setter methods if mapToObject has a valid value. It doe not even check the value of mapToProperty. I patched this as well. -----Original Message----- From: Bill [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 11:30 AM To: Turbine Users List Subject: RE: Question about intake We are using 2.1 with some patches and in-house updates, none of which seem likely to have changed this functionality. However, I am not entirely sure how much Intake has changed in 2.2 so I cant say that this works in that version. This is a url from the archives where someone else made the same suggestion: http://www.mail-archive.com/[email protected]/msg09717.htm l Maybe you'll find something in that thread that will be of use. I missed the beginning of this thread so i dont know what you are trying to do. I'll go look thru the archives and see if something in your previous posts triggers any ideas. Could you post the error you are getting with the mapToProperty=""? On Thu, 2002-12-12 at 21:56, Quinton McCombs wrote: > Are you using the coupled version of Intake in T2.2? > > -----Original Message----- > From: Bill [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 12, 2002 8:41 AM > To: Turbine Users List > Subject: RE: Question about intake > > > I have groups that are mapped to objects, in the group definition I > map the fields that correspond to a property to that property, fields > you do not want mapped still need the mapToProperty value set to blank. > > property is mapped: <field name="Description" key="DescriptionKey" > type="String" mapToProperty="description"> </field> > > property is unmapped: <field name="Description" key="DescriptionKey" > type="String" mapToProperty=""> </field> > > On Thu, 2002-12-12 at 19:31, Quinton McCombs wrote: > > How? By default when you map the group to an object, all fields > > defined are mapped to properties. You can change the property that > > each field gets mapped to by using the mapToProperty="xxxx" attrbiute. > > > I tried mapToProperty="" but that did not work either. > > > > -----Original Message----- > > From: Bill [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, December 12, 2002 6:48 AM > > To: Turbine Users List > > Subject: Re: Question about intake > > > > > > Works for me. > > > > > > On Thu, 2002-12-12 at 17:27, Quinton McCombs wrote: > > > Is it possible to have some fields in your group mapped to a > > > property > > > and others not? I have a group that is mapped to an object. I need > > > > to have a few fields in that group that are not mapped to a > property. > > > > > Is that supported? > > > > > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
