Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 4701 invoked from network); 25 Jan 2010 13:27:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Jan 2010 13:27:08 -0000 Received: (qmail 30404 invoked by uid 500); 25 Jan 2010 13:27:07 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 30308 invoked by uid 500); 25 Jan 2010 13:27:07 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 30300 invoked by uid 99); 25 Jan 2010 13:27:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jan 2010 13:27:07 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rickmcg@gmail.com designates 209.85.211.186 as permitted sender) Received: from [209.85.211.186] (HELO mail-yw0-f186.google.com) (209.85.211.186) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jan 2010 13:26:59 +0000 Received: by ywh16 with SMTP id 16so2666808ywh.25 for ; Mon, 25 Jan 2010 05:26:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :user-agent:mime-version:to:subject:references:in-reply-to :content-type; bh=USwT4Dwf3n6ee8pFXAViTTjqLm0t6a+M+3fC2ul8YsE=; b=EFjAwcFNt05dcssmIpol6Vb033XMM5MPxhjFGT3WKdKm909PRPc94s2ffeICIozQ5i uY2lnfhsjtJmlhlta+yN1nlrWs7J+c3aVaztcLk3BjJQDrJX9mZOYfYfBHwoNZhG3hLS hbgPU6c4oFCvxc1IM/gQcwQQALukwAnl7qwiw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type; b=J2/BtHLqbv1M3bqj5hAZ3Tr6FK5BWC1WDkCUl44YokqLIaY4iZCrhLhqpF2gGIPb+9 Rtr9sKF1uGFZ7ksu+itciqxitEe/DagpauHHITksavakdx8H0Xbp3mRf/qHRXLHwpmMf 2PQm5X2s08woLCgpof1ce3WVyA5GVoS6nzdX4= Received: by 10.150.118.18 with SMTP id q18mr4708992ybc.113.1264425997707; Mon, 25 Jan 2010 05:26:37 -0800 (PST) Received: from ?192.168.1.103? (24-151-82-15.dhcp.nwtn.ct.charter.com [24.151.82.15]) by mx.google.com with ESMTPS id 9sm1719291ywf.35.2010.01.25.05.26.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 25 Jan 2010 05:26:36 -0800 (PST) Message-ID: <4B5D9C0A.7090008@gmail.com> Date: Mon, 25 Jan 2010 08:26:34 -0500 From: Rick McGuire Reply-To: rickmcg@gmail.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: dev@geronimo.apache.org Subject: Re: rfc66 update References: <5eb405c71001231855u497b874ckc06ae42ecafb4089@mail.gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------080902030208050707060405" This is a multi-part message in MIME format. --------------080902030208050707060405 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 1/25/2010 8:06 AM, Delos wrote: > It's really great news! > > But I have some questions about current implementation.Just want to > learn more from it. > > 1) I found only active and starting bundles are taken into account in > current implementation. What about resolved bundles? That's the requirement of the RFC66 specification. Resolution is a requirement for a bundle to transition to the active or starting states, but the extender is not supposed to take action until one of those states is seen. It's the same way with Blueprint. > > 2) For lazy activiated bundles, only starting bundles will be > deployed.But in RFC 66, it said "A bundle that has a lazy activation > policy should not be transitioned to the STARTING state by the web > extender unless a request is made that requires a class to be loaded." > Does the implementation violate the document? This is a statement that the extender should not explicitly force the bundle into a started state, but rather should leave that transition to one triggered by a class load. If the processing the extender needs to perform in processing the bundle results in a triggering class load, that's ok. > > 3) In RFC 66, static content can be requested without starting a WAB. > It's not in the TODO file. Do you have any idea for it? I'm not sure > if configuration of WAB can become accessible before actually it's > started. The note about static content is marked as an optional feature. For a lot of processing, it would not be possible to achieve deployment without performing a classload. > > Thanks! > > 2010/1/24 David Jencks > > > great news! congratulations! > > david jencks > > > On Jan 23, 2010, at 6:55 PM, Jarek Gawor wrote: > > Hi all, > > Today I checked in an initial version of the rfc66 extender > that can > actually deploy WABs with simple servlets and jsps. There is still > much work to be done (for example updating the Jasper module > builder > to work with Bundles) but simple stuff seems to be working. In > fact > with David's recent JNDI (rfc142) integration work I was able to > deploy the Aries blog sample in Geronimo. > > Here are the steps I took to run the sample: > > 1) Build latest blog sample in Aries > 2) Build latest Geronimo trunk > 3) cd plugins/wab/web-tomcat-server/target/assembly (or > web-jetty-server if you prefer) > 4) Create database for blog sample using blogDB.sql from blog > sample: > > java -cp > repository/org/apache/geronimo/bundles/derby-all/10.4.2.0-SNAPSHOT/derby-all-10.4.2.0-SNAPSHOT.jar > org.apache.derby.tools.ij > /samples/blog-sample/blog-assembly/target/blogDB.sql > > 5) Move created blogDB directory to > plugins/wab/web-tomcat-server/target/assembly/var/derby > > 6) Start server: > > ./bin/geronimo -l > > 7) Install and start all the blog sample bundles > (blog-api-1.0.0.jar, > blog-persistence-1.0.0.jar, blog-1.0.0.jar, > blog-servlet-1.0.0.jar) > using the karaf console. > > 8) Once you start the blog-servlet-1.0.0.jar bundle, the WAB > will be > deployed and you should be able to access > http://localhost:8080/blog. > And if everything is running right you should be able to add > new blog > entries, etc. > > Enjoy, > Jarek > > > > > > -- > Best Regards, > > Delos --------------080902030208050707060405 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 1/25/2010 8:06 AM, Delos wrote:
It's really great news!

But I have some questions about current implementation.Just want to learn more from it.

1) I found only active and starting bundles are taken into account in current implementation. What about resolved bundles?

That's the requirement of the RFC66 specification.  Resolution is a requirement for a bundle to transition to the active or starting states, but the extender is not supposed to take action until one of those states is seen.  It's the same way with Blueprint.


2) For lazy activiated bundles, only starting bundles will be deployed.But in RFC 66, it said "A bundle that has a lazy activation policy should not be transitioned to the STARTING state by the web extender unless a request is made that requires a class to be loaded." Does the implementation violate the document?

This is a statement that the extender should not explicitly force the bundle into a started state, but rather should leave that transition to one triggered by a class load.  If the processing the extender needs to perform in processing the bundle results in a triggering class load, that's ok.


3) In RFC 66, static content can be requested without starting a WAB. It's not in the TODO file. Do you have any idea for it? I'm not sure if configuration of WAB can become accessible before actually it's started.

The note about static content is marked as an optional feature.  For a lot of processing, it would not be possible to achieve deployment without performing a classload. 


Thanks!

2010/1/24 David Jencks <david_jencks@yahoo.com>
great news! congratulations!

david jencks


On Jan 23, 2010, at 6:55 PM, Jarek Gawor wrote:

Hi all,

Today I checked in an initial version of the rfc66 extender that can
actually deploy WABs with simple servlets and jsps. There is still
much work to be done (for example updating the Jasper module builder
to work with Bundles) but simple stuff seems to be working. In fact
with David's recent JNDI (rfc142) integration work I was able to
deploy the Aries blog sample in Geronimo.

Here are the steps I took to run the sample:

1) Build latest blog sample in Aries
2) Build latest Geronimo trunk
3) cd plugins/wab/web-tomcat-server/target/assembly (or
web-jetty-server if you prefer)
4) Create database for blog sample using blogDB.sql from blog sample:

java -cp repository/org/apache/geronimo/bundles/derby-all/10.4.2.0-SNAPSHOT/derby-all-10.4.2.0-SNAPSHOT.jar
org.apache.derby.tools.ij
<aries>/samples/blog-sample/blog-assembly/target/blogDB.sql

5) Move created blogDB directory to
plugins/wab/web-tomcat-server/target/assembly/var/derby

6) Start server:

./bin/geronimo -l

7) Install and start all the blog sample bundles (blog-api-1.0.0.jar,
blog-persistence-1.0.0.jar, blog-1.0.0.jar, blog-servlet-1.0.0.jar)
using the karaf console.

8) Once you start the blog-servlet-1.0.0.jar bundle, the WAB will be
deployed and you should be able to access http://localhost:8080/blog.
And if everything is running right you should be able to add new blog
entries, etc.

Enjoy,
Jarek




--
Best Regards,

Delos

--------------080902030208050707060405--