You are right, they are not. Thanks! I did not realize the cache file was a jar.
:) Thanks for setting me straight on that one.

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Boris
> Gertsberg
> Sent: Thursday, December 28, 2000 11:21 AM
> To: Orion-Interest
> Subject: Re: Can not locate ..... when running orion under Jbuilder?
>
>
> To Russ:
> Wrappers generated by Orion are not JAXed. At least they were not JAXed in
> old verisons.
> By the way you can use JAD just in case Orion deleted those wrappers too
> fast. It is a Java decompiler written on C++, so it is very fast.
>
>
> To Darren:
> Orion compiles wrappers, jar them and put to
> $ORION_PATH/application-deployments/$your_application_name/$jar_file_name
> directory/deployment.cache
> It is a jar, don't let the name confuse you.
>
> ----- Original Message -----
> From: "Russ White" <[EMAIL PROTECTED]>
> To: "Orion-Interest" <[EMAIL PROTECTED]>
> Sent: Thursday, December 28, 2000 8:50 AM
> Subject: RE: Can not locate ..... when running orion under Jbuilder?
>
>
> > The point was that the question was specifically about the wrapper class.
> >
> > You are right about JBuilder decompiling classes when it can, but you
> forget an
> > important fact. The Orion classes are JAXed (Obfuscated) so that feature
> is
> > defeated no matter which debugger you use unless you have the source or
> JAX. :)
> >
> > By the way, NetBeans also is a very nice IDE and I use it and JBuilder
> quite a
> > lot. It is also very cool that it now includes a slick ANT module. I
> mention
> > this because it is free, and it does remote debugging pretty well. Also as
> you
> > mentioned it is very easy to set up JBuilder to run Orion in process and
> then
> > debug from there. See the how-to on orionsupport.com
> >
> > Russ
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]On Behalf Of Boris
> > > Gertsberg
> > > Sent: Wednesday, December 27, 2000 6:16 PM
> > > To: Orion-Interest
> > > Subject: Re: Can not locate ..... when running orion under Jbuilder?
> > >
> > >
> > > As I said in my email "there ALMOST no need in sources of Orion wrapper
> > > classes".
> > > It looks like JBuilder just don't have place where Orion deployed
> > > Hello_StatelessSessionBeanWrapper0.class  in it's classpath , so it asks
> for
> > > at least a source of that class.
> > > I am not an expert in JBuilder but as I heard JBuilder  is one of those
> > > Debuggers that do decompile of the classes if needed.
> > >
> > > Boris
> > >
> > > ----- Original Message -----
> > > From: "Russ White" <[EMAIL PROTECTED]>
> > > To: "Orion-Interest" <[EMAIL PROTECTED]>
> > > Sent: Wednesday, December 27, 2000 2:15 PM
> > > Subject: RE: Can not locate ..... when running orion under Jbuilder?
> > >
> > >
> > > > Boris,
> > > >
> > > > Your statement is true but irrelevant when you want to debug all of
> the
> > > classes
> > > > your application uses. This of course, would include the wrapper
> classes.
> > > :)
> > > > Sometime you want to see exactly what the wrapper is doing behind the
> > > scenes.
> > > > Usually I don't bother worrying about the wrappers and debug just the
> code
> > > I
> > > > have written, but read the original question and you will understand
> my
> > > reply a
> > > > little better. Specifically read the "Can not locate
> > > > Hello_StatelessSessionBeanWrapper0.java from project source/class
> path"
> > > part. ;)
> > > > By the way, the previous post about copying the files to a source
> > > directory
> > > > while they do exist (which is any time before compiling if finished by
> > > Orion) is
> > > > exactly right, and that is what I do when I have to. Sure would be
> nice if
> > > the
> > > > wrappers would just stick around though. :)
> > > >
> > > > Cheers,
> > > > Russ
> > > > > -----Original Message-----
> > > > > From: [EMAIL PROTECTED]
> > > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Boris
> > > > > Gertsberg
> > > > > Sent: Wednesday, December 27, 2000 12:36 PM
> > > > > To: Orion-Interest
> > > > > Subject: Re: Can not locate ..... when running orion under Jbuilder?
> > > > >
> > > > >
> > > > > Actually, there almost no need in sources of Orion wrapper classes.
> You
> > > can
> > > > > do debugging in your debugger if it supports
> > > > > JPDA (every debugger that I know of do). You can set breakpoints,
> step
> > > > > through your code in beans and  watch properties just as if it would
> be
> > > > > usual java application.
> > > > > Read Debugging how-to on orionsupport.com to set it up.
> > > > >
> > > > > Boris
> > > > >
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Russ White" <[EMAIL PROTECTED]>
> > > > > To: "Orion-Interest" <[EMAIL PROTECTED]>
> > > > > Sent: Wednesday, December 27, 2000 10:27 AM
> > > > > Subject: RE: Can not locate ..... when running orion under Jbuilder?
> > > > >
> > > > >
> > > > > > Good day to all,
> > > > > >
> > > > > > The cause of your (and my) debugging woes is that orion does make
> the
> > > > > source of
> > > > > > it's wrapper classes available to us developers. There is a split
> > > second
> > > > > while
> > > > > > orion is deploying your app that the source files exist in the
> orion
> > > root
> > > > > > directory, but the they are quickly snatched away from the prying
> eyes
> > > of
> > > > > hard
> > > > > > working developers. So in short you are seeing the message
> correctly,
> > > and
> > > > > there
> > > > > > is not a debugger in the world  (except for a few that decompile
> > > classes
> > > > > for
> > > > > > you) that can step through source that does not exist. :)what I
> > > generally
> > > > > do in
> > > > > > a case like yours is set a breakpoint directly after the call you
> are
> > > > > interested
> > > > > > in. That way you can hit F9 when you get your icky message and
> still
> > > > > monitor the
> > > > > > results of the call. Also placing a break point in the ejb class
> > > itself
> > > > > will
> > > > > > provide a way to step into the ejb.
> > > > > >
> > > > > > HTH
> > > > > >
> > > > > > Russ White
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: [EMAIL PROTECTED]
> > > > > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Darren
> > > Pamatat
> > > > > > > Sent: Wednesday, December 27, 2000 9:12 AM
> > > > > > > To: Orion-Interest
> > > > > > > Subject: Can not locate ..... when running orion under Jbuilder?
> > > > > > >
> > > > > > >
> > > > > > > I have just started working with orion, and have just
> > > > > > > sucessfully finished getting the orion primer ejb
> > > > > > > example running. All works fine.
> > > > > > >
> > > > > > > Now I'm trying to get this to run under the debugger.
> > > > > > > I have setup Jbuilder 4 projects with all the
> > > > > > > necessary orion libs as per doc on setting up JB4 with
> > > > > > > orion, and can run the orion app inside. I have even
> > > > > > > got a simple servlet working where I can step through
> > > > > > > it's code.
> > > > > > > The problem is, when I try this with the orion primer
> > > > > > > simple ejb example, I hit the servlet, and it stops on
> > > > > > > a break point. Good. Now I start stepping over, until
> > > > > > > I get to the line:
> > > > > > >
> > > > > > > answer = _hello.sayHello();
> > > > > > >
> > > > > > > I try and step into this, and the JB debugger won't
> > > > > > > let me. It states in the status bar in red:
> > > > > > > "Can not locate
> > > > > > > Hello_StatelessSessionBeanWrapper0.java from project
> > > > > > > source/class path"
> > > > > > >
> > > > > > > I'm not sure where this file is, as I searched and can
> > > > > > > not find it on my system anywhere.
> > > > > > >
> > > > > > > Is there any way to debug orion ejb components inside
> > > > > > > JB? Any ideas as what I'm doing wrong?
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Darren
> > > > > > >
> > > > > > >
> > > > > > > __________________________________________________
> > > > > > > Do You Yahoo!?
> > > > > > > Yahoo! Shopping - Thousands of Stores. Millions of Products.
> > > > > > > http://shopping.yahoo.com/
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> >
>
>
>


Reply via email to