beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eddie O'Neil (JIRA)" <beehive-...@incubator.apache.org>
Subject [jira] Updated: (BEEHIVE-699) wsm-employee problems
Date Fri, 13 May 2005 16:20:07 GMT
     [ http://issues.apache.org/jira/browse/BEEHIVE-699?page=all ]

Eddie O'Neil updated BEEHIVE-699:
---------------------------------

    Fix Version: TBD
                     (was: V1)

At this point, we're not going to ship the employeeWS samples with the Beehive release.  Postponing
to TBD.

Squawk if there are any questions.

> wsm-employee problems
> ---------------------
>
>          Key: BEEHIVE-699
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-699
>      Project: Beehive
>         Type: Bug
>   Components: Samples
>     Versions: V1
>  Environment: Beehive Dist 20050510
>     Reporter: Jeremiah Johnson
>      Fix For: TBD

>
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message