RE: SCA distribution is really big now

2007-08-13 Thread Anderson, Jeff T (CA - Toronto)
I like having the samples, in the absence of extensive documentation these are 
key to understanding Tuscany...
I like the idea of packaging the samples as simple SCA contribution jar's.  I 
think keeping the footprint as little as possible is important, both in terms 
of optics and managing the complexity and understanding.
Just my humble opinion...
Jeff



From: haleh mahbod [mailto:[EMAIL PROTECTED]
Sent: Mon 2007-08-13 14:55
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Tuscany Users
Subject: Re: SCA distribution is really big now



It would be good to get user 's view on this as well.  I am re-posting to
tuscany-user list since I am not sure if  everyone monitors both lists.

On 8/11/07, ant elder [EMAIL PROTECTED] wrote:

 Our SCA binary distribution is over 100Meg now and there's still
 extensions
 and dependencies I've not added yet. This seems a little big considering
 we're trying to sell Tuscany as all svelte and light weight.

 So what to do? The reason its so big is that every webapp sample and demo
 we
 have ends up including a copy of most of the runtime and dependencies. One
 solution could be to just ship fewer prebuilt webapp samples and demos.
 Another could be to change the way we do those samples so that each
 sample/demo is just a simple SCA contribution jar and you have to deploy
 that to some Tuscany runtime. We've already the webapp runtime that would
 work for that, and the Geronimo Tuscany support, and we could  create
 another standalone runtime if you don't want to use Tomcat or Geronimo.

 What do people think, does the size matter, are there some other things we
 could do?

...ant






-
**
Confidentiality Warning: This message and any attachments are
intended only for the use of the intended recipient(s), are
confidential, and may be privileged. If you are not the intended
recipient, you are hereby notified that any review, retransmission,
conversion to hard copy, copying, circulation or other use of this
message and any attachments is strictly prohibited. If you are not
the intended recipient, please notify the sender immediately by
return e-mail, and delete this message and any attachments from
your system. Thank you. 

Information confidentielle: Le présent message, ainsi que tout
fichier qui y est joint, est envoyé à l'intention exclusive de son
ou de ses destinataires; il est de nature confidentielle et peut
constituer une information privilégiée. Nous avertissons toute
personne autre que le destinataire prévu que tout examen,
réacheminement, impression, copie, distribution ou autre
utilisation de ce message et de tout fichier qui y est joint est
strictement interdit. Si vous n'êtes pas le destinataire prévu,
veuillez en aviser immédiatement l'expéditeur par retour de
courriel et supprimer ce message et tout document joint de votre
système. Merci.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: SCA distribution is really big now

2007-08-13 Thread Jean-Sebastien Delfino

Anderson, Jeff T (CA - Toronto) wrote:

I like having the samples, in the absence of extensive documentation these are 
key to understanding Tuscany...
I like the idea of packaging the samples as simple SCA contribution jar's.  I 
think keeping the footprint as little as possible is important, both in terms 
of optics and managing the complexity and understanding.
Just my humble opinion...
Jeff

  


+1 to keep the samples as simple SCA contribution JARs.

The current webapp packaging is not quite right anyway as it's 
introducing a half baked mix of J2EE and SCA programming model inside 
the webapp.


I'd suggest the following:

- Package SCA sample components as simple SCA contribution JARs, stay 
away from webapps.


- To allow JSP and servlets to invoke SCA service component, support 
implementation.web Web components as described in [1].


[1] http://www.osoa.org/pages/viewpage.action?pageId=3980





From: haleh mahbod [mailto:[EMAIL PROTECTED]
Sent: Mon 2007-08-13 14:55
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Tuscany Users
Subject: Re: SCA distribution is really big now



It would be good to get user 's view on this as well.  I am re-posting to
tuscany-user list since I am not sure if  everyone monitors both lists.

On 8/11/07, ant elder [EMAIL PROTECTED] wrote:
  

Our SCA binary distribution is over 100Meg now and there's still
extensions
and dependencies I've not added yet. This seems a little big considering
we're trying to sell Tuscany as all svelte and light weight.

So what to do? The reason its so big is that every webapp sample and demo
we
have ends up including a copy of most of the runtime and dependencies. One
solution could be to just ship fewer prebuilt webapp samples and demos.
Another could be to change the way we do those samples so that each
sample/demo is just a simple SCA contribution jar and you have to deploy
that to some Tuscany runtime. We've already the webapp runtime that would
work for that, and the Geronimo Tuscany support, and we could  create
another standalone runtime if you don't want to use Tomcat or Geronimo.

What do people think, does the size matter, are there some other things we
could do?

   ...ant



--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]