javadata-developer Mailing List for Java Data Tools

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

====================
Release 1.0.8
January 10, 2006
====================

- fixed Quik parser infinite loop that happens when attributes and  
tags are not properly terminated

New version of javadata:

	1.0.7

Changes:

	Quik parser fix -- more gracefully handles single quotes in parsing  
instructions

-- Gary

A new release of javadata -- 1.0.6 -- with minor changes:

1. Tag now extends Serializable -- from v 1.0.5

2. The Printer implementations now properly print instances of  
classes that implement Tagged.Output and Chars.Output and not  
Children.Output.

javadata usage [if anyone cares]:

1. heavy use at Chockstone.

2. Bart's unigrok java/xml/web server tool uses javadata. Used in  
production apps at Chockstone. Check it out at www.unigrok.com.

If you're still on the sourceforge javadata developer mailing list  
because you forgot to unsubscribe, well, this is the price you pay  
for such forgetfulness. If you're still on the list because your  
interest in javadata is in fact measurable, I'd be happy to organize  
a get together to talk shop.

In any case, take care until the next release announcement.

-- Gary

Dear Open Source developer

I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate.
You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it.

With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development.

With many thanks for your participation,
Benno Luthiger

PS:
The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/.
We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list.

_______________________________________________________________________

Benno Luthiger
Swiss Federal Institute of Technology Zurich
8092 Zurich

Mail: benno.luthiger(at)id.ethz.ch
_______________________________________________________________________
bug fix...

====================
Release 1.0.3
March 14, 2004
====================

- removed io.IOps System.err.println(...) invocation

Fast parser fixes.

====================
Release 1.0.2
February 28, 2004
====================

- io.xml.quik.Quik bug fix
- io.IOps bug fix (toCharArray(...))

Also, note the removal of PullInputObjectFactory. In the future, this 
class and parser-related classes like it will reside in a separate jar 
file.

====================
Release 1.0.1
January 24, 2004
====================

- an io.xml.quik.Quik bug fix -- entities within character content

====================
Release 1.0
January 21, 2004
====================

- no changes, just a new moniker

The release below is a candidate release, so much a candidate release 
that v1.0 could be on sourceforge by tomorrow night.

====================
Release 1.0-alpha-8
January 20, 2004
====================

- removed PullInputObjectFactory
- added XMLOps.createObject(Reader rdr, TaggedObjectFactory);
- added XMLOps.createObject(char[] chars, int off, int len, 
TaggedObjectFactory);
- Quik xml parser bug fixes
- javadoc additions

This release will be one of the last releases before we release version 
1.0 of javadata. The main differences between this release [alpha6] and 
v1.0 will be in the packaging of classes and documentation.

With respect to packaging, we will at least move the classes related to 
xml pull parsers into another jar file. With xml parsing included in 
the 1.4.1 release, there will then be no need for packages other than 
javadata and the standard jdk packages to compile and deploy javadata 
apps. There are other useful packaging configurations that factor the 
code even more, but for now we're keeping the changes to a minimum.

If you are interested in an xml parser that's fast (10x) and robust, 
try replacing your current InputObjectFactory with a 
QuikInputObjectFactory. Bart's Quik parser does not support xml schema 
or dtd validation, but because it is integrated with the javadata 
object creation framework, it does support namespaces.

-- Gary

====================
Release 1.0-alpha-6
December 19, 2003
====================

- This release includes Bart's fast xml parser, Quik, which operates on 
a subset of xml
   and runs up to 10 times faster than the Sax parser supplied with the 
Java 1.4.1 JDK.

- additional classes

	io
		CountInputStream

	io.xml
		QuikInputObjectFactory

	io.xml.quik
		Quik
		StringProto
		TagProto

- additional methods

	io.IOps
		public static char[] toCharArray(InputStream is, int len) throws 
IOException;
		public static char[] toCharArray(Reader r) throws IOException;

More goodies...
...Gary

====================
Release 1.0-alpha-5
November 17, 2003
====================

- This release contains the implementations of 2 new axes, ATTRIBUTE 
and CHILD_SELF, which were resurrected from previous lives of the code 
base, and includes a bug fix in nav.node.DescendantSelfIterator.

- additional interface

	data.Attribute

- additional classes

	nav.node.
		AttributeIterator
		ChildSelfIterator
	nav.children.
		AttributeIterator
		ChildSelfIterator

- additional axes

	nav.NavConstants
		ATTRIBUTE
		CHILD_SELF

	NOTE:	Iterators constructed using an ATTRIBUTE axis in a single Path
		or contained in the last Path of a Path array (Path[]) produce
		instances of the Attribute interface.
Greetings!

Bart is working on a fast xml parser at Chockstone that parses a 
data-oriented subset of xml. While the parser effort is proprietary 
[for the time being], the associated changes to javadata will make it 
easier for implementors of xml parsers to plug into javadata with 
minimal overhead.

-- Gary

----------------------------------------------------

from the release notes...

====================
Release 1.0-alpha-4
October 25, 2003
====================

- This release contains changes inspired by Bart's efforts at 
implementing a
fast parser that parses a data-oriented subset of xml.

- javadocs

	- minor tweaks

- interface changes

	io.xml.ParseHandler

		signature changes:

			startElement(String namespace, String localName, AttributeAccessor 
ats)
			==>
			startElement(Tag tag, AttributeAccessor ats)

			endElement(String namespace, String localName)
			==>
			endElement(Tag tag)

	io.InputObjectFactory

		new method:

			Object createObject(byte[] bytes, int offset, int length)

	io.xml.AttributeAccessor

		removed methods:

			String getNamespace(int i)
			String getLocalName(int i)

		added method:

			Tag getTag(int i)

		all methods now throw Exception

- classes changed to reflect interface changes

	io.xml.SaxInputObjectFactory
	io.xml.PullInputObjectFactory
	io.xml.DefaultParseHandler

Slowed down by new job, flu, and bronchitis.

I'm putting intro and higher-level docs into javadocs buckets (e.g. - 
overview.html, package.html).

The current package/class/interface organization is holding up under 
the onslaught of documentation.

Comments welcome.

-- Gary

====================
Release 1.0-alpha-2
February 28, 2003
====================

- javadocs

	- unfinished intro in overview

	- org.javadata.data package.html in place

- method added:

	IOps.createReader(InputStream);

I've decided to put all of the javadata documentation into the source 
tree. In fact, I'm putting the intro into a javadocs overview.html file 
that gets included at the top level of the source tree, so everything 
is in the same egg carton. Saves some organizational effort and allows 
the intro to be fully integrated into the javadocs. I'll try to write 
the overview so that if anyone wants a pdf, I can turn overview.html 
without alterations into a pdf using mac os x native pdf support. I'm 
doing this partly because I'm starting a job on Monday, so I'm looking 
for ways to make all of this easier to create, maintain, and publish.

Comments welcome.

-- Gary

The alpha1 releases of javadata source code, jars, and javadocs are 
available on sourceforge.

	sourceforge package:	javadata-data
	java package:			org.javadata.data

	sourceforge package:	javadata-rule
	java package			org.javadata.rule

	sourceforge package:	javadata-sql
	java package:			org.javadata.sql

My next task is to resume work on the javadata intro.

-- Gary

In case you're interested, I'm not doing nothin' here.

The javadoc effort is around 80% done. I hope to have the code base 
including javadocs ready for review by mid-week, if anyone's 
interested. At that point I will release the first alpha tar.gz file 
that bundles up the source code jar file, class jar file, and javadocs. 
Note that there are three cvs modules currently relating to javadata 
1.0: data, rule, and sql. The code may be reviewed at:

	http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/javadata

The introduction to javadata is around 30% done and around 70% thought 
through. I hope to have some useful percentage of it ready for review 
by early next week.

-- Gary

More housecleaning efforts at the javadata SourceForge project...

1. I have acquired the javadata.org domain and plan to change the 
package names in javadata from org.toadcode.* to org.javadata.*.

2. I plan to create three separate cvs modules:

	- data:  	org.javadata.data.*			[formerly org.toadcode.data.*]
	- sql:	org.javadata.sql			[formerly org.toadcode.app.sql]
	- rule:	org.javadata.rule			[formerly org.toadcode.app.rule]

	Each module will have its own ant build.xml file.
		[thanks to AJ for the initial build.xml for javadata]

	Each module will have its own release cycle through SourceForge file 
releases.

If there's a better way on any issue here, please let me know. All 
comments are welcome.

-- Gary

> 1. What do you all think about a domain of javadata.org? It's available. 

domains are cheap. don't regret later.

> 2. I spoke with someone today about software licensing. There are 
> other companies besides MS that will not allow the use of software 
> licensed under GPL or LGPL. Is now a good time to switch to a 
> different type of open source license that will be less likely to 
> limit javadata's use? 

i think it depends on what you want your user community to do. if you 
want people to contribute back, then xGPL seems reasonable to me. if you 
don't care if people take it, screw it up out of your field of vision 
and then pronounce it Bad Work, then go with a BSD.

i have a problem with being pre-bullied by a company whose licensing 
terms upset even casual users of their products.

that said, i understand some companies prefer BSD systems for their work 
because they want to hack it without having to reveal their trade 
secrets. at least that's what they say - a lot of these companies are in 
the berzerkely intellectual hegemony..

1. What do you all think about a domain of javadata.org? It's available.

2. I spoke with someone today about software licensing. There are other 
companies besides MS that will not allow the use of software licensed 
under GPL or LGPL. Is now a good time to switch to a different type of 
open source license that will be less likely to limit javadata's use?

Note:  I'm copying to Henry because he is having technical difficulties 
with his email situation and to Bob because of potential difficulties 
relating to his hot pepper situation.

-- Gary

This is still a work in progress. Please give any suggestions.
Greetings,

The attached document contains a minor change that combines 
nav.TestConstants and nav.PathConstants into one interface, 
nav.NavConstants.

javadata1 is in the SourceForge javadata cvs repository.

I hope to have an alpha release out there pretty soon to bring=20
javadata1 into the alpha era.

era: 1.0 alpha

	=95 =3D=3D>stable code base
	=95=A0tutorial v.1
	=95 javadocs
	=95 app package efforts

era: 1.0 beta

	=95 public postings (e.g. - freshmeat)

-- Gary

PLEASE NOTE:  All subsequent javadata announcements will be sent only=20
to the sourceforge javadata mailing lists.=

Here is a revision of the reorg document. I think it's close...

...but no cigar until we get past this one:  Bart requested that Tag be 
renamed to Name. This is how it used to be when javadata first started 
out, but Bob and Bart made a good point about Tag being more 
recognizable in an xml context. Well, it's six or seven months later 
and we're close to pushing this puppy out of the kennel. While I prefer 
Name over Tag for a variety of reasons, I'm a little bit hesitant as 
this change would require significant changes to the source code. I am 
willing to do it, but I have no interest in going back to Tag once the 
changes are in place.

All comments are welcome at jav...@li....

-- Gary

2003	Jan	Feb (10)	Mar (1)	Apr	May	Jun	Jul	Aug	Sep	Oct (1)	Nov (1)	Dec (1)
2004	Jan (3)	Feb (1)	Mar (1)	Apr	May (1)	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2005	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (2)	Dec
2006	Jan (1)	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

javadata-developer Mailing List for Java Data Tools

javadata-developer — a list for developers interested in javadata