Hi,

I've come across a couple of issues while using registry checkin-client that
is shipped with GREG 3.6.0 with DSS 2.5.1. So I would greatly appreciate any
help on getting them fixed.

*The first issue arises as the script (checkin-client.sh) refers to the
library location CARBON_HOME/lib/core/* but there's no such directory named
"core" can be found in DSS_2.5.1_HOME/lib. Then I've compared DSS 2.5.1 with
2.6.0 so there this seems to have been fixed for the latter version and the
check-in client (shipped with GREG 4.0.0) works fine without any problem.
(This might actually be some issue related to DSS 2.5.1)

*The second issue pops out as it refers to some invalid location for the
log4j.properties file. (I believe, this has also been fixed in the latest
GREG version)

However, the registry dump gets created with DSS 2.5.1 even when those
issues are present. But I had to change the location of the log4j.properties
file and commented out the following snippet in the attached
checkin-client.sh in order to get rid of them.

#if [ -n "`ls -A $CARBON_HOME/lib/core/WEB-INF/lib`" ]
#then
#    for f in `ls $CARBON_HOME/lib/core/WEB-INF/lib/*.jar`
#    do
#      CHECKINCLIENT_CLASSPATH=$CHECKINCLIENT_CLASSPATH:$f
#    done
#fi

Is this approach correct? (or else, are those artifacts located
in CARBON_HOME/lib/core/WEB-INF/lib/ actually used in the checkin-checkout
process?)


Cheers,
-- 
PrabathA
<http://harshana05.blogspot.com/>

Attachment: checkin-client.sh
Description: Bourne shell script

_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to