Shawn,
that indicates that you're missing the Saxon stuff on your classpath.
You need the glue code XMLBeans supplies (xbean_xpath.jar) along
with saxon9.jar and saxon9-dom.jar.
Also, to clarify, it would seem that this is not a build problem,
this is a runtime problem. So it is your runtime classpath that is
at issue.
- Wing Yew

-----Original Message-----
From: Shawn Bernard [mailto:[email protected]] 
Sent: Friday, January 02, 2009 2:10 PM
To: Shawn Bernard
Cc: [email protected]
Subject: Re: " FAILED on declare namespace" error

Oops, forgot the error:

java.lang.RuntimeException:  Trying XBeans path engine... Trying
XQRL... Trying delegated path engine... FAILED on declare namespace
om='http://schema.mydomain.com/'; $this/om:table-co...@table-
name='Address']
      [java]     at
org.apache.xmlbeans.impl.store.Path.getCompiledPath(Path.java:173)
      [java]     at
org.apache.xmlbeans.impl.store.Path.getCompiledPath(Path.java:130)
      [java]     at
org.apache.xmlbeans.impl.store.Cursor._selectPath(Cursor.java:902)
      [java]     at
org.apache.xmlbeans.impl.store.Cursor.selectPath(Cursor.java:2634)
      [java]     at
org
.apache
.xmlbeans.impl.values.XmlObjectBase.selectPath(XmlObjectBase.java:462)
      ...

Thanks again,

-S

On Jan 2, 2009, at 2:08 PM, Shawn Bernard wrote:

> I'm using xmlbeans along with saxon9 on a project that is currently
> using ant, but I'm switching to maven2.  Everything works fine in
> the ant build, but for some reason, I'm getting the following error
> when trying to build with maven2.
>
> I've googled the error, and it looked at first to be a missing
> dependency, but I've tried adding a whole slew of different
> dependencies, and I'm still getting the error.
>
> Any ideas?
>
> -S


---------------------------------------------------------------------
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]

Reply via email to