Return-Path: Delivered-To: apmail-beehive-user-archive@www.apache.org Received: (qmail 47779 invoked from network); 17 Jan 2007 15:33:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Jan 2007 15:33:24 -0000 Received: (qmail 35238 invoked by uid 500); 17 Jan 2007 15:33:30 -0000 Delivered-To: apmail-beehive-user-archive@beehive.apache.org Received: (qmail 35230 invoked by uid 500); 17 Jan 2007 15:33:30 -0000 Mailing-List: contact user-help@beehive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Beehive Users" Delivered-To: mailing list user@beehive.apache.org Received: (qmail 35216 invoked by uid 99); 17 Jan 2007 15:33:30 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jan 2007 07:33:30 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of shammer@bea.com designates 66.248.192.22 as permitted sender) Received: from [66.248.192.22] (HELO usremg02.bea.com) (66.248.192.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jan 2007 07:33:21 -0800 Received: from usremr02.bea.com (mailrelay.bea.com [10.160.29.92]) by usremg02.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id l0HFWxww021123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 17 Jan 2007 07:32:59 -0800 Received: from repbex02.amer.bea.com (repbex02.bea.com [10.160.26.99]) by usremr02.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id l0HFWvJ2002894 for ; Wed, 17 Jan 2007 07:32:57 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Recommended Pattern for Control Call from Beehive JSP? Date: Wed, 17 Jan 2007 07:32:57 -0800 Message-ID: <78F99D8FA7200845947DE3B1121743D90182A8A9@repbex02.amer.bea.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Recommended Pattern for Control Call from Beehive JSP? Thread-Index: Acc6DhAJswS1asAnSpSyEN44HuTpFgAAN1GAAA7AR4Y= References: <288627B7268ACD4FA45342701B7BB0EC010B4584@PRTRRA06-XCS01.telkom.co.za> From: "Scott Hammer" To: "Beehive Users" X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.0.283055, Antispam-Data: 2007.1.2.131432 X-Virus-Checked: Checked by ClamAV on apache.org In the WLP 8.1.x version of the netui-data taglib, there were and tags for making a control metho= d call from a JSP. The Beehive 1.0.x netui-data taglib has neither tag; ho= wever, the documentation seems to hint that it is possible to call a contro= l using the tag. The API doc actually refers to a = "controlId" attribute that does not actually seem to be a part of the tag i= nterface. See: =20 http://beehive.apache.org/docs/1.0.2/netui/apidocs/taglib/beehive.apache.or= g/netui/tags-databinding-1.0/callMethod.html=20 =20 Is it possible to make a call to a custom control (which in turn calls an E= JB control and the Portal Caching framework) from a JSP in a Beehive pagefl= ow? Will the control be executed in a control container so that the EJB co= ntrol actually works?=20=20 =20 If so, could someone provide some sample code for my use case? From the JS= P, I would like to call the getOrganizations() method on a custom control c= alled com.mycustomer.control.ListCacheControl, returning the java.util.List= result in a pageContext variable called "orgs". The result would then be = used as the optionsDataSource for a tag. =20 My incorrect attempts: // ListCacheCont= rol exposed as a public pageFlow attribute - I don't like this Thanks, Scott _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.