Caught your post on the reddit feed, I work on Jaxer at Aptana and felt I should jump in and comment on this thread.

The Jaxer.Response object you were trying to access is a constructor and is documented as such in the api. So as you discovered what you needed was the instance of the Response, in our system, and a common programming practice, the instance is given a lowercase name.

Next you were running into problem with HTMl and XHTML, this is a mozilla thing, and not really under the control of jaxer, you just need to use the correct doc types/file extensions. When Mozilla serializes a document It will do it in accordance with the doc/file type provided, so it can result in tags being altered, there have been ongoing discussions in the jaxer forums on this. http://forums.aptana.com/viewtopic.php?t=7123

The issue around files being accessible to the outside world, is simply because you placed the files in a location accessible as such. The default jaxer conf files contain directives to provide a way to not serve specific Js content, as unlike something like PHP, you’d generally allow js to be served by Apache. any file referenced with a path containing jaxer-include would not be served in out base config. You can change that to suit you own preferences but that is the exemplar we ship.

One other major issue, which is relatively new, and wasn’t in the earlier beta’s is that in Jaxer you dont need to have an HTML file, you can just as easily serve and process a js only file, this is a much better fit if you want to have some controller logic, as that is more naturally placed in a ‘code’ file rather than a layout file like html.

Now that we have the code stable and shipped, we are working on greatly improving the docs and examples, as this is a ‘brave new world’ and will certainly take you experience into account and make some alterations to make the things you ran into less confusing.

Sorry you found creating an account too much of a burden for filing a ticket for your issues, but as we try to minimize spam on the forums and ticketing system, we do require you to have one for write access to those systems, though that doesn’t prevent you from reading the forums or tickets.

If you do decide to take the plunge and create an account, i look forward to helping you on the forums.

cheers
davey

Your post is great.. Thanks for talk about jsRepeater (i didn’t know about it)..

# Place any files that are to be served only to Jaxer (usually to be included)
# in a folder structure that has /jaxer-include/ somewhere in the hierarchy above them.

# prevents processing by Jaxer before it’s served back to Jaxer JaxerPassThrough on
Order Deny,Allow
# Jaxer will fetch these files directly from the file system, not via Apache
Deny from all #this is the important line..

I’m not sure what the point is of manipulating the DOM server side…I suppose you could make more dynamic templates, or that it could act as a “push” templating model, but it sounds like trouble to me.

For a tool like this to succeed, it will need clear separation of concerns. It will need to be far engineered than this system appears to be.