this just makes sense. straight talk from one to all and vice versa. the way it should be. this doesn't even require rationalization ... it just is. simplicity. freedom. catalyst. we have all the tools we need. let's step it up, kick some butt, change the world and have some fun along the way. it starts now.

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Massive Attack/Mezzanine/Risingson

ready ... set ... !go!

the jxta demos that will be on display this year includes:

• brevient - collaboration
• vista portal - data mining
• jacknet - x10
• myjxta - im
• j2me/j2se picshare

3 of the jxta sessions this year cover:

• jxta/web services
• jxta/j2ee
• jxta/knowledge networks

lastly, the hand-on labs have been greatly expanded this year and a jxta lab has been added to the mix.

myjxta will be running on the floor, during the hands-on lab and in the "java everywhere in action" showcase. as such, feel free to dial in on channel jxta and say hi whenever you want, whereever you may be, and on whatever system you find yourself. the connected net is now.

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Massive Attack/Mezzanine/Black Milk

the weekend came early for me. well, to be honest it simply shifted a day given i'll be working to breathe life into the JXTA demos for JavaOne this sunday. played with my son quite a bit today, going to the local osh and the like as we are gearing up to install a sprinkler system next week. should be fun.

all the JXTA demos are in the queue, ready to start the race that is about to ensue. perhaps i'll get a chance to hack around with some of the MyJXTA ideas i've been bouncing about. that should be cool.

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: The Cars/Anthology Just What I Needed/Dangerous Type

i can now generate this nightly build in minutes on any system whereas this nightly build took hours and was not portable across systems. i still have some doc structuring to do and i need to meld in the cvs commit calls but in general, building stuff from this point on is going to be a completely predictable and repeatable process. the ingredients are ant, bean scripting framework and the rhino javascript engine.

now, back to my regularly scheduled life.

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: The Cars/Anthology Just What I Needed/Touch & Go

oh, this is good. jdnc just popped. coding webapps just became fun again. couldn't really ask for more. a signficant meld of rich client constructs, declarative design elements, variable deployment models, minimal dependencies, and, did i say rich client constructs. the three webstart enabled demos are excellent proof points that this pup is only going to get better.

with this framework in hand we should be able to see the web with eyes wide open vs the bespectacled view constrained via the trusted yet tired browser. good times.

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Death Cab for Cutie/Transatlanticism/Tiny Vessels

an aged component has finally been removed from the project. net impact on the new and *entirely* optimized and signicantly reduced build process ... operated like a champ, just the way it should. the "process elder" would've severely hurled.

next up, i need to dynamically gen the associated html doc to look something like the existing builds. given the contents can vary my thoughts are to use the Ant script tag coupled with rhino jar. turns out the latest bsf and rhino don't compile and based on some google'ing this looks to be an open issue for awhile. so, i pulled the source and hacked a quick bsf patch ... something about a JavaScriptException that needed 3 more args in the constructor ... and now have it compiling and trivial examples working. i posted the following trivial diff to the bsf list:

Index: src/org/apache/bsf/engines/javascript/JavaScriptEngine.java
===================================================================
RCS file: /home/cvspublic/jakarta-bsf/src/org/apache/bsf/engines/javascript/JavaScriptEngine.java,v
retrieving revision 1.9
diff -u -r1.9 JavaScriptEngine.java
--- src/org/apache/bsf/engines/javascript/JavaScriptEngine.java 14 Jun 2004 17:29:40 -0000     1.9
+++ src/org/apache/bsf/engines/javascript/JavaScriptEngine.java 23 Jun 2004 08:16:48 -0000
@@ -119,7 +119,7 @@
           //       Any way to make these arguments *sensible?
           if (fun == Scriptable.NOT_FOUND)
               throw new EvaluatorException("function " + method +
-                                             " not found.", "none", 0);
+                                             " not found.", "none", 0, "", 0);

           cx.setOptimizationLevel(-1);
           cx.setGeneratingDebug(false); 

i considered an xml/xslt solution but my head hurts the way it is and at this point i'm simply trying to stop the bleeding vs dress this pup for the prom.

next up: 

• cvs rm old artifacts
• gen releative index.html
• cvs add new artificats
• cvs commit
• smile and crack a beer ... franziskaner is my fave

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Modest Mouse/The Moon & Antarctica/Tiny Cities Made of Ashes

we'll i for one don't want to miss out on a java/blog melding of the minds ... oh, and the beer will be relished with delight.

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: RadioHead/Amnesiac/You and Whose Army

I've heard it said, at times, that "things get worse before they get better." I'm unsure as to the story behind this phrase and out of context it is not entirely inspirational, to me at least ... but nonetheless the phrase is entirely appropriate for the bit'o slogging I have been involved with as of late.

Here's the skinny. We got JXTA 2.3 out the door and on time which is fine, noble, etc ... but, in doing so this go 'round I was directly exposed to the herculean effort required to connect all the disparent pieces and effectively making the process appear "seemless." Being a "glass is half-full" kind of a guy, most days anyways, I acknowledge that there is typically always room for improvement and as such spend little time rooting out causes short to say that I too, as an application/framework/etc contributor to the overall deliverable am entirely at fault for not keying in to the "big picture." Put another way, generating a release shouldn't be a life altering event. Optimally, a release, or more precisely the process behind a release, will just be another turn'o the key, another drop in the bucket, just another day, etc. as we all have more interesting and necessary work to chew on. For me, specifically, I was was unable to add the more interesting JavaOne JXTA Lab excercises as I had initially strived for (I'll get 'em in next go 'round), nor shored up the JXTA Ext package as fully as I would've liked, or add kew1 new features to MyJXTA, etc. Making compromises is a part of the gig, I accept that, but, moving forward, I intend to do my steady best to contstrain to the fullest extent possible exercise that are not entirely productive when taking a holistic perspective.

So, why am I not as gloomy today. Turns out the legacy build process "just gave out" as it understandably made a number of assumptions to work it's mojo. Alas, things changed, which in and of itself is a good thing (I'm a *huge* XP fan), and the gears ground to a screaching halt. What now. Long story short, I've effectively factored away 5.5k lines of platform/system specifc scripts/data files/etc in favor of roughly 200 lines of Ant files that rightfully delegates to the projects themselves to do the heavy lifting and as such are free to (largely) vary over time. Further, I can run this process on any system, incrementally, reliably, etc. More work is required but at this point in time I see the light ... or, at least I'm happy believing I see the light. As an aside, there is an interesting downside to taking on this type of problem domain work that I'm not entirely thrilled about but given we have a net gain I'm happy to report "it's all good."

To summarize, when something doesn't feel right, fix it when you can vs. when you have to. Just *$%# do it. The rainbow on the horizon ... why Maven of course.

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: RadioHead/Amnesiac/Dollars & Cents

shudson310 looks to be a fellow colo native. colo. great state! great state of mind!

i grew up in grand jct, colo. basically between salt lake and denver. to be more precise, i my neck of the woods is the "redlands" which is aptly named. lots of red dirt, lizards and sage brush. we ran a ranch of about 120 charlette(sp) cattle, 15 wild mustang horses and other breed horses, 100s of chickens, etc. good way to grow up. tough way to make a living ... then again my dad worked two full time jobs concurrently, a doctor by day and night and a rancher in between ... as if there was an in between.

my dad's side of the family has been rooted in colo for generations. there are still small western slope towns using functional resevoirs that were carved out with horse and team by my relatives of not so long ago. further back a bit i am related to abraham lincoln via marriage to mary todd lincoln.

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: RadioHead/KidA/Motion Picture SoundTrack

this one might be old school for some but is a bit new to me given that i have been working on "edge" systems for awhile now. anyways, i'm in a situation where a process is a bit platform specific. not that this is entirely wrong it is just that i'm a fan of having options and in this case i want to run on a fast platform with ample disk, etc. what to do ...

firstly, get the release out the door regardless. done. next, remember the pain. repeat ... do not forget, do not pass go, do not collect $200, do not drink away your woes ... wait a minute ... no, definitely do not drink away your worries. lastly, squirrel away some time to amp up the infrastructure processes. doing this is not all that sexy but conversely is all the more important so that one can, in turn, spend more time on critical work and further enable one to readily spin out new builds at the drop of a dime. more/faster/rinse/repeat.

ok. take inventory. runsocks ... fine. tsocks ... interesting. putty ... hmmmmm, i remember playing with silly putty as a kid. something is wrong. i don't want/need/desire platform anymore platform specific scripts then we already. in fact, i am actively trying to banish said situations. what next. think, think, think ... remembering an email thread where a colleague slipped into this very problem to which another colleague responded briefly espousing something about "... j2ssh cvs tunneled over ssh ..." ahhhh, found the email. next step ... implement. within minutes i'm served with a nice and readily accessible cvs service running that is visible to any intranet system that effectively proxies over ssh to our external repository. !sweet! now i can fire up our build jxta 1-2-3 from any system ... at anytime. cool. last step. drive the processes locally via ant on the target systems leveraging said process and shore up the artifact cvs commits. i like. next up. maven ... the holy grail of build systems.

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: The Streets/A Grand Don't Come For Free/Empty Cans

on a concall ... what to do ... what to do ... i know! it is blog thirty!

my little boy is rapidly becoming not so little. while i am extremely proud i am also a bit saddened with this way to rapid transformation. such is life i guess. anyways, this morning he was oh so proud that he could put on his "big boy pants," our handle for "not diapers," all on his own. this was an experience beyond words. hmmmm, perhaps snoop would have something to say. anyways, as he was struggling he made sure we were watching every step of the way and he very much wanted to do it all by himself. the smile at the end, priceless. man, if i could bottle that stuff i would die a happy man.

we've been extremely patient, well, i'd like to believe we have been patient, parents with regards to encourging our little man graduating to "big boy pants", etc. it was frustrating at times and diapers have many associated costs but to see how proud he felt have achieved this task on his own is a pattern i want very much to replicate.

life is good.

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Death Cab for Cutie/Transatlanticism/Tiny Vessels

Ok, folks that know me know that I don't converse in the style portrayed within. Busted by a lad that works at a blue company but I still like the "temple dawg" anyways :)

So, here's a look at gonzo**** - the uncut edition. Thank goodness for editors ehhhhh.

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Death Cab for Cutie/Transatlanticism/Title and Registration

Check out the kew1 new JXTA Connected button:

Are you connected?

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Death Cab for Cutie/Transatlanticism/Passenger Seat

We've got some process automation cleanup to do but that aside JXTA 2.3 has shipped.

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Death Cab for Cutie/Transatlanticism/Transatlanticism

ok, guilty. i'm tweaking my lnf. hang w/. i'll get there ... where there != "the norm."

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Death Cab for Cutie/Transatlanticism/We Looked Like Giants