persevere-framework - Project Hosting on Google Code

Last 7 days Dec 08, 2009 issue 246 (pjs.getUserName(); Always returns null) commented on by deepak.nadar - Works when used after getStores() call: // works dojox.data.PersevereStore.getStores(). addCallback(function(stores) { console.debug(pjs.getUserName()); }); Works when used after getStores() call: // works dojox.data.PersevereStore.getStores(). addCallback(function(stores) { console.debug(pjs.getUserName()); }); Dec 08, 2009 issue 246 (pjs.getUserName(); Always returns null) commented on by deepak.nadar - Same issue here. Also, trying it after page load also fails - but, it does work when manually trying it using Firebug (in FF)...there is a specific event to wait for, just don't know which one. // fails dojo.addOnLoad(function() { console.debug(pjs.getUserName()); }); Same issue here. Also, trying it after page load also fails - but, it does work when manually trying it using Firebug (in FF)...there is a specific event to wait for, just don't know which one. // fails dojo.addOnLoad(function() { console.debug(pjs.getUserName()); }); Last 30 days Nov 30, 2009 r675 (Pintura reorg) committed by kriszyp - Pintura reorg Pintura reorg Nov 25, 2009 issue 259 (Array slicing [0:2] is not working right on 1.0 latest sourc...) reported by dtynan - I usually get an empty result set when using the array indexing operator (like [:3] or [0:1]), even though I should have results. I see this from console as well as web. Here is a console example: js>b = load("resfull6") [object Array of 4 elements] js>b = load("resfull6/[?blah='Austin']") [object Array of 3 elements] js>b = load("resfull6/[?blah='Austin'][:2]") [object Array of 0 elements] <<<<---- problem js>b = load("resfull6/[0:2]") [object Array of 0 elements] <<<<---- problem js>b = load("resfull6/[1:1]") [object Array of 0 elements] <<<<---- problem js>serialize(a) [ {"id":"resfull6/1", "blah":"Austin" }, {"id":"resfull6/2", "blah":"Austin" }, {"id":"resfull6/3", "blah":"Junk" }, {"id":"resfull6/4", "blah":"Austin" } What version of the product are you using? On what operating system? I'm on version 1.0 (actually, r661 is the revision) I've duplicated this on windows & linux Please provide any additional information below. I see the same issue from the HTTP interface as from the command line. Strangely, on my own (much larger) database, the slicing operator DOES work on some fields (or perhaps randomly), but it's rare. I usually get an empty result set when using the array indexing operator (like [:3] or [0:1]), even though I should have results. I see this from console as well as web. Here is a console example: js>b = load("resfull6") [object Array of 4 elements] js>b = load("resfull6/[?blah='Austin']") [object Array of 3 elements] js>b = load("resfull6/[?blah='Austin'][:2]") [object Array of 0 elements] <<<<---- problem js>b = load("resfull6/[0:2]") [object Array of 0 elements] <<<<---- problem js>b = load("resfull6/[1:1]") [object Array of 0 elements] <<<<---- problem js>serialize(a) [ {"id":"resfull6/1", "blah":"Austin" }, {"id":"resfull6/2", "blah":"Austin" }, {"id":"resfull6/3", "blah":"Junk" }, {"id":"resfull6/4", "blah":"Austin" } What version of the product are you using? On what operating system? I'm on version 1.0 (actually, r661 is the revision) I've duplicated this on windows & linux Please provide any additional information below. I see the same issue from the HTTP interface as from the command line. Strangely, on my own (much larger) database, the slicing operator DOES work on some fields (or perhaps randomly), but it's rare. Nov 23, 2009 r674 (Add join to lazy) committed by kriszyp - Add join to lazy Add join to lazy Nov 23, 2009 r673 (Add support for in method Convert full-text to set of ids) committed by kriszyp - Add support for in method Convert full-text to set of ids Add support for in method Convert full-text to set of ids Nov 21, 2009 issue 258 (using .length() instead of .length causes server problem) Status changed by kriszyp - Status: Verified Status: Verified Nov 21, 2009 issue 258 (using .length() instead of .length causes server problem) commented on by dtynan - I tried this again using Persevere 1.0 and could not recreate the issue I was seeing. Using .length() does cause a bunch of junk to scroll by on the console, and then an error, but it doesn't appear to cause any crashes/hangs/denial of service/etc as far as I can tell. This bug can be closed out. I tried this again using Persevere 1.0 and could not recreate the issue I was seeing. Using .length() does cause a bunch of junk to scroll by on the console, and then an error, but it doesn't appear to cause any crashes/hangs/denial of service/etc as far as I can tell. This bug can be closed out. Nov 20, 2009 issue 258 (using .length() instead of .length causes server problem) commented on by dtynan - This may just be my installation ... please ignore this defect for the moment while I verify. This may just be my installation ... please ignore this defect for the moment while I verify. Nov 20, 2009 r672 (throw an error for xml-rpc failures) committed by kriszyp - throw an error for xml-rpc failures throw an error for xml-rpc failures Nov 20, 2009 r671 (Updated querying) committed by kriszyp - Updated querying Updated querying Nov 20, 2009 r670 (query refactoring) committed by kriszyp - query refactoring query refactoring Nov 19, 2009 r669 (Updates) committed by kriszyp - Updates Updates Nov 19, 2009 r668 (Updated login) committed by kriszyp - Updated login Updated login Nov 19, 2009 r667 (Update narwhal) committed by kriszyp - Update narwhal Update narwhal Nov 19, 2009 r666 (Pintura updates) committed by kriszyp - Pintura updates Pintura updates Nov 17, 2009 issue 258 (using .length() instead of .length causes server problem) reported by dtynan - What steps will reproduce the problem? 1. Put parentheses on the .length jsonquery (which is not valid, I just keep doing it accidentally) 2. So your URL looks something like: http://whatever:8080/[?price<50].length() What is the expected output? What do you see instead? I would just expect this to fail, but instead it runs for a long time and then fails with a message on the server saying "should not get here". What version of the product are you using? On what operating system? I'm seeing this on a moderately old installation (which is close to production). Obviously not an issue unless I mistype my commands, but it should be fixed, if it hasn't already on a newer version, since it would allow anyone to cause problems. (forgive me if this is already fixed on a recent version, didn't have a chance to try it) Thanks, Dylan What steps will reproduce the problem? 1. Put parentheses on the .length jsonquery (which is not valid, I just keep doing it accidentally) 2. So your URL looks something like: http://whatever:8080/[?price<50].length() What is the expected output? What do you see instead? I would just expect this to fail, but instead it runs for a long time and then fails with a message on the server saying "should not get here". What version of the product are you using? On what operating system? I'm seeing this on a moderately old installation (which is close to production). Obviously not an issue unless I mistype my commands, but it should be fixed, if it hasn't already on a newer version, since it would allow anyone to cause problems. (forgive me if this is already fixed on a recent version, didn't have a chance to try it) Thanks, Dylan Nov 14, 2009 r665 (Fixes full text querying matching) committed by kriszyp - Fixes full text querying matching Fixes full text querying matching Nov 14, 2009 r664 (Removed deleted files) committed by kriszyp - Removed deleted files Removed deleted files Nov 14, 2009 r663 (Updates to JSONQuery parsing for sql module) committed by kriszyp - Updates to JSONQuery parsing for sql module Updates to JSONQuery parsing for sql module Nov 13, 2009 r662 (Updates for uploading multipart/files) committed by kriszyp - Updates for uploading multipart/files Updates for uploading multipart/files Nov 13, 2009 persevere1.0.war (Persevere Server 1.0 (Servlet WAR)) file uploaded by kriszyp - Labels: Featured Type-Archive OpSys-All Labels: Featured Type-Archive OpSys-All Nov 13, 2009 persevere1.0.zip (Persevere Server 1.0 (zip file)) file uploaded by kriszyp - Labels: Featured Type-Archive OpSys-All Labels: Featured Type-Archive OpSys-All Nov 13, 2009 persevere1.0.tar.gz (Persevere Server 1.0) file uploaded by kriszyp - Labels: Featured OpSys-All Type-Archive Labels: Featured OpSys-All Type-Archive Nov 13, 2009 r661 (Undo the sequence id logging statements) committed by kriszyp - Undo the sequence id logging statements Undo the sequence id logging statements Nov 13, 2009 r660 (Might as well look at env.QUERY_STRING as well) committed by kriszyp - Might as well look at env.QUERY_STRING as well Might as well look at env.QUERY_STRING as well Nov 13, 2009 r659 (Have the REST handler look at env.PATH_INFO for the path) committed by kriszyp - Have the REST handler look at env.PATH_INFO for the path Have the REST handler look at env.PATH_INFO for the path Nov 12, 2009 r658 (Updates to SQLStore Remove unneeded files) committed by kriszyp - Updates to SQLStore Remove unneeded files Updates to SQLStore Remove unneeded files Nov 12, 2009 r657 (Refactor packages Remove .git folders) committed by kriszyp - Refactor packages Remove .git folders Refactor packages Remove .git folders Earlier this year Nov 10, 2009 r656 (authenticatedUser -> remoteUser additional help for JsonQuer...) committed by kriszyp - authenticatedUser -> remoteUser additional help for JsonQuery with full-text Fixed sorting in json-query module authenticatedUser -> remoteUser additional help for JsonQuery with full-text Fixed sorting in json-query module Nov 10, 2009 r655 (Fixes some issues with sorting where some objects have restr...) committed by kriszyp - Fixes some issues with sorting where some objects have restricted access Fixes some issues with sorting where some objects have restricted access Nov 09, 2009 r654 (Removes errant import) committed by kriszyp - Removes errant import Removes errant import Nov 09, 2009 r653 (Fixes doing data manipulation SQL queries) committed by kriszyp - Fixes doing data manipulation SQL queries Fixes doing data manipulation SQL queries Nov 09, 2009 r652 (persistence -> persisted) committed by kriszyp - persistence -> persisted persistence -> persisted Nov 09, 2009 r651 (Refactoring class creation Fixed transaction committing in f...) committed by kriszyp - Refactoring class creation Fixed transaction committing in full text env -> request in a number of places Refactoring class creation Fixed transaction committing in full text env -> request in a number of places Nov 06, 2009 r650 (Renamed full text module Fixed date handling with lucene) committed by kriszyp - Renamed full text module Fixed date handling with lucene Renamed full text module Fixed date handling with lucene Nov 04, 2009 issue 254 ("%23" (encoded #) for some reason is converted to "." in the...) commented on by d...@deanlandolt.com - Stupid google won'tl et me reopen. But in any event... The problem isn't actually fixed -- "%23" now comes in as "param0", a second %23 is param1, etc. Theoretically I could replace(/param\d/g, "#") but this would be a pretty bad hack. Stupid google won'tl et me reopen. But in any event... The problem isn't actually fixed -- "%23" now comes in as "param0", a second %23 is param1, etc. Theoretically I could replace(/param\d/g, "#") but this would be a pretty bad hack. Nov 04, 2009 issue 256 (Class ids with slashes should be broken aparet and layered i...) commented on by d...@deanlandolt.com - I found a way to do this in js by wrapping Class. It's generalizable into a customizable package model -- if anyone's interested I can add more information. I found a way to do this in js by wrapping Class. It's generalizable into a customizable package model -- if anyone's interested I can add more information. Nov 02, 2009 r649 (Determine the file path correctly inside of contexts) committed by kriszyp - Determine the file path correctly inside of contexts Determine the file path correctly inside of contexts Nov 02, 2009 r648 (Some logging debugging) committed by kriszyp - Some logging debugging Some logging debugging Nov 02, 2009 r647 (Added support for using settings for mail configuration Defa...) committed by kriszyp - Added support for using settings for mail configuration Defaults to WEB-INF/jslib for module directory if none specified Added support for using settings for mail configuration Defaults to WEB-INF/jslib for module directory if none specified Nov 02, 2009 issue 257 (ID sort order AND ID fully qualified behavior) commented on by beau.croteau - Expected Output response is in the 'additional information' section. Expected Output response is in the 'additional information' section. Nov 02, 2009 issue 257 (ID sort order AND ID fully qualified behavior) reported by beau.croteau - What steps will reproduce the problem? 1. Create class 'example_simple' 2. Add 10 objects to the class with {name:'A...J'} 3. Attempt to filter and sort: http://localhost:8080/example_simple%5B?name=%27%27][/id] What is the expected output? What do you see instead? [{id:1, id:2, id:3...}] Also, flip flops between fully qualified ID and int-only ID for specific queries. What version of the product are you using? On what operating system? R605 from Source and RC 2. Please provide any additional information below. You'll get something like the default back: http://localhost:8080/example_simple {}&&[ {"id":"example_simple/1", "name":"a" }, {"id":"example_simple/2", "name":"b" } ... But when you sort by id (it drops the 'example_simple' prefix) http://localhost:8080/example_simple%5B/id%5D {}&&[ {"id":"1", "name":"a" }, {"id":"2", "name":"b" } ... And worse filter then sort (back to what look like ints, but they're really sorted strings): http://localhost:8080/example_simple%5B?name=%27%27][/id] {}&&[ {"id":"1", "name":"a" }, {"id":"10", "name":"E" } What steps will reproduce the problem? 1. Create class 'example_simple' 2. Add 10 objects to the class with {name:'A...J'} 3. Attempt to filter and sort: http://localhost:8080/example_simple%5B?name=%27%27][/id] What is the expected output? What do you see instead? [{id:1, id:2, id:3...}] Also, flip flops between fully qualified ID and int-only ID for specific queries. What version of the product are you using? On what operating system? R605 from Source and RC 2. Please provide any additional information below. You'll get something like the default back: http://localhost:8080/example_simple {}&&[ {"id":"example_simple/1", "name":"a" }, {"id":"example_simple/2", "name":"b" } ... But when you sort by id (it drops the 'example_simple' prefix) http://localhost:8080/example_simple%5B/id%5D {}&&[ {"id":"1", "name":"a" }, {"id":"2", "name":"b" } ... And worse filter then sort (back to what look like ints, but they're really sorted strings): http://localhost:8080/example_simple%5B?name=%27%27][/id] {}&&[ {"id":"1", "name":"a" }, {"id":"10", "name":"E" } Oct 30, 2009 issue 256 (Class ids with slashes should be broken aparet and layered i...) reported by d...@deanlandolt.com - Here's a patch to add . This could probably be a little nicer, but it gets the job done. I've tested and all is well but I'll create some core tests to test this and other slash-based package functionality and throw another patch over the fence. Here's a patch to add . This could probably be a little nicer, but it gets the job done. I've tested and all is well but I'll create some core tests to test this and other slash-based package functionality and throw another patch over the fence. Oct 30, 2009 r646 (Refactored lazy arrays to use some method instead of forEach...) committed by kriszyp - Refactored lazy arrays to use some method instead of forEach for more efficient exits Refactored lazy arrays to use some method instead of forEach for more efficient exits Oct 30, 2009 issue 254 ("%23" (encoded #) for some reason is converted to "." in the...) Status changed by kriszyp - Status: Fixed Status: Fixed Oct 30, 2009 r645 (Fixes handling of # in some ids) committed by kriszyp - Fixes handling of # in some ids Fixes handling of # in some ids Oct 30, 2009 issue 255 (content negotiation broken in 1.0 tip) Status changed by kriszyp - Status: Fixed Status: Fixed Oct 30, 2009 r644 (Fixed Accept header handler) committed by kriszyp - Fixed Accept header handler Fixed Accept header handler Oct 30, 2009 r643 (Fixed an unnecessary import Turn on idle checking of connect...) committed by kriszyp - Fixed an unnecessary import Turn on idle checking of connections Fixed an unnecessary import Turn on idle checking of connections

issue 259 (Array slicing [0:2] is not working right on 1.0 latest sourc...) reported by dtynan - I usually get an empty result set when using the array indexing operator (like [:3] or [0:1]), even though I should have results. I see this from console as well as web. Here is a console example: js>b = load("resfull6") [object Array of 4 elements] js>b = load("resfull6/[?blah='Austin']") [object Array of 3 elements] js>b = load("resfull6/[?blah='Austin'][:2]") [object Array of 0 elements] <<<<---- problem js>b = load("resfull6/[0:2]") [object Array of 0 elements] <<<<---- problem js>b = load("resfull6/[1:1]") [object Array of 0 elements] <<<<---- problem js>serialize(a) [ {"id":"resfull6/1", "blah":"Austin" }, {"id":"resfull6/2", "blah":"Austin" }, {"id":"resfull6/3", "blah":"Junk" }, {"id":"resfull6/4", "blah":"Austin" } What version of the product are you using? On what operating system? I'm on version 1.0 (actually, r661 is the revision) I've duplicated this on windows & linux Please provide any additional information below. I see the same issue from the HTTP interface as from the command line. Strangely, on my own (much larger) database, the slicing operator DOES work on some fields (or perhaps randomly), but it's rare.

I usually get an empty result set when using the array indexing operator (like [:3] or [0:1]), even though I should have results. I see this from console as well as web. Here is a console example: js>b = load("resfull6") [object Array of 4 elements] js>b = load("resfull6/[?blah='Austin']") [object Array of 3 elements] js>b = load("resfull6/[?blah='Austin'][:2]") [object Array of 0 elements] <<<<---- problem js>b = load("resfull6/[0:2]") [object Array of 0 elements] <<<<---- problem js>b = load("resfull6/[1:1]") [object Array of 0 elements] <<<<---- problem js>serialize(a) [ {"id":"resfull6/1", "blah":"Austin" }, {"id":"resfull6/2", "blah":"Austin" }, {"id":"resfull6/3", "blah":"Junk" }, {"id":"resfull6/4", "blah":"Austin" } What version of the product are you using? On what operating system? I'm on version 1.0 (actually, r661 is the revision) I've duplicated this on windows & linux Please provide any additional information below. I see the same issue from the HTTP interface as from the command line. Strangely, on my own (much larger) database, the slicing operator DOES work on some fields (or perhaps randomly), but it's rare.

Last 7 days

Last 30 days

Earlier this year