Raman, You caught two issues here.
1) The psml ajaxapi code dies (NPE) when a PortletDefinition cannot be retrieved. This has been fixed and checked-in. 2) The maven-1 j2-admin dependencies fail to include the spring-support-2.0.jar. This has been fixed and checked-in. Thanks for the info. Steve -----Original Message----- From: Tallamraju, Raman [mailto:[EMAIL PROTECTED] Sent: Friday, December 01, 2006 9:32 AM To: Jetspeed Developers List Subject: RE: Ajax pipeline broken? BTW, here's what I see in the Dojo debug window: FATAL exception raised: PageContentListenerCreateWidget error url: http://localhost:8080/jetspeed/ajaxapi type: error error: XMLHttpTransport.watchInFlight Error: TypeError: pageElement has no properties DEBUG: XMLHttpTransport error callback failed: Error: PageContentListenerCreateWidget error url: http://localhost:8080/jetspeed/ajaxapi type: error error: XMLHttpTransport.watchInFlight Error: TypeError: pageElement has no properties I believe the watchInFlight error above usually indicates that the javascript callback function being called by DOJO is throwing an exception. The above error is coming from line 558 in BrowserIO.js. HTH, Raman -----Original Message----- From: Tallamraju, Raman Sent: Friday, December 01, 2006 10:59 AM To: Jetspeed Developers List Subject: Ajax pipeline broken? Hi All, I've been monitoring the desktop pipeline (I know this is under development and not complete) and when I built the latest jetspeed code today to check out the changes, I found the desktop pipeline to be broken. Digging in a little more, I see that the call to http://localhost:8080/jetspeed/ajaxapi which usually returns the default page psml in an XML format now returns: <js> <status>failure</status> <action>getpage</action> <reason>$reason</reason> <id>unknown</id> </js> I'm wondering - if the ajax pipeline is broken? You probably know this already - but thought I'd flag it anyways. The desktop pipeline was showing all the demo portlets till a couple days ago (I believe Tuesday is when I built latest code last). Thanks, Raman --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
