Mailing-List: contact beehive-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Developers" <beehive-dev@incubator.apache.org>
Message-ID: <840809544.1116966716125.JavaMail.jira@ajax.apache.org>
Date: Tue, 24 May 2005 22:31:56 +0200 (CEST)
From: "Krista Baker (JIRA)" <beehive-dev@incubator.apache.org>
To: beehive-dev@incubator.apache.org
Subject: [jira] Updated: (BEEHIVE-764) Website has minor typos and some other
 things
In-Reply-To: <1401823324.1116966715083.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/BEEHIVE-764?page=all ]

Krista Baker updated BEEHIVE-764:
---------------------------------

    Attachment: J764.txt

> Website has minor typos and some other things
> ---------------------------------------------
>
>          Key: BEEHIVE-764
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-764
>      Project: Beehive
>         Type: Bug
>   Components: Documentation
>     Versions: V1
>     Reporter: Krista Baker
>     Assignee: Steve Hanson
>     Priority: Minor
>      Fix For: TBD
>  Attachments: J764.txt
>
> I went through the website and noted that there were some typos and also in the pageFlow databinding documentation that there were some outstanding issues which did not have the correct databinding information.
> I will attach a patch for the items that I have found and my attempts to fix them.
> The following items are still outstanding/are not included in the attached patch:
> /trunk/docs/forrest/src/documentation/content/xdocs/pageflow/pageflow_building.xml
>   This file still references the old way of building, using webappRuntimeCore.xml, which I replaced with beehive-runtime, however, under the heading: Running Ant, the reference to buildWebapp.xml still exists.  This should be updated by having the user copy from the samples or by including an instructional item on how to create a build file.  Currently, the user without fishing around quite a bit will not be able to build thier web app.
> /trunk/docs/forrest/src/documentation/content/xdocs/system-controls/jdbc/jdbcControlDevGuide.xml
> Jdbc stuff: POINTBASE Example: The following table lists the relationships between database types and Java types for the PointBase Version 4.4 database, which is installed with WebLogic Server.
>   Should we leave off the "which is installed with???"
> /trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsContainment.xml
> [todo]'s and to be completed:
>   Nesting/Composition
>   Property Management/Access
>   Contextual Services
>   Resource Management
>   State Management
>   External Event Dispatch
> /trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsProgramming.xml
>   [todo][Issue: there is not a declarative..... (I commented out the [todo] item but left the [Issue:].)
> /trunk/docs/forrest/src/documentation/content/xdocs/wsm/wsm_JWSFiles.xml
> [todo]'s and to be completed:
>   @WebService: SOAP document generated by this web service will reference...[todo]
>   @WebMethod: ... [todo]
>   Separating the Public and Implementation Names of Methods and Parameters, last line....Changing the method invoked...[todo: doable?] (commented out in patch)
>   @WebResult
>   @SOAPBinding
>   @SecurityIdentity
>   @SecurityRoles
>   @SOAPMessageHandlers
> /trunk/docs/forrest/src/documentation/content/xdocs/wsm/annotations/wsm_annotations.xml
>   None of the web service annotation links work

-- 
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