headers
Philip Weaver | 1 Dec 02:02
Picon

Re: Server.properties - webPort

Nice catch Kris. The only place I had noticed to change it is in start.sh - so thanks for posting this. I hope somebody will edit the docs.

A fellow Helma user,
Philip

On Nov 30, 2007 1:03 AM, Kris Leite < kleite <at> imcsoftware.com> wrote:
Oops I also noticed that the ajp13Port, rmiPort, xmlrpcPort could also
be put into the server.properties file.  I have not tested to make sure
that they work but it looks like they should since the webPort property
does.

Thanks,
Kris

Kris Leite wrote:
> I just found out that the Helma web server port number can be set in
> the server.properties file using the property name of "webPort'.  It
> might be helpful if that was documented in the Servers and Application
> Properties page.
>
> Thanks,
> Kris
>
>
_______________________________________________
Helma-user mailing list
Helma-user <at> helma.org
http://helma.org/mailman/listinfo/helma-user

_______________________________________________
Helma-user mailing list
Helma-user <at> helma.org
http://helma.org/mailman/listinfo/helma-user
Permalink | Reply | 1 comment |
headers
Philip Weaver | 1 Dec 07:41
Picon

Editability of the Gibo Site

The Gobi site does not appear to be editable for me. I think it's pretty silly that Gobi is a wiki-ish tool however the Gobi site is not editable by new users to enhance the documentation. (it seems). Can someone acknowledge this or fix this? Gobi rules! (Yes, I am cross-posting this.:-p  )

Thanks,
Philip

_______________________________________________
Helma-user mailing list
Helma-user <at> helma.org
http://helma.org/mailman/listinfo/helma-user
Permalink | Reply | 0 comments |
headers
Joshua Paine | 2 Dec 01:01

getOrderedView() cached, child updates not seen

Using the built-in object DB, the results of getOrderedView seem to get 
cached such that if I update a child and change the property on which 
I'm ordering subsequent calls to getOrderedView return the same as 
before the update. It *does* update correctly when a new child is 
attached, however.

It turns out that calling .invalidate() on the collection nukes the 
cached view, too, so getOrderedView works again. Is this correct 
behavior, such that I should call this._parent.invalidate() in any code 
that updates an object, or is it a bug?

-Joshua
Permalink | Reply | 0 comments |
headers
Kris Leite | 3 Dec 00:58

Re: Server.properties - webPort

Hi Philip,

Thank you. You are welcome
Kris

Philip Weaver wrote:
Nice catch Kris. The only place I had noticed to change it is in start.sh - so thanks for posting this. I hope somebody will edit the docs.

A fellow Helma user,
Philip

On Nov 30, 2007 1:03 AM, Kris Leite < kleite <at> imcsoftware.com> wrote:
Oops I also noticed that the ajp13Port, rmiPort, xmlrpcPort could also
be put into the server.properties file.  I have not tested to make sure
that they work but it looks like they should since the webPort property
does.

Thanks,
Kris

Kris Leite wrote:
> I just found out that the Helma web server port number can be set in
> the server.properties file using the property name of "webPort'.  It
> might be helpful if that was documented in the Servers and Application
> Properties page.
>
> Thanks,
> Kris
>
>
_______________________________________________
Helma-user mailing list
Helma-user <at> helma.org
http://helma.org/mailman/listinfo/helma-user

_______________________________________________ Helma-user mailing list Helma-user <at> helma.org http://helma.org/mailman/listinfo/helma-user 
_______________________________________________
Helma-user mailing list
Helma-user <at> helma.org
http://helma.org/mailman/listinfo/helma-user
Permalink | Reply | 0 comments |
headers
Philip Weaver | 3 Dec 09:20
Picon

Additional Helma Documentation

I just found some additional Helma documentation online and I'm just sharing the link:

http://michi.knallgrau.at/helma-documentation/helma-documentation.html

Philip

_______________________________________________
Helma-user mailing list
Helma-user <at> helma.org
http://helma.org/mailman/listinfo/helma-user
Permalink | Reply | 0 comments |
headers
Chris Zumbrunn | 6 Dec 08:20
Gravatar

Re: Server.properties - webPort


On Nov 30, 2007, at 8:03 , Kris Leite wrote:

> Oops I also noticed that the ajp13Port, rmiPort, xmlrpcPort could also
> be put into the server.properties file.  I have not tested to make  
> sure
> that they work but it looks like they should since the webPort  
> property
> does.

I fixed the docs to include ajp13Port, rmiPort, xmlrpcPort and webPort  
as possible server.properties and added cron, which was also missing,  
to the list for app.properties.

Chris
Permalink | Reply | 1 comment |
headers
Chris Zumbrunn | 6 Dec 08:22
Gravatar

Re: Server.properties - webPort


On Dec 6, 2007, at 8:20 , Chris Zumbrunn wrote:

> On Nov 30, 2007, at 8:03 , Kris Leite wrote:
>
>> Oops I also noticed that the ajp13Port, rmiPort, xmlrpcPort could  
>> also
>> be put into the server.properties file.  I have not tested to make
>> sure
>> that they work but it looks like they should since the webPort
>> property
>> does.
>
> I fixed the docs to include ajp13Port, rmiPort, xmlrpcPort and webPort
> as possible server.properties and added cron, which was also missing,
> to the list for app.properties.

http://helma.org/docs/guide/properties/listall/

Chris
Permalink | Reply | 0 comments |
headers
Michael Platzer | 7 Dec 12:23
Picon

modify response buffer

Hi list,

I would like to overwrite the response buffer with a complete new string 
within onResponse. As has been suggested here [1], i should simply call 
res.reset. But this also reset all response headers, that i've already 
set. Is there a simple way to preserve them?

Currently I write sthg like:
   var contentType = res.contentType;
   var charset = res.charset;
   var cache = res.cache;
   // FIXME: I need to preserve all existing headers
   // in particular cookies that are being set
   res.reset();
   res.contentType = contentType;
   res.charset = charset;
   res.cache = cache;
   res.write(str);

A method like res.setBuffer (like [2]) would come in handy for such a task.

greets,
  michi

[1] http://helma.org/pipermail/helma-dev/2007-January/003249.html
[2] 
http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/servlet/ServletResponse.html#resetBuffer()
Permalink | Reply | 1 comment |
headers
Joshua Paine | 9 Dec 07:28

CouchDB beginnings

FYI, I've ported the basic CouchDB javascript lib that comes with 
CouchDB from browser XMLHttpRequest, etc. to helma.Http. In so doing I 
had to work through a bug in helma.Http, so if you want to use this 
you'll need to make the changes to your local modules/helma/Http.js that 
I suggest in:

<http://helma.org/bugs/show_bug.cgi?id=583>

And then get the CouchDB lib from:

<http://helma.pastebin.com/f7082c07e>

Once you have patched Http.js and included CouchDB.js, you can do easy 
stuff like this:

var c = new CouchDB('testing','localhost',8888);
c.createDb();
c.save({ title:'Testing', content:[1,2,3] });

Congrats! You just created a DB and saved a document in it.

See 
<http://jan.prima.de/~jan/plok/archives/108-Programming-CouchDB-with-Javascript.html> 
for a sample client-side app and the docs at 
<http://www.couchdbwiki.com/index.php?title=HTTP_REST_API>.

-Joshua
Permalink | Reply | 1 comment |
headers
Philip Weaver | 10 Dec 12:16
Picon

Re: CouchDB beginnings

Nice work, Joshua. I hope to try it out soon. It would be cool if Helma's internal database were one day also JSON based but this is an excellent move with CouchDB.

I've been working with Persevere server for a few days. Technologically it is really cool - is Rhino based, supports JSONPath, running Javascript on the server via JSON-RPC, supports multiple data sources. However it is beta software and I'm working through a few issues.

Phil

On Dec 9, 2007 12:28 AM, Joshua Paine <joshua <at> papercrown.org> wrote:
FYI, I've ported the basic CouchDB javascript lib that comes with
CouchDB from browser XMLHttpRequest, etc. to helma.Http. In so doing I
had to work through a bug in helma.Http, so if you want to use this
you'll need to make the changes to your local modules/helma/Http.js that
I suggest in:

<http://helma.org/bugs/show_bug.cgi?id=583>

And then get the CouchDB lib from:

< http://helma.pastebin.com/f7082c07e>

Once you have patched Http.js and included CouchDB.js, you can do easy
stuff like this:

var c = new CouchDB('testing','localhost',8888);
c.createDb ();
c.save({ title:'Testing', content:[1,2,3] });

Congrats! You just created a DB and saved a document in it.

See
< http://jan.prima.de/~jan/plok/archives/108-Programming-CouchDB-with-Javascript.html>
for a sample client-side app and the docs at
< http://www.couchdbwiki.com/index.php?title=HTTP_REST_API>.

-Joshua
_______________________________________________
Helma-user mailing list
Helma-user <at> helma.org
http://helma.org/mailman/listinfo/helma-user

_______________________________________________
Helma-user mailing list
Helma-user <at> helma.org
http://helma.org/mailman/listinfo/helma-user
Permalink | Reply | 0 comments |

Gmane