[news.eclipse.tools] Re: Wow - big progress

["Patrick Mueller" <patrick_mueller@xxxxxxx>]

hmmm ... this may be related to the fact that Personal Configuration ALSO
ships SWT, and probably a slightly different version; the one with Personal
Config may be newer.  The two versions of SWT are most likely compatible,
however if they ARE different, they will be using different .dlls, which may
also be confusing something.  Also, if you've got personal config on your
boot, something may be getting confused because it's managing to load SWT
out of the boot now, instead out of the plugin class loader.

--
----------------------------------------------------
Patrick_Mueller@xxxxxxx
----------------------------------------------------


"Marcelo Paternostro" <marcelop@xxxxxxxxxx> wrote in message
news:9ldsqs$fd7$1@xxxxxxxxxxxxxxxx
> Hi,
>
> Thx for the offer :)
>
> I downloaded and installed the VAME1.4.  After Bruno's tip I also
downloaded
> and installed the Personal Configuration which add some directories and
> files to the previous installation.  Then I set this VM as the default one
> for Eclipse -setting its type to J9.
>
> After run my code - I am using Eclipse to develop plugins - I am not able
to
> open any of my UI components (views, editors, ...).  There are tons of
> errors on the log and most of then are related to problems during the
class
> loading attempt.
>
> I'll try to manually add the jars to the classes.zip file but I really
think
> this is a little wild.  Since both Eclipse and J9 are developed by OTI and
> J9 provides a very important feature to the development environment I
think
> it should be a top priority to define an *easy* way to use this VM.  Maybe
> it should be shipped with the Eclipse - being a "checkbox setting" and not
> requiring the 2 console windows that appear when we run the app.
>
> Ok... I confess... VAJ spoiled me...
>
> Regards.
>
>
> "Patrick Mueller" <patrick_mueller@xxxxxxx> wrote in message
> news:9ldkh4$csh$1@xxxxxxxxxxxxxxxx
> > java.beans is in our "Personal Configuration" in the "Technologies"
> section
> > of the VAME download zone:
> >
> >     http://www.embedded.oti.com/download/zone.phtml
> >
> > For Marcelo, append some of your walkbacks, and I'll take a guess ...
> >
> > For everyone else, there were some pointers that our Personal
> Configuration
> > does provide AWT support, and in fact will run some amount of Swing
1.1.1
> > code.  I think the biggest caveat with this stuff is that it is AWT 1.1
> > level code, which is all VAME's Personal Configuration is aimed to
support
> > (since that's the standard for embedded platforms).  It's >very< likely,
> > that if you use Swing, or even AWT, that you are using features added in
> AWT
> > or Swing at the 1.2, 1.3 (or later) levels.  Which means your code won't
> run
> > on our Personal Configuration.  A typical example would be references to
> > Graphics2D, which is NOT in our Personal Configuration.
> >
> > Further note, Personal Configuration is shipped as
> > prsnlwin.jar/prsnlmot.jar/prsnlnto.jar for Windows/Linux-Motif/Photon
> > (photon being not interesting here).  This jar needs to be on your boot
> > class path, if you are doing anything interesting at all, as opposed to
> the
> > application class path.  ie, needs to be on j9's -bp: as opposed
to -cp:.
> I
> > have no clue how you would make this happen in Eclipse, and actually I
> > believe there is some functionality lacking in boot class path support
in
> > Eclipse for target stuff, so that may be another hurdle to jump ... it
> might
> > be easier for folks to just combine the j9 jclMax/classes.zip +
> prsnlXXX.jar
> > into a new and improved jclMax/classes.zip with your flavorite .zip tool
> ...
> >
> > --
> > ----------------------------------------------------
> > Patrick_Mueller@xxxxxxx
> > ----------------------------------------------------
> >
> >
> > "Randy Hudson" <someone@xxxxxxxxxx> wrote in message
> > news:9lch01$14i$1@xxxxxxxxxxxxxxxx
> > > I had a similar problem at one point.
> > > Besides awt and Swing, J9 does not include java.beans.*, and some of
the
> > > newer Collection stuff if I remember correctly.  Chances are that you
> are
> > > using java.beans.PropertyChangeEvent, and related classes.  These are
> > > missing from J9.
> > >
> > >
> > > "Marcelo Paternostro" <marcelop@xxxxxxxxxx> wrote in message
> > > news:9lbr0t$ptt$1@xxxxxxxxxxxxxxxx
> > > > Thx.  With your tip I was able to solve the problem.  But now I am
> > facing
> > > > another one...  Using VAME1.4 as the defualt VM my plugin doesn't
> work -
> > > it
> > > > works fine with the standard one. The log has tons of exceptions
and,
> if
> > > you
> > > > want to, I can copy it here.
> > > >
> > > > Any idea?
> > > >
> > > > "Bruno Leroux" <bleroux@xxxxxxxxxx> wrote in message
> > > > news:3B79702A.F5258DE0@xxxxxxxxxxxxx
> > > > >
> > > > >
> > > > > Marcelo Paternostro wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I just downloaded the VAME 1.4 and set it as the default VM to
> build
> > > and
> > > > > > launch Java app.  Now when I run a plugin I am developing,
> following
> > > > error
> > > > > > is thrown: "Fatal error: Unable to find and initialize required
> > class
> > > > > > java/lang/Object"
> > > > > >
> > > > > > Note: The JRE_LIB and JRE_SRC.
> > > > > >
> > > > > > What did I forget to do?
> > > > > >
> > > > > >
> > > > >
> > > > > I encountered the same problem. I solved it by updating my
JAVA_HOME
> > > > environment variable (set it to vame\ive).
> > > > > It is used in the default bootclasspath of J9 VM.
> > > > >
> > > > > Bruno
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>