Hi Keith,

I played and played with Eclipse build path order etc. to see if I
could get the GWT plugin to use the JDK parser, not the one from the
J2EE app server OC4J. No Luck. Not sure what is driving this.

I looked at the source code In the dev subproject
com.google.gwt.dev.util.xml.ReflectiveParser.java
and found that it sets the feature 
http://apache.org/xml/features/nonvalidating/load-external-dtd
to false.

>From http://xerces.apache.org/xerces-j/features.html

http://apache.org/xml/features/nonvalidating/load-external-dtd
True:   Load the external DTD.
False:          Ignore the external DTD completely.
Default:        true
Note:   This feature is always on when validation is on.

Not sure what the JAXP spec says but the code here is assuming (I
think) a Apache (xerses) parser which in this case
may not be a good assumption. Perhaps the ReflectiveParser should
catch this exception explicitly
"org.xml.sax.SAXNotRecognizedException" and log it or something. Not
sure if the Oracle impl should ignore features that it doesn't
understand but we have no control over that. Anyway, hopefully this
can be fixed and until then ...

Workaround for GWT compile for OC4J
Advanced->VM arguments
-
Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl

Thanks for the pointers - gave me some motivation to dig deeper,
Eric

On Apr 8, 2:11 pm, Keith Platfoot <[email protected]> wrote:
> Hi Eric,
>
> Hm, I'm not really sure about that error.  Is it possible to use another
> parser rather than the Oracle Parser?  Also, are there DTD references in
> your module file?  The error mentions a 
> missinghttp://apache.org/xml/features/nonvalidating/load-external-dtdfeature,
> which might only be an problem if you actually have references to external
> DTD's in your XML.  Just a guess.
>
> Keith
>
>
>
>
>
> On Mon, Apr 5, 2010 at 10:22 PM, ekr <[email protected]> wrote:
> > Hi Keith,
>
> > I'm very encouraged - I was able to get my existing project updated
> > using Google -> Web Application properties and the Web Toolkit
> > properties. I'm using GWT 2.0.3 and Google Plugin for Eclipse 3.5 -
> > 1.3.2.v201003242055.  I have a manual build (Ant) working with a
> > Dynamic Web Project with a WebContent directory.
>
> > Now the GWT Compile Project recognizes the project but when I try to
> > run it I have a problem. I'm using OC4J 10.1.3.5.0 which includes the
> > Oracle Parser which doesn't like the feature. Any Ideas?
>
> > Thanks, Eric
>
> > [ERROR] Failure while parsing XML
> > org.xml.sax.SAXNotRecognizedException:
> >http://apache.org/xml/features/nonvalidating/load-external-dtd
> >        at
> > oracle.xml.jaxp.JXSAXParserFactory.setFeature(JXSAXParserFactory.java:
> > 128)
> >        at com.google.gwt.dev.util.xml.ReflectiveParser
> > $Impl.parse(ReflectiveParser.java:320)
> >        at com.google.gwt.dev.util.xml.ReflectiveParser$Impl.access
> > $100(ReflectiveParser.java:48)
> >        at
> > com.google.gwt.dev.util.xml.ReflectiveParser.parse(ReflectiveParser.java:
> > 398)
> >        at
> > com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:
> > 257)
> >        at
> > com.google.gwt.dev.cfg.ModuleDefLoader$1.load(ModuleDefLoader.java:
> > 169)
> >        at
> > com.google.gwt.dev.cfg.ModuleDefLoader.doLoadModule(ModuleDefLoader.java:
> > 283)
> >        at
>
> > com.google.gwt.dev.cfg.ModuleDefLoader.loadFromClassPath(ModuleDefLoader.ja­va:
> > 141)
> >        at com.google.gwt.dev.Compiler.run(Compiler.java:184)
> >        at com.google.gwt.dev.Compiler$1.run(Compiler.java:152)
> >        at
> > com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:
> > 87)
> >        at
>
> > com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRu­nner.java:
> > 81)
> >        at com.google.gwt.dev.Compiler.main(Compiler.java:159)
> > [ERROR] Unexpected error while processing XML
> > com.google.gwt.core.ext.UnableToCompleteException: (see previous log
> > entries)
> >        at com.google.gwt.dev.util.xml.ReflectiveParser
> > $Impl.parse(ReflectiveParser.java:351)
> >        at com.google.gwt.dev.util.xml.ReflectiveParser$Impl.access
> > $100(ReflectiveParser.java:48)
> >        at
> > com.google.gwt.dev.util.xml.ReflectiveParser.parse(ReflectiveParser.java:
> > 398)
> >        at
> > com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:
> > 257)
> >        at
> > com.google.gwt.dev.cfg.ModuleDefLoader$1.load(ModuleDefLoader.java:
> > 169)
> >        at
> > com.google.gwt.dev.cfg.ModuleDefLoader.doLoadModule(ModuleDefLoader.java:
> > 283)
> >        at
>
> > com.google.gwt.dev.cfg.ModuleDefLoader.loadFromClassPath(ModuleDefLoader.ja­va:
> > 141)
> >        at com.google.gwt.dev.Compiler.run(Compiler.java:184)
> >        at com.google.gwt.dev.Compiler$1.run(Compiler.java:152)
> >        at
> > com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:
> > 87)
> >        at
>
> > com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRu­nner.java:
> > 81)
> >        at com.google.gwt.dev.Compiler.main(Compiler.java:159)
>
> > On Mar 18, 8:33 am, Keith Platfoot <[email protected]> wrote:
> > > Hi Neciu,
>
> > > We just released the 1.3 version of the Google Plugin for Eclipse on
> > > Tuesday, which should have a Google > Web Application project property
> > page
> > > with the WAR directory field.  Are you certain your plugin version is
> > 1.3?
>
> > > Keith
>
> > > On Mon, Mar 15, 2010 at 3:41 PM, Neciu <[email protected]> wrote:
> > > > Hi Keith,
>
> > > > can you tell how to configure Eclipse + Google Plugin for Eclipse (the
> > > > newest version), so I can debug my GWT project with DB connections?
> > > > Your previous solution doesn't work anymore (I can't find anythig
> > > > about WAR in "Web Application property").
>
> > > > Thanks in advance,
> > > > Neciu.
>
> > > > On 18 Lut, 17:40, Keith Platfoot <[email protected]> wrote:
> > > > > Hi Chris,
>
> > > > > Thanks for posting this.  It's a good explanation of how to get WTP
> > and
> > > > GPE
> > > > > 1.2 working together, which is not a trivial task.  However, in the
> > next
> > > > > release of the plugin we're planning on making this integration a
> > whole
> > > > lot
> > > > > easier<
> > > >http://groups.google.com/group/google-web-toolkit/msg/8ff67143cce64e1..
> > .>
> > > > > .
>
> > > > > With GPE 1.3, you'll be able to adapt an existing Dynamic Web Project
> > as
> > > > a
> > > > > GWT project and debug using hosted/dev mode quite easily.  Here's a
> > sneak
> > > > > preview of how this will work in GPE 1.3:
>
> > > > > 1. In your project's Properties dialog, select Google > Web Toolkit
> > and
> > > > > check the box: *Use Google Web Toolkit*.
>
> > > > > 2. Switch to the Web Application property page and change *WAR source
> > > > > directory* to "WebContent" and uncheck the box: *Also use this
> > directory
> > > > as
> > > > > the output WAR directory.*
> > > > > *
> > > > > *
> > > > > 3. Start your project's server (be it GlassFish, Tomcat, etc.) using
> > your
> > > > > configured WTP server adapter.
>
> > > > > 4. Create a new Web Application launch configuration.  On the Server
> > tab,
> > > > > uncheck: *Run built-in server* (since we want to use WTP's server
> > > > adapter)
> > > > > and on the GWT tab, change the -startupUrl argument to point to your
> > > > server
> > > > > (e.g.http://localhost:8080/WebApp)
>
> > > > > 5. Run/Debug your new launch configuration.  The first time you do
> > this,
> > > > > you'll have to select the location of the WAR directory WTP is
> > publishing
> > > > to
> > > > > (this is configurable, but I think by default it is
>
> > <workspace>/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/­­<project>).
>
> > > > > 6. Presto!  GWT hosted/dev mode is now running in your own server,
> > and
> > > > you
> > > > > can debug either server-side or client-side code, and get automatic
> > > > redeploy
> > > > > of modified class files or static resources thanks to WTP's
> > auto-publish
> > > > > mechanism.
>
> > > > > We're going to be uploading a preview built of GPE 1.3 later this
> > month
> > > > so
> > > > > you can try it out for yourself and let us know what you think, ahead
> > of
> > > > the
> > > > > official release.  Stay tuned!
>
> > > > > Keith
>
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "Google Web Toolkit" group.
> > > > To post to this group, send email to
> > [email protected].
> > > > To unsubscribe from this group, send email to
> > > > [email protected]<google-web-toolkit%2bunsubs­[email protected]>
> > <google-web-toolkit%2bunsubs­[email protected]>
> > > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/google-web-toolkit?hl=en.-Hide quoted
> > text -
>
> > > - Show quoted text -
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google Web Toolkit" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected]<google-web-toolkit%2bunsubs­[email protected]>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/google-web-toolkit?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Google Web Toolkit" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group 
> athttp://groups.google.com/group/google-web-toolkit?hl=en.- Hide quoted text -
>
> - Show quoted text -

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to