trying to generate schema classes...

[Thom Park <Th...@borland.com>]

Dear All,

 

I do believe I'm on a roll today - now I'm in OpenSourceHell with schema
generation...

 

When I unleash maven on my schema file I get the following stack trace:

 

    [echo] Generated schema producer classes for samba.schema

ASTIdentifier : java.lang.reflect.InvocationTargetException

java.lang.reflect.InvocationTargetException

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.

java:39)

        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces

sorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:585)

        at
org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImp

l.invoke(UberspectImpl.java:304)

        at
org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:56)

        at
org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java

:106)

<remainder of trace omitted to protect the reader's sanity>

 

The parser is blowing when it tries to process my schema file. I believe
I've set up the dependencies correctly in the project.properties file
but from the stack trace

it's unclear to me what line in my schema file is the culprit in this
failure.

 

Can anyone advise what I should be looking at in the trace to tell me
what part of the schema file is wrong please?

 

-Thom

 

Re: trying to generate schema classes...

[Emmanuel Lecharny <el...@apache.org>]

On Thu, 2005-09-29 at 15:49 -0700, Thom Park wrote:
> Dear All,
> 
>  
> 
> I do believe I’m on a roll today – now I’m in OpenSourceHell with
> schema generation…

Sorry about it...

> When I unleash maven on my schema file I get the following stack
> trace:

Is it something possible that you post as an attachment the schema you
are trying to parse?

And could you also post the specific command you type, and some
information about your environment :
 - JVM
 - system
 - Maven version
 - directory form which you are launching your command

It could help more that a stack trace, actually ;)