[wsabi4axis-users] Questions on WSABI 0.6

[Hewitt, C. <Chr...@td...>]

Hi,

I've been testing WSABI for a few days, and seem to have everything =
configured an running.

There are a few issues that I have come across, and would like to know =
if they are problems at my end, or are to be handled in a future WSABI =
release.

1)
The Health Index value is always 0.  I noticed this is the case in the =
demo as well.

2)
When viewing the handlers for a service, their Name (QName) is of the =
format NO_NAME_####.  This occurs whenever a handler is configured for a =
specific service via <handler type=3D"someName" />, where someName is =
the name of a handler already defined in the main body of =
server-config.wsdd. =20
Perhaps for this case, the name and type attributes could be obtained =
referencing the main handler definition.

3)
WSABI has problems using my Oracle database, unless I disable the =
constraint on the PERF_INDEX_DATAPOINT table.

4)
For cases where WSABI is accessed via http://<host>/wsabi4axis/..., I =
got 404 errors when accessing audit details.  This was because the hard =
link "/monitor/audit/log/detail.do..." is used in about 4 places in the =
code. In other words, the browser tries to access =
http://<host>/monitor/audit/log/detail.do.. without the /wsabi4axis/ =
part.
I changed the paths in the code to be relative to the current location =
("log/detail.do..." and "detail.do...") and all is good.

5)
Configuration changes such as allowedMethods do not seem to get saved to =
server-config.wsdd.  They only remain in-memory or some temporary =
location.  If the app server is restarted, the changes are back to how =
they were before.

6)
WSABI is great.  I would really like to see this tool grow.

Thanks.

Chris Hewitt
TD Securities - Technology Solutions
Email: chr...@td...