On Thu, May 29, 2008 at 9:23 PM, David Jencks <[EMAIL PROTECTED]> wrote: > I wonder if having xbean add an editor if there is nothing there for a class > already would work.
Possibly. But will xbean then keep on working? Also there's a question of timing. What code gets called first etc.. I'm not sure what does xbean need the property editor manager for.. it seems to register the editors in it's own data structures as well.. Milos > > thanks > david jencks > > On May 29, 2008, at 12:06 PM, Milos Kleint wrote: > >> Well, the PropertyEditors class in xbean sets every imaginable property >> editor >> to java.beans.PropertyEditorManager.registerEditor() >> overriding and IDE's own editors. That means property customizers >> disappear etc, some places in the IDE don't cope with that.. >> I've seen a report where the GridBagLayout property setting WeightX >> turns java code to question marks instead of correct number settings, >> making the class uncompilable. >> >> as a hotfix, I've commented out every reference to >> PropertyEditorManager in the PropertyEditors class and used that. >> Seems to have no influence on the maven build or project loading. and >> fixes the issue. >> >> >> Milos >> >> >> http://svn.apache.org/repos/asf/geronimo/xbean/trunk/xbean-reflect/src/main/java/org/apache/xbean/propertyeditor/PropertyEditors.java >> >> On Thu, May 29, 2008 at 7:03 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote: >>> >>> Milos, >>> >>> Additionally, it is impossible for us to know unless there is some >>> representative test that is run on our side. I've had XBR in there for >>> over >>> a month now. Anything with system properties, threads, and now property >>> editors have to have some representation in the tests. If you create >>> something that represents the problem I'll fix it by the end of next >>> week. >>> >>> On 29-May-08, at 5:47 AM, Milos Kleint wrote: >>> >>>> Hey.. >>>> >>>> I've upgraded the netbeans users to latest 2.1-SNAPSHOT of maven >>>> embedder. I've done so to get the fix for issue with bad metaversion >>>> (RELEASE/LATEST) resolving.. However I've ended up with another severe >>>> problem. xbean seems to register it's own property editors into >>>> PropertyEditorManager on startup, wreaking havoc in the IDE. >>>> >>>> http://www.netbeans.org/issues/show_bug.cgi?id=135868 (50 duplicate >>>> reports since 2 days) >>>> or >>>> http://www.netbeans.org/issues/show_bug.cgi?id=136067 >>>> >>>> and there's probably more. >>>> >>>> is there a way to make xbean stop doing it? will I in turn end up with >>>> broken maven/plexus? >>>> >>>> Thanks for any pointers. >>>> >>>> Milos >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>> >>> Thanks, >>> >>> Jason >>> >>> ---------------------------------------------------------- >>> Jason van Zyl >>> Founder, Apache Maven >>> jason at sonatype dot com >>> ---------------------------------------------------------- >>> >>> A man enjoys his work when he understands the whole and when he >>> is responsible for the quality of the whole >>> >>> -- Christopher Alexander, A Pattern Language >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
