[cddlm] A new endpoint!
Steve Loughran
steve_loughran at hpl.hp.com
Fri Apr 28 15:51:03 CDT 2006
I am pleased to announce the availability of the HP CDDLM endpoint,
public beta
release
The URL for the portal is :-
http://deployapi.iseran.com:8080/alpine/portal/
It is visible through the (three) firewalls, and has been tested remotely.
A GET will return a short note confirming the endpoint's existence. Make
sure
you have the trailing / as the servlet is unforgiving. If the connection
is refused, the endpoint is probably down.
Notes
-this is a new SOAP stack with its own WSA and WSRF implementation. It only
implements the subset we need, and those are not adequately interop
tested.
please mail your results to the group or direct to me.
-deployment is not working. I will find out why next week, but will then
have to actually implement security on the endpoint before deploying a
fixed
version
-System:addFile is not finished, and when it is it will initially only
support
inline (base 64) content, not attachments. MTOM Is not on the todo list.
-WS-Notification has not even begun; I dont even implement the
properties that
list supported topics. Frankly, I'm not overwhelmingly motivated to
implement
WS-N.
-It's hosted on a laptop on the WLAN somewhere in my house. It needs more
memory. Please be gentle with it :)
Monday in the UK is a holiday (May 1st, Socialist Unity Day!), so there
is no
likelihood of any changes to the stack being made before Tuesday. I'll field
basic interop problems first (namespaces, WSA headers, SOAPAction), then
worry
about
-better fault reporting
-automating a checkout, rebuild and redeploy early every morning.
-testing Alpine's WSA impl. against the .NET 2.0 endpoints
-making the server-side logs public by logging to log4j's HTML logger and
serving those pages up somewhere.
-have the server host the deployapi tests for our client and run them
against
all public stacks, again serving the data up for browsing.
Clearly not all of these can be achieved in the finite time before
GGF17, but we
should be able to make progress along both the interop and functionality
axes. Now if you'll excuse me, I have an extended weekend to attend to.
Steve
More information about the cddlm-wg
mailing list