Hi,
Ok this is how I got it to work:
1) Open the ejbassembler and got to File --> Open
2) The first trick is to browse to your application directory (the one in
server.xml that is specified by <application name="appName"
path="C:\OrionApp" /> where appName is your application name and C:\OrionApp
is the directory is resides in (contains \META-INF\ejb.jar.xml and also
contains \orion\orion-ejb-jar.xml)
3) Highlight the aforementioned directory but dont double click on it to
open it. Click Open and a new TabbedPane will appear with the name of the
directory as its title e. g.C:\OrionApp. If its got C:\OrionApp\OrionApp as
the title then you haven't done step 2 properly.
4)If you already have beans deployed for this app, if you expand the Beans
node on the tree you get a list of deployed beans.
5) To add a new bean, go to Jar --> Add EJB
6) Choose the type of bean you want to add.
7) In Remote type the name of the Remote Interface including its package
name. eg. The Remote Interface is Address and the package is com.business
the type com.business.Address.
8) The other two fields are filled in automatically and if you used ejbmaker
to create them you shouldn't have to change them. eg Home Interface =
com.business.AddressHome; Bean implementatioan class =
com.business.AddressEJB.
9) Choose the primary key type (for entity beans). We only use long type
oid's so we type in java.lang.Long.
10) Click on OK and the new bean is added to into the tree, at the bottom of
the Beans node.
Thats it.
Let me know if that doesn't work,
Regards,
Rob Hargreaves.
-----Original Message-----
From: Jim Archer [mailto:[EMAIL PROTECTED]]
Sent: 24 August 2000 18:01
To: Orion-Interest
Cc: Robert Hargreaves
Subject: RE: 1.2 GUI tools - Do they work?
I agree that if I could get it to work it would sure not be pointless, so
that why I tried. Maybe you can help me?
If I click "add bean" I then get a dialog with three text fields in which I
am supposed to specify a bean. What should I type there? A full path to the
class file? Just the bean name? Whatever I type, it says it can't find it.
I t complaines specifficially about the actual bean. It never complains
abut the first two entries (I think they were the remote interface and home
interface, but thats off the top of my head).
I did see it automatically added EJB after the name, which for my stuff is
wrong. I changed the EJB to Bean, which is the correct name of my beans.
Could that be it?
Thanks...
Jim
--On Thursday, August 24, 2000 9:09 AM +0100 Robert Hargreaves
<[EMAIL PROTECTED]> wrote:
> I've been using the ejbassembler with 1.2 successfully since it came out
> and it works great (apart from the JTree not showing on startup). Don't
> really understand why its 'pointless', I mean what else is quicker when
> deploying CMP entity beans?
>
> Just my ten bob.
>
> Regards
>
> Rob Hargreaves
>
> -----Original Message-----
> From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED]]
> Sent: 24 August 2000 07:30
> To: Orion-Interest
> Subject: RE: 1.2 GUI tools - Do they work?
>
>
> Never used the assembler (pointless tool IMHO *g*) but the ejb maker
> works? Save only saves a skeleton. You're looking for "Create Beans At"
> then select a folder (don't open it, select it) and hit create or save
> button (can't remember)
>
> Presto!
>
> Mike
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Archer
> Sent: Thursday, August 24, 2000 3:50 PM
> To: Orion-Interest
> Subject: 1.2 GUI tools - Do they work?
>
>
> Hi All...
>
> I have just lost the battle with the GUI tools that came with Orion 1.2,
> which I realize is a beta.
>
> Are they supposed to work? I got the console to work, but I was unable to
> get the EJB Maker or the EJB Assembler to work.
>
> In the case of the EJB Maker, hitting the save button when I wanted to
> create my beans did nothing (I was able to save the skeleton). This was
> true whether I asked for 2.0 or 1.1 version beans.
>
> In the cas of the EJB Assembler, I was unable to add beans. I would try to
> add a bean and would get the dialog that asks for the name of the bean,
> but no matter what I typed it complained it could not find it. I tried
> just the bean name, a full path with drive letter, a full pate without
> the drive letter, a partial path, with the .class extensions and without.
> No luck.
>
> If they are supposed to work, I would sure appreciate some hints. If not,
> thats OK. Heck, they are beta. But at least I'll know not to bother. I
> have killed the entire evening on deployment issues (very little
> success). Time for bed.
>
> Thanks!
>
> Jim
>
>
>
>
