I put in a hack to the build so that we can retain wsasadmin. The Mashup Server has its own service to handle DataService interactions in the Mashup Server.
Thanks, Keith. Keith Chapman wrote: > Hi all > > With the integration of DataServices to the Mashup Server we are facing > difficulties in reusing WSAS backend services. WSAS basically assumes > that dataservices will be in a specific folder whereas the Mashup Server > has it on a peruser basis. The work around would be to replace > conflicting WSAS backend services with our own services (Having the save > service names, otherwise we cannot reuse there UI stuff). This is a hack > though, and this requires users to be signed into WSAS. > > I thought of updating the Mashup Servers login service to automatically > log a user into WSAS when ever he signs into the Mashup Server. But this > too has limitations. I cannot do this if a user logs in using infocard > (Cause I don't know the password) and openID in future. > > I propose abandoning wsasadmin so that we have have our own services > with the same serviceNames so that we can reuse the UI. We can still > make use of there backend functionality by extending there classes. > > WDYT? > > Thanks, > Keith. > > _______________________________________________ > Mashup-dev mailing list > [email protected] > http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev > _______________________________________________ Mashup-dev mailing list [email protected] http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
