At 15:44 16/07/2002 +0200, you wrote:
>Berin Loritsch wrote:
>
>>Cocoon can definitely use its own blueprint. A Cocoon Application
>>Blueprint is an essential document that we need. There are two ways
>>of using Cocoon: integrated in with a traditional J2EE environment,
>>and standalone. The bl
Piroumian Konstantin wrote:
> IMO, the application should be business oriented, e.g. Banking, Billing,
> CRM, Reporting or so. We can questionnairre users to see what is the most
> needed use-case.
I'm in dire need of the usual web based interface to
source code control
problem tracking
pro
racle forms and it
was a totally useless example.
-Andy
>
>
>>-Original Message-
>>From: Anthony W. Marino [mailto:[EMAIL PROTECTED]]
>>Sent: Tuesday, July 16, 2002 7:41 AM
>>To: [EMAIL PROTECTED]; Piroumian Konstantin;
>>'[EMAIL PROTECT
Berin Loritsch wrote:
> Cocoon can definitely use its own blueprint. A Cocoon Application
> Blueprint is an essential document that we need. There are two ways
> of using Cocoon: integrated in with a traditional J2EE environment,
> and standalone. The blueprint will define exactly what part of
Original Message-
> From: Anthony W. Marino [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 16, 2002 7:41 AM
> To: [EMAIL PROTECTED]; Piroumian Konstantin;
> '[EMAIL PROTECTED]'
> Subject: Re: [RT] Cocoon Integration Model
>
>
> My $0.02 is:
> A ) Create
>
>
>-It's more fun than a screw-shop sample.
>
>
... nah... no comment.
>fabien.
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, email: [EMAIL PROTECTED]
>
>
>
>
--
My $0.02 is:
A ) Create a Cocoon version of PetStore (XPetStore?) app similar to what
JPetStore ( http://www.ibatis.com/jpetstore/jpetstore.html ) has done. This
gives developers insight into the capabilities of Cocoon in a digestable
manner.
B ) In order for Cocoon to make it in a huge way I
Artur Bialecki wrote:
>I think cocoon web application blueprints are a great idea.
>I had to get around many cocoon quirks to get it working
>in a J2EE environment. I've always seen cocoon advertised
>for web-publishing so I always thought that I'm not using
>it for what it was intended. To be f
the whole
thing...
Piroumian
Konstantin To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
Subjec
> From: TREGAN Fabien [mailto:[EMAIL PROTECTED]]
>
> >
> >* Insert your own idea here.
>
> I've always thought that a Chess Webbapp would demonstrate
> Cocoon power :
> -It has complexe application logic (you can check the
> validity of a move,
> you can get the whole state of the board fr
>We need something that does three basic things:
>
>1) Has complex application logic--i.e. one approval
> fires off several actions. That application logic
> should be encapsulated in application specific
> components.
>
>2) Need for a non-trivial model. In other words, let's
> not talk
>
>
>>3) Need for reports. Cocoon's integration with FOP is an
>> excelent way to show off how reporting is integrated.
>> We can show how to handle offline generated reports, and
>> reports generated on demand.
>>
>>
>
>And something in rtf and excel.
>
>
+1
>J.
>
>
>---
> From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
> > From: Artur Bialecki [mailto:[EMAIL PROTECTED]]
> >
> > I think cocoon web application blueprints are a great idea.
> > I had to get around many cocoon quirks to get it working
> > in a J2EE environment. I've always seen cocoon advertised
>
>
>
>>Now, let's not do another PetStore, maybe something
>>more along the B to B model?
>>
>>
>
>We need something that does three basic things:
>
>1) Has complex application logic--i.e. one approval
> fires off several actions. That application logic
> should be encapsulated in applica
>"Berin
>
>Loritsch"To: <[EMAIL PROTECTED]>
>
>
&g
Berin
Loritsch"To: <[EMAIL PROTECTED]>
Subject: RE: [RT] Cocoon In
>Cocoon can definitely use its own blueprint. A Cocoon Application
>Blueprint is an essential document that we need. There are two ways
>of using Cocoon: integrated in with a traditional J2EE environment,
>and standalone. The blueprint will define exactly what part of the
>puzzle Cocoon suppo
> From: Artur Bialecki [mailto:[EMAIL PROTECTED]]
>
> I think cocoon web application blueprints are a great idea.
> I had to get around many cocoon quirks to get it working
> in a J2EE environment. I've always seen cocoon advertised
> for web-publishing so I always thought that I'm not using
>
I think cocoon web application blueprints are a great idea.
I had to get around many cocoon quirks to get it working
in a J2EE environment. I've always seen cocoon advertised
for web-publishing so I always thought that I'm not using
it for what it was intended. To be fair J2EE has many quirks
to
Berin Loritsch wrote:
> As of right now, the oppinions on how to get the best out of Cocoon
> are as varied as the number of developers on the list.
Amen.
--
Steven Noelshttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
[EM
20 matches
Mail list logo
