[ http://wso2.org/jira/browse/MASHUP-498?page=comments#action_15132 ] Jonathan Marsh commented on MASHUP-498: ---------------------------------------
Yes, that is the explicit behavior (I can remove the "print" statements if we want). When caching I do a "try" to read the cache and if I get a fault back I create a new cache. That's where the 'No XML' errors come from. Not sure how or whether to suppress them. For now I'm happy calling this "by design." > WARINING on nthe console when digit2image is accessed > ----------------------------------------------------- > > Key: MASHUP-498 > URL: http://wso2.org/jira/browse/MASHUP-498 > Project: WSO2 Mashup Server > Issue Type: Bug > Components: Samples > Affects Versions: 0.3 > Environment: WinXP, JDK1.5, IE7 > Reporter: Yumani Ranaweera > Assigned To: Keith Godwin Chapman > Fix For: 1.0 > > > Steps: > ------- > 1. Login to Mashup server ui as admin > 2. access digit2image service > Steps: > ------- > The warining shown below appears. > WARN [2008-01-07 11:35:00,937] triggerActionNotSupportedFault: > messageContext: [MessageContext: > logID=urn:uuid:9CABD1BE59538283881199684101821] prob > lemAction: > http://services.mashup.wso2.org/storexml/ServiceInterface/storeRequest > java.lang.NullPointerException: nulljava.lang.NullPointerException: null -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://wso2.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ Mashup-dev mailing list [email protected] http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
