Skip to main content



      Home
Home » Archived » Visual Editor (VE) » VE Exception with BasicAllocationProcesser class
VE Exception with BasicAllocationProcesser class [message #75803] Tue, 28 December 2004 16:48 Go to next message
Eclipse UserFriend
I am using SDK 3.0.1, EMF 2.0.1, GEF 3.0.1 and VE 1.0.2.

Not sure what might be causing this, but while trying to open an existing
java file (originated from JBuilder - which contains jbInit for the
initalizer), I get the following Exception:

java.lang.ExceptionInInitializerError: IWAV0118E Class IWAV0189E unknown (or
one of its superclasses) is not found or has errors.
at
org.eclipse.ve.internal.java.core.BasicAllocationProcesser.i nstantiateWithSt
ring(BasicAllocationProcesser.java:203)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.basicInit ializationString
Allocation(BeanProxyAdapter.java:903)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.primInsta ntiateBeanProxy(
BeanProxyAdapter.java:879)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.instantia teBeanProxy(Bean
ProxyAdapter.java:773)
at
org.eclipse.ve.internal.java.core.CompositionProxyAdapter.in itSetting(Compos
itionProxyAdapter.java:158)
at
org.eclipse.ve.internal.java.core.CompositionProxyAdapter.in itBeanProxy(Comp
ositionProxyAdapter.java:119)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.r
un(JavaVisualEditorPart.java:1612)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

It almost looks as though BasicAllocationProcesser (is that spelled right)
is missing. Where should this be found? Do I need to included any
additional jar files in my project or elsewhere?

Any suggestions?

Eric
Re: VE Exception with BasicAllocationProcesser class [message #75820 is a reply to message #75803] Tue, 28 December 2004 18:44 Go to previous messageGo to next message
Eclipse UserFriend
Not sure if this is a separate or similar issue, but I also received this
Exception:

java.lang.NullPointerException
at
org.eclipse.ve.internal.java.codegen.java.EventInvocationHel per.isValidArgum
ents(EventInvocationHelper.java:203)
at
org.eclipse.ve.internal.java.codegen.java.EventDecoderHelper .decode(EventDec
oderHelper.java:370)
at
org.eclipse.ve.internal.java.codegen.java.AbstractEventDecod er.decode(Abstra
ctEventDecoder.java:91)
at
org.eclipse.ve.internal.java.codegen.model.CodeEventRef.deco deExpression(Cod
eEventRef.java:142)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeExpress
ion(JavaSourceTranslator.java:681)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.buildComposit
ionModel(JavaSourceTranslator.java:807)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocumen
t(JavaSourceTranslator.java:924)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(Jav
aSourceTranslator.java:657)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.r
un(JavaVisualEditorPart.java:1566)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

I have also since upgraded to the 3.1 milestone from 12/16/2004 as well but
continue to get these types of Exceptions.

Eric
Re: VE Exception with BasicAllocationProcesser class [message #75837 is a reply to message #75820] Tue, 28 December 2004 18:49 Go to previous messageGo to next message
Eclipse UserFriend
Not sure if this is were the problem is and may be a bug of some type but
tracing this some, I think it is in the isValidArguments function in
EventInvocationHelper that may have a problem...I think there may be an
incorrect if block. There is a section where it tries to do: StringBuffer
b = new StringBuffer(resolvedType.getName()) ; I think resolvedType may
not get set at this point due to the branch of the if statement being worked
on.

Can someone on the development side confirm this and/or correct it?


Eric

"Eric Bresie" <ebresie@usa.net> wrote in message
news:cqsr03$ag$1@www.eclipse.org...

> Not sure if this is a separate or similar issue, but I also received this
> Exception:
>
> java.lang.NullPointerException
> at
>
org.eclipse.ve.internal.java.codegen.java.EventInvocationHel per.isValidArgum
> ents(EventInvocationHelper.java:203)
> at
>
org.eclipse.ve.internal.java.codegen.java.EventDecoderHelper .decode(EventDec
> oderHelper.java:370)
> at
>
org.eclipse.ve.internal.java.codegen.java.AbstractEventDecod er.decode(Abstra
> ctEventDecoder.java:91)
> at
>
org.eclipse.ve.internal.java.codegen.model.CodeEventRef.deco deExpression(Cod
> eEventRef.java:142)
> at
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeExpress
> ion(JavaSourceTranslator.java:681)
> at
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.buildComposit
> ionModel(JavaSourceTranslator.java:807)
> at
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocumen
> t(JavaSourceTranslator.java:924)
> at
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(Jav
> aSourceTranslator.java:657)
> at
>
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.r
> un(JavaVisualEditorPart.java:1566)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
>
> I have also since upgraded to the 3.1 milestone from 12/16/2004 as well
but
> continue to get these types of Exceptions.
>
> Eric
>
>
Re: VE Exception with BasicAllocationProcesser class [message #75854 is a reply to message #75837] Wed, 29 December 2004 11:48 Go to previous messageGo to next message
Eclipse UserFriend
Not sure if it's related, but it may be similar to the ResolveType
referenced described here in this bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=71418

Maybe some more work on the ResolveType is need?

Eric

"Eric Bresie" <ebresie@usa.net> wrote in message
news:cqsra1$14s$1@www.eclipse.org...
> Not sure if this is were the problem is and may be a bug of some type but
> tracing this some, I think it is in the isValidArguments function in
> EventInvocationHelper that may have a problem...I think there may be an
> incorrect if block. There is a section where it tries to do:
StringBuffer
> b = new StringBuffer(resolvedType.getName()) ; I think resolvedType may
> not get set at this point due to the branch of the if statement being
worked
> on.
>
> Can someone on the development side confirm this and/or correct it?
>
>
> Eric
>
> "Eric Bresie" <ebresie@usa.net> wrote in message
> news:cqsr03$ag$1@www.eclipse.org...
>
> > Not sure if this is a separate or similar issue, but I also received
this
> > Exception:
> >
> > java.lang.NullPointerException
> > at
> >
>
org.eclipse.ve.internal.java.codegen.java.EventInvocationHel per.isValidArgum
> > ents(EventInvocationHelper.java:203)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.java.EventDecoderHelper .decode(EventDec
> > oderHelper.java:370)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.java.AbstractEventDecod er.decode(Abstra
> > ctEventDecoder.java:91)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.model.CodeEventRef.deco deExpression(Cod
> > eEventRef.java:142)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeExpress
> > ion(JavaSourceTranslator.java:681)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.buildComposit
> > ionModel(JavaSourceTranslator.java:807)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocumen
> > t(JavaSourceTranslator.java:924)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(Jav
> > aSourceTranslator.java:657)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.r
> > un(JavaVisualEditorPart.java:1566)
> > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
> >
> > I have also since upgraded to the 3.1 milestone from 12/16/2004 as well
> but
> > continue to get these types of Exceptions.
> >
> > Eric
> >
> >
>
>
Re: VE Exception with BasicAllocationProcesser class [message #76055 is a reply to message #75803] Mon, 03 January 2005 14:14 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

This message means that it could not find some class that you
referenced, or there was an initialization error in your class. This
doesn't mean that BasicAllocationProcesser is missing. It is the
BasicAllocationProcesser class that is creating the message.

There should of been another message just before this that mentions the
initialization string that is causing the error.

Eric Bresie wrote:
> I am using SDK 3.0.1, EMF 2.0.1, GEF 3.0.1 and VE 1.0.2.
>
> Not sure what might be causing this, but while trying to open an existing
> java file (originated from JBuilder - which contains jbInit for the
> initalizer), I get the following Exception:
>
> java.lang.ExceptionInInitializerError: IWAV0118E Class IWAV0189E unknown (or
> one of its superclasses) is not found or has errors.
> at
> org.eclipse.ve.internal.java.core.BasicAllocationProcesser.i nstantiateWithSt
> ring(BasicAllocationProcesser.java:203)
> at
> org.eclipse.ve.internal.java.core.BeanProxyAdapter.basicInit ializationString
> Allocation(BeanProxyAdapter.java:903)
> at
> org.eclipse.ve.internal.java.core.BeanProxyAdapter.primInsta ntiateBeanProxy(
> BeanProxyAdapter.java:879)
> at
> org.eclipse.ve.internal.java.core.BeanProxyAdapter.instantia teBeanProxy(Bean
> ProxyAdapter.java:773)
> at
> org.eclipse.ve.internal.java.core.CompositionProxyAdapter.in itSetting(Compos
> itionProxyAdapter.java:158)
> at
> org.eclipse.ve.internal.java.core.CompositionProxyAdapter.in itBeanProxy(Comp
> ositionProxyAdapter.java:119)
> at
> org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.r
> un(JavaVisualEditorPart.java:1612)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
>
> It almost looks as though BasicAllocationProcesser (is that spelled right)
> is missing. Where should this be found? Do I need to included any
> additional jar files in my project or elsewhere?
>
> Any suggestions?
>
> Eric
>
>

--
Thanks,
Rich Kulp
Re: VE Exception with BasicAllocationProcesser class [message #76071 is a reply to message #75854] Mon, 03 January 2005 14:23 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

All of your problems may be inter-related and due to the way JBuilder
created the code that we don't understand.

Please create a VE bug titled:

"Can't parse my JBuilder class" and attach your source to the bug so
that we can debug what is going on? Please attach the .log file too so
that we can see all of the errors.


Eric Bresie wrote:
> Not sure if it's related, but it may be similar to the ResolveType
> referenced described here in this bug:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=71418
>
> Maybe some more work on the ResolveType is need?
>
> Eric
>
> "Eric Bresie" <ebresie@usa.net> wrote in message
> news:cqsra1$14s$1@www.eclipse.org...
>
>>Not sure if this is were the problem is and may be a bug of some type but
>>tracing this some, I think it is in the isValidArguments function in
>>EventInvocationHelper that may have a problem...I think there may be an
>>incorrect if block. There is a section where it tries to do:
>
> StringBuffer
>
>>b = new StringBuffer(resolvedType.getName()) ; I think resolvedType may
>>not get set at this point due to the branch of the if statement being
>
> worked
>
>>on.
>>
>>Can someone on the development side confirm this and/or correct it?
>>
>>
>>Eric
>>
>>"Eric Bresie" <ebresie@usa.net> wrote in message
>>news:cqsr03$ag$1@www.eclipse.org...
>>
>>
>>>Not sure if this is a separate or similar issue, but I also received
>
> this
>
>>>Exception:
>>>
>>>java.lang.NullPointerException
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.java.EventInvocationHel per.isValidArgum
>
>>>ents(EventInvocationHelper.java:203)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.java.EventDecoderHelper .decode(EventDec
>
>>>oderHelper.java:370)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.java.AbstractEventDecod er.decode(Abstra
>
>>>ctEventDecoder.java:91)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.model.CodeEventRef.deco deExpression(Cod
>
>>>eEventRef.java:142)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeExpress
>
>>>ion(JavaSourceTranslator.java:681)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.buildComposit
>
>>>ionModel(JavaSourceTranslator.java:807)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocumen
>
>>>t(JavaSourceTranslator.java:924)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(Jav
>
>>>aSourceTranslator.java:657)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.r
>
>>>un(JavaVisualEditorPart.java:1566)
>>>at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
>>>
>>>I have also since upgraded to the 3.1 milestone from 12/16/2004 as well
>>
>>but
>>
>>>continue to get these types of Exceptions.
>>>
>>>Eric
>>>
>>>
>>
>>
>
>

--
Thanks,
Rich Kulp
Re: VE Exception with BasicAllocationProcesser class [message #604127 is a reply to message #75803] Tue, 28 December 2004 18:44 Go to previous message
Eclipse UserFriend
Not sure if this is a separate or similar issue, but I also received this
Exception:

java.lang.NullPointerException
at
org.eclipse.ve.internal.java.codegen.java.EventInvocationHel per.isValidArgum
ents(EventInvocationHelper.java:203)
at
org.eclipse.ve.internal.java.codegen.java.EventDecoderHelper .decode(EventDec
oderHelper.java:370)
at
org.eclipse.ve.internal.java.codegen.java.AbstractEventDecod er.decode(Abstra
ctEventDecoder.java:91)
at
org.eclipse.ve.internal.java.codegen.model.CodeEventRef.deco deExpression(Cod
eEventRef.java:142)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeExpress
ion(JavaSourceTranslator.java:681)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.buildComposit
ionModel(JavaSourceTranslator.java:807)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocumen
t(JavaSourceTranslator.java:924)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(Jav
aSourceTranslator.java:657)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.r
un(JavaVisualEditorPart.java:1566)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

I have also since upgraded to the 3.1 milestone from 12/16/2004 as well but
continue to get these types of Exceptions.

Eric
Re: VE Exception with BasicAllocationProcesser class [message #604131 is a reply to message #75820] Tue, 28 December 2004 18:49 Go to previous message
Eclipse UserFriend
Not sure if this is were the problem is and may be a bug of some type but
tracing this some, I think it is in the isValidArguments function in
EventInvocationHelper that may have a problem...I think there may be an
incorrect if block. There is a section where it tries to do: StringBuffer
b = new StringBuffer(resolvedType.getName()) ; I think resolvedType may
not get set at this point due to the branch of the if statement being worked
on.

Can someone on the development side confirm this and/or correct it?


Eric

"Eric Bresie" <ebresie@usa.net> wrote in message
news:cqsr03$ag$1@www.eclipse.org...

> Not sure if this is a separate or similar issue, but I also received this
> Exception:
>
> java.lang.NullPointerException
> at
>
org.eclipse.ve.internal.java.codegen.java.EventInvocationHel per.isValidArgum
> ents(EventInvocationHelper.java:203)
> at
>
org.eclipse.ve.internal.java.codegen.java.EventDecoderHelper .decode(EventDec
> oderHelper.java:370)
> at
>
org.eclipse.ve.internal.java.codegen.java.AbstractEventDecod er.decode(Abstra
> ctEventDecoder.java:91)
> at
>
org.eclipse.ve.internal.java.codegen.model.CodeEventRef.deco deExpression(Cod
> eEventRef.java:142)
> at
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeExpress
> ion(JavaSourceTranslator.java:681)
> at
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.buildComposit
> ionModel(JavaSourceTranslator.java:807)
> at
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocumen
> t(JavaSourceTranslator.java:924)
> at
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(Jav
> aSourceTranslator.java:657)
> at
>
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.r
> un(JavaVisualEditorPart.java:1566)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
>
> I have also since upgraded to the 3.1 milestone from 12/16/2004 as well
but
> continue to get these types of Exceptions.
>
> Eric
>
>
Re: VE Exception with BasicAllocationProcesser class [message #604136 is a reply to message #75837] Wed, 29 December 2004 11:48 Go to previous message
Eclipse UserFriend
Not sure if it's related, but it may be similar to the ResolveType
referenced described here in this bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=71418

Maybe some more work on the ResolveType is need?

Eric

"Eric Bresie" <ebresie@usa.net> wrote in message
news:cqsra1$14s$1@www.eclipse.org...
> Not sure if this is were the problem is and may be a bug of some type but
> tracing this some, I think it is in the isValidArguments function in
> EventInvocationHelper that may have a problem...I think there may be an
> incorrect if block. There is a section where it tries to do:
StringBuffer
> b = new StringBuffer(resolvedType.getName()) ; I think resolvedType may
> not get set at this point due to the branch of the if statement being
worked
> on.
>
> Can someone on the development side confirm this and/or correct it?
>
>
> Eric
>
> "Eric Bresie" <ebresie@usa.net> wrote in message
> news:cqsr03$ag$1@www.eclipse.org...
>
> > Not sure if this is a separate or similar issue, but I also received
this
> > Exception:
> >
> > java.lang.NullPointerException
> > at
> >
>
org.eclipse.ve.internal.java.codegen.java.EventInvocationHel per.isValidArgum
> > ents(EventInvocationHelper.java:203)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.java.EventDecoderHelper .decode(EventDec
> > oderHelper.java:370)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.java.AbstractEventDecod er.decode(Abstra
> > ctEventDecoder.java:91)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.model.CodeEventRef.deco deExpression(Cod
> > eEventRef.java:142)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeExpress
> > ion(JavaSourceTranslator.java:681)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.buildComposit
> > ionModel(JavaSourceTranslator.java:807)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocumen
> > t(JavaSourceTranslator.java:924)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(Jav
> > aSourceTranslator.java:657)
> > at
> >
>
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.r
> > un(JavaVisualEditorPart.java:1566)
> > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
> >
> > I have also since upgraded to the 3.1 milestone from 12/16/2004 as well
> but
> > continue to get these types of Exceptions.
> >
> > Eric
> >
> >
>
>
Re: VE Exception with BasicAllocationProcesser class [message #604218 is a reply to message #75803] Mon, 03 January 2005 14:14 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

This message means that it could not find some class that you
referenced, or there was an initialization error in your class. This
doesn't mean that BasicAllocationProcesser is missing. It is the
BasicAllocationProcesser class that is creating the message.

There should of been another message just before this that mentions the
initialization string that is causing the error.

Eric Bresie wrote:
> I am using SDK 3.0.1, EMF 2.0.1, GEF 3.0.1 and VE 1.0.2.
>
> Not sure what might be causing this, but while trying to open an existing
> java file (originated from JBuilder - which contains jbInit for the
> initalizer), I get the following Exception:
>
> java.lang.ExceptionInInitializerError: IWAV0118E Class IWAV0189E unknown (or
> one of its superclasses) is not found or has errors.
> at
> org.eclipse.ve.internal.java.core.BasicAllocationProcesser.i nstantiateWithSt
> ring(BasicAllocationProcesser.java:203)
> at
> org.eclipse.ve.internal.java.core.BeanProxyAdapter.basicInit ializationString
> Allocation(BeanProxyAdapter.java:903)
> at
> org.eclipse.ve.internal.java.core.BeanProxyAdapter.primInsta ntiateBeanProxy(
> BeanProxyAdapter.java:879)
> at
> org.eclipse.ve.internal.java.core.BeanProxyAdapter.instantia teBeanProxy(Bean
> ProxyAdapter.java:773)
> at
> org.eclipse.ve.internal.java.core.CompositionProxyAdapter.in itSetting(Compos
> itionProxyAdapter.java:158)
> at
> org.eclipse.ve.internal.java.core.CompositionProxyAdapter.in itBeanProxy(Comp
> ositionProxyAdapter.java:119)
> at
> org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.r
> un(JavaVisualEditorPart.java:1612)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
>
> It almost looks as though BasicAllocationProcesser (is that spelled right)
> is missing. Where should this be found? Do I need to included any
> additional jar files in my project or elsewhere?
>
> Any suggestions?
>
> Eric
>
>

--
Thanks,
Rich Kulp
Re: VE Exception with BasicAllocationProcesser class [message #604221 is a reply to message #75854] Mon, 03 January 2005 14:23 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

All of your problems may be inter-related and due to the way JBuilder
created the code that we don't understand.

Please create a VE bug titled:

"Can't parse my JBuilder class" and attach your source to the bug so
that we can debug what is going on? Please attach the .log file too so
that we can see all of the errors.


Eric Bresie wrote:
> Not sure if it's related, but it may be similar to the ResolveType
> referenced described here in this bug:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=71418
>
> Maybe some more work on the ResolveType is need?
>
> Eric
>
> "Eric Bresie" <ebresie@usa.net> wrote in message
> news:cqsra1$14s$1@www.eclipse.org...
>
>>Not sure if this is were the problem is and may be a bug of some type but
>>tracing this some, I think it is in the isValidArguments function in
>>EventInvocationHelper that may have a problem...I think there may be an
>>incorrect if block. There is a section where it tries to do:
>
> StringBuffer
>
>>b = new StringBuffer(resolvedType.getName()) ; I think resolvedType may
>>not get set at this point due to the branch of the if statement being
>
> worked
>
>>on.
>>
>>Can someone on the development side confirm this and/or correct it?
>>
>>
>>Eric
>>
>>"Eric Bresie" <ebresie@usa.net> wrote in message
>>news:cqsr03$ag$1@www.eclipse.org...
>>
>>
>>>Not sure if this is a separate or similar issue, but I also received
>
> this
>
>>>Exception:
>>>
>>>java.lang.NullPointerException
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.java.EventInvocationHel per.isValidArgum
>
>>>ents(EventInvocationHelper.java:203)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.java.EventDecoderHelper .decode(EventDec
>
>>>oderHelper.java:370)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.java.AbstractEventDecod er.decode(Abstra
>
>>>ctEventDecoder.java:91)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.model.CodeEventRef.deco deExpression(Cod
>
>>>eEventRef.java:142)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeExpress
>
>>>ion(JavaSourceTranslator.java:681)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.buildComposit
>
>>>ionModel(JavaSourceTranslator.java:807)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocumen
>
>>>t(JavaSourceTranslator.java:924)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(Jav
>
>>>aSourceTranslator.java:657)
>>>at
>>>
>>
> org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.r
>
>>>un(JavaVisualEditorPart.java:1566)
>>>at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
>>>
>>>I have also since upgraded to the 3.1 milestone from 12/16/2004 as well
>>
>>but
>>
>>>continue to get these types of Exceptions.
>>>
>>>Eric
>>>
>>>
>>
>>
>
>

--
Thanks,
Rich Kulp
Previous Topic:VE doesn't work
Next Topic:SWT GridLayout bug ?
Goto Forum:
  


Current Time: Tue Jul 22 07:42:55 EDT 2025

Powered by FUDForum. Page generated in 0.05683 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top