From tuscanymeghan68@example.com Wed Feb 01 13:38:24 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 19006 invoked from network); 1 Feb 2006 13:38:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 13:38:23 -0000 Received: (qmail 78219 invoked by uid 500); 1 Feb 2006 13:38:17 -0000 Delivered-To: meghan68@example.com Received: (qmail 78190 invoked by uid 500); 1 Feb 2006 13:38:17 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 78181 invoked by uid 99); 1 Feb 2006 13:38:16 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 05:38:16 -0800 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of meghan68@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO e32.co.us.ibm.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 05:38:15 -0800 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [83.161.120.155]) by e32.co.us.ibm.com (8.12.11/8.12.11) with ESMTP id k11DbtNj002875 for <meghan68@example.com>; Wed, 1 Feb 2006 08:37:55 -0500 Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [83.161.120.155]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id k11DZx9M266956 for <meghan68@example.com>; Wed, 1 Feb 2006 06:35:59 -0700 Received: from d03av03.boulder.ibm.com (loopback [83.161.120.155]) by d03av03.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id k11Dbs54031889 for <meghan68@example.com>; Wed, 1 Feb 2006 06:37:55 -0700 Received: from d03nm129.boulder.ibm.com (d03nm129.boulder.ibm.com [83.161.120.155]) by d03av03.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id k11Dbsl0031886 for <meghan68@example.com>; Wed, 1 Feb 2006 06:37:54 -0700 In-Reply-To: <meghan68@example.com> To: meghan68@example.com Subject: Re: User group presentation - where and what format? MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005 From: Fuhwei Lwo <meghan68@example.com> Message-ID: <meghan68@example.com> Date: Wed, 1 Feb 2006 08:40:19 -0500 X-MIMETrack: Serialize by Router on D03NM129/03/M/IBM(Release 7.0HF124 | January 12, 2006) at 02/01/2006 06:40:19, Serialize complete at 02/01/2006 06:40:19 Content-Type: multipart/alternative; boundary="=_alternative 004ADD7A85257108_=" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --=_alternative 004ADD7A85257108_= Content-Type: text/plain; charset="US-ASCII" Can we create a new directory called presentation under http://incubator.apache.org/tuscany/ to contain all presentation files? Then create an index page for all presentations. Then create a link called "Presentation" under Tuscany at the left hand side of the Tuscany main page to link to the presentation index page. PPT format is fine with me. In fact, any format with browser plugins should be allowed. Fuhwei Lwo Jeremy Boynes <meghan68@example.com> Sent by: meghan68@example.com 01/31/2006 10:22 PM Please respond to meghan68@example.com To meghan68@example.com cc Subject User group presentation - where and what format? I would like to upload a presentation I did to the RTP WUG to the Tuscany site - is there a good location on the site to post it to and in what format? Currently I have a PPT file. Thanks -- Jeremy --=_alternative 004ADD7A85257108_=-- From tuscanymeghan68@example.com Wed Feb 01 16:51:48 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 53222 invoked from network); 1 Feb 2006 16:51:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 16:51:48 -0000 Received: (qmail 73542 invoked by uid 500); 1 Feb 2006 16:51:46 -0000 Delivered-To: meghan68@example.com Received: (qmail 73386 invoked by uid 500); 1 Feb 2006 16:51:45 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 73282 invoked by uid 99); 1 Feb 2006 16:51:45 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO ajax.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 08:51:44 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id DB24DCB for <meghan68@example.com>; Wed, 1 Feb 2006 17:51:23 +0100 (CET) Message-ID: <meghan68@example.com> Date: Wed, 1 Feb 2006 17:51:23 +0100 (CET) From: "Frank Budinsky (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Reopened: (TUSCANY-21) SDO change summary not working properly In-Reply-To: <meghan68@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/TUSCANY-21?page=all ] Frank Budinsky reopened TUSCANY-21: ----------------------------------- Assign To: Frank Budinsky There is a bug in the change recorder set up > SDO change summary not working properly > --------------------------------------- > > Key: TUSCANY-21 > URL: http://issues.apache.org/jira/browse/TUSCANY-21 > Project: Tuscany > Type: Bug > Components: Java SDO Implementation > Reporter: Brent Daniel > Assignee: Frank Budinsky > > I'm having trouble with the change history in the SDO 2 implementation. > 1) The normal pattern in the DAS is to build a data graph and then turn on change recording. When you do this, the adapter for the change recorder doesn't seem to get added to the DataObject instances in the graph, so no changes are recorded. > 2) You can't do a summarize() and then resumeLogging(). The implementation will complain that logging is still enabled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From tuscanymeghan68@example.com Wed Feb 01 16:59:28 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 57619 invoked from network); 1 Feb 2006 16:59:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 16:59:28 -0000 Received: (qmail 93397 invoked by uid 500); 1 Feb 2006 16:59:27 -0000 Delivered-To: meghan68@example.com Received: (qmail 93368 invoked by uid 500); 1 Feb 2006 16:59:27 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 93358 invoked by uid 99); 1 Feb 2006 16:59:27 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO ajax.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 08:59:25 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id 03BB2CB for <meghan68@example.com>; Wed, 1 Feb 2006 17:59:05 +0100 (CET) Message-ID: <meghan68@example.com> Date: Wed, 1 Feb 2006 17:59:05 +0100 (CET) From: "Frank Budinsky (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Resolved: (TUSCANY-21) SDO change summary not working properly In-Reply-To: <meghan68@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/TUSCANY-21?page=all ] Frank Budinsky resolved TUSCANY-21: ----------------------------------- Resolution: Fixed fix in class DataObjectImpl commited to svn. > SDO change summary not working properly > --------------------------------------- > > Key: TUSCANY-21 > URL: http://issues.apache.org/jira/browse/TUSCANY-21 > Project: Tuscany > Type: Bug > Components: Java SDO Implementation > Reporter: Brent Daniel > Assignee: Frank Budinsky > > I'm having trouble with the change history in the SDO 2 implementation. > 1) The normal pattern in the DAS is to build a data graph and then turn on change recording. When you do this, the adapter for the change recorder doesn't seem to get added to the DataObject instances in the graph, so no changes are recorded. > 2) You can't do a summarize() and then resumeLogging(). The implementation will complain that logging is still enabled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From tuscanymeghan68@example.com Wed Feb 01 18:03:45 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 90634 invoked from network); 1 Feb 2006 18:03:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 18:03:44 -0000 Received: (qmail 11685 invoked by uid 500); 1 Feb 2006 18:03:44 -0000 Delivered-To: meghan68@example.com Received: (qmail 11572 invoked by uid 500); 1 Feb 2006 18:03:43 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 11563 invoked by uid 99); 1 Feb 2006 18:03:43 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO ajax.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 10:03:41 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id F22D8C9 for <meghan68@example.com>; Wed, 1 Feb 2006 19:03:19 +0100 (CET) Message-ID: <meghan68@example.com> Date: Wed, 1 Feb 2006 19:03:19 +0100 (CET) From: "Frank Budinsky (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Commented: (TUSCANY-20) Default SDO 2 types not available or working correctly In-Reply-To: <meghan68@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/TUSCANY-20?page=comments#action_12364836 ] Frank Budinsky commented on TUSCANY-20: --------------------------------------- I added support for some of the sdo XSD annotaions (e.g., sdoXML:propertyType and sdoJava:instanceClass). Registering the standard types by default is still TBD. > Default SDO 2 types not available or working correctly > ------------------------------------------------------ > > Key: TUSCANY-20 > URL: http://issues.apache.org/jira/browse/TUSCANY-20 > Project: Tuscany > Type: Bug > Components: Java SDO Implementation > Reporter: Brent Daniel > > The commonj.sdo data types are not available by default through the TypeHelper. > They can be loaded in using XSDHelper.define() with the sdoModel.xsd file. However, the default instance class for commonj.sdo.Integer is java.math.BigInteger. Calling DataObject.set(property, value) where property is of type commonj.sdo.Integer and value is a java.lang.Integer will fail with a ClassCastException. > Modifying the instance class in the sdoModel.xsd will not solve this, as the instanceClass attribute is being ignored and the runtime will default to BigInteger. XSDEcoreHelper is looking for the instanceClass attribute in the Ecore namespace but it is defined in the commonj.sdo/java namespace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From tuscanymeghan68@example.com Wed Feb 01 19:22:42 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 33263 invoked from network); 1 Feb 2006 19:22:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 19:22:40 -0000 Received: (qmail 55457 invoked by uid 500); 1 Feb 2006 19:22:32 -0000 Delivered-To: meghan68@example.com Received: (qmail 55283 invoked by uid 500); 1 Feb 2006 19:22:31 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 55265 invoked by uid 99); 1 Feb 2006 19:22:30 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO ajax.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 11:22:28 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id B19EDCB for <meghan68@example.com>; Wed, 1 Feb 2006 20:22:07 +0100 (CET) Message-ID: <meghan68@example.com> Date: Wed, 1 Feb 2006 20:22:07 +0100 (CET) From: "Jack D. Unrue (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Commented: (TUSCANY-1) port build process to Maven2 In-Reply-To: <meghan68@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/TUSCANY-1?page=comments#action_12364863 ] Jack D. Unrue commented on TUSCANY-1: ------------------------------------- Setting antfile="${basedir}/build.xml" doesn't seem to help the sub-modules. I am continuing to investigate. > port build process to Maven2 > ---------------------------- > > Key: TUSCANY-1 > URL: http://issues.apache.org/jira/browse/TUSCANY-1 > Project: Tuscany > Type: Improvement > Components: Build System > Environment: Java > Reporter: Jack D. Unrue > Assignee: Jeremy Boynes > Attachments: acceptance_poms.zip, tuscany_m2_poms.zip > > Port the existing Tuscany/Java build process from Maven1.x to Maven2.x. Leave the existing maven files in place until the new build is working and there is consensus to remove the old build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From tuscanymeghan68@example.com Wed Feb 01 20:28:55 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 76212 invoked from network); 1 Feb 2006 20:28:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 20:28:55 -0000 Received: (qmail 68076 invoked by uid 500); 1 Feb 2006 20:28:54 -0000 Delivered-To: meghan68@example.com Received: (qmail 68049 invoked by uid 500); 1 Feb 2006 20:28:54 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 68040 invoked by uid 99); 1 Feb 2006 20:28:53 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 12:28:53 -0800 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of meghan68@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO e6.ny.us.ibm.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 12:28:53 -0800 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [83.161.120.155]) by e6.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id k11KSWVU031619 for <meghan68@example.com>; Wed, 1 Feb 2006 15:28:32 -0500 Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [83.161.120.155]) by d01relay04.pok.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id k11KSWSX218034 for <meghan68@example.com>; Wed, 1 Feb 2006 15:28:32 -0500 Received: from d01av04.pok.ibm.com (loopback [83.161.120.155]) by d01av04.pok.ibm.com (8.12.11/8.13.3) with ESMTP id k11KSWw1006680 for <meghan68@example.com>; Wed, 1 Feb 2006 15:28:32 -0500 Received: from d25ml03.torolab.ibm.com (d25ml03.torolab.ibm.com [83.161.120.155]) by d01av04.pok.ibm.com (8.12.11/8.12.11) with ESMTP id k11KSWk3006677 for <meghan68@example.com>; Wed, 1 Feb 2006 15:28:32 -0500 In-Reply-To: <meghan68@example.com> To: meghan68@example.com MIME-Version: 1.0 Subject: Re: SDO code generation using ASM X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 Message-ID: <meghan68@example.com> From: Frank Budinsky <meghan68@example.com> Date: Wed, 1 Feb 2006 15:28:29 -0500 X-MIMETrack: Serialize by Router on D25ML03/25/M/IBM(Release 6.5.4|March 27, 2005) at 02/01/2006 15:28:32, Serialize complete at 02/01/2006 15:28:32 Content-Type: text/plain; charset="US-ASCII" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I took a look at the code and think this is very cool. There are actually two independent (but most often used together) things being demonstrated in the prototype: 1) extracting the SDO metamodel from an annotated Java interface. 2) runtime generation of an implementation class for an existing Java interface. The first one could also be used to import a model and then generate a static implementation at development time. The second one could be seamlessly added as a fallback (instead of throwing an exception) when an SDO object is created (e.g., with DataFactory.create) for a Type where instanceClass is set, but no corresponding implementation class exists (not sure how best to determine that though). I think it would be pretty easy to make #2 work with the existing EMF-based impl, by simply changing the base class and the signature of the generated indexed-get call. Of course there's still the change recording, container management, reference handshaking, etc., code to generate, but I think this would be a very valuable feature. I'd like to help with this, but have no ASM experience myself, so I would definitely need help with that. Doing #1 also seems pretty straightforward, but we would need to propose an API because the SDO spec does not currently provide a define() method that takes a Java class. We'd also need to design the necessary Java annotations and propose them for a future version of SDO. I'd also be willing to help with this if someone else can take the lead. Frank Jeremy Boynes <meghan68@example.com> wrote on 01/23/2006 09:48:44 AM: > Daniel Berg wrote: > > Development time generation will still be necessary for the static > > interfaces so client code can compile against the static types. > > Do you agree? > > > > The interfaces need to be there at development time but the user has the > option of generating them from XSD or other metadata source or simply > just writing/reusing them. Having a generation step is the user's choice > rather than a requirement imposed by the SDO implementation. > > -- > Jeremy From tuscanymeghan68@example.com Wed Feb 01 20:51:52 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 89593 invoked from network); 1 Feb 2006 20:51:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 20:51:52 -0000 Received: (qmail 7119 invoked by uid 500); 1 Feb 2006 20:51:52 -0000 Delivered-To: meghan68@example.com Received: (qmail 7095 invoked by uid 500); 1 Feb 2006 20:51:52 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 7086 invoked by uid 99); 1 Feb 2006 20:51:51 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 12:51:51 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [83.161.120.155] (HELO rwcrmhc12.comcast.net) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 12:51:50 -0800 Received: from [83.161.120.155] (c-24-5-172-141.hsd1.ca.comcast.net[83.161.120.155]) by comcast.net (rwcrmhc12) with ESMTP id <20060201205129m12009r95re>; Wed, 1 Feb 2006 20:51:29 +0000 Message-ID: <meghan68@example.com> Date: Wed, 01 Feb 2006 12:51:33 -0800 From: Jean-Sebastien Delfino <meghan68@example.com> User-Agent: Thunderbird 1.5 (X11/20051025) MIME-Version: 1.0 To: meghan68@example.com Subject: Roadmap for the next few weeks Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi, I started to put together a list of items that I think we should support in our first SCA/Java Milestone. The idea is to establish reasonable goals in terms of function and timeframe. I also think that this will help people find areas where they can contribute, since this is pretty broad. Core Module assembly model - align implementation with a subset of SCA 0.9 (the implementation diverges from SCA 0.9 in some areas today) - support for module and fragment SCDL - support for componentType - no multiplicity - simple properties only, no complex properties - support for both Java and WSDL interfaces Subsystem assembly model - support for subsystem SCDL - ModuleComponents only no externalService and entryPoint at the subsystem level - Support for wiring/specifying endpoints on externalServices - Support for overriding properties of moduleComponents - On Tomcat, subsystem maps to a Tomcat instance, moduleComponent maps to a Web app - In J2SE, you can run a single moduleComponent Client and implementation model - align implementation with a subset of SCA 0.9 - support for SDO2 as well as regular Java objects - basic scope management (request, session, module) - no metadata API - no request context - no session id - no service references - no conversational, no callbacks Development Tools - WSDL2Java and Java2WSDL generators - XSD2SDO and Java2SDO generators - both in the form of API and maven plugins Bindings - Web Service binding using AXIS 2 (SOAP/HTTP, doc literal only, support for streaming) - Pluggable data-binding (start with regular Java objects and SDO) - I think that we can live with just a WS binding for now and look at the default SCA binding later (maybe it'll just be a variation of the WS binding with some defaults anyway). Extensibility - Support contribution of a new binding (I'm thinking about a sample HTTP binding to illustrate that) - Support contribution of a new component type (Ant's sample Javascript component type) Admin - just doc or basic tools (maven plugin?) to install/uninstall a subsystem and module component - just doc or basic tools to start/stop a subsystem and module component - wiring, configuration of module component properties require editing SCDL file and bouncing the subsystem - Simple monitoring/logging Target environments - JDK 5.0 - Tomcat - J2SE Samples I think we need samples for most of the items in this list to illustrate how various user roles will use Tuscany (app. developer, assembler, deployer-admin, system-developer who wants to extend or integrate with Tuscany) and help drive all this work from concrete scenarios. Any thoughts and ideas are welcome. -- Jean-Sebastien From tuscanymeghan68@example.com Wed Feb 01 21:56:30 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 22080 invoked from network); 1 Feb 2006 21:56:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 21:56:30 -0000 Received: (qmail 11475 invoked by uid 500); 1 Feb 2006 21:56:30 -0000 Delivered-To: meghan68@example.com Received: (qmail 11428 invoked by uid 500); 1 Feb 2006 21:56:29 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 11417 invoked by uid 99); 1 Feb 2006 21:56:28 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO ajax.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 13:56:26 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id 82DFACB for <meghan68@example.com>; Wed, 1 Feb 2006 22:56:05 +0100 (CET) Message-ID: <meghan68@example.com> Date: Wed, 1 Feb 2006 22:56:05 +0100 (CET) From: "Jack D. Unrue (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Commented: (TUSCANY-1) port build process to Maven2 In-Reply-To: <meghan68@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/TUSCANY-1?page=comments#action_12364876 ] Jack D. Unrue commented on TUSCANY-1: ------------------------------------- I've solved this (needed to use pluginManagement in the parent pom.xml, then reference in the acceptance modules). This allows the Tomcat-related tasks to execute whether mvn is run from the top-level acceptance dir or an individual acceptance module, and only run once in either case. I am now looking at a follow-on problem where the Tomcat zip isn't being located properly when mvn is run from a specific module dir. > port build process to Maven2 > ---------------------------- > > Key: TUSCANY-1 > URL: http://issues.apache.org/jira/browse/TUSCANY-1 > Project: Tuscany > Type: Improvement > Components: Build System > Environment: Java > Reporter: Jack D. Unrue > Assignee: Jeremy Boynes > Attachments: acceptance_poms.zip, tuscany_m2_poms.zip > > Port the existing Tuscany/Java build process from Maven1.x to Maven2.x. Leave the existing maven files in place until the new build is working and there is consensus to remove the old build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From tuscanymeghan68@example.com Wed Feb 01 22:35:04 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 41391 invoked from network); 1 Feb 2006 22:35:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 22:35:04 -0000 Received: (qmail 77790 invoked by uid 500); 1 Feb 2006 22:35:04 -0000 Delivered-To: meghan68@example.com Received: (qmail 77675 invoked by uid 500); 1 Feb 2006 22:35:02 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 77660 invoked by uid 99); 1 Feb 2006 22:35:02 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO ajax.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 14:34:59 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id 52BBAE1 for <meghan68@example.com>; Wed, 1 Feb 2006 23:34:38 +0100 (CET) Message-ID: <meghan68@example.com> Date: Wed, 1 Feb 2006 23:34:38 +0100 (CET) From: "Jean-Sebastien Delfino (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Commented: (TUSCANY-1) port build process to Maven2 In-Reply-To: <meghan68@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/TUSCANY-1?page=comments#action_12364886 ] Jean-Sebastien Delfino commented on TUSCANY-1: ---------------------------------------------- If we can now run mvn from the acceptance dir then it's fine, I think we can commit that and work the issue when you run it from a subdir later. I had the problem not finding build.xml even when running from the acceptance dir, but I'm running Linux not Windows so it may also be an environment problem. Can you upload your change and I'll try it again here. Thanks. > port build process to Maven2 > ---------------------------- > > Key: TUSCANY-1 > URL: http://issues.apache.org/jira/browse/TUSCANY-1 > Project: Tuscany > Type: Improvement > Components: Build System > Environment: Java > Reporter: Jack D. Unrue > Assignee: Jeremy Boynes > Attachments: acceptance_poms.zip, tuscany_m2_poms.zip > > Port the existing Tuscany/Java build process from Maven1.x to Maven2.x. Leave the existing maven files in place until the new build is working and there is consensus to remove the old build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From tuscanymeghan68@example.com Wed Feb 01 23:28:33 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 63212 invoked from network); 1 Feb 2006 23:28:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 23:28:33 -0000 Received: (qmail 42921 invoked by uid 500); 1 Feb 2006 23:28:32 -0000 Delivered-To: meghan68@example.com Received: (qmail 42791 invoked by uid 500); 1 Feb 2006 23:28:31 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 42724 invoked by uid 99); 1 Feb 2006 23:28:30 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO ajax.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 15:28:26 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id 7CBF8E1 for <meghan68@example.com>; Thu, 2 Feb 2006 00:28:05 +0100 (CET) Message-ID: <meghan68@example.com> Date: Thu, 2 Feb 2006 00:28:05 +0100 (CET) From: "Jack D. Unrue (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Updated: (TUSCANY-1) port build process to Maven2 In-Reply-To: <meghan68@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/TUSCANY-1?page=all ] Jack D. Unrue updated TUSCANY-1: -------------------------------- Attachment: acceptance_poms_v2.zip Updated pom.xml files and build.xml for acceptance tests. mvn runs from the acceptance directory, but the test cases fail with error code 500 in Tomcat as described previously. A couple other comments: - still have to determine why ${user.home} is not being set properly when build.xml runs; if that were working properly, there would be no need to specify -Dmaven.local.repo="%USERPROFILE%/.m2/repository" or equivalent unless you really wanted to override the default repo location - need to reconcile the fact that the Ant targets will run for each acceptance module, but on the first such occasion, all of the sample wars are deployed > port build process to Maven2 > ---------------------------- > > Key: TUSCANY-1 > URL: http://issues.apache.org/jira/browse/TUSCANY-1 > Project: Tuscany > Type: Improvement > Components: Build System > Environment: Java > Reporter: Jack D. Unrue > Assignee: Jeremy Boynes > Attachments: acceptance_poms.zip, acceptance_poms_v2.zip, tuscany_m2_poms.zip > > Port the existing Tuscany/Java build process from Maven1.x to Maven2.x. Leave the existing maven files in place until the new build is working and there is consensus to remove the old build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From tuscanymeghan68@example.com Thu Feb 02 02:25:50 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 29847 invoked from network); 2 Feb 2006 02:25:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2006 02:25:50 -0000 Received: (qmail 8188 invoked by uid 500); 2 Feb 2006 02:25:49 -0000 Delivered-To: meghan68@example.com Received: (qmail 8147 invoked by uid 500); 2 Feb 2006 02:25:49 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 8137 invoked by uid 99); 2 Feb 2006 02:25:48 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 18:25:48 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of meghan68@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO zproxy.gmail.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 18:25:48 -0800 Received: by zproxy.gmail.com with SMTP id f1so299297nzc for <meghan68@example.com>; Wed, 01 Feb 2006 18:25:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iYBgC9zxUyA8EEm3v0DtyXsdEFan6L/JSFlVlZD9WTHEifKhAUYd7lahSH1AJrmHna29JHae9Ad/L86JnZe0Tg0aYeKPCj6OXF1ijnxoyq+monBgmd3vwqmP6FPcVlzgGAjbUas4VRbs1l2ZvlmIfYca0ITc8xJ/nyFf56FGhS0= Received: by 83.161.120.155 with SMTP id v13mr255357nzd; Wed, 01 Feb 2006 18:25:27 -0800 (PST) Received: by 83.161.120.155 with HTTP; Wed, 1 Feb 2006 18:25:27 -0800 (PST) Message-ID: <meghan68@example.com> Date: Wed, 1 Feb 2006 18:25:27 -0800 From: Jeremy Boynes <meghan68@example.com> Sender: meghan68@example.com To: meghan68@example.com Subject: Re: SDO code generation using ASM In-Reply-To: <meghan68@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <meghan68@example.com> <meghan68@example.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 2/1/06, Frank Budinsky <meghan68@example.com> wrote: > I took a look at the code and think this is very cool. There are actually > two independent (but most often used together) things being demonstrated > in the prototype: > > 1) extracting the SDO metamodel from an annotated Java interface. > 2) runtime generation of an implementation class for an existing Java > interface. > > The first one could also be used to import a model and then generate a > static implementation at development time. The second one could be > seamlessly added as a fallback (instead of throwing an exception) when an > SDO object is created (e.g., with DataFactory.create) for a Type where > instanceClass is set, but no corresponding implementation class exists > (not sure how best to determine that though). > > I think it would be pretty easy to make #2 work with the existing > EMF-based impl, by simply changing the base class and the signature of th= e > generated indexed-get call. Of course there's still the change recording, > container management, reference handshaking, etc., code to generate, but = I > think this would be a very valuable feature. I'd like to help with this, > but have no ASM experience myself, so I would definitely need help with > that. > I think we can tweak the generator code so that it can be driven visitor style from the Type metadata. We could then have implementations that are able to generate either source or binary code for both interface and implementation. For starters, I will set it up to generate the same code that the current source generator does - I see some examples of that in the tree but others would be appreciated. I should be able to get this into the main tree over the weekend. > Doing #1 also seems pretty straightforward, but we would need to propose > an API because the SDO spec does not currently provide a define() method > that takes a Java class. We'd also need to design the necessary Java > annotations and propose them for a future version of SDO. I'd also be > willing to help with this if someone else can take the lead. > I would suggest that we create a new sandbox project which we use as a strawman for this, get happy with it ourselves and then take it to the spec group (unless of course we can persuade them to observe and chip in :-) -- Jeremy From tuscanymeghan68@example.com Thu Feb 02 14:18:15 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 46055 invoked from network); 2 Feb 2006 14:18:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2006 14:18:10 -0000 Received: (qmail 98014 invoked by uid 500); 2 Feb 2006 14:18:00 -0000 Delivered-To: meghan68@example.com Received: (qmail 97910 invoked by uid 500); 2 Feb 2006 14:17:59 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Delivered-To: moderator for meghan68@example.com Received: (qmail 57445 invoked by uid 99); 2 Feb 2006 05:19:29 -0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of meghan68@example.com designates 83.161.120.155 as permitted sender) To: meghan68@example.com MIME-Version: 1.0 Subject: subscribe X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 Message-ID: <meghan68@example.com> From: Chidanandan Theyancheri <meghan68@example.com> Date: Wed, 1 Feb 2006 21:19:05 -0800 X-MIMETrack: Serialize by Router on d27ml602/27/M/IBM(Release 7.0|August 18, 2005) at 02/01/2006 11:19:06 PM, Serialize complete at 02/01/2006 11:19:06 PM Content-Type: multipart/alternative; boundary="=_alternative 001D233E88257109_=" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --=_alternative 001D233E88257109_= Content-Type: text/plain; charset="US-ASCII" --=_alternative 001D233E88257109_=-- From tuscanymeghan68@example.com Thu Feb 02 15:44:59 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 2620 invoked from network); 2 Feb 2006 15:44:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2006 15:44:59 -0000 Received: (qmail 58463 invoked by uid 500); 2 Feb 2006 15:44:58 -0000 Delivered-To: meghan68@example.com Received: (qmail 58440 invoked by uid 500); 2 Feb 2006 15:44:57 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 58410 invoked by uid 99); 2 Feb 2006 15:44:57 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2006 07:44:57 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of meghan68@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO uproxy.gmail.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2006 07:44:55 -0800 Received: by uproxy.gmail.com with SMTP id m2so225976ugc for <meghan68@example.com>; Thu, 02 Feb 2006 07:44:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=nbW7mYGYuIw48FVdpyrd0cny7Ez+XHFDrTpZ1U9QoSRyq3K+IIGlEsMFXlRfWr14KxoOmo1f1asyEcix2rBSlX9RAgGBuZAQW5XzmUGWmYBY1VP7Bz09YpZZPK5AdC1qe7Q+QZ1aj2rv6glesdTCI2/hAWs4zmihOm9b6BloqQ4= Received: by 83.161.120.155 with SMTP id g7mr170470nfc; Thu, 02 Feb 2006 07:44:33 -0800 (PST) Received: from ?83.161.120.155? ( [83.161.120.155]) by mx.gmail.com with ESMTP id c10sm750373nfb.283.161.120.155.44.33; Thu, 02 Feb 2006 07:44:33 -0800 (PST) Message-ID: <meghan68@example.com> Date: Thu, 02 Feb 2006 15:44:31 +0000 From: Mike Edwards <meghan68@example.com> User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: meghan68@example.com Subject: Re: SVN Repositiry unreachable References: <meghan68@example.com> <meghan68@example.com> <meghan68@example.com> In-Reply-To: <meghan68@example.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Kevin, It works for me now - there must have been some temporary problem. Yours, Mike. Kevin Williams wrote: > I am unable to reach our SVN repository > (https://svn.apache.org/repos/asf/incubator/tuscany/java). I also > notice that our web site (http://incubator.apache.org/tuscany/) is not > responding. > > From tuscanymeghan68@example.com Thu Feb 02 15:54:31 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 11356 invoked from network); 2 Feb 2006 15:54:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2006 15:54:31 -0000 Received: (qmail 89720 invoked by uid 500); 2 Feb 2006 15:54:30 -0000 Delivered-To: meghan68@example.com Received: (qmail 89691 invoked by uid 500); 2 Feb 2006 15:54:30 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 89682 invoked by uid 99); 2 Feb 2006 15:54:30 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2006 07:54:30 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [83.161.120.155] (HELO mpls-qmqp-02.inet.qwest.net) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 02 Feb 2006 07:54:29 -0800 Received: (qmail 96288 invoked by uid 0); 2 Feb 2006 15:54:08 -0000 Received: from unknown (83.161.120.155) by mpls-qmqp-02.inet.qwest.net with QMQP; 2 Feb 2006 15:54:08 -0000 Received: from 68-69-138-189.clspco.adelphia.net (HELO ?83.161.120.155?) (83.161.120.155) by mpls-pop-02.inet.qwest.net with SMTP; 2 Feb 2006 15:54:08 -0000 Date: Thu, 02 Feb 2006 08:54:03 -0700 Message-ID: <meghan68@example.com> From: "Kevin Williams" <meghan68@example.com> To: meghan68@example.com User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 Subject: Re: Roadmap for the next few weeks References: <meghan68@example.com> In-Reply-To: <meghan68@example.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Along the same lines, I would like to offer these first-milestone development items for the RDB DAS: -Complete the transition to SDO2 -DAS integrated into BigBank sample -Best-practice DAS sample (Stand-alone and SCA-integrated) -Datasource definition in Config file -Tools support - Export metadata - return the SDO Types and/or write an XML file that contains the Types created from the config + resultSetMetadata -- Kevin Jean-Sebastien Delfino wrote: > Hi, > > I started to put together a list of items that I think we should > support in our first SCA/Java Milestone. The idea is to establish > reasonable goals in terms of function and timeframe. I also think that > this will help people find areas where they can contribute, since this > is pretty broad. > > Core Module assembly model > - align implementation with a subset of SCA 0.9 (the implementation > diverges from SCA 0.9 in some areas today) > - support for module and fragment SCDL > - support for componentType > - no multiplicity > - simple properties only, no complex properties > - support for both Java and WSDL interfaces > > Subsystem assembly model > - support for subsystem SCDL > - ModuleComponents only no externalService and entryPoint at the > subsystem level > - Support for wiring/specifying endpoints on externalServices > - Support for overriding properties of moduleComponents > - On Tomcat, subsystem maps to a Tomcat instance, moduleComponent maps > to a Web app > - In J2SE, you can run a single moduleComponent > > Client and implementation model > - align implementation with a subset of SCA 0.9 > - support for SDO2 as well as regular Java objects - basic scope > management (request, session, module) > - no metadata API > - no request context > - no session id > - no service references > - no conversational, no callbacks > > Development Tools > - WSDL2Java and Java2WSDL generators > - XSD2SDO and Java2SDO generators > - both in the form of API and maven plugins > > Bindings > - Web Service binding using AXIS 2 (SOAP/HTTP, doc literal only, > support for streaming) > - Pluggable data-binding (start with regular Java objects and SDO) > - I think that we can live with just a WS binding for now and look at > the default SCA binding later (maybe it'll just be a variation of the > WS binding with some defaults anyway). > > Extensibility > - Support contribution of a new binding (I'm thinking about a sample > HTTP binding to illustrate that) > - Support contribution of a new component type (Ant's sample > Javascript component type) > > Admin > - just doc or basic tools (maven plugin?) to install/uninstall a > subsystem and module component > - just doc or basic tools to start/stop a subsystem and module component > - wiring, configuration of module component properties require editing > SCDL file and bouncing the subsystem > - Simple monitoring/logging > > Target environments > - JDK 5.0 > - Tomcat > - J2SE > > Samples > I think we need samples for most of the items in this list to > illustrate how various user roles will use Tuscany (app. developer, > assembler, deployer-admin, system-developer who wants to extend or > integrate with Tuscany) and help drive all this work from concrete > scenarios. > > Any thoughts and ideas are welcome. > > -- > Jean-Sebastien > > > > From tuscanymeghan68@example.com Thu Feb 02 16:37:37 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 48518 invoked from network); 2 Feb 2006 16:37:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2006 16:37:32 -0000 Received: (qmail 86281 invoked by uid 500); 2 Feb 2006 16:37:31 -0000 Delivered-To: meghan68@example.com Received: (qmail 86247 invoked by uid 500); 2 Feb 2006 16:37:30 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 86234 invoked by uid 99); 2 Feb 2006 16:37:30 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2006 08:37:30 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [83.161.120.155] (HELO rwcrmhc14.comcast.net) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2006 08:37:29 -0800 Received: from [83.161.120.155] (c-24-5-172-141.hsd1.ca.comcast.net[83.161.120.155]) by comcast.net (rwcrmhc14) with ESMTP id <20060202163709m14007jef9e>; Thu, 2 Feb 2006 16:37:09 +0000 Message-ID: <meghan68@example.com> Date: Thu, 02 Feb 2006 08:37:16 -0800 From: Jean-Sebastien Delfino <meghan68@example.com> User-Agent: Thunderbird 1.5 (X11/20051025) MIME-Version: 1.0 To: meghan68@example.com Subject: Re: Roadmap for the next few weeks References: <meghan68@example.com> <meghan68@example.com> In-Reply-To: <meghan68@example.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Kevin Williams wrote: > Along the same lines, I would like to offer these first-milestone > development items for the RDB DAS: > > -Complete the transition to SDO2 > -DAS integrated into BigBank sample > -Best-practice DAS sample (Stand-alone and SCA-integrated) > -Datasource definition in Config file -Tools support - Export > metadata - return the SDO Types and/or write > an XML file that contains the Types created from the config + > resultSetMetadata > > -- > Kevin > > > > Jean-Sebastien Delfino wrote: > >> Hi, >> >> I started to put together a list of items that I think we should >> support in our first SCA/Java Milestone. The idea is to establish >> reasonable goals in terms of function and timeframe. I also think >> that this will help people find areas where they can contribute, >> since this is pretty broad. >> >> Core Module assembly model >> - align implementation with a subset of SCA 0.9 (the implementation >> diverges from SCA 0.9 in some areas today) >> - support for module and fragment SCDL >> - support for componentType >> - no multiplicity >> - simple properties only, no complex properties >> - support for both Java and WSDL interfaces >> >> Subsystem assembly model >> - support for subsystem SCDL >> - ModuleComponents only no externalService and entryPoint at the >> subsystem level >> - Support for wiring/specifying endpoints on externalServices >> - Support for overriding properties of moduleComponents >> - On Tomcat, subsystem maps to a Tomcat instance, moduleComponent >> maps to a Web app >> - In J2SE, you can run a single moduleComponent >> >> Client and implementation model >> - align implementation with a subset of SCA 0.9 >> - support for SDO2 as well as regular Java objects - basic scope >> management (request, session, module) >> - no metadata API >> - no request context >> - no session id >> - no service references >> - no conversational, no callbacks >> >> Development Tools >> - WSDL2Java and Java2WSDL generators >> - XSD2SDO and Java2SDO generators >> - both in the form of API and maven plugins >> >> Bindings >> - Web Service binding using AXIS 2 (SOAP/HTTP, doc literal only, >> support for streaming) >> - Pluggable data-binding (start with regular Java objects and SDO) >> - I think that we can live with just a WS binding for now and look at >> the default SCA binding later (maybe it'll just be a variation of the >> WS binding with some defaults anyway). >> >> Extensibility >> - Support contribution of a new binding (I'm thinking about a sample >> HTTP binding to illustrate that) >> - Support contribution of a new component type (Ant's sample >> Javascript component type) >> >> Admin >> - just doc or basic tools (maven plugin?) to install/uninstall a >> subsystem and module component >> - just doc or basic tools to start/stop a subsystem and module component >> - wiring, configuration of module component properties require >> editing SCDL file and bouncing the subsystem >> - Simple monitoring/logging >> >> Target environments >> - JDK 5.0 >> - Tomcat >> - J2SE >> >> Samples >> I think we need samples for most of the items in this list to >> illustrate how various user roles will use Tuscany (app. developer, >> assembler, deployer-admin, system-developer who wants to extend or >> integrate with Tuscany) and help drive all this work from concrete >> scenarios. >> >> Any thoughts and ideas are welcome. >> >> -- >> Jean-Sebastien >> >> >> >> > > > Kevin, Looks pretty good to me, I think this fit wells with the other items I listed for SCA. I have two questions: - how do you see the config of the datasource? is this going to be integrated with an SCA binding? or another config mechanism? will you need any changes in the extensibility mechanisms from the core SCA runtime or are you happy with the existing extension points? - what do you see under tools support? command line tools? maven integration? any integration with the SDO, XSD and WSDL tools we are listing under the SCA roadmap? Next I guess we need to see how all of this fits with our SDO roadmap. Frank, any thoughts? -- Jean-Sebastien From tuscanymeghan68@example.com Thu Feb 02 17:09:32 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 74445 invoked from network); 2 Feb 2006 17:09:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2006 17:09:32 -0000 Received: (qmail 69972 invoked by uid 500); 2 Feb 2006 17:09:31 -0000 Delivered-To: meghan68@example.com Received: (qmail 69949 invoked by uid 500); 2 Feb 2006 17:09:31 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 69940 invoked by uid 99); 2 Feb 2006 17:09:31 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2006 09:09:31 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [83.161.120.155] (HELO rwcrmhc13.comcast.net) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2006 09:09:30 -0800 Received: from [83.161.120.155] (c-24-5-172-141.hsd1.ca.comcast.net[83.161.120.155]) by comcast.net (rwcrmhc13) with ESMTP id <20060202170910m1300akos5e>; Thu, 2 Feb 2006 17:09:10 +0000 Message-ID: <meghan68@example.com> Date: Thu, 02 Feb 2006 09:09:17 -0800 From: Jean-Sebastien Delfino <meghan68@example.com> User-Agent: Thunderbird 1.5 (X11/20051025) MIME-Version: 1.0 To: meghan68@example.com Subject: Re: m2 POMs for acceptance tests References: <meghan68@example.com> <meghan68@example.com> <meghan68@example.com> <meghan68@example.com> <meghan68@example.com> <meghan68@example.com> <meghan68@example.com> In-Reply-To: <meghan68@example.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Jeremy Boynes wrote: > I can't but help sense a disconnect, specifically over what a "unit test" is. > > Quoting the oracle, OK http://en.wikipedia.org/wiki/Unit_testing > "a unit test is a procedure used to verify that a particular module of > source code is working properly" They are of use to *developers* to > check a specific module (class) is functioning. > > I tend to agree with Jim that unit tests should just rely on objects > that can be constructed in memory, with the use of mock objects to > support specific test cases. There should be no need for macro > configuration objects like sidefiles - if these are needed then the > test is too broad. > > I would also say that JUnit is more than just a unit test framework; > you can use it to construct integration or other tests as well as its > original purpose for unit testing. The big benefit to us here is the > built-in integration of the JUnit framework with the default Maven > build process. We need to be clear when we are talking about "unit > testing" in general and junit in specific. > > Finally, running Tomcat embedded is "no big thing" - it is not hard to > set up and not hard to use (although I would contend that Jetty may be > even simpler). We did this in Geronimo for testing container > integration (both Tomcat and Jetty) and it was not hard to get a > simple config like the one we need working. I think this is worth > investigating as the effort put in now will make it easier to add even > more tests in the future. I'm traveling this week with sporadic access > but would be willing to work with someone this weekend/next week to > help get it going. > > -- > Jeremy > > Yes there is a disconnect here. Thanks for educating us on what a unit test is, but somebody is going to have to explain to me how we test Tuscany without using side files when the most of the SCA assembly spec is about configuring and wiring components using SCDL side files. With respect to running Tomcat embedded or as you say even simpler Jetty, I know that is is not a big thing. The only thing I'm saying is that we need to focus and put priority on the main scenarios that we want to support. As far as I know the main scenario that we want to support at the moment is running Tuscany on top of an existing/regular Tomcat installation, so we should focus our efforts on that scenario. If we want to change direction in terms of architecture and instead focus on running Tomcat or Jetty inside Tuscany, then fine , at some point we can have an architecture discussion on this subject and determine why/if/when we ever want to do that. In the meantime I feel that running Jetty embedded in Tuscany with made-up models constructed in memory from Java code is a little ... disconnected... from our main goal, which is to run with SCDL files, with Tuscany running on top of Tomcat. -- Jean-Sebastien From tuscanymeghan68@example.com Thu Feb 02 17:47:35 2006 Return-Path: <tuscanymeghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 97650 invoked from network); 2 Feb 2006 17:47:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2006 17:47:35 -0000 Received: (qmail 78507 invoked by uid 500); 2 Feb 2006 17:47:34 -0000 Delivered-To: meghan68@example.com Received: (qmail 78450 invoked by uid 500); 2 Feb 2006 17:47:34 -0000 Mailing-List: contact meghan68@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:meghan68@example.com> List-Unsubscribe: <mailto:meghan68@example.com> List-Post: <mailto:meghan68@example.com> List-Id: <tuscany-dev.ws.apache.org> Reply-To: meghan68@example.com Delivered-To: mailing list meghan68@example.com Received: (qmail 78441 invoked by uid 99); 2 Feb 2006 17:47:33 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2006 09:47:33 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of meghan68@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO zproxy.gmail.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2006 09:47:33 -0800 Received: by zproxy.gmail.com with SMTP id f1so121034nzc for <meghan68@example.com>; Thu, 02 Feb 2006 09:47:12 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=o4xXF946P4pTiiymGPFvfzKeAjpgOp5LrCp6stWu6E/i37TC3VHuIi3Giju+sKhDb7HFLLVJNvMcQ+Uv4pDXEmEFPGk90LILDcSVKQAygtUVpj9bDq3HyayISMkz3nnpkCzjBUmn2nP3mnXz+JsN/eMmtRg7fK7txor2d0MijXE= Received: by 83.161.120.155 with SMTP id p5mr849131nzi; Thu, 02 Feb 2006 09:47:12 -0800 (PST) Received: by 83.161.120.155 with HTTP; Thu, 2 Feb 2006 09:47:11 -0800 (PST) Message-ID: <meghan68@example.com> Date: Thu, 2 Feb 2006 09:47:11 -0800 From: Jeremy Boynes <meghan68@example.com> Sender: meghan68@example.com To: meghan68@example.com Subject: Re: m2 POMs for acceptance tests In-Reply-To:
{'source': 'Apache Software Foundation Public Mail Archives'}