[MOBY-l] Problem with SAWSDLServlet

[Ha X. Dang]

Hi,

I couldn't get SAWSDLServlet to work. I just followed the instruction at
http://biomoby.open-bio.org/CVS_CONTENT/moby-live/Java/docs/sawsdlServlet.html

It seems to me that bioxml.info is not available for LSID. Does anyone
ever made it work recently or know what happens? Please help. Thanks.

Here is the error message:

===============================

type Exception report

message 

description The server encountered an internal error () that prevented
it from fulfilling this request.

exception 

javax.servlet.ServletException: Servlet execution threw an exception

root cause 

java.lang.NoClassDefFoundError: org/xbill/DNS/SOARecord
	org.xbill.DNS.Cache.addMessage(Cache.java:670)
	org.xbill.DNS.Lookup.lookup(Lookup.java:399)
	org.xbill.DNS.Lookup.resolve(Lookup.java:424)
	org.xbill.DNS.Lookup.run(Lookup.java:441)
	org.biomoby.shared.LSIDResolver.findAuthorityWSDL(LSIDResolver.java:84)
	org.biomoby.shared.LSIDResolver.resolveURL(LSIDResolver.java:128)
	org.biomoby.shared.LSIDResolver.resolveDataURL(LSIDResolver.java:120)
	ca.ucalgary.services.util.WSDLConfig.getLiftingSchemaFromOperation(WSDLConfig.java:464)
	ca.ucalgary.services.util.WSDLConfig.getSecondaryParamRestrictionsFromService(WSDLConfig.java:352)
	ca.ucalgary.services.util.WSDLConfig.getSecondaryParamRestrictions(WSDLConfig.java:289)
	ca.ucalgary.services.util.WSDLConfig.wsdlParam2MobySecondaryParam(WSDLConfig.java:267)
	ca.ucalgary.services.util.WSDLConfig.parseSOAPMessageSpec(WSDLConfig.java:175)
	ca.ucalgary.services.util.WSDLConfig.parseSOAPMessageSpecs(WSDLConfig.java:128)
	ca.ucalgary.services.util.WSDLConfig.parse(WSDLConfig.java:113)
	ca.ucalgary.services.util.WSDLConfig.<init>(WSDLConfig.java:92)
	ca.ucalgary.services.WSDLService.createServiceFromConfig(WSDLService.java:173)
	org.biomoby.service.MobyServlet.doGet(MobyServlet.java:92)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:729)

note The full stack trace of the root cause is available in the Apache
Tomcat/5.5.27 logs.


- Ha