I believe I read somewhere in a FAQ or tutorial that spaces in the path
name (such as "Program Files") would break jBoss. I think it's safe to
assume that is what was wrong in your instance.
On other note, on the site it says that jBoss 2 runs in JDK1.2.2 when in
fact the AutoLoader uses java.lang.reflect.InvocationHandler which
was only introduced in JDK1.3.
-ryan
On Mon, Jul 31, 2000 at 10:08:59AM -0500, David Solum wrote:
> Ken,
>
> As an FYI, I was having all sorts of trouble with the Chapter 4 examples
> until I finally saw this in another message and it looked familiar:
>
> > > >java.net.MalformedURLExcption: no
> protocol:Files/jboss2/lib/ext/jboss.jar]
> > >
> > > That means you've installed jBoss in C:\Program Files\jboss2 (the
> default
> > > location) and the space in the URL is throwing off the whole URL. Try
> > > installing in a different directory (like C:\jboss2\) or using
> "progra~1"
> > > instead of "Program Files".
>
> My Chapter 4 stateless session bean was failing to lookup the Cabin entity
> bean successfully, until I uninstalled and reinstalled jBoss in C:\jboss2
> rather that the default C:\Program Files\jboss2. Then I finally got it to
> work, after wasting lots of time. I do wonder at this point if jBoss is
> actually broken when installed in C:\Program Files\jboss2. Does anyone
> know?
>
> If this causes serious problems, I suggest to the powers that be at least
> changing the installer's default directory, if not actually refusing to
> install in a directory with spaces in the path (at least one Java IDE
> I've used does this).
>
> David
>
>
> > At 08:21 PM 07/24/2000 -0500, Ken Jenks wrote:
> > >Anyone in need of help with the examples from this book, I'll have a
> > >tutorial ready this coming weekend (for both Linux and Windows) showing
> > >how to build and run the examples from chapter 4. You might hold off on
> > >fiddling with these examples until then -- or you might keep fiddling,
> > >then compare your solution to mine.
> >
> > As promised, here's my first solution. It includes Windows batch
> > files and
> > Linux shell scripts for compiling, deploying and running on the latest
> > jBoss binary. (Warning: will not work on last week's version of
> > jBoss 2.0.)
> >
> > This is NOT the optimum jBoss solution. I revised the client code
> > and even
> > the TravelAgentBean to use jBoss' local JNDI names. What I should
> > have done
> > -- and what I'll do next week -- is to use jboss.xml to re-map the JNDI
> > names used in the examples to jBoss' local JNDI names without
> > revising the
> > client code. (That's how jBoss is supposed to work. I think.)
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-- Benjamin Franklin
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
