Re: [Springframework-developer] Re: Spring IDE - Eclipse Plugin: Migration of SpringUI finished; Version 1.0.0 ready

[Torsten J. <tju...@ya...>]

Rob,

thanx for pointing to Eclipse's bugzilla entry
regarding the Xerces plugin. This entry states that
after 2004-04-02 Eclipse 3.0 SDK will ship WITHOUT the
org.apache.xerces plug-in.

Hhm, bad news for the Spring Beans UI plugin. This
results in "bring your own" DOM level 3 compliant
parser (IMHO the implementation shipped with the
current JDK 1.4.2 does not support the DOM Level 3
API).


Btw. does anyone know a DOM Level 3 comliant XML
parser with a small footprint for re-distribution with
the Spring Beans plugin?
Shipping Xerces with the plugin-in is not a good
option :-(

Cheers,
Torsten


--- Rob Moore <Rob...@pe...> wrote:
> Just to follow up, this may be related to the
> following issue:
> 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=37696
> 
> I have emf (http://eclipse.org/emf/) installed and
> it may be specifying 
> the xerces plugin. Just a hunch.
> 
> Rob
> 
> Rob Moore wrote:
> > Hi, Torsten,
> > 
> > Thanks for looking into this. I'm unable to
> determine where the 
> > XMLParserConfiguration is being set. It is not in
> the command line (as 
> > you suggested). I'm thinking that another plug-in
> may be setting it (I'm 
> > using a trial of oXygen xml editor, so perhaps
> that's the culprit.
> > 
> > Rob
> > 
> > Torsten Juergeleit wrote:
> > 
> >> Rob,
> >>
> >> in your system summary the JVM system property
> >>
>
"org.apache.xerces.xni.parser.XMLParserConfiguration"
> >> is defined. This property overrides the same
> property
> >> defined in xercesImpl.jar (META-INF/services/)
> which
> >> references the (correct) class
> >>
>
"org.apache.xerces.parsers.StandardParserConfiguration".
> >> The class referenced in your (manually set)
> system
> >> property references the class
> >>
>
"org.apache.xerces.parsers.XIncludeParserConfiguration"
> >> which is not available in Eclipse's Xerces
> >> implementation.
> >>
> >> I have successfully reproduced your error by
> adding
> >> this invalid system property to the launch
> >> configuration of an Eclipse workbench (first tab
> "(x)
> >> Arguments", input field "VM Arguments").
> >>
> >>
> >> You have to get rid of this invalid system
> property
> >> (listed in Eclipse's system summary) to run
> Spring IDE
> >> Beans UI. Maybe it's defined in your Eclipse
> shortcut
> >> on the windows desktop (as commandline parameter
> >>
>
"-Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XIncludeParserConfiguration".
> 
> >>
> >>
> >> Cheers,
> >> Torsten
> > 
> > 
> > 
> >
>
-------------------------------------------------------
> > This SF.Net email is sponsored by: IBM Linux
> Tutorials
> > Free Linux tutorial presented by Daniel Robbins,
> President and CEO of
> > GenToo technologies. Learn everything from
> fundamentals to system
> >
>
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux
> Tutorials
> Free Linux tutorial presented by Daniel Robbins,
> President and CEO of
> GenToo technologies. Learn everything from
> fundamentals to system
>
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
>
https://lists.sourceforge.net/lists/listinfo/springframework-developer



	
		
__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25¢
http://photos.yahoo.com/ph/print_splash