beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Johnson (JIRA)" <>
Subject [jira] Closed: (BEEHIVE-699) wsm-employee problems
Date Tue, 15 Nov 2005 00:14:28 GMT
     [ ]
Jeremiah Johnson closed BEEHIVE-699:

    Assign To: Jeremiah Johnson

The wsm-employee Web service now compiles.  It doesn't do anything when deployed, but it compiles

Verified in dist build from SVN 344258.

> wsm-employee problems
> ---------------------
>          Key: BEEHIVE-699
>          URL:
>      Project: Beehive
>         Type: Bug
>   Components: Samples
>     Versions: v1m1
>  Environment: Beehive Dist 20050510
>     Reporter: Jeremiah Johnson
>     Assignee: Jeremiah Johnson
>      Fix For: 1.1

> A decision will be made with BEEHIVE-661 whether wsm-employee should be part of the distribution
or not.  It wsm-employee does become part of the distribution, then it needs to be changed.
 This bug is to make sure that changes to wsm-employee happen without it getting into the
dist just because it compiles.
> wsm-employee won't compile as it is - not on Unix, anyway.  Just to get it to compile,
wsm-employee/WEB-INF/build.xml needs the following changes: web.inf.dir needs to be WEB-INF
rather than web-inf; the taskdef for apt needs to use classpath ${beehive.home}/lib/controls/beehive-controls.jar
rather than lib/beehive-controls.jar; classpathref needs to be lib.path rather than jars;
and the line with derby_46005.jar needs to be removed.
> The EmployeeDBControl.jcx uses the controls-db control, but I think that should be changed
over to use the jdbc-control rather than the sample.  The two reasons for that are 1) jdbc-control
could benefit from sample customers and 2) the controls-db only supports jndiName.  Pervious
discussions about using JNDI in the samples has resulted in the preference of using the driver
rather than JNDI.

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