From meghan68@example.com Thu Mar 02 01:09:19 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 22204 invoked from network); 2 Mar 2006 01:09:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Mar 2006 01:09:19 -0000 Received: (qmail 28254 invoked by uid 500); 2 Mar 2006 01:10:06 -0000 Delivered-To: meghan68@example.com Received: (qmail 28040 invoked by uid 500); 2 Mar 2006 01:10:04 -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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 28019 invoked by uid 99); 2 Mar 2006 01:10:03 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL 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 Mar 2006 17:10:01 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id ADA34DE for <meghan68@example.com>; Thu, 2 Mar 2006 02:09:40 +0100 (CET) Message-ID: <meghan68@example.com> Date: Thu, 2 Mar 2006 02:09:40 +0100 (CET) From: "Julie Zhuo (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Closed: (BEEHIVE-1071) Move the jsr173 jar to beehive01.bea.com 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/BEEHIVE-1071?page=all ] Julie Zhuo closed BEEHIVE-1071: ------------------------------- Assign To: Julie Zhuo (was: Eddie O'Neil) Verified fixed with rev381904. > Move the jsr173 jar to beehive01.bea.com > ---------------------------------------- > > Key: BEEHIVE-1071 > URL: http://issues.apache.org/jira/browse/BEEHIVE-1071 > Project: Beehive > Type: Bug > Components: Build > Versions: 1.0.1 > Reporter: Julie Zhuo > Assignee: Julie Zhuo > Fix For: 1.0.1 > Attachments: patch.txt > > Will attach a patch shortly. -- 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 meghan68@example.com Thu Mar 02 18:54:17 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 63480 invoked from network); 2 Mar 2006 18:54:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Mar 2006 18:54:17 -0000 Received: (qmail 6469 invoked by uid 500); 2 Mar 2006 18:55:04 -0000 Delivered-To: meghan68@example.com Received: (qmail 6433 invoked by uid 500); 2 Mar 2006 18:55:03 -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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 6422 invoked by uid 99); 2 Mar 2006 18:55:03 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL 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; Thu, 02 Mar 2006 10:55:02 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id 1ECEDDD for <meghan68@example.com>; Thu, 2 Mar 2006 19:54:41 +0100 (CET) Message-ID: <meghan68@example.com> Date: Thu, 2 Mar 2006 19:54:41 +0100 (CET) From: "Krista Baker (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Commented: (BEEHIVE-1070) bindingUpdateErrors expression="${aValue}" always returns tag error 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/BEEHIVE-1070?page=comments#action_12368569 ] Krista Baker commented on BEEHIVE-1070: --------------------------------------- Any updates on which is the proper behavior for this tag? The documentation example or the current implementation? -Thanks! > bindingUpdateErrors expression="${aValue}" always returns tag error > ------------------------------------------------------------------- > > Key: BEEHIVE-1070 > URL: http://issues.apache.org/jira/browse/BEEHIVE-1070 > Project: Beehive > Type: Bug > Components: NetUI > Versions: 1.0.1 > Reporter: Krista Baker > Fix For: v.next > > As listed in the JSP tag documentation, the following tag will always produce a tag error > <netui:bindingUpdateErrors expression="${actionForm.firstName}"/> > with a message of: Attribute 'expression' is required to have a value. The value "" is illegal. This is often caused by binding to an object with a null value. > If the above expression="${actionForm.firstName}" is changed to "actionForm.firstName", the expected behavior will be observed. > The netui test of coretags/binding/nullbinding is an example of this where the error is seen only because the expression="${ }". > From this index.jsp: > <li><netui:bindingUpdateErrors expression="${pageFlow.nullValue}" /> -- Binding Errors</li> > Even though the value remains null, if the expression is changed to the following, > <li><netui:bindingUpdateErrors expression="pageFlow.nullValue" /> -- Binding Errors</li> > the error will not occur even though the pageFlow value is still null. > There are three netui testRecorder tests that use this element and attribute combination: > coretags/binding/nullbinding - uses expression="${}" > coretags/binding/report - uses expression="" > tags/bindingUpdateErrors - uses expression="" > I am not sure if the example in the docs (http://beehive.apache.org/docs/1.0.1/netui/apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/bindingUpdateErrors.html) and the nullbinding test are incorrect or if it is the other way around that the other two tests, even though currently producing expected results, are wrong. -- 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 meghan68@example.com Fri Mar 03 02:25:31 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 57296 invoked from network); 3 Mar 2006 02:25:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Mar 2006 02:25:31 -0000 Received: (qmail 81622 invoked by uid 500); 3 Mar 2006 02:26:17 -0000 Delivered-To: meghan68@example.com Received: (qmail 81600 invoked by uid 500); 3 Mar 2006 02:26: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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 81587 invoked by uid 99); 3 Mar 2006 02:26:16 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL 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; Thu, 02 Mar 2006 18:26:16 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id 5DF2EDF for <meghan68@example.com>; Fri, 3 Mar 2006 03:25:55 +0100 (CET) Message-ID: <meghan68@example.com> Date: Fri, 3 Mar 2006 03:25:55 +0100 (CET) From: "Jim Cummings (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Created: (BEEHIVE-1074) can you include generated src in the src dist - like for the system controls 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 can you include generated src in the src dist - like for the system controls ---------------------------------------------------------------------------- Key: BEEHIVE-1074 URL: http://issues.apache.org/jira/browse/BEEHIVE-1074 Project: Beehive Type: Improvement Components: Controls Versions: v.next Reporter: Jim Cummings Priority: Minor I noticed the src dist doesn't include generated src like control beans, etc for the system controls. It would be useful if those were included so devs could debug into those files when having tricky problems. -- 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 meghan68@example.com Fri Mar 03 03:01:16 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 69322 invoked from network); 3 Mar 2006 03:01:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Mar 2006 03:01:16 -0000 Received: (qmail 9287 invoked by uid 500); 3 Mar 2006 03:02:02 -0000 Delivered-To: meghan68@example.com Received: (qmail 9254 invoked by uid 500); 3 Mar 2006 03:02: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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 9243 invoked by uid 99); 3 Mar 2006 03:02:01 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL 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; Thu, 02 Mar 2006 19:02:01 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id 6536EDD for <meghan68@example.com>; Fri, 3 Mar 2006 04:01:40 +0100 (CET) Message-ID: <meghan68@example.com> Date: Fri, 3 Mar 2006 04:01:40 +0100 (CET) From: "Eddie O'Neil (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Updated: (BEEHIVE-998) Compilation error for generated client initializer due to generated eventAdaptor not implementing methods in super intf of EventSet intf 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/BEEHIVE-998?page=all ] Eddie O'Neil updated BEEHIVE-998: --------------------------------- Assign To: Eddie O'Neil I think that this was fixed in SVN 366968. Need to double check that it's the right thing to do; then I'll resolve this bug. > Compilation error for generated client initializer due to generated eventAdaptor not implementing methods in super intf of EventSet intf > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: BEEHIVE-998 > URL: http://issues.apache.org/jira/browse/BEEHIVE-998 > Project: Beehive > Type: Bug > Components: Controls > Versions: V1 > Reporter: Pradeep Bollineni > Assignee: Eddie O'Neil > > Have the following control interface and extension definitions: > @ControlInterface interface BaseControl { > @EventSet interface BaseCallback { > void base_callback(); > } > } > @ControlExtension interface DerivedControl { > @EventSet interface DerivedCallback extends BaseCallback { > void derived_callback(); > } > } > Generated event adapter class in the client initializer using the DerivedControl: > public static class ControlClientDerivedControlEventAdaptor > implements DerivedControl.DerivedCallback, > EventAdaptor, java.io.Serializable > { > processes.parent2SBC _client; > > public ControlClientDerivedControlEventAdaptor(processes.parent2SBC client) { _client = client; } > > public Object getClient() { return _client; } > > public void derived_callback() > { > _client.derived_callback_clientResponse(); > } > } > Get a compilation error for the client initalizer as the generated ControlClientDerivedControlEventAdaptor does not implement the callback super interface method base_callback. > Is there a workaround? > Thanks > Pradeep Bollineni -- 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 meghan68@example.com Fri Mar 03 03:38:25 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 80753 invoked from network); 3 Mar 2006 03:38:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Mar 2006 03:38:25 -0000 Received: (qmail 40132 invoked by uid 500); 3 Mar 2006 03:39:05 -0000 Delivered-To: meghan68@example.com Received: (qmail 40048 invoked by uid 500); 3 Mar 2006 03:39:05 -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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 40019 invoked by uid 99); 3 Mar 2006 03:39:05 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL 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; Thu, 02 Mar 2006 19:39:04 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id 72266DD for <meghan68@example.com>; Fri, 3 Mar 2006 04:38:43 +0100 (CET) Message-ID: <meghan68@example.com> Date: Fri, 3 Mar 2006 04:38:43 +0100 (CET) From: "Eddie O'Neil (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Assigned: (BEEHIVE-996) Compilation error on an extended control bean when callback intf on base ctrl intf and extended crtl intf have same name In-Reply-To: <{{EMAIL+PHONE}}> 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/BEEHIVE-996?page=all ] Eddie O'Neil reassigned BEEHIVE-996: ------------------------------------ Assign To: Eddie O'Neil > Compilation error on an extended control bean when callback intf on base ctrl intf and extended crtl intf have same name > ------------------------------------------------------------------------------------------------------------------------ > > Key: BEEHIVE-996 > URL: http://issues.apache.org/jira/browse/BEEHIVE-996 > Project: Beehive > Type: Bug > Components: Controls > Versions: V1 > Environment: Win XP > Reporter: Pradeep Bollineni > Assignee: Eddie O'Neil > > The control bean generated for the control extension has ambiguous reference to Callback interface in the callback listener methods when there is a callback interface extension in the control extension as shown below: > @ControlInterface > interface BaseControl { > @EventSet > public interface Callback { > void method1(); > } > } > @ControlExtension > interface ExtendedControl extends BaseControl { > @EventSet > public interface Callback extends BaseControl.Callback { > void method2(); > } > } > Generated ControlBean listener method: > public class ExtendedControlBean extends BaseControlBean implements ExtendedControl { > public synchronized void removeCallbackListener(Callback listener) > { > CallbackNotifier notifier = (CallbackNotifier)getEventNotifier(Callback.class); //ambiguous reference as there is a Callback in BaseControlBean and ExtendedControl > notifier.removeListener(listener); > } > } > Is there a work around for this other than re-naming the interface in the extended control? -- 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 meghan68@example.com Fri Mar 03 03:43:23 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 83161 invoked from network); 3 Mar 2006 03:43:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Mar 2006 03:43:22 -0000 Received: (qmail 43133 invoked by uid 500); 3 Mar 2006 03:44:09 -0000 Delivered-To: meghan68@example.com Received: (qmail 43116 invoked by uid 500); 3 Mar 2006 03:44:08 -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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 43103 invoked by uid 99); 3 Mar 2006 03:44:08 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL 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; Thu, 02 Mar 2006 19:44:08 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id 57DA5DD for <meghan68@example.com>; Fri, 3 Mar 2006 04:43:41 +0100 (CET) Message-ID: <meghan68@example.com> Date: Fri, 3 Mar 2006 04:43:41 +0100 (CET) From: "Eddie O'Neil (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Updated: (BEEHIVE-1074) can you include generated src in the src dist - like for the system controls 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/BEEHIVE-1074?page=all ] Eddie O'Neil updated BEEHIVE-1074: ---------------------------------- Fix Version: v.next Version: V1 1.0.1 (was: v.next) Assign To: Eddie O'Neil Ah -- good catch. I'd not thought of that. Will have that committed to trunk/ shortly. > can you include generated src in the src dist - like for the system controls > ---------------------------------------------------------------------------- > > Key: BEEHIVE-1074 > URL: http://issues.apache.org/jira/browse/BEEHIVE-1074 > Project: Beehive > Type: Improvement > Components: Controls > Versions: V1, 1.0.1 > Reporter: Jim Cummings > Assignee: Eddie O'Neil > Priority: Minor > Fix For: v.next > > I noticed the src dist doesn't include generated src like control beans, etc for the system controls. It would be useful if those were included so devs could debug into those files when having tricky problems. -- 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 meghan68@example.com Fri Mar 03 04:14:19 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 96466 invoked from network); 3 Mar 2006 04:14:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Mar 2006 04:14:18 -0000 Received: (qmail 74320 invoked by uid 500); 3 Mar 2006 04:15:05 -0000 Delivered-To: meghan68@example.com Received: (qmail 74303 invoked by uid 500); 3 Mar 2006 04:15:05 -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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 74292 invoked by uid 99); 3 Mar 2006 04:15:04 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL 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; Thu, 02 Mar 2006 20:15:04 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id 71B61DD for <meghan68@example.com>; Fri, 3 Mar 2006 05:14:42 +0100 (CET) Message-ID: <meghan68@example.com> Date: Fri, 3 Mar 2006 05:14:42 +0100 (CET) From: "Eddie O'Neil (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Resolved: (BEEHIVE-1074) can you include generated src in the src dist - like for the system controls 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/BEEHIVE-1074?page=all ] Eddie O'Neil resolved BEEHIVE-1074: ----------------------------------- Resolution: Fixed Fixed in SVN 382648. > can you include generated src in the src dist - like for the system controls > ---------------------------------------------------------------------------- > > Key: BEEHIVE-1074 > URL: http://issues.apache.org/jira/browse/BEEHIVE-1074 > Project: Beehive > Type: Improvement > Components: Controls > Versions: V1, 1.0.1 > Reporter: Jim Cummings > Assignee: Eddie O'Neil > Priority: Minor > Fix For: v.next > > I noticed the src dist doesn't include generated src like control beans, etc for the system controls. It would be useful if those were included so devs could debug into those files when having tricky problems. -- 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 meghan68@example.com Fri Mar 03 18:56:16 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 68488 invoked from network); 3 Mar 2006 18:56:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Mar 2006 18:56:16 -0000 Received: (qmail 28105 invoked by uid 500); 3 Mar 2006 18:57:02 -0000 Delivered-To: meghan68@example.com Received: (qmail 28084 invoked by uid 500); 3 Mar 2006 18:57: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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 28072 invoked by uid 99); 3 Mar 2006 18:57:01 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL 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; Fri, 03 Mar 2006 10:57:01 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id 0B53ADC for <meghan68@example.com>; Fri, 3 Mar 2006 19:56:39 +0100 (CET) Message-ID: <meghan68@example.com> Date: Fri, 3 Mar 2006 19:56:39 +0100 (CET) From: "Chad Schoettger (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Resolved: (BEEHIVE-1048) generateScopeId not rendering required JavaScript in some cases 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/BEEHIVE-1048?page=all ] Chad Schoettger resolved BEEHIVE-1048: -------------------------------------- Resolution: Fixed Assign To: Alejandro Ramirez (was: Carlin Rogers) Fixed with svn rev 382910. > generateScopeId not rendering required JavaScript in some cases > --------------------------------------------------------------- > > Key: BEEHIVE-1048 > URL: http://issues.apache.org/jira/browse/BEEHIVE-1048 > Project: Beehive > Type: Bug > Components: NetUI > Versions: V1 > Reporter: Chad Schoettger > Assignee: Alejandro Ramirez > Fix For: v.next > > I was able to recreate this using this html snippet. > <netui:html generateIdScope="true"> > <netui:scriptHeader/> > <netui:divPanel tagId="foo"/> > </netui:html> > This is the HTML that was generated, note it doesn't have any lookup javascript. > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" > > > <html lang="en" netui:idScope="n0"> > <script language="JavaScript" type="text/JavaScript" src="/expr6Web/resources/beehive/version1/javascript/netui-tree.js"></script> > <div id="n0.foo" netui-div-panel="true"></div> > <script language="JavaScript" type="text/JavaScript"> > <!-- > // **** Start the NetUI Framework Generated JavaScript **** > // write out the webapp name > netUI.webAppName = "/expr6Web"; > netUI.netUIDivPanel = new NetUIDivPanel(); > netUI.netUIDivPanel.init(); > --> > </script> > </html> -- 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 meghan68@example.com Fri Mar 03 19:29:19 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 84431 invoked from network); 3 Mar 2006 19:29:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Mar 2006 19:29:19 -0000 Received: (qmail 83786 invoked by uid 500); 3 Mar 2006 19:30:05 -0000 Delivered-To: meghan68@example.com Received: (qmail 83763 invoked by uid 500); 3 Mar 2006 19:30:05 -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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 83749 invoked by uid 99); 3 Mar 2006 19:30:04 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL 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; Fri, 03 Mar 2006 11:30:02 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id 54301DD for <meghan68@example.com>; Fri, 3 Mar 2006 20:29:41 +0100 (CET) Message-ID: <meghan68@example.com> Date: Fri, 3 Mar 2006 20:29:41 +0100 (CET) From: "Chad Schoettger (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Assigned: (BEEHIVE-996) Compilation error on an extended control bean when callback intf on base ctrl intf and extended crtl intf have same name In-Reply-To: <{{EMAIL+PHONE}}> 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/BEEHIVE-996?page=all ] Chad Schoettger reassigned BEEHIVE-996: --------------------------------------- Assign To: Chad Schoettger (was: Eddie O'Neil) > Compilation error on an extended control bean when callback intf on base ctrl intf and extended crtl intf have same name > ------------------------------------------------------------------------------------------------------------------------ > > Key: BEEHIVE-996 > URL: http://issues.apache.org/jira/browse/BEEHIVE-996 > Project: Beehive > Type: Bug > Components: Controls > Versions: V1 > Environment: Win XP > Reporter: Pradeep Bollineni > Assignee: Chad Schoettger > > The control bean generated for the control extension has ambiguous reference to Callback interface in the callback listener methods when there is a callback interface extension in the control extension as shown below: > @ControlInterface > interface BaseControl { > @EventSet > public interface Callback { > void method1(); > } > } > @ControlExtension > interface ExtendedControl extends BaseControl { > @EventSet > public interface Callback extends BaseControl.Callback { > void method2(); > } > } > Generated ControlBean listener method: > public class ExtendedControlBean extends BaseControlBean implements ExtendedControl { > public synchronized void removeCallbackListener(Callback listener) > { > CallbackNotifier notifier = (CallbackNotifier)getEventNotifier(Callback.class); //ambiguous reference as there is a Callback in BaseControlBean and ExtendedControl > notifier.removeListener(listener); > } > } > Is there a work around for this other than re-naming the interface in the extended control? -- 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 meghan68@example.com Sat Mar 04 07:48:34 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 89963 invoked from network); 4 Mar 2006 07:48:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Mar 2006 07:48:34 -0000 Received: (qmail 14267 invoked by uid 500); 4 Mar 2006 07:49:20 -0000 Delivered-To: meghan68@example.com Received: (qmail 14241 invoked by uid 500); 4 Mar 2006 07:49:20 -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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 14230 invoked by uid 99); 4 Mar 2006 07:49:19 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL 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; Fri, 03 Mar 2006 23:49:17 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id 54080DD for <meghan68@example.com>; Sat, 4 Mar 2006 08:48:56 +0100 (CET) Message-ID: <meghan68@example.com> Date: Sat, 4 Mar 2006 08:48:56 +0100 (CET) From: "Carlin Rogers (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Updated: (BEEHIVE-1073) Modify the popup window ActionForward handling to forward to a framework JSP (or Servlet) instead of writing directly to the response in the DefaultActionForwardHandler 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/BEEHIVE-1073?page=all ] Carlin Rogers updated BEEHIVE-1073: ----------------------------------- Attachment: j1073-patch.txt Attaching a patch that can be used to resolve this feature change request. This design change started with some off line discussion, however, before committing this I'd like to post some of the details to the dev list. I also include a couple of questions for the dev list. Any feedback is appreciated and I'll rework this patch as needed and then commit it. Thanks. > Modify the popup window ActionForward handling to forward to a framework JSP (or Servlet) instead of writing directly to the response in the DefaultActionForwardHandler > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: BEEHIVE-1073 > URL: http://issues.apache.org/jira/browse/BEEHIVE-1073 > Project: Beehive > Type: Improvement > Components: NetUI > Versions: V1, 1.0.1, v.next > Reporter: Carlin Rogers > Assignee: Carlin Rogers > Fix For: v.next > Attachments: j1073-patch.txt > > I have a request to change the design of the popup window ActionForward handling to forward to a framework JSP (or Servlet) instead of writing directly to the response in the DefaultActionForwardHandler. Currently, when the DefaultActionForwardHandler.processForward() routine gets the "_auto" Forward of the return to page flow, we write directly to the response (just with our own javascript, no other markup) and return null. This is a perfectly legal and valid design. However, a design change is needed to support framework implementations (portal) that have a sort of two phase process of first running the action, then including the rendering of return URI from the ActionForward. > The change would be that the DefaultActionForwardHandler.processForward() would no longer write any markup to the response. Instead it would return an ActionForward with a path to a JSP or servlet that would handle the actual rendering. -- 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 meghan68@example.com Sat Mar 04 07:54:42 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 90989 invoked from network); 4 Mar 2006 07:54:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Mar 2006 07:54:42 -0000 Received: (qmail 19986 invoked by uid 500); 4 Mar 2006 07:55:29 -0000 Delivered-To: meghan68@example.com Received: (qmail 19790 invoked by uid 500); 4 Mar 2006 07:55:28 -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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 19779 invoked by uid 99); 4 Mar 2006 07:55:28 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Mar 2006 23:55:28 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=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 zproxy.gmail.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Mar 2006 23:55:27 -0800 Received: by zproxy.gmail.com with SMTP id r28so880252nza for <meghan68@example.com>; Fri, 03 Mar 2006 23:55:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=SCje5dhmwzXgvUYBZ/Rd22+Vn3holYg9ajXn0UdxmxyYKFpTY/o6Jw8ZY3eFi9q1cctCiNnsUdHOHo8fSaBdVahlyA4pURpk98I8njyQZcJCRTL6VCaHdA4SPyZwDS2Z1spVmBN9N0X01N2/nFUCK/HVCF7P4ROD+taTq+Gzu4A= Received: by 83.161.120.155 with SMTP id o20mr4271363nzo; Fri, 03 Mar 2006 23:55:06 -0800 (PST) Received: by 83.161.120.155 with HTTP; Fri, 3 Mar 2006 23:55:06 -0800 (PST) Message-ID: <meghan68@example.com> Date: Sat, 4 Mar 2006 00:55:06 -0700 From: "Carlin Rogers" <meghan68@example.com> To: "Beehive Developers" <meghan68@example.com> Subject: Patch for beehive-1073 and changes to the nested page flow returns from a popup window feature... MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_21275_13328900.1141458906662" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_21275_13328900.1141458906662 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline All, I've attached a patch that can be used to resolve the feature change reques= t in BEEHIVE-1073. http://issues.apache.org/jira/browse/BEEHIVE-1073 Some details about the design changes in this patch are below, followed by = a couple of questions for the dev list. Now, when returning from a nested page flow popup window, after executing the action, an ActionForward is created to forward to a servlet rather that writing directly to the response. The forward path could have been to a new framework JSP, however, it was suggested that a servlet will allow us to extend this type of solution to other types of framework generated output. After calling the action, the code path continues through the DefaultActionForwardHandler.doAutoViewRender(). However, rather than writin= g to the response at this stage, it adds the ViewRenderer instance to the request as an attribute, constructs a URI mapped to the XmlHttpRequestServlet, and returns an ActionForward with this URI as the path. Then in the rendering phase when we process this new forward, the XHR servlet gets the ViewRenderer object from the request attribute and writes the framework generated output (JavaScript) to the response. Following the design pattern of the XHR servlet, there's now a new request interceptor (ViewRendererCRI) that handles the forwarded request. It will check to see if the request has the desired extension, then get the ViewRenderer instance from the request and call its renderView() method. Other details... - By default, the URI in the forward is constructed with a ".render" extension for the servlet path. (E.g. "/returnActionViewRenderer.render?handler=3D_netui:ViewRenderer") - The web.xml file of the NetUI web-app that uses the nested page flow popu= p window feature will need to be updated to to include the serlvet mapping. (release notes) <servlet-mapping> <servlet-name>XmlHttpRequestServlet</servlet-name> <url-pattern>*.render</url-pattern> </servlet-mapping> A different extension mapping for this view rendering can also be configure= d via a <context-param> in the web.xml. Something like... <context-param> <param-name>ViewRenderingExtension</param-name> <param-value>myExtension</param-value> </context-param> and <servlet-mapping> <servlet-name>XmlHttpRequestServlet</servlet-name> <url-pattern>*.myExtension</url-pattern> </servlet-mapping> - The ViewRendererCRI has been added to the default beehive-netui-config.xm= l. However, any NetUI web-app that has a beehive-netui-config.xml and uses the nested page flow popup window feature will need to update this configuratio= n file to include the new request interceptor. <request-interceptor> <interceptor-class> org.apache.beehive.netui.tags.internal.ViewRendererCRI </interceptor-class> </request-interceptor> Other thoughts? This design definitely requires some configuration changes for anyone already using this feature in their web-app today. Any additional thoughts/concerns about handling these changes? Also, it was suggested that I use the NameService to store the ViewRenderer instance. It would implement Daryl's INameable interface and the name would be a param in the request. Then the ViewRendererCRI would use the name to retrieve the ViewRenderer instance from the NameService. This follows the same design as the other interceptors, TreeCRI and DivPanelCRI. I didn't us= e the NameService in this patch but if people feel it should be used for consistency or have some other thoughts, let me know and I'll add it in. Ca= n be done easily. Kind regards, Carlin ------=_Part_21275_13328900.1141458906662-- From meghan68@example.com Sun Mar 05 01:50:00 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 96668 invoked from network); 5 Mar 2006 01:49:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Mar 2006 01:49:59 -0000 Received: (qmail 46240 invoked by uid 500); 5 Mar 2006 01:50:45 -0000 Delivered-To: meghan68@example.com Received: (qmail 46223 invoked by uid 500); 5 Mar 2006 01:50: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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 46212 invoked by uid 99); 5 Mar 2006 01:50:45 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Mar 2006 17:50:45 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=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 xproxy.gmail.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Mar 2006 17:50:44 -0800 Received: by xproxy.gmail.com with SMTP id s7so627989wxc for <meghan68@example.com>; Sat, 04 Mar 2006 17:50:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=r1V8vQj6jQ6cwimHK4/zeos5kG3kG/QNC8VDfuIvfpmqTwn9TrYUaBGCt0fPZtTPw2rh9zzd+pw8Xj0xpLRl83PQNkeFFfWUuQPk29g8S1NFve5UiyZaKVKS7hWhrKXV+7/jPOb6U0XFkr7JXL6crZTe2HCcsu9VP2K/JtYPq3k= Received: by 83.161.120.155 with SMTP id o13mr6225366wxc; Sat, 04 Mar 2006 17:50:23 -0800 (PST) Received: by 83.161.120.155 with HTTP; Sat, 4 Mar 2006 17:50:23 -0800 (PST) Message-ID: <meghan68@example.com> Date: Sat, 4 Mar 2006 18:50:23 -0700 From: "Daryl Olander" <meghan68@example.com> To: "Beehive Developers" <meghan68@example.com> Subject: Re: Patch for beehive-1073 and changes to the nested page flow returns from a popup window feature... In-Reply-To: <meghan68@example.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_6743_23333649.1141523423288" References: <meghan68@example.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_6743_23333649.1141523423288 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline +1 for using the name service.... On 3/4/06, Carlin Rogers <meghan68@example.com> wrote: > > All, > > I've attached a patch that can be used to resolve the feature change > request > in BEEHIVE-1073. > http://issues.apache.org/jira/browse/BEEHIVE-1073 > > Some details about the design changes in this patch are below, followed b= y > a > couple of questions for the dev list. > > Now, when returning from a nested page flow popup window, after executing > the action, an ActionForward is created to forward to a servlet rather > that > writing directly to the response. The forward path could have been to a > new > framework JSP, however, it was suggested that a servlet will allow us to > extend this type of solution to other types of framework generated output= . > > After calling the action, the code path continues through the > DefaultActionForwardHandler.doAutoViewRender(). However, rather than > writing > to the response at this stage, it adds the ViewRenderer instance to the > request as an attribute, constructs a URI mapped to the > XmlHttpRequestServlet, and returns an ActionForward with this URI as the > path. Then in the rendering phase when we process this new forward, the > XHR > servlet gets the ViewRenderer object from the request attribute and write= s > the framework generated output (JavaScript) to the response. > > Following the design pattern of the XHR servlet, there's now a new reques= t > interceptor (ViewRendererCRI) that handles the forwarded request. It will > check to see if the request has the desired extension, then get the > ViewRenderer instance from the request and call its renderView() method. > > Other details... > - By default, the URI in the forward is constructed with a ".render" > extension for the servlet path. (E.g. > "/returnActionViewRenderer.render?handler=3D_netui:ViewRenderer") > > - The web.xml file of the NetUI web-app that uses the nested page flow > popup > window feature will need to be updated to to include the serlvet mapping. > (release notes) > > <servlet-mapping> > <servlet-name>XmlHttpRequestServlet</servlet-name> > <url-pattern>*.render</url-pattern> > </servlet-mapping> > > A different extension mapping for this view rendering can also be > configured > via a <context-param> in the web.xml. Something like... > <context-param> > <param-name>ViewRenderingExtension</param-name> > <param-value>myExtension</param-value> > </context-param> > and > <servlet-mapping> > <servlet-name>XmlHttpRequestServlet</servlet-name> > <url-pattern>*.myExtension</url-pattern> > </servlet-mapping> > > - The ViewRendererCRI has been added to the default > beehive-netui-config.xml. > However, any NetUI web-app that has a beehive-netui-config.xml and uses > the > nested page flow popup window feature will need to update this > configuration > file to include the new request interceptor. > <request-interceptor> > <interceptor-class> > org.apache.beehive.netui.tags.internal.ViewRendererCRI > </interceptor-class> > </request-interceptor> > > > Other thoughts? > This design definitely requires some configuration changes for anyone > already using this feature in their web-app today. Any additional > thoughts/concerns about handling these changes? > > Also, it was suggested that I use the NameService to store the > ViewRenderer > instance. It would implement Daryl's INameable interface and the name > would > be a param in the request. Then the ViewRendererCRI would use the name to > retrieve the ViewRenderer instance from the NameService. This follows the > same design as the other interceptors, TreeCRI and DivPanelCRI. I didn't > use > the NameService in this patch but if people feel it should be used for > consistency or have some other thoughts, let me know and I'll add it in. > Can > be done easily. > > Kind regards, > Carlin > > ------=_Part_6743_23333649.1141523423288-- From meghan68@example.com Sun Mar 05 19:38:04 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 69032 invoked from network); 5 Mar 2006 19:38:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Mar 2006 19:38:04 -0000 Received: (qmail 73016 invoked by uid 500); 5 Mar 2006 19:38:50 -0000 Delivered-To: meghan68@example.com Received: (qmail 72989 invoked by uid 500); 5 Mar 2006 19:38: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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 72973 invoked by uid 99); 5 Mar 2006 19:38:49 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Mar 2006 11:38:49 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=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 zproxy.gmail.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Mar 2006 11:38:48 -0800 Received: by zproxy.gmail.com with SMTP id r28so1091241nza for <meghan68@example.com>; Sun, 05 Mar 2006 11:38:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=Ii23KnlEwGA3uFfcCRjLVxoLwB56rMfUZGzQwvViiwkOS3T4SjCBfq9cKGJSHbv4Y0OjT3FhmfxVy+BcyJ4QdEByttF3L1o/x+zcmHKhtW/X1m1pjSnQu0+m73hcN+jWH3WBpujPSUdT3TN2U1psr3SPOJFHu/xtAk1Hal/bJQY= Received: by 83.161.120.155 with SMTP id a18mr6046586nzc; Sun, 05 Mar 2006 11:38:27 -0800 (PST) Received: by 83.161.120.155 with HTTP; Sun, 5 Mar 2006 11:38:27 -0800 (PST) Message-ID: <meghan68@example.com> Date: Sun, 5 Mar 2006 12:38:27 -0700 From: "Carlin Rogers" <meghan68@example.com> To: "Beehive Developers" <meghan68@example.com> Subject: Re: Patch for beehive-1073 and changes to the nested page flow returns from a popup window feature... In-Reply-To: <meghan68@example.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_27172_3669421.1141587507777" 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 ------=_Part_27172_3669421.1141587507777 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Daryl, One question/concern I have about using the NameService. When we are at the point of creating the new ActionForward and want to add the ViewRenderer to the NameService, The only reference to the ViewRenderer is the PageFlowRequestWrapper. In a framework (like a portal) or application that uses a call to PageFlowUtils.strutsLookup(), we return a ActionResult and a= t this point, I think the only reference to the ViewRenderer would be the wea= k reference in the NameService. Wouldn't there be the potential that the ViewRenderer could be garbage-collected before the XHR servlet gets the forwarded request and tries to retrieve the INameable? Thanks, Carlin On 3/4/06, Daryl Olander <meghan68@example.com> wrote: > > +1 for using the name service.... > > On 3/4/06, Carlin Rogers <meghan68@example.com> wrote: > > > > All, > > > > I've attached a patch that can be used to resolve the feature change > > request > > in BEEHIVE-1073. > > http://issues.apache.org/jira/browse/BEEHIVE-1073 > > > > Some details about the design changes in this patch are below, followed > by > > a > > couple of questions for the dev list. > > > > Now, when returning from a nested page flow popup window, after > executing > > the action, an ActionForward is created to forward to a servlet rather > > that > > writing directly to the response. The forward path could have been to a > > new > > framework JSP, however, it was suggested that a servlet will allow us t= o > > extend this type of solution to other types of framework generated > output. > > > > After calling the action, the code path continues through the > > DefaultActionForwardHandler.doAutoViewRender(). However, rather than > > writing > > to the response at this stage, it adds the ViewRenderer instance to the > > request as an attribute, constructs a URI mapped to the > > XmlHttpRequestServlet, and returns an ActionForward with this URI as th= e > > path. Then in the rendering phase when we process this new forward, the > > XHR > > servlet gets the ViewRenderer object from the request attribute and > writes > > the framework generated output (JavaScript) to the response. > > > > Following the design pattern of the XHR servlet, there's now a new > request > > interceptor (ViewRendererCRI) that handles the forwarded request. It > will > > check to see if the request has the desired extension, then get the > > ViewRenderer instance from the request and call its renderView() method= . > > > > Other details... > > - By default, the URI in the forward is constructed with a ".render" > > extension for the servlet path. (E.g. > > "/returnActionViewRenderer.render?handler=3D_netui:ViewRenderer") > > > > - The web.xml file of the NetUI web-app that uses the nested page flow > > popup > > window feature will need to be updated to to include the serlvet > mapping. > > (release notes) > > > > <servlet-mapping> > > <servlet-name>XmlHttpRequestServlet</servlet-name> > > <url-pattern>*.render</url-pattern> > > </servlet-mapping> > > > > A different extension mapping for this view rendering can also be > > configured > > via a <context-param> in the web.xml. Something like... > > <context-param> > > <param-name>ViewRenderingExtension</param-name> > > <param-value>myExtension</param-value> > > </context-param> > > and > > <servlet-mapping> > > <servlet-name>XmlHttpRequestServlet</servlet-name> > > <url-pattern>*.myExtension</url-pattern> > > </servlet-mapping> > > > > - The ViewRendererCRI has been added to the default > > beehive-netui-config.xml. > > However, any NetUI web-app that has a beehive-netui-config.xml and uses > > the > > nested page flow popup window feature will need to update this > > configuration > > file to include the new request interceptor. > > <request-interceptor> > > <interceptor-class> > > org.apache.beehive.netui.tags.internal.ViewRendererCRI > > </interceptor-class> > > </request-interceptor> > > > > > > Other thoughts? > > This design definitely requires some configuration changes for anyone > > already using this feature in their web-app today. Any additional > > thoughts/concerns about handling these changes? > > > > Also, it was suggested that I use the NameService to store the > > ViewRenderer > > instance. It would implement Daryl's INameable interface and the name > > would > > be a param in the request. Then the ViewRendererCRI would use the name > to > > retrieve the ViewRenderer instance from the NameService. This follows > the > > same design as the other interceptors, TreeCRI and DivPanelCRI. I didn'= t > > use > > the NameService in this patch but if people feel it should be used for > > consistency or have some other thoughts, let me know and I'll add it in= . > > Can > > be done easily. > > > > Kind regards, > > Carlin > > > > > > ------=_Part_27172_3669421.1141587507777-- From meghan68@example.com Mon Mar 06 22:35:57 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 14472 invoked from network); 6 Mar 2006 22:35:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 6 Mar 2006 22:35:56 -0000 Received: (qmail 23395 invoked by uid 500); 6 Mar 2006 22:35:56 -0000 Delivered-To: meghan68@example.com Received: (qmail 23326 invoked by uid 500); 6 Mar 2006 22:35:55 -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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 23315 invoked by uid 99); 6 Mar 2006 22:35:55 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2006 14:35:55 -0800 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) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2006 14:35:54 -0800 Received: from ajax (localhost.localdomain [83.161.120.155]) by ajax (Postfix) with ESMTP id B3BA1D49F9 for <meghan68@example.com>; Mon, 6 Mar 2006 22:35:33 +0000 (GMT) Message-ID: <1029004533.1141684533732.JavaMail.jira@ajax> Date: Mon, 6 Mar 2006 22:35:33 +0000 (GMT) From: "Chad Schoettger (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Resolved: (BEEHIVE-996) Compilation error on an extended control bean when callback intf on base ctrl intf and extended crtl intf have same name In-Reply-To: <{{EMAIL+PHONE}}> 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/BEEHIVE-996?page=all ] Chad Schoettger resolved BEEHIVE-996: ------------------------------------- Resolution: Fixed Assign To: Alejandro Ramirez (was: Chad Schoettger) Fixed 3/6/06. > Compilation error on an extended control bean when callback intf on base ctrl intf and extended crtl intf have same name > ------------------------------------------------------------------------------------------------------------------------ > > Key: BEEHIVE-996 > URL: http://issues.apache.org/jira/browse/BEEHIVE-996 > Project: Beehive > Type: Bug > Components: Controls > Versions: V1 > Environment: Win XP > Reporter: Pradeep Bollineni > Assignee: Alejandro Ramirez > > The control bean generated for the control extension has ambiguous reference to Callback interface in the callback listener methods when there is a callback interface extension in the control extension as shown below: > @ControlInterface > interface BaseControl { > @EventSet > public interface Callback { > void method1(); > } > } > @ControlExtension > interface ExtendedControl extends BaseControl { > @EventSet > public interface Callback extends BaseControl.Callback { > void method2(); > } > } > Generated ControlBean listener method: > public class ExtendedControlBean extends BaseControlBean implements ExtendedControl { > public synchronized void removeCallbackListener(Callback listener) > { > CallbackNotifier notifier = (CallbackNotifier)getEventNotifier(Callback.class); //ambiguous reference as there is a Callback in BaseControlBean and ExtendedControl > notifier.removeListener(listener); > } > } > Is there a work around for this other than re-naming the interface in the extended control? -- 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 meghan68@example.com Mon Mar 06 22:35:57 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 14503 invoked from network); 6 Mar 2006 22:35:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 6 Mar 2006 22:35:57 -0000 Received: (qmail 23566 invoked by uid 500); 6 Mar 2006 22:35:57 -0000 Delivered-To: meghan68@example.com Received: (qmail 23541 invoked by uid 500); 6 Mar 2006 22:35:56 -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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 23530 invoked by uid 99); 6 Mar 2006 22:35:56 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2006 14:35:56 -0800 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) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2006 14:35:56 -0800 Received: from ajax (localhost.localdomain [83.161.120.155]) by ajax (Postfix) with ESMTP id ED42FD49FC for <meghan68@example.com>; Mon, 6 Mar 2006 22:35:34 +0000 (GMT) Message-ID: <1902689675.1141684534968.JavaMail.jira@ajax> Date: Mon, 6 Mar 2006 22:35:34 +0000 (GMT) From: "Chad Schoettger (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Assigned: (BEEHIVE-815) Nested controls: cannot initialize a public control field when using a Java security manager 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/BEEHIVE-815?page=all ] Chad Schoettger reassigned BEEHIVE-815: --------------------------------------- Assign To: (was: Chad Schoettger) > Nested controls: cannot initialize a public control field when using a Java security manager > -------------------------------------------------------------------------------------------- > > Key: BEEHIVE-815 > URL: http://issues.apache.org/jira/browse/BEEHIVE-815 > Project: Beehive > Type: Bug > Components: Controls > Versions: v1m1 > Reporter: Rich Feit > Attachments: j815-exceptions.txt, jira815.zip > > This bug involves using a *public* @Control field, which should be possible even if "suppressAccessChecks" is not set in the security policy. > Repro (the easiest way to reproduce this): > - cd to $CATALINA_HOME/bin. > - create a file called mysecurity.policy (and REPLACE my c:/prog/... tomcat/jdk directories with ones of your own): > --- > grant codeBase "file:///c:/prog/jakarta-tomcat-5.0.25/-"{ > permission java.security.AllPermission; > }; > grant codeBase "file:///c:/prog/jdk1.5.0/-"{ > permission java.security.AllPermission; > }; > grant { > permission java.util.PropertyPermission "*", "read"; > permission java.lang.RuntimePermission "accessDeclaredMembers"; > }; > --- > - set the JAVA_OPTS environment variable: > (windows) set JAVA_OPTS=-Djava.security.manager -Djava.security.policy=mysecurity.policy > (linux) export JAVA_OPTS="-Djava.security.manager -Djava.security.policy=mysecurity.policy" > - start tomcat: > (windows) .\startup.bat > (linux) ./startup.sh > - Overlay the attached page flow and controls onto a webapp, and deploy it to the running tomcat. > - Hit the page flow (/usecontrol/Controller.jpf): > EXPECTED: see the message "hello there" in the displayed page. > ACTUAL: a series of exceptions, with this root cause: > Caused by: java.security.AccessControlException: access denied (java.lang.reflect.ReflectPermission suppressAccessChecks) > at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264) > at java.security.AccessController.checkPermission(AccessController.java:427) > at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) > at java.lang.reflect.AccessibleObject.setAccessible(AccessibleObject.java:107) > at usecontrol.ControllerClientInitializer.<clinit>(ControllerClientInitializer.java:21) > ... 85 more -- 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 meghan68@example.com Mon Mar 06 23:06:27 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 33227 invoked from network); 6 Mar 2006 23:06:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 6 Mar 2006 23:06:27 -0000 Received: (qmail 65756 invoked by uid 500); 6 Mar 2006 23:06:24 -0000 Delivered-To: meghan68@example.com Received: (qmail 65675 invoked by uid 500); 6 Mar 2006 23:06:24 -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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 65595 invoked by uid 99); 6 Mar 2006 23:06:24 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2006 15:06:24 -0800 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) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2006 15:06:23 -0800 Received: from ajax (localhost.localdomain [83.161.120.155]) by ajax (Postfix) with ESMTP id 6B6AFD49FE for <meghan68@example.com>; Mon, 6 Mar 2006 23:06:02 +0000 (GMT) Message-ID: <+1-587-343-6921.1141686362437.JavaMail.jira@ajax> Date: Mon, 6 Mar 2006 23:06:02 +0000 (GMT) From: "Carlin Rogers (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Created: (BEEHIVE-1075) NPE in ScopedRequestImpl.registerOuterAttribute() when running without asserts. 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 NPE in ScopedRequestImpl.registerOuterAttribute() when running without asserts. ------------------------------------------------------------------------------- Key: BEEHIVE-1075 URL: http://issues.apache.org/jira/browse/BEEHIVE-1075 Project: Beehive Type: Bug Components: NetUI Versions: V1, 1.0.1 Reporter: Carlin Rogers Assigned to: Carlin Rogers Priority: Minor Fix For: v.next The routine ScopedRequestImpl.registerOuterAttribute() should not be called if the ScopedRequest is constructed such that the attributes of the outer request are visible in the scoped request. There is an assert to check this. However, when the code is run without asserts it will through an NPE. I think it should just log the error and return. -- 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 meghan68@example.com Tue Mar 07 00:45:54 2006 Return-Path: <meghan68@example.com> Delivered-To: meghan68@example.com Received: (qmail 73865 invoked from network); 7 Mar 2006 00:45:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 7 Mar 2006 00:45:54 -0000 Received: (qmail 68504 invoked by uid 500); 7 Mar 2006 00:45:54 -0000 Delivered-To: meghan68@example.com Received: (qmail 68481 invoked by uid 500); 7 Mar 2006 00:45: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: <dev.beehive.apache.org> Reply-To: "Beehive Developers" <meghan68@example.com> Delivered-To: mailing list meghan68@example.com Received: (qmail 68469 invoked by uid 99); 7 Mar 2006 00:45:53 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2006 16:45:53 -0800 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) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2006 16:45:53 -0800 Received: from ajax (localhost.localdomain [83.161.120.155]) by ajax (Postfix) with ESMTP id 4945E6ACA9 for <meghan68@example.com>; Tue, 7 Mar 2006 00:45:32 +0000 (GMT) Message-ID: <311857449.1141692332297.JavaMail.jira@ajax> Date: Tue, 7 Mar 2006 00:45:32 +0000 (GMT) From: "Carlin Rogers (JIRA)" <meghan68@example.com> To: meghan68@example.com Subject: [jira] Resolved: (BEEHIVE-1075) NPE in ScopedRequestImpl.registerOuterAttribute() when running without asserts. In-Reply-To: <+1-587-343-6921.1141686362437.JavaMail.jira@ajax> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked
{'source': 'Apache Software Foundation Public Mail Archives'}