db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stan Bradbury (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-547) Update and Name changes to article on using Derby w/ JPetStore deployed on WebSperhe
Date Wed, 31 Aug 2005 03:09:05 GMT
     [ http://issues.apache.org/jira/browse/DERBY-547?page=all ]

Stan Bradbury updated DERBY-547:

    Attachment: WebSphereUpdate.zip

See description in issue:  Updated XML text and renamed ZIPFILE

> Update and Name changes to article on using Derby w/ JPetStore deployed on WebSperhe
> ------------------------------------------------------------------------------------
>          Key: DERBY-547
>          URL: http://issues.apache.org/jira/browse/DERBY-547
>      Project: Derby
>         Type: Task
>   Components: Web Site
>  Environment: Forrest
>     Reporter: Stan Bradbury
>     Assignee: Jean T. Anderson
>  Attachments: WebSphereUpdate.zip
> Updated integration article with standardized filenames reflecting the application name
and the Server environment documented.  
> Zipfile containing updated / renamed files:  WebSphereUpdate.zip
> This has been staged on beefy and can be viewed via the following URL:
>        http://beefy.usca.ibm.com:8000/derby-stan/JPetStoreWebSphere.html
> NOTE:  the file JPetStoreWebSphere.xml must replace the existing JPetStoreDerby.html
file.  All links the the new ZIPFILE name have been updated and the title has been changed.
 The new title to be reflected in all index / link files is:
>    "Using Apache Derby with iBATIS JPetStore 4 on the WebSphere Server"
> The contents of the ZIPFILE have not changed so the file can be renamed OR it can be
replaces with the renamed file in  WebSphereUpdate.zip
> The names have changed as follows:
> JPetStoreDerby.html          to      JPetStoreWebSphere.xml  - the article w/ changes
> Derby-JPetStore.zip        to         JPetStoreAPP4WebSphere.zip  - deployment files
and database (this file has only been renamed)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message