Hi,
Thanks all for the advices I got about EJB.
At the moment one colleague of mine is working on Together
and he's quite happy about it.
I feel very confortable with JBuilder yet I think that one "perfect"
tool doesn't exist at the moment but maybe in the next releases.
For example somebody asked me about little problems with JBuilder
-in very short terms I don't want to be O.T. -
So I could see some problems when creating Session beans: the XML Descriptor
generated for my Enterprise Server (Weblogic) isn't correct with JBuilder.
It omits
a few elements like the Connection pool (which in my case is
weblogic.jdbc.jts.OraclePool).
I have to generate this with another tool & do cut and paste .(Structure
Builder for example generates it
correctly). It seems to me that JBuilder Generates a valid XML file just for
InPrise Application
Server.
Another Problem I have when I generate Entity bean with the Modeler:
sometimes the file PK
is missing at the end of the generation process, or I have to do some minor
changes to the code,
inside ejbLoad & create because JBuilder doesn't instantiate the PK class at
the beginning of the
method....and it's necessary for correct process of the transaction.....
Anyway I think that with more careful reading of Borland docs these problems
could
disapper......maybe (!)
regards to all the (kind) people of this newsletter
Francesco
----- Original Message -----
From: Benjamin Kurzweil <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Cc: Benjamin Kurzweil <[EMAIL PROTECTED]>
Sent: Thursday, November 23, 2000 3:30 PM
Subject: Re: What tool do you use for design?
Hi Francesco.
I am not a missionary, neither an emplyee from Together, but take a look at
this and decide for yourself.
On page 252 and 253 in the Together 4.1 manuals (a pdf file), you see two
excellent diagrams and the following text:
How Together simplifies EJB development:
If you have developed EJBs before, then you know that the typical
development
process is something like this:
� Model EJB in some CASE tool.
� Generate source code framework with CASE tool.
� Develop the EJB code using an IDE or code editor.
� Compile the EJB classes using IDE or JDK.
� Debug any errors with some debugger.
� Write deployment descriptor in XML (typically with a text editor) that
describes serialization and other properties of the EJB in the context of an
application.
� Generate container-specific classes using tools from the application
server vendor.
� Package everything into a JAR file using JDK utility or other tool.
� Deploy the EJB to the app server using tools from the application server
vendor.
Together's approach to EJB development:
Together's EJB development features are designed to speed up the process,
get your distributed systems working sooner, and let you to focus on good
design and development.
A major benefit is that you don't have to write deployment
descriptors. Together stores bean properties right in the
model. You can put bean-specific info into a special
diagram type: the EJB assembly diagram, and at
deployment time Together packages up everything and
deploys to the server. With Together, the EJB
development process looks like this:
� Model, code, and debug your EJB with Together's
modeling and development tools. The source code
framework stays in sync with visual model at all
times.
� Run Together's EJB deployment expert.
The EJB Deployment Expert is a time saver that
automates many of the tedious post-development chores
into a simple set of steps. The expert will:
� Compile your EJB classes
� Generate container-specific classes for any
supported app server
� Generate an XML deployment descriptor and
manifest files for the selected server platform
� Package everything up into a JAR file written to
any location you specify
� Connect to the app server and deploy.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
