agilewiki-wiki — General discussion.

[AgileWiki] Cabinet ArkDbPropertiesAndTables is now complete, what's next

[Bill la F. <bil...@su...>]

Well, it looks like we've now got the basic documentation needed to 
understand the AgileWiki, though we could probably use something on 
descriptor units. And it also looks like the server is reasonably 
stable. Cheers!   :-)

At this point I want to switch back to writing a bit of code, specificly 
the remove parent command. And then get ready for the 3.0.0.0 release. 
My attention is also turning to what we need for 3.1. There are several 
possible directions:

1. AgileWiki 3.0 is not at all agile, to the point where I don't enjoy 
using it. At a minimum I think we need the post, promote and demote 
commands from AgileWiki2.

2. The table API needs to be made bi-directional. Its just a bit wierd 
the way it works now.

3. We need a better way to install applications than having to create a 
whole new Ark from scratch.

4. Every Rolon should have its own URL which can be referenced from 
external web pages.

To date, the focus has been on getting AW3 to the point where it can 
self-host its own documentation. But there are areas which are seriously 
broken. These need to be addressed.

Bill

[AgileWiki] more documentation!

[Bill la F. <bil...@su...>]

I've just started a new cabinet at agilewiki.org, ArkDbPropertiesAndTables.

This document, together with the other cabinest, should provide enough 
information for you to reason much of how the AgileWiki works, at least 
conceptually. And it should be a great help when using the various API, 
as it connects the wiki to the persistant data structures of TKS.

Of course, its not finished yet. Indeed, I've quite a ways to go yet. 
But please take a peek. If it doesn't make sense to you now, it is not 
going to get any better when its finished--unless you say something!!!

It is also providing a great test of the database. And I'm happy to 
report that there have been no crashes since the installation of the 
last release. But perhaps that's not saying to much? I only just 
installed the last release this morning. Only time will tell.

Bill

[AgileWiki] almost beta

[Bill La F. <Wil...@Su...>]

http://laforge49.blogspot.com/2006/07/almost-beta.html

[AgileWiki] more documentation, alpha29-2

[Bill la F. <bil...@su...>]

With the release of alpha29-2, the DeveloperGuide cabinet at 
agilewiki.org now includes links to Gordan's latest documentation on how 
to run AW using NetBeans. Note that this includes bringing up the 
servlet, so it might be of interest.

Bill

gordan milojevic wrote:

>
>     Hi Bill,
>     I was trying to start both AwSwingClient and Servlet client
>     (thin and thick client) and it working so good on my pc.
>     On localhost 8080 I was making kind of simulation like is
>     on the http://agilewiki.org/index.html
>      
>     Now, practicaly, can try to create topics drawer, making
>     comments, and now could be clearly about princips
>     of agilewiki to me!
>      
>      
>     Best regards
>     Gordan
>

[AgileWiki] Looks like there's another bug

[Bill la F. <bil...@su...>]

I'm not completely suprised, just a bit disapoited. There is apparently 
another case where the tks table is being updated outside of a 
transaction context. I just got up, logged on, and found the traceback 
below. Bill

Exception during request procesing: java.lang.Exception Update without 
transactional cover
java.lang.Exception: Update without transactional cover
        at org.agilewiki.ark.tks.Table.updated(Table.java:269)
        at org.agilewiki.ark.tks.cache.Cache.allocate(Cache.java:114)
        at 
org.agilewiki.ark.tks.cache.WriteCache.allocate(WriteCache.java:62)
        at org.agilewiki.ark.tks.TKS.getRptTable(TKS.java:446)
        at org.agilewiki.ark.tks.TKS.getKeys(TKS.java:495)
        at org.agilewiki.ark.rolons.Rolon.getKeys(Rolon.java:266)
        at org.agilewiki.ark.rolons.Rolon.getParents(Rolon.java:354)
        at org.agilewiki.ark.rolons.Rolon.getPathnameObject(Rolon.java:1805)
        at org.agilewiki.ark.rolons.Rolon.getPathname(Rolon.java:1768)
        at org.agilewiki.ark.rolons.Rolon.pathnameEvent(Rolon.java:1753)
        at org.agilewiki.framework.uims.WikiUIM.header(WikiUIM.java:26)
        at org.agilewiki.framework.Session.process(Session.java:517)
        at 
org.agilewiki.framework.Portal.processClientRequest(Portal.java:117)
        at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at 
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
        at sun.rmi.transport.Transport$1.run(Transport.java:153)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
        at 
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
        at 
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
        at java.lang.Thread.run(Thread.java:595)

[AgileWiki] more documentation, alpha29-1

[Bill la F. <bil...@su...>]

First, I'm happy to note that we have more documentation from Gordan, 
this time on how to run the server, servlet and swing clients using 
NetBeans. I've just added it to svn. its in directory 
AwServlet\web\usingnetbeans and includes both pdf and html. It will be 
included in the next release (alpha30?).

Now I am also hopeful about agilewiki.org. Release alpha29-1 has been 
installed, so we've got the fix in for a major database bug which has 
been causing a crash every day or so. Hopefully things will now be a lot 
more stable. Of course to test it, I've got to add more content to the 
wiki. :-)

Bill

[AgileWiki] the fix is in

[Bill la F. <bil...@su...>]

A table is marked dirty when set is called to add/change an entry in the 
table.

Unfortunately, set is called when the table is initialized. And tables 
are initialized when a table is read. And tables are read outside of a 
transaction. So tables were marked dirty outside a transaction. And when 
there are too many open tables, a dirty table may get flushed to disk.

And if a table is flushed to disk outside of a transaction, a crash occurs.

So I've done two things now:

1. Initializing a table no longer results in the table being marked 
dirty. Hey, this should speed things up as well as fixing the bug!

2. When a table is marked dirty without a transaction, an exception is 
raised--catch bugs earlier so the failure is more repeatable.

So, well, I'm thinking of doing a release of alpha29a very soon now.

Bill

[AgileWiki] the database just crashed again, but this time I got the traceback

[Bill la F. <bil...@su...>]

If we can fix this, then it is time for another release, fer sure! --b

Exception during request procesing: java.util.EmptyStackException null
java.util.EmptyStackException
        at java.util.Stack.peek(Stack.java:79)
        at org.agilewiki.ark.tks.btree.BTree.bImage(BTree.java:644)
        at org.agilewiki.ark.tks.btree.Block._put(Block.java:365)
        at org.agilewiki.ark.tks.btree.Block.put(Block.java:357)
        at org.agilewiki.ark.tks.btree.BTree.put(BTree.java:482)
        at org.agilewiki.ark.tks.TKS.saveTable(TKS.java:389)
        at org.agilewiki.ark.tks.Table.save(Table.java:245)
        at 
org.agilewiki.ark.tks.cache.WriteCache.poolPut(WriteCache.java:77)
        at 
org.agilewiki.ark.tks.cache.WriteCache.poolPut(WriteCache.java:19)
        at org.agilewiki.ark.tks.pool.Poolable.decRef(Poolable.java:64)
        at org.agilewiki.ark.tks.TKS.getKeyValue(TKS.java:584)
        at org.agilewiki.ark.rolons.Rolon.getKeyValue(Rolon.java:250)
        at 
org.agilewiki.ark.rolons.Rolon.getClassifierEntryValue(Rolon.java:1492)
        at org.agilewiki.ark.rolons.Rolon.getName(Rolon.java:470)
        at org.agilewiki.ark.rolons.Rolon.nameEvent(Rolon.java:477)
        at org.agilewiki.ark.rolons.Rolon.nrolonEvent(Rolon.java:401)
        at 
org.agilewiki.ark.rolons.TopicRolon.childrenEvent(TopicRolon.java:195)
        at org.agilewiki.framework.uims.WikiUIM.show(WikiUIM.java:47)
        at 
org.agilewiki.framework.CmdEvaluator.evaluate(CmdEvaluator.java:37)
        at org.agilewiki.framework.Session.evaluate(Session.java:344)
        at org.agilewiki.framework.Session.process(Session.java:504)
        at 
org.agilewiki.framework.Portal.processClientRequest(Portal.java:117)
        at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at 
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
        at sun.rmi.transport.Transport$1.run(Transport.java:153)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
        at 
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
        at 
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
        at java.lang.Thread.run(Thread.java:595)

[AgileWiki] Making it all a bit faster

[Bill la F. <bil...@su...>]

I've now dropped the attributes command and the one index which only it 
used. My hooe was that this would be a significant improvement. However, 
the size of the database only dropped from 3360K to 3296K, a 2% 
reduction in size. The improvement in speed may be more, but likely 
nothing worth writing home about.

Conceptually it does make the database simpler, though I was able to 
remove only a small amount of code.

Bill

[AgileWiki] rebuild now faster, uses less memory

[Bill la F. <bil...@su...>]

Transactions normally hold all the updates for the log file in memory 
until the transaction commits. And if we're trying to rebuild the entire 
database, that's a pretty large amount of data. And it isn't even used, 
as rebuild does not create a log file.

I've now changed TKS and Rebuild to prevent the log file data from being 
created. Now we don't run out of memory when rebuilding.

This is a critical change, for without it we can no longer rebuild the 
database at agilewiki.org. So there might just be an early release of 
alpha30.

Bill

Re: [AgileWiki] Request for Gordan (Bill La Forge)

[Bill la F. <bil...@su...>]

Gordan,

It does look better. I've just added it to the servlet.

Bill

gordan milojevic wrote:

>
> Hi Bill,
> Its very useful part of agilewiki3 applications, and I was taking it from
> http://agilewiki.org/aw3/AwServlet.
> I have download agilewiki3 alpha 29 and I have second way for starting
> agilewiki3 client and server over bat file.(it have pic with web 
> optimal size)
> (its zip file in atachment)
> As agileWiki3 alpha 29, I was taking and AgileWiki3 alpha 7 (oldest 
> version)
> with Framework.jar which can be helpful ( timeknowledgesystem(TKS) is 
> some in all
> alpha versions, version alpha7 have line commands help, citation, ccc 
> which
> is extensible, into abstract class cmd, and can be display in abstract 
> class
> textDisplay.  
> In next couple days will reach agilewiki3 alpha 14 with first gui, 
> afther that
> I think that  I will understend agilewiki3 all.
>  
> Best regards
>
> Gordan,

[AgileWiki] rebuild design flaw

[Bill la F. <bil...@su...>]

I cheated a bit when I wrote the rebuild logic--I made the entire 
rebuild run under a single transaction. Hey, its a whole lot faster that 
way.

Now its catching up with me. When I installed alpha29, I downloaded all 
the log files. I just tried to do a rebuild and ran out of memory.

So now I can either change the design (oo, but its fast the way it is) 
or see if I'm saving data for the commit that isn't needed when running 
rebuild.

Bill

Re: [AgileWiki] server keeps crashing with the same message

[Bill la F. <bil...@su...>]

Found a bug in my startup script--I was not getting errorout. Fixed 
that. Now I just need to wait for the next crash.

A load utility will still be necessary at some point. I'm sure there are 
some obscure bugs we will not find otherwise. And ofcourse we'll want to 
do some sizing studies, mm?

Bill

Bill la Forge wrote:

>All,
>
>It seems to run for quite a while before crashing, probably because of 
>how I have it tuned. I have gotten this message several times now:
>      Exception during request procesing: java.util.EmptyStackException null
>
>Anyone want to spend some time on a utility which interacts with the 
>server, creating a load? We could run several at the same time and give 
>the multi-threading capabilities a workout as well. Starting place would 
>be the text client.
>
>Bill
>

[AgileWiki] server keeps crashing with the same message

[Bill la F. <bil...@su...>]

All,

It seems to run for quite a while before crashing, probably because of 
how I have it tuned. I have gotten this message several times now:
      Exception during request procesing: java.util.EmptyStackException null

Anyone want to spend some time on a utility which interacts with the 
server, creating a load? We could run several at the same time and give 
the multi-threading capabilities a workout as well. Starting place would 
be the text client.

Bill

[AgileWiki] Request for Gordan

[Bill La F. <Wil...@Su...>]

Gordan,

I've now added a bunch more documentation--this time it is in the agile 
wiki itself.

So go to http://agilewiki.org, dig in, and let me know what you think.

I would especially like to know which sections are unreadable, which are 
most helpful and what else you would like to see.

Bill

gordan milojevic wrote:

> Hi Bill,
> I m still learnig AgileWiki3 all project, and using
> all documentation, and update all new revision, every day.
>
> I have free time and all time try to undersend better AgileWiki3.
> Reading all version of AgileWiki3 alpha 1 to alpha 27 with all fresh 
> update
> I didnt enought undersend princip of AgileWiki, and AgileWiki 27 
> become very
> big project, so I was thinking that is for me the best way begin with 
> AgileWiki3 alpha1
> As you said on February 06 "..but more than half of the architecture 
> is in place"
>  
> I was try to undersend  basics princip, and I was found and understend 
> cmds.txt (from AgileWiki3 alpha1)
> as
> file with context of all classes(which allow class loader from 
> CmdManager.java)
> all classes from folder cmds represent commands (help, Ct, CcC, CcA, 
> Attributes, Journal)
> and all extends cmd class(base class for all commands).
> (this is very good way how to read context, parameters and attributes)
> Thats one of constitutive elements of couple, one is ark.java
> which  is knowledge database, its class with represents kind of object 
> base, its very clever
> way to store the data.
> (I think that searcing and update is faster then using for example 
> pointbase 4.2re I was using before)
> Whith documentation which explain rolons, ark, drawer, topic, 
> sections, I have more clearly
> thinking of all project.
> I know for Change Name  command and think about that, and it will
> be implement, I m every day looking, thinking and analysing
> all AgileWiki3 alpha1, and now I think that basics princips of
> AgileWiki3 could be clearly undersending.
> I m every day reading all mail from 
> com...@li... 
> <mailto:com...@li...>.
> I was thinking in all projects (including and UML diagrams which can be
> implemented)
> I just need small time, and I will change name
> (I know its class which have to implement QueryCmd(base class on 
> AgileWiki3 alpha27 AwServer/framework)
> and will have basics methods public final help(), requestDisplay(), 
> boolean applicable(),
> final void process() plus methods for change name which will have 
> adequate implement
> (AgileWiki3 alpha1 have basic princips like AgileWiki3 alpha27, but 
> alpha 27 is very
> biger then alpha1, and this big project make me confused, so now I can 
> undersend
> and alpha27, but not so clearly.
> So, I will implement change name very soon, at the this  weekend, or 
> day or two afther.
>  
>  
>  
> best regards
>  
> gordanmilojevic
>
> *//*

[AgileWiki] agilewiki.org is back up again

[Bill La F. <Wil...@Su...>]

--b

[AgileWiki] The persistant data structures have now been documented.

[Bill la F. <bil...@su...>]

At http://agilewiki.org I've now completed another cabinet, 
PersistantDataStructures. And it is, if I do say so myself, quite 
readable. I expect this will be quite helpful when trying to work with 
the AgileWiki API. Enjoy!
 
Bill

[AgileWiki] Introducing Ed Tidwell--expect great things

[Bill la F. <bil...@su...>]

I am quite delighted to introduce Ed Tidwell to this group:

I've been doing nothing but Swing applications for the past 6 years.  I 
have a very light and simple framework called TFrame.  It is one the 
java.net site. Be happy to refactor the application to add any 
functionality you like.

I was suppose to be working with Hans on JSR 296 but by the time I got 
everything threw legal Han had picked his team. It would be great to do 
some GUI work.  I just wrapped up a 2 year project and my new work is 
all middle layer API/framework type work.

I'm taking a week of vacation next week but after that I will have free 
time to work on a new GUI front end.

[AgileWiki] login, persistant structures

[Bill la F. <bil...@su...>]

I've removed the display from the login command. It wasn't adding any 
value and was just "in the way".

And having completed the file layouts, I'm going to try working on 
documentation for the persistant data structures. This is a more complex 
topic, but you may also find it quite helpful.

Bill

Re: [AgileWiki] Regarding IDE

[Bill la F. <bil...@su...>]

Eclipse? Should be interesting.

1. Please do not use Eclipse to work on AwSwingClient.

This should not be too big a restriction, as it is a thin client and its 
pretty small.
The AwServer program is where the bulk of the code lives.

2. The project build files are all NetBeans generated. I think they will 
work
outside of NetBeans--they are complete. But as for working inside Eclipse,
I haven't a clue.

3. The entire NetBeans project directory is included under subversion, so
you can simply open a project directly with NetBeans. With eclipse you
will likely need to define these projects first.

4. Support for subversion is not yet included in NetBeans (soon, now).
So we mostly use TortoiseSVN when running on windows or the svn
command lines on other OSs. I don't know about Eclipse or if it would have
problems with the NetBeans directory structures even if it does support 
subversion.

So, you can try Eclipse. (But not on AwSwingClient, please!).
I'd like to hear how it goes. It would be good to know.

As for understanding the project, well, its a bit large for that 
approach. This is what
Gordan is doing, but he has a lot of available time and has yet to 
contribute any
code--though I am hopeful.

Rather, I suggest focusing on the creation of commands and forms to 
begin with,
then taking a small project and get your hands dirty. A starting point 
is the commands.txt
file located in the agilewiki package in the AwServer project--it lists 
all the command
names and classes.

But even before digging into the code, become a user first. Register at 
agilewiki.org
and experiment in your own Cabinet. Besides, you will need to use the 
program to
access the (very limited but slowly growing) documentation.

I will note that I am a very frustrated user of AgileWiki3! I miss the 
features in the
AgileWiki2 prototype that made it so easy to reorganize content. But 
we'll get there,
methinks, in a month or 3.

Bill

Ajay R wrote:

>Hi Bill
>
>Thanks, yeah I'll take some time to look at the
>project and understand how it works.
>
>Another questions I have is regarding NetBeans. I know
>all of you have been using NetBeans as the IDE, but I
>have had experience with Eclipse. Would there be any
>copmpatibility issues if eclipse is used over
>netbeans. It's just that I dont want to worry about
>getting used to another IDE.
>
>Regards
>
>Ajay Ravichandran
>

[AgileWiki] Regarding IDE

[Ajay R <aja...@ya...>]

Hi Bill

Thanks, yeah I'll take some time to look at the
project and understand how it works.

Another questions I have is regarding NetBeans. I know
all of you have been using NetBeans as the IDE, but I
have had experience with Eclipse. Would there be any
copmpatibility issues if eclipse is used over
netbeans. It's just that I dont want to worry about
getting used to another IDE.

Regards

Ajay Ravichandran

--- Ajay R <aja...@ya...> wrote:

> Hi Everyone
> 
> My name is Ajay Ravichandran. I am currently a
> Master's student from the Univ. of Louisiana, doing
> an
> internship over here. My hometown is Bangalore. I
> have
> been working with Java for about 2 years now. I
> would
> love to be part of this project and contribute
> 
> Thanks
> 
> Ajay Ravichandran
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam
> protection around 
> http://mail.yahoo.com 
> 
> Using Tomcat but need to do more? Need to support
> web services, security?
> Get stuff done quickly with pre-integrated
> technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1
> based on Apache Geronimo
>
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Compstrm-wiki mailing list
> Com...@li...
>
https://lists.sourceforge.net/lists/listinfo/compstrm-wiki
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[AgileWiki] File layouts are now complete, including the database layout

[Bill la F. <bil...@su...>]

The file layouts are complete. Cheers! But the database layout is not so 
helpful as you might think. Boo!

The database layout will give you a feel for how I handle large data 
values--I expect we will need to handle multi-megabyte files once we 
support a mail client. But its not going to help you understand how the 
database works, because there are a couple layers of abstraction 
involved--structures which implement structures which implement 
structures, in fact. But hey, you've gotta start somewhere!  :-)

So do me a favor, and look it over. Point out any bloopers. And tell me 
where I loose you. 'Cause if you don't understand the first step, then 
none of the rest will make much sense. One thing you may quickly observe 
is that the database file layout and the log file layout deal with 
different layers of abstraction--don't even try to understand how they 
interrelate, because they don't. (And actually, this is one of the 
reasons why things work so well. The log file is dealing with something 
closer to the application layer, and is not simply a log of the changes 
made to the database.)

Bill

[AgileWiki] Before image file layout has been documented at agilewiki.org

[Bill La F. <Wil...@Su...>]

I've now completed the file layout for the before image file. But don't 
get excited--there's not a lot there.

The layout of the database file is next/last. Its a bit more complex 
than the others. :-)

Bill

[AgileWiki] admin commands checked in

[Bill la F. <bil...@su...>]

I've now completed the setDU, setCEnt, setDEnt and setLEnt commands. 
(Remember to do a build clean of AwServer after the svn up.)

These are semi-hidden commands. You must be a member of the admin group 
to use these commands AND you need to use the rolonic interface.

Using these commands, you can make low-level changes. Use them for 
configuring things with special requirements and for fixing things that 
have gone bad. But note that there are very little validation done. So 
have a care.

Bill

Re: [AgileWiki] Interested in Contributing to this project

[Bill la F. <bil...@su...>]

Ajay,

Here's the pitch. Go to http://agilewiki.org and dig in. You will find 
the agile wiki running there (most of the time--it still crashes about 
once a day) and we've got a fair amount of user documentation either in 
agile wiki or referenced by agile wiki. I've also just started with the 
file layouts and more documentation will follow. You will also find a 
lot of new terminology specific to this project. Sorry 'bout that, but 
its important.

Learn the tool. You'll need to be able to run it anyway for testing. 
Right now its a so so wiki, unlike the prototype that came before it. We 
need to change that, as well as work on making it a good application 
platform. Get familiar with subversion and NetBeans. Etc, etc etc. :-)

And you will also find in the OpenIssues cabinet a whole long list of 
things to work on. Once you get oriented, then you can start cranking.

But be sure to let folk know what you're working on. And remember to ask 
questions on this list--I'm sure everything is not perfectly clear!

And be welcome.

Bill

Ajay R wrote:

>Hi Everyone
>
>My name is Ajay Ravichandran. I am currently a
>Master's student from the Univ. of Louisiana, doing an
>internship over here. My hometown is Bangalore. I have
>been working with Java for about 2 years now. I would
>love to be part of this project and contribute
>
>Thanks
>
>Ajay Ravichandran
>  
>