[mashup-dev] ScraperService or ScraperHostObject?

[thilina at wso2.com]

Small note:
>
> We cannot have both of these implementations too (Unless we have saxon
> in the global classpath). They cant coexist together cause the first
> requires webharvest  to be on the global classpath and the second method
> requires it to be inside the lib of the service.
They can exist.. IIRC both of them were in working condition in the 0.1
release. Both will work if you put Saxon in the global classpath.

But in the 0.1 release we had Saxon only inside the lib of the service.
Not having Saxon in the classpath was the reason for not being able to do
XPath using the host object.

I prefer to have the hosted service with a custom written js stub that can
be imported or else hiding the service and then host object redirecting
the calls to the service. But IMHO second of the above  does not seems to
be an elegent solution.

thanks,
Thilina
>
> Are we going to decide to use one of these?
>
> What do you guys think?
>
> Thanks,
> Keith.
>
> _______________________________________________
> Mashup-dev mailing list
> Mashup-dev at wso2.org
> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
>