Re[2]: What documentation?
Hello Danut. Monday, February 26, 2001, 8:14:16 PM, you wrote: NN> At 05:37 PM 2/26/01 -0600, you wrote: >>A few weeks ago after I asked some questions and posted some opinion I was >>sent by some guys to RFM. Very inpolite >>Well, I still have the same problems and I am asking the same question: >>why is not possible to use a GUI tool to specify all I want for deploying >>my application? You need to code it yourself, because there are lot of orion-specific things, and they haven't code a good deployment tool for that. >>Speaking about documentation and RFM please go into >>"The deployment info for a J2EE-application. Manually created or >>automatically produced when auto-deploying a J2EE-application (.ear). It >>extends and substitutes the assembly info found in the " application.xml file If you want that orion uses your own orion-application.xml (and fill the blanks you left) put it under $(APP-HOME)/orion directory. You can do that for the orion-ejb-jar.xml ( $(APP-HOME)/$(EJB-MODULE)/orion ), and I think you can do it for orion-web.xml but I'm not sure where it goes. At some place in the archives of this list is a message with the whole dir structure. -- Best regards, Rafaelmailto:[EMAIL PROTECTED]
RE: What documentation?
I'm not a complete app-server 'Ludite' (sp?) but I do find it quite informative putting together applications by hand and I believe that you can obtain valuable experience in not only J2ee but the appserver as well. I've pressed gui buttons on the RI, EA Server, and WebLogic - and yes it is easy but not very informative as to the underlying structure. For me, anyway, to get the most out of Orion, I've had to do things like, oh, read the various specs, etc. Very valuable. Even more so if you NEED to read them! Anyway - I am sure that the Orion GUI tools will be much more mature as time passes and we can all happily press buttons... Cheers --- Kemp Randy-W18971 <[EMAIL PROTECTED]> wrote: > GUI tools? Give the guys at Orion some time, and I am sure they will > develop some, or perfect the existing ones. Same goes with the open source > projects. They just need some time to mature. > > -Original Message- > From: Gary Shea [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 26, 2001 7:41 PM > To: Orion-Interest > Subject: Re: What documentation? > > > Today, Danut Prisacaru ([EMAIL PROTECTED]) wrote: > > Well, I still have the same problems and I am asking the same question: > why > > is not possible to use a GUI tool to specify all I want for deploying my > > application? Why do I need to go into the application-deployments folder > > and modify what Orion has alredy deployed. If you are stuck and still do > > not get go and play with Sun's RI or WebLogic and ypu will udnerstand what > > I mean. > > The same thing was bothering me, because having to modify orion's > deployment descriptors was getting old. > It turns out that you can make the orion web, ejb, and application > deployment documents be part of your distribution. > I create simplified versions that have just the stuff I care about > in them, for instance: > > autocreate-tables="false" > treat-zero-as-null="false" > > > > > By putting these into the appropriate places in your .ear or > directory heirarchy, orion will find them and incorporate the > information you specify in them into the final deployment > descriptor that lives in the application-deployment directory. > It's pretty slick. > > Hope that's useful. > > Gary > > > > > Speaking about documentation and RFM please go into > > "orion-application.xml.html" and read this: > > > > "The deployment info for a J2EE-application. Manually created or > > automatically produced when auto-deploying a J2EE-application (.ear). It > > extends and substitutes the assembly info found in the " > > > > Where is the rest of the sentence? > > > > Sayonara! > > Danut > > __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
Re: What documentation?
Thanks Gary! It does help. Danut At 06:41 PM 2/26/2001 -0700, Gary Shea wrote: >The same thing was bothering me, because having to modify orion's >deployment descriptors was getting old. >It turns out that you can make the orion web, ejb, and application >deployment documents be part of your distribution. >I create simplified versions that have just the stuff I care about >in them, for instance: > > autocreate-tables="false" > treat-zero-as-null="false" > > > > >By putting these into the appropriate places in your .ear or >directory heirarchy, orion will find them and incorporate the >information you specify in them into the final deployment >descriptor that lives in the application-deployment directory. >It's pretty slick. > >Hope that's useful. > > Gary _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
RE: What documentation?
GUI tools? Give the guys at Orion some time, and I am sure they will develop some, or perfect the existing ones. Same goes with the open source projects. They just need some time to mature. -Original Message- From: Gary Shea [mailto:[EMAIL PROTECTED]] Sent: Monday, February 26, 2001 7:41 PM To: Orion-Interest Subject: Re: What documentation? Today, Danut Prisacaru ([EMAIL PROTECTED]) wrote: > Well, I still have the same problems and I am asking the same question: why > is not possible to use a GUI tool to specify all I want for deploying my > application? Why do I need to go into the application-deployments folder > and modify what Orion has alredy deployed. If you are stuck and still do > not get go and play with Sun's RI or WebLogic and ypu will udnerstand what > I mean. The same thing was bothering me, because having to modify orion's deployment descriptors was getting old. It turns out that you can make the orion web, ejb, and application deployment documents be part of your distribution. I create simplified versions that have just the stuff I care about in them, for instance: By putting these into the appropriate places in your .ear or directory heirarchy, orion will find them and incorporate the information you specify in them into the final deployment descriptor that lives in the application-deployment directory. It's pretty slick. Hope that's useful. Gary > > Speaking about documentation and RFM please go into > "orion-application.xml.html" and read this: > > "The deployment info for a J2EE-application. Manually created or > automatically produced when auto-deploying a J2EE-application (.ear). It > extends and substitutes the assembly info found in the " > > Where is the rest of the sentence? > > Sayonara! > Danut
Re: What documentation?
No,
it is a convertion error from the template errors that generate these docs rather, it
has been fixed in the internal bundle to be pushed with the next version a while ago.
What was to follow was a link ("href") to another document, there's a few places where
you'll see this happen. The description should have continued after the ref as well
(and now does).
Hope it helps!
/Magnus Stenman, the Orion team
- Original Message -
From: "Nick Newman" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Tuesday, February 27, 2001 1:14 AM
Subject: Re: What documentation?
> I think I can answer the second question about the dangling sentence. In
> the DTD the tag description looks like this:
>
>
> (ejb-module*,web-module*,client-module*,security-role-mapping*,
> persistence?, library*, principals?, mail-session*, user-manager?, log?,
> data-sources?, namespace-access?)>
>
>
> and from that it seems fairly clear that the intention was for the sentence
> to run on into the tag name. That is, the author thought it would be
> fairly clear that it was supposed to end " ...assembly info found in the
> orion-application".
>
> Unfortunately, once the automatic formatting tool got through with it to
> produce the HTML documentation it is nothing like so clear! (At least,
> that's my guess. Anyone got anything better?)
>
>
> Nick Newman
>
>
> At 05:37 PM 2/26/01 -0600, you wrote:
> >A few weeks ago after I asked some questions and posted some opinion I was
> >sent by some guys to RFM.
> >
> >Well, I still have the same problems and I am asking the same question:
> >why is not possible to use a GUI tool to specify all I want for deploying
> >my application? Why do I need to go into the application-deployments
> >folder and modify what Orion has alredy deployed. If you are stuck and
> >still do not get go and play with Sun's RI or WebLogic and ypu will
> >udnerstand what I mean.
> >
> >Speaking about documentation and RFM please go into
> >"orion-application.xml.html" and read this:
> >
> >"The deployment info for a J2EE-application. Manually created or
> >automatically produced when auto-deploying a J2EE-application (.ear). It
> >extends and substitutes the assembly info found in the "
> >
> >Where is the rest of the sentence?
> >
> >Sayonara!
> >Danut
> >
> >
> >_
> >Do You Yahoo!?
> >Get your free @yahoo.com address at http://mail.yahoo.com
> >
>
Re: What documentation?
Today, Danut Prisacaru ([EMAIL PROTECTED]) wrote: > Well, I still have the same problems and I am asking the same question: why > is not possible to use a GUI tool to specify all I want for deploying my > application? Why do I need to go into the application-deployments folder > and modify what Orion has alredy deployed. If you are stuck and still do > not get go and play with Sun's RI or WebLogic and ypu will udnerstand what > I mean. The same thing was bothering me, because having to modify orion's deployment descriptors was getting old. It turns out that you can make the orion web, ejb, and application deployment documents be part of your distribution. I create simplified versions that have just the stuff I care about in them, for instance: By putting these into the appropriate places in your .ear or directory heirarchy, orion will find them and incorporate the information you specify in them into the final deployment descriptor that lives in the application-deployment directory. It's pretty slick. Hope that's useful. Gary > > Speaking about documentation and RFM please go into > "orion-application.xml.html" and read this: > > "The deployment info for a J2EE-application. Manually created or > automatically produced when auto-deploying a J2EE-application (.ear). It > extends and substitutes the assembly info found in the " > > Where is the rest of the sentence? > > Sayonara! > Danut
Re: What documentation?
I think I can answer the second question about the dangling sentence. In the DTD the tag description looks like this: and from that it seems fairly clear that the intention was for the sentence to run on into the tag name. That is, the author thought it would be fairly clear that it was supposed to end " ...assembly info found in the orion-application". Unfortunately, once the automatic formatting tool got through with it to produce the HTML documentation it is nothing like so clear! (At least, that's my guess. Anyone got anything better?) Nick Newman At 05:37 PM 2/26/01 -0600, you wrote: >A few weeks ago after I asked some questions and posted some opinion I was >sent by some guys to RFM. > >Well, I still have the same problems and I am asking the same question: >why is not possible to use a GUI tool to specify all I want for deploying >my application? Why do I need to go into the application-deployments >folder and modify what Orion has alredy deployed. If you are stuck and >still do not get go and play with Sun's RI or WebLogic and ypu will >udnerstand what I mean. > >Speaking about documentation and RFM please go into >"orion-application.xml.html" and read this: > >"The deployment info for a J2EE-application. Manually created or >automatically produced when auto-deploying a J2EE-application (.ear). It >extends and substitutes the assembly info found in the " > >Where is the rest of the sentence? > >Sayonara! >Danut > > >_ >Do You Yahoo!? >Get your free @yahoo.com address at http://mail.yahoo.com >
What documentation?
A few weeks ago after I asked some questions and posted some opinion I was sent by some guys to RFM. Well, I still have the same problems and I am asking the same question: why is not possible to use a GUI tool to specify all I want for deploying my application? Why do I need to go into the application-deployments folder and modify what Orion has alredy deployed. If you are stuck and still do not get go and play with Sun's RI or WebLogic and ypu will udnerstand what I mean. Speaking about documentation and RFM please go into "orion-application.xml.html" and read this: "The deployment info for a J2EE-application. Manually created or automatically produced when auto-deploying a J2EE-application (.ear). It extends and substitutes the assembly info found in the " Where is the rest of the sentence? Sayonara! Danut _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
