Hi,
I send along a netbeans friendly blank netui project and have also
made netui-samples a bit more netbeans friendly (the mailer deamon
wont allow me to sent it to the list because of its size, though).
Directory structure
are much like jakarta recommendation
(http://jakarta.apache.org/tomcat/tomcat-4.1-doc/appdev/source.html)
I have attached a minimal guide as to the netbeans blank project and
spotted a couple of typos in some jsp inside samples/, the patch is
attached.
Any ideas as to how AJAX is supposed to be implemented for some tags
(from the ground up, use some already available library etc) ?
I am playing a bit with it and would really want to be in synch with
you guys...
Adriano
Eddie O'Neil wrote:
Adriano--
Great! Glad to hear that you've got a "wish list". Feel free to
contribute patches, discuss on the [EMAIL PROTECTED] list, or add such items
to the wiki page:
http://wiki.apache.org/beehive/FrontPage/WishList
Definitely, send along your changes to netui-blank; in general, I
tend to prefer the web application project model that the
samples/petstore uses which is probably similar to your NetBeans setup
and has the src/ directory separated from the URL addressable content.
How did you end up laying out your project? Also, how well did the
Beehive annotation processors integrate with the NetBeans build
system?
Maybe we can just reorganize the netui-blank template in the
distribution to be more IDE friendly. :)
I agree that it'd be a good idea to have a "contrib" section in SVN
where we can put things that are released out-of-band with the rest of
Beehive. The Tomcat container adapter might be an example of
something like this. We'll probably tackle this once the 1.0 has
shipped.
Eddie
On 8/23/05, Glauber Adriano Reis <[EMAIL PROTECTED]> wrote:
Ok, thanks for the advice. We, at work (using Weblogic Workshop), also
have a "wish list" of features that would be cool seeing in Beehive
such as having AJAXified valiadation tightly integrated with netui
tags.
I know it is low priority fetures but...
I 've built Beehive from svn and will take a look at "Beehive -
Unassigned".
Would it be possible to have a directory "contrib" under samples? As a
netbeans users I'd like to have my Beehive projects using the full
power
of netbeans Web Application and so I did last weekend. I made some
small
changes to "netui-blank" in order to make the directory structure a bit
more as jakarta recommends and ant script a bit "netbeans" friendly
since I wanted to use all netbeans Web App ant targets that comes for
free. So a small nebeans-based sample beehive application would be
cool.
Adriano
Rich Feit wrote:
And... if you're simply looking for a way to contribute, without
necessarily having a clear agenda for what you'd like to change, you
can take a crack at an unassigned issue:
- Create an account at ASF JIRA (issue tracking system):
http://issues.apache.org/jira
- When logged in, click the Filters link in the upper-righthand
corner.
- Choose "Beehive - Unassigned".
Page Flow issues are in the "NetUI" component. If you do find one
you're interested in, feel free to discuss it on this list!
Rich
Eddie O'Neil wrote:
And, if you're interested in getting Beehive building from SVN,
check out this wiki page:
http://wiki.apache.org/beehive/For_Beehive_Developers
Eddie
On 8/19/05, Kenneth Tam <[EMAIL PROTECTED]> wrote:
Hi Adriano,
A good place to start is to think about what you'd like to change or
add in Beehive based on your experience building applications
with it
-- for example, is there a feature that doesn't quite work the
way you
think it should, or that is missing entirely? Then you can
engage the
rest of the developers on this list to talk about what it might mean
to make that change.
On 8/19/05, Glauber Adriano Reis <[EMAIL PROTECTED]> wrote:
Hello,
I've been working with Weblogic Workshop and got amazed by Page
Flows
features. I'm quite impressive with Beehive project as well.
I'd really like to get involved to Beehive but don' t know
where to
start from. I find Page Flows and Controls really interesting,
is it a
good starting point?
Adriano
------------------------------------------------------------------------
Index: forrest/release/src/documentation/content/xdocs/site.xml
===================================================================
--- forrest/release/src/documentation/content/xdocs/site.xml (revision 264071)
+++ forrest/release/src/documentation/content/xdocs/site.xml (working copy)
@@ -89,6 +89,7 @@
<control-blank label="Project: Control"
href="controls/sampleControlsBlank.html"/>
<wsm-blank label="Project: Web Service"
href="wsm/sample_wsm-blank.html"/>
<ws-control-blank label="Project: Web Service Control"
href="system-controls/webservices/sample-ws-control-blank.html" />
+ <netui-nb label="Project:NetBeans Page Flow and Control"
href="pageflow/sample_netui-nb.html"/>
</samples>
<reference label="Reference">
<infra label="Build Tools">
Index: forrest/release/src/documentation/content/xdocs/samples/index.xml
===================================================================
--- forrest/release/src/documentation/content/xdocs/samples/index.xml
(revision 264071)
+++ forrest/release/src/documentation/content/xdocs/samples/index.xml (working
copy)
@@ -40,6 +40,9 @@
<li>
<a href="site:ws-control-blank">Project: Web Service Control</a>
</li>
+ <li>
+ <a href="site:netui-nb">Project: NetBeans Page Flow and
Control</a>
+ </li>
</ul>
</body>
<footer>
------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN"
"http://forrest.apache.org/dtd/document-v20.dtd">
<document>
<header>
<title>NetBeans 4.1 Page Flow and Control Blank Project </title>
</header>
<body>
<section id="intro">
<title>Introduction</title>
<p>Use the NetBeans Project sample (located at
<code><BeehiveRoot>/samples/nb-netui-blank</code>)
as a starting point for building your own Page Flow and Control applications inside NetBeans 4.1
IDE.</p>
<note><BeehiveRoot> refers to the top-level directory of your Beehive
installation.
A typical value for <BeehiveRoot> would be
<code>/apache/apache-beehive-1.0</code>. </note>
<p>
Before opening the exemple inside NetBeans IDE 4.1, you need to set a library
comprising all Beehive runtime
dependencies by going to Tools > Library Manager and adding a new library named
<code>Beehive</code> . After that, you can add the runtime dependencies by clicking
Add JAR/Folder button in the Classpath tab.
<br/>
<strong>Runtime dependencies:</strong>
</p>
<ul>
<li><BeehiveRoot>/lib/common/apache-xbean.jar</li>
<li><BeehiveRoot>/lib/common/log4j-1.2.8.jar</li>
<li><BeehiveRoot>/lib/common/velocity-1.4.jar</li>
<li><BeehiveRoot>/lib/common/commons-codec-1.3.jar</li>
<li><BeehiveRoot>/lib/common/velocity-dep-1.4.jar</li>
<li><BeehiveRoot>/lib/common/commons-logging-1.0.4.jar</li>
<li><BeehiveRoot>/lib/common/commons-discovery-0.2.jar</li>
<li><BeehiveRoot>/lib/common/jsr173_1.0_api.jar</li>
<li><BeehiveRoot>/lib/controls/beehive-controls.jar</li>
<li><BeehiveRoot>/lib/netui/beehive-netui-core.jar</li>
<li><BeehiveRoot>/lib/netui/beehive-netui-tags.jar</li>
<li><BeehiveRoot>/lib/netui/commons-beanutils.jar</li>
<li><BeehiveRoot>/lib/netui/commons-collections.jar</li>
<li><BeehiveRoot>/lib/netui/commons-digester.jar</li>
<li><BeehiveRoot>/lib/netui/commons-el.jar</li>
<li><BeehiveRoot>/lib/netui/commons-fileupload.jar</li>
<li><BeehiveRoot>/lib/netui/commons-validator.jar</li>
<li><BeehiveRoot>/lib/netui/jakarta-oro.jar</li>
<li><BeehiveRoot>/lib/netui/jstl.jar</li>
<li><BeehiveRoot>/lib/netui/standard.jar</li>
<li><BeehiveRoot>/lib/netui/struts.jar</li>
</ul>
<p>
The template contains everything needed in a basic Page Flow and Control
application </p>
</section>
<section id="using">
<title>Using NetBeans 4.1 Page Flow and Control Blank Project</title>
<p>The following instruction assume that you have completed all of
required and optional steps in the Beehive set up
procedure at
<a href="site:../setup">Installation and
Setup</a>.</p>
<p>To use the sample, follow these steps:</p>
<section id="copy_rename">
<title>Copy the Sample Folder</title>
<p>Copy the folder
<code><BeehiveRoot>/samples/nb</code>
to your
NetBeans development directory. </p>
<p>Below we assume that you have copied <code>nb</code> into the
folder
<strong><code>/myDevelopmentDirectory</code></strong>.</p>
<source
xml:space="preserve">/myDevelopmentDirectory/nb-netui-blank</source>
<source
xml:space="preserve">/myDevelopmentDirectory/myWebApplication</source>
</section>
<section id="edit_properties_file">
<title>Edit the <code>build.properties</code> File</title>
<p>In this section you will edit the <code>build.properties</code>
file--the file
that sets the build-related properties for your
web application.</p>
<p>Open the file <code>/myDevelopmentDirectory/nb/build.properties</code>
in a text editor.</p>
<p>Edit the <code>beehive.home</code> property so that it points to the
top-level folder of your beehive
installation.
</p>
<p> For example, if you beehive installation
resides at <code>/apache/apache-beehive-1.0</code>,
then your <code>build.properties</code> file
would appear as follows.</p>
<p><strong>Note:</strong> the value of <code><SomeContext></code>
will determine the
app's URL address.</p>
<source
xml:space="preserve">beehive.home=<strong>/apache/apache-beehive-1.0</strong>
</source>
<note>Windows users must use forwardslashes (/) not backslashes (\) in the
<code>build.properties</code> file.</note>
</section>
<section id="build">
<title>Building and Deploying the Project</title>
<p>From inside the IDE, you can build and deploy the project to the bundled
Tomcat servlet container as you do with any other NetBeans Web Application Project.
</p>
<note>If you have set this project as the <code>Main Project</code> you can build it by simply pressing
<code>Shift-F11</code> (clean and build) and <code>F6</code> to run it inside the bundled Tomcat
servlet container.</note>
</section>
</section>
</body>
<footer>
<legal>Java, J2EE, and JCP are trademarks or registered trademarks of
Sun Microsystems, Inc. in the United States and other
countries.<br/> © 2004, Apache Software Foundation
</legal>
</footer>
</document>
------------------------------------------------------------------------
Index: netui-samples/ui/datagrid/masterdetail/Controller.jpf
===================================================================
--- netui-samples/ui/datagrid/masterdetail/Controller.jpf (revision 264077)
+++ netui-samples/ui/datagrid/masterdetail/Controller.jpf (working copy)
@@ -24,7 +24,7 @@
/**
*/
@Jpf.Controller(forwards={
- @Jpf.Forward(name="index", path="matser.jsp"),
+ @Jpf.Forward(name="index", path="master.jsp"),
@Jpf.Forward(name="detail", path="detail.jsp")
})
public class Controller
Index: netui-samples/ui/select/repeatingSelectWithOptionBody.jsp
===================================================================
--- netui-samples/ui/select/repeatingSelectWithOptionBody.jsp (revision 264077)
+++ netui-samples/ui/select/repeatingSelectWithOptionBody.jsp (working copy)
@@ -32,7 +32,7 @@
<br/>
<br/>
<netui:select dataSource="actionForm.name" optionsDataSource="${pageInput.petList}"
repeater="true">
- <netui:selectOption value="${container.item.petID}"
repeatingType="option">
+ <netui:selectOption value="${container.item.petId}"
repeatingType="option">
<netui:content value="${container.item.name}"/>
</netui:selectOption>
</netui:select>
@@ -42,4 +42,5 @@
</netui:form>
<br/>
</netui-template:section>
-</netui-template:template>
\ No newline at end of file
+</netui-template:template>
+
Index: netui-samples/ui/pageinput/index.jsp
===================================================================
--- netui-samples/ui/pageinput/index.jsp (revision 264077)
+++ netui-samples/ui/pageinput/index.jsp (working copy)
@@ -29,7 +29,7 @@
<br/>
<table>
<tr><td colspan="2"><b>Pet Details</b></td></tr>
- <tr><td>Identifier:</td><td>${pageInput.pet.petID}</td></tr>
+ <tr><td>Identifier:</td><td>${pageInput.pet.petId}</td></tr>
<tr><td>Name:</td><td>${pageInput.pet.name}</td></tr>
<tr><td>Price:</td><td>${pageInput.pet.price}</td></tr>
<tr><td>Description:</td><td>${pageInput.pet.description}</td></tr>
@@ -43,4 +43,5 @@
that <i>does</i> provide the required page input.
<br/>
</netui-template:section>
-</netui-template:template>
\ No newline at end of file
+</netui-template:template>
+