domify-interest — General discussion of the Domify package

Re: [Domify-interest] status/direction of the code in CVS?

[Geoffrey M. <geo...@ho...>]

I did briefly.  I'm sorry, but I've been really busy.  I tried to do 
some work on domify a couple weekends ago and it had been so long since 
I'd looked at it that I could hardly remember what I was doing!  I will 
try to get back to it before too long...but this month is already shot.  
I'll do what I can!

toby cabot wrote:

>>>>Toby, once I get the basics nailed down, if you'd like to contribute 
>>>>some standard adapters for SQLDate and Date objects, that would be cool.
>>>>        
>>>>
>
>Hi Geoffrey,
>
>Have you had a chance to look at the code in patch 1830697?
>
>Thanks,
>Toby
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Microsoft
>Defy all challenges. Microsoft(R) Visual Studio 2008.
>http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>_______________________________________________
>Domify-interest mailing list
>Dom...@li...
>https://lists.sourceforge.net/lists/listinfo/domify-interest
>
>
>  
>

-- 
Geoffrey Mitchell
Programmer/Analyst
Home Decorator's Collection
314-684-1062

Re: [Domify-interest] status/direction of the code in CVS?

[toby c. <to...@ca...>]

> >>Toby, once I get the basics nailed down, if you'd like to contribute 
> >>some standard adapters for SQLDate and Date objects, that would be cool.

Hi Geoffrey,

Have you had a chance to look at the code in patch 1830697?

Thanks,
Toby

Re: [Domify-interest] trunk code with java 1.4.2?

[Geoffrey M. <geo...@ho...>]

>Hi Geoff,
>
>I'm trying to build a domify.jar with 1.4.2 and the new build system
>but I stubbed my toe.  If I run Maven with 1.5 it compiles, runs a
>bunch of unit tests and builds the jar just fine.  If I build with 1.4
>Maven compiles the "main" code but the unit test compile fails so the
>jar doesn't get built.  Is there a way to tell Maven to build the jar
>before it compiles and runs the unit tests?
>
>Thanks,
>Toby
>
>  
>
Toby,

Is there a reason that you need to run maven with 1.4.2?  The jar 
generated should be 1.4.2 compatible either way. 


-- 
Geoffrey Mitchell
Programmer/Analyst
Home Decorator's Collection
314-684-1062

Re: [Domify-interest] trunk code with java 1.4.2?

[toby c. <to...@ca...>]

On Fri, Nov 02, 2007 at 10:32:22AM -0500, Geoffrey Mitchell wrote:
> The trunk should now compile and run with 1.4.2.  Note that 1.5 is 
> required to build and run the unit tests, however.

Hi Geoff,

I'm trying to build a domify.jar with 1.4.2 and the new build system
but I stubbed my toe.  If I run Maven with 1.5 it compiles, runs a
bunch of unit tests and builds the jar just fine.  If I build with 1.4
Maven compiles the "main" code but the unit test compile fails so the
jar doesn't get built.  Is there a way to tell Maven to build the jar
before it compiles and runs the unit tests?

Thanks,
Toby

Re: [Domify-interest] status/direction of the code in CVS?

[toby c. <to...@ca...>]

On Tue, Oct 09, 2007 at 02:50:31PM -0500, Geoffrey Mitchell wrote:
> Toby, once I get the basics nailed down, if you'd like to contribute 
> some standard adapters for SQLDate and Date objects, that would be cool.

Hi Geoff,

I updated bug 1808993 so the patch applies to the new code tree, and
submitted patch 1830697 which is a proof-of-concept of an enhanced
Adapter for util.Date and sql.Date.  Comments welcome.

Thanks,
Toby

Re: [Domify-interest] trunk code with java 1.4.2?

[Geoffrey M. <geo...@ho...>]

This is fixed. 

The trunk should now compile and run with 1.4.2.  Note that 1.5 is 
required to build and run the unit tests, however.

Geoffrey Mitchell wrote:

>Toby,
>
>Yes, the trunk is intended to work with 1.4.  I was compiling with 
>source=1.4, but it didn't catch the problem.  I will fix it.  Thanks!
>
>Geoff
>
>toby cabot wrote:
>
>  
>
>>Hi Folks,
>>
>>I'm taking a look at the new trunk code and wonder whether it's a goal
>>that it work with 1.4.2.  I had a compile problem with
>>DelegatingNodeListAdapterFactory using a two-argument constructor to
>>IllegalStateException which only showed up in 1.5.  If 1.4.2 is a
>>non-goal that's OK, I'll use a branch, but if 1.4.2 is a goal then
>>here's a trivial fix to get it to compile:
>>
>>Index: src/main/java/org/infohazard/domify/DelegatingNodeListAdapterFactory.java
>>===================================================================
>>RCS file: /cvsroot/domify/domify/core/src/main/java/org/infohazard/domify/DelegatingNodeListAdapterFactory.java,v
>>retrieving revision 1.1
>>diff -u -d -u -r1.1 DelegatingNodeListAdapterFactory.java
>>--- src/main/java/org/infohazard/domify/DelegatingNodeListAdapterFactory.java	21 Oct 2007 23:07:53 -0000	1.1
>>+++ src/main/java/org/infohazard/domify/DelegatingNodeListAdapterFactory.java	30 Oct 2007 11:24:08 -0000
>>@@ -56,10 +56,10 @@
>>            return (NodeList) factoryMethod.invoke(null,new Object[]{parentElement});
>>        } catch (IllegalAccessException e) {
>>            log.error("Unable to invoke factory method on adapter class.",e);
>>-            throw new IllegalStateException("Unable to invoke factory method on adapter class.",e);
>>+            throw new IllegalStateException("Unable to invoke factory method on adapter class: " + e.getMessage());
>>        } catch (InvocationTargetException e) {
>>            log.error("Error while invoking factory method on adapter class.",e);
>>-            throw new IllegalStateException("Error while invoking factory method on adapter class.",e);
>>+            throw new IllegalStateException("Error while invoking factory method on adapter class: " + e.getMessage());
>>        }
>>    }
>>
>>
>>Thanks,
>>Toby
>>
>>-------------------------------------------------------------------------
>>This SF.net email is sponsored by: Splunk Inc.
>>Still grepping through log files to find problems?  Stop.
>>Now Search log events and configuration files using AJAX and a browser.
>>Download your FREE copy of Splunk now >> http://get.splunk.com/
>>_______________________________________________
>>Domify-interest mailing list
>>Dom...@li...
>>https://lists.sourceforge.net/lists/listinfo/domify-interest
>>
>>
>> 
>>
>>    
>>
>
>  
>

-- 
Geoffrey Mitchell
Programmer/Analyst
Home Decorator's Collection
314-684-1062

Re: [Domify-interest] trunk code with java 1.4.2?

[Geoffrey M. <geo...@ho...>]

Toby,

Yes, the trunk is intended to work with 1.4.  I was compiling with 
source=1.4, but it didn't catch the problem.  I will fix it.  Thanks!

Geoff

toby cabot wrote:

>Hi Folks,
>
>I'm taking a look at the new trunk code and wonder whether it's a goal
>that it work with 1.4.2.  I had a compile problem with
>DelegatingNodeListAdapterFactory using a two-argument constructor to
>IllegalStateException which only showed up in 1.5.  If 1.4.2 is a
>non-goal that's OK, I'll use a branch, but if 1.4.2 is a goal then
>here's a trivial fix to get it to compile:
>
>Index: src/main/java/org/infohazard/domify/DelegatingNodeListAdapterFactory.java
>===================================================================
>RCS file: /cvsroot/domify/domify/core/src/main/java/org/infohazard/domify/DelegatingNodeListAdapterFactory.java,v
>retrieving revision 1.1
>diff -u -d -u -r1.1 DelegatingNodeListAdapterFactory.java
>--- src/main/java/org/infohazard/domify/DelegatingNodeListAdapterFactory.java	21 Oct 2007 23:07:53 -0000	1.1
>+++ src/main/java/org/infohazard/domify/DelegatingNodeListAdapterFactory.java	30 Oct 2007 11:24:08 -0000
>@@ -56,10 +56,10 @@
>             return (NodeList) factoryMethod.invoke(null,new Object[]{parentElement});
>         } catch (IllegalAccessException e) {
>             log.error("Unable to invoke factory method on adapter class.",e);
>-            throw new IllegalStateException("Unable to invoke factory method on adapter class.",e);
>+            throw new IllegalStateException("Unable to invoke factory method on adapter class: " + e.getMessage());
>         } catch (InvocationTargetException e) {
>             log.error("Error while invoking factory method on adapter class.",e);
>-            throw new IllegalStateException("Error while invoking factory method on adapter class.",e);
>+            throw new IllegalStateException("Error while invoking factory method on adapter class: " + e.getMessage());
>         }
>     }
> 
>
>Thanks,
>Toby
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc.
>Still grepping through log files to find problems?  Stop.
>Now Search log events and configuration files using AJAX and a browser.
>Download your FREE copy of Splunk now >> http://get.splunk.com/
>_______________________________________________
>Domify-interest mailing list
>Dom...@li...
>https://lists.sourceforge.net/lists/listinfo/domify-interest
>
>
>  
>

-- 
Geoffrey Mitchell
Programmer/Analyst
Home Decorator's Collection
314-684-1062

[Domify-interest] trunk code with java 1.4.2?

[toby c. <to...@ca...>]

Hi Folks,

I'm taking a look at the new trunk code and wonder whether it's a goal
that it work with 1.4.2.  I had a compile problem with
DelegatingNodeListAdapterFactory using a two-argument constructor to
IllegalStateException which only showed up in 1.5.  If 1.4.2 is a
non-goal that's OK, I'll use a branch, but if 1.4.2 is a goal then
here's a trivial fix to get it to compile:

Index: src/main/java/org/infohazard/domify/DelegatingNodeListAdapterFactory.java
===================================================================
RCS file: /cvsroot/domify/domify/core/src/main/java/org/infohazard/domify/DelegatingNodeListAdapterFactory.java,v
retrieving revision 1.1
diff -u -d -u -r1.1 DelegatingNodeListAdapterFactory.java
--- src/main/java/org/infohazard/domify/DelegatingNodeListAdapterFactory.java	21 Oct 2007 23:07:53 -0000	1.1
+++ src/main/java/org/infohazard/domify/DelegatingNodeListAdapterFactory.java	30 Oct 2007 11:24:08 -0000
@@ -56,10 +56,10 @@
             return (NodeList) factoryMethod.invoke(null,new Object[]{parentElement});
         } catch (IllegalAccessException e) {
             log.error("Unable to invoke factory method on adapter class.",e);
-            throw new IllegalStateException("Unable to invoke factory method on adapter class.",e);
+            throw new IllegalStateException("Unable to invoke factory method on adapter class: " + e.getMessage());
         } catch (InvocationTargetException e) {
             log.error("Error while invoking factory method on adapter class.",e);
-            throw new IllegalStateException("Error while invoking factory method on adapter class.",e);
+            throw new IllegalStateException("Error while invoking factory method on adapter class: " + e.getMessage());
         }
     }
 

Thanks,
Toby

[Domify-interest] New Features in CVS

[Geoffrey M. <geo...@ho...>]

You can now register a new adapter for handling a specific class using 
DOMAdapter.registerNodeListAdapter.  The stringify functionality has 
been modified to delegate to this mechanism internally.

I still have a lot of cleanup work to do (including re-incorporating the 
annotation functionality), but it *should* work.

So, check out the HEAD and give it a shot.


-- 
Geoffrey Mitchell
Programmer/Analyst
Home Decorator's Collection
314-684-1062

Re: [Domify-interest] status/direction of the code in CVS?

[Geoffrey M. <geo...@ho...>]

FYI, I'm still working on this.  I've been very busy at home lately, so 
haven't been able to dedicate time to it for a while.  I should get a 
chance to make some progress on it this weekend.  With luck, I will have 
something you can work with by next week.

Geoff

toby cabot wrote:

>On Tue, Oct 09, 2007 at 02:50:31PM -0500, Geoffrey Mitchell wrote:
>  
>
>>Toby, once I get the basics nailed down, if you'd like to contribute 
>>some standard adapters for SQLDate and Date objects, that would be cool.
>>    
>>
>
>Sounds like a plan!
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc.
>Still grepping through log files to find problems?  Stop.
>Now Search log events and configuration files using AJAX and a browser.
>Download your FREE copy of Splunk now >> http://get.splunk.com/
>_______________________________________________
>Domify-interest mailing list
>Dom...@li...
>https://lists.sourceforge.net/lists/listinfo/domify-interest
>
>
>  
>

-- 
Geoffrey Mitchell
Programmer/Analyst
Home Decorator's Collection
314-684-1062

Re: [Domify-interest] status/direction of the code in CVS?

[toby c. <to...@ca...>]

On Tue, Oct 09, 2007 at 02:50:31PM -0500, Geoffrey Mitchell wrote:
> Toby, once I get the basics nailed down, if you'd like to contribute 
> some standard adapters for SQLDate and Date objects, that would be cool.

Sounds like a plan!

Re: [Domify-interest] status/direction of the code in CVS?

[Geoffrey M. <geo...@ho...>]

I started working on a couple of things:

1) I'm migrating the build to maven2...just because I feel like it.  :-)
2) I'm splitting the annotation stuff into a separate module, which will 
be packaged seperately, and can be used or not used as you see fit (I 
also intend to add an annotation for specifying an adapter for a field, 
in addition to the basic mechanism of registering adapters by class).  
The core module will continue to be jvm 1.4 compatible.

Once this is accomplished, I will start working on the plugin 
mechanism...which, actually, should be rather easy.

Toby, once I get the basics nailed down, if you'd like to contribute 
some standard adapters for SQLDate and Date objects, that would be cool.

On an interesting side note, I happened to look at the 
domify.sourceforge.net web page and it says on there (last updated in 
2002 or so) that a future version will include pluggable adapters.  
Heh.  I guess it finally will.  :-)

Thanks!
Geoff

toby cabot wrote:

>>I'll try to work on it tonight or tomorrow (and get HEAD building as well).
>>    
>>
>
>Cool, thanks.  If you want to delegate some of the work please let me
>know.
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc.
>Still grepping through log files to find problems?  Stop.
>Now Search log events and configuration files using AJAX and a browser.
>Download your FREE copy of Splunk now >> http://get.splunk.com/
>_______________________________________________
>Domify-interest mailing list
>Dom...@li...
>https://lists.sourceforge.net/lists/listinfo/domify-interest
>
>
>  
>

-- 
Geoffrey Mitchell
Programmer/Analyst
Home Decorator's Collection
314-684-1062

Re: [Domify-interest] status/direction of the code in CVS?

[toby c. <to...@ca...>]

> I'll try to work on it tonight or tomorrow (and get HEAD building as well).

Cool, thanks.  If you want to delegate some of the work please let me
know.

Re: [Domify-interest] status/direction of the code in CVS?

[Geoffrey M. <geo...@ho...>]

>yup, but I'd prefer to have the date represented in a standard format.
>Doesn't toString() vary by locale, etc?
>
>  
>
Probably true.

>That's a good idea.  I've used another tool that's similar to Domify
>called Skaringa that allows you to plug in custom handlers and that
>feature has come in handy.
>
>Looks like Domify stores the list of "stringified" classes in the
>DOMAdapter class and dips into it from the
>ElementAdapter.getNodeListAdapter().  We could add a
>DOMAdapter.findAdapter() method that returns a NodeList or null.
>getNodeListAdapter() could look to see if there's a specific adapter
>or else fall back to the existing logic.
>
>We could probably write a new DOMAdapter.stringify() method that used
>the new mechanism, to keep back-compatibility.
>
>Is this along the lines of what you were thinking?
>
>  
>
Yep, that's more or less what I was thinking.

I'll try to work on it tonight or tomorrow (and get HEAD building as well).

Geoff


-- 
Geoffrey Mitchell
Programmer/Analyst
Home Decorator's Collection
314-684-1062

Re: [Domify-interest] status/direction of the code in CVS?

[toby c. <to...@ca...>]

> One solution would be to use the already existing 
> DOMAdapter.stringify(...) mechanism to specify that java.sql.Date 
> objects should be serialized as their string representations. 

yup, but I'd prefer to have the date represented in a standard format.
Doesn't toString() vary by locale, etc?

> I definitely see merit in both ideas.  I'm wondering if a more general 
> "custom handler" mechanism would have more value than a couple of date 
> hacks.  Similar to the "stringify" mechanism, you could specify a custom 
> handler for a specific class (strinigify would become a special case of 
> a custom handler), that returned the element representing the class, and 
> could represent it however you wanted.  Perhaps this solves the more 
> generalized case of both problems?

That's a good idea.  I've used another tool that's similar to Domify
called Skaringa that allows you to plug in custom handlers and that
feature has come in handy.

Looks like Domify stores the list of "stringified" classes in the
DOMAdapter class and dips into it from the
ElementAdapter.getNodeListAdapter().  We could add a
DOMAdapter.findAdapter() method that returns a NodeList or null.
getNodeListAdapter() could look to see if there's a specific adapter
or else fall back to the existing logic.

We could probably write a new DOMAdapter.stringify() method that used
the new mechanism, to keep back-compatibility.

Is this along the lines of what you were thinking?

Thanks,
Toby

Re: [Domify-interest] status/direction of the code in CVS?

[Geoffrey M. <geo...@ho...>]

>Domify works well, so I guess it's no surprise that it doesn't have a
>lot of churn.  I was thinking about mucking around in a couple of
>things, though, so please let me know if I'm too far off base.  I've
>got one problem and one potential enhancement.  The problem is
>processing of Date classes (java.util and java.sql).  java.sql.Date
>has the obnoxious property of throwing an exception in getHours(),
>which has already been reported.  I figured that it would be pretty
>straightforward to catch the exception so you wouldn't get hours but
>you'd get the other data.
>
>  
>
Yep, that really annoyed me about java.sql.Date.  It is our policy to 
make darn good and sure that java.sql.Date objects are not passed out of 
the data access layer, precicely for that reason.

One solution would be to use the already existing 
DOMAdapter.stringify(...) mechanism to specify that java.sql.Date 
objects should be serialized as their string representations. 

>The problem with both Date classes is that the domified output isn't
>all that useful so I've ended up in a few cases having to format a
>Date into a string in Java and then use that in my xslt.  My idea was
>to handle Date classes specially by including another element that
>contains an XML schema-formatted representation of the date, in
>addition to the other elements (for back-compatibility).  There seem
>to be xslt bits out there to reformat XSD-format dates.[1]
>
>'frinstance, currently the output looks something like:
>
><rcvTime>
> <date>5</date>
> <hours>14</hours>
> <minutes>42</minutes>
> <month>9</month>
> <seconds>18</seconds>
> <time>1191609738061</time>
> <year>107</year>
> <day>5</day>
> <timezoneOffset>240</timezoneOffset>
></rcvTime>
>
>It might be more useful if there were another element like:
>
> <isoFormat>2007-10-04T14:42:18-0400<isoFormat>
>
>... as a child of the rcvTime element.
>
>  
>
Again, you could use stringify if the toString output works for you. 

>If you think that these ideas are worthwhile then I can start to mess
>around in the code, starting from the 1.1.1 tag.
>
>  
>
I definitely see merit in both ideas.  I'm wondering if a more general 
"custom handler" mechanism would have more value than a couple of date 
hacks.  Similar to the "stringify" mechanism, you could specify a custom 
handler for a specific class (strinigify would become a special case of 
a custom handler), that returned the element representing the class, and 
could represent it however you wanted.  Perhaps this solves the more 
generalized case of both problems?


Thanks a lot for your interest in the project! 

Geoff

-- 
Geoffrey Mitchell
Programmer/Analyst
Home Decorator's Collection
314-684-1062

Re: [Domify-interest] status/direction of the code in CVS?

[toby c. <to...@ca...>]

On Fri, Oct 05, 2007 at 10:16:23AM -0500, Geoffrey Mitchell wrote:
> The intent is definitely to maintain 1.4 support.
> 
> For now, I would suggest that you checkout the v1-1-1 tag.  That will 
> give you the code from the most recent release.  I believe that the only 
> change since then was the addition of the 1.5 specific code you mentioned. 

Cool, thanks, will do.

> I will try to go in and get the build working again sometime in the next 
> week or two.

Thanks!

> Domify has definitely not been under active development for a long 
> time.  The project had been dormant since 2002 when I took it over last 
> year to fix some problems related to Java 5 Enums.

Domify works well, so I guess it's no surprise that it doesn't have a
lot of churn.  I was thinking about mucking around in a couple of
things, though, so please let me know if I'm too far off base.  I've
got one problem and one potential enhancement.  The problem is
processing of Date classes (java.util and java.sql).  java.sql.Date
has the obnoxious property of throwing an exception in getHours(),
which has already been reported.  I figured that it would be pretty
straightforward to catch the exception so you wouldn't get hours but
you'd get the other data.

The problem with both Date classes is that the domified output isn't
all that useful so I've ended up in a few cases having to format a
Date into a string in Java and then use that in my xslt.  My idea was
to handle Date classes specially by including another element that
contains an XML schema-formatted representation of the date, in
addition to the other elements (for back-compatibility).  There seem
to be xslt bits out there to reformat XSD-format dates.[1]

'frinstance, currently the output looks something like:

<rcvTime>
 <date>5</date>
 <hours>14</hours>
 <minutes>42</minutes>
 <month>9</month>
 <seconds>18</seconds>
 <time>1191609738061</time>
 <year>107</year>
 <day>5</day>
 <timezoneOffset>240</timezoneOffset>
</rcvTime>

It might be more useful if there were another element like:

 <isoFormat>2007-10-04T14:42:18-0400<isoFormat>

... as a child of the rcvTime element.

If you think that these ideas are worthwhile then I can start to mess
around in the code, starting from the 1.1.1 tag.

Thanks,
Toby

[1] http://xsltsl.sourceforge.net/date-time.html, 
    http://www.exslt.org/date/functions/format-date/index.html

Re: [Domify-interest] status/direction of the code in CVS?

[Geoffrey M. <geo...@ho...>]

The intent is definitely to maintain 1.4 support.

For now, I would suggest that you checkout the v1-1-1 tag.  That will 
give you the code from the most recent release.  I believe that the only 
change since then was the addition of the 1.5 specific code you mentioned. 

I will try to go in and get the build working again sometime in the next 
week or two.

Domify has definitely not been under active development for a long 
time.  The project had been dormant since 2002 when I took it over last 
year to fix some problems related to Java 5 Enums.



Nicolas Marchildon wrote:

>toby cabot a écrit :
>  
>
>>I'm using Maverick/Domify on a project and am starting to poke around
>>in the code so I checked out the head from cvs and built it. It looks
>>as if things are in an "in between" state now - the ant script
>>specifies 1.4 source and target but there's some 1.5 code in the tree
>>so the build fails. The workaround is easy enough, just tell ant to
>>use 1.5 for the source and target.
>>    
>>
>
>That may be because we added support for the @HiddenNode annotation.
>
>  
>
>>Is Domify moving to require 1.5? I'm using it in 1.4 projects so I'd
>>prefer that it not require 1.5 (or maybe have a 1.4 support branch)
>>but I'm just one user :)
>>    
>>
>
>I don't think the project is actively being maintained. Perhaps you can
>fetch an older version from CVS and go from there, creating a branch if
>you wish so, once you got commit access from the project admins.
>
>  
>
>------------------------------------------------------------------------
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc.
>Still grepping through log files to find problems?  Stop.
>Now Search log events and configuration files using AJAX and a browser.
>Download your FREE copy of Splunk now >> http://get.splunk.com/
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Domify-interest mailing list
>Dom...@li...
>https://lists.sourceforge.net/lists/listinfo/domify-interest
>  
>

-- 
Geoffrey Mitchell
Programmer/Analyst
Home Decorator's Collection
314-684-1062

Re: [Domify-interest] status/direction of the code in CVS?

[Nicolas M. <ni...@ma...>]

toby cabot a =E9crit :
> I'm using Maverick/Domify on a project and am starting to poke around
> in the code so I checked out the head from cvs and built it. It looks
> as if things are in an "in between" state now - the ant script
> specifies 1.4 source and target but there's some 1.5 code in the tree
> so the build fails. The workaround is easy enough, just tell ant to
> use 1.5 for the source and target.

That may be because we added support for the @HiddenNode annotation.

> Is Domify moving to require 1.5? I'm using it in 1.4 projects so I'd
> prefer that it not require 1.5 (or maybe have a 1.4 support branch)
> but I'm just one user :)

I don't think the project is actively being maintained. Perhaps you can
fetch an older version from CVS and go from there, creating a branch if
you wish so, once you got commit access from the project admins.

--=20
Nicolas Marchildon
Software Developer
Sherpa Solutions
http://sherpa-solutions.com/
Office: +1 514 382-6762
Cell: +1 514 578-4775
Jabber IM: ni...@li...

[Domify-interest] status/direction of the code in CVS?

[toby c. <to...@ca...>]

Hi Folks,

I'm using Maverick/Domify on a project and am starting to poke around
in the code so I checked out the head from cvs and built it.  It looks
as if things are in an "in between" state now - the ant script
specifies 1.4 source and target but there's some 1.5 code in the tree
so the build fails.  The workaround is easy enough, just tell ant to
use 1.5 for the source and target.

Is Domify moving to require 1.5?  I'm using it in 1.4 projects so I'd
prefer that it not require 1.5 (or maybe have a 1.4 support branch)
but I'm just one user :)

Thanks,
Toby

Re: [Domify-interest] domify not working?

[Geoffrey M. <geo...@ho...>]

Jay,

Could you share the code you are using to convert your object to xml?

I do the following:

import org.infohazard.domify.DOMAdapter;
import org.w3c.dom.Node;

import javax.xml.transform.*;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.stream.StreamResult;
import javax.xml.transform.stream.StreamSource;
import java.io.*;

TransformerFactory tf = TransformerFactory.newInstance();
Transformer transformer = transformerFactory.newTransformer(source);  // 
Create identity transformer

DOMAdapter domAdapter = new DOMAdapter();
Node node = domAdapter.adapt(o, rootName);
DOMSource source = new DOMSource(node);

StreamResult result = new StreamResult(outputStream);
transformer.transform(source, result);  // Write xml to outputStream

I think some of the "test" code included with the Domify distribution is 
very out of date.  I should update it, but it has not been my focus.

I hope that helps....
Geoff


Jahanzeb Abdur-Rahman wrote:

> Hey there,
>
> Following on from last post ...
>
>  
>
> If I use domify to convert a collection of beans to xml .. I get only
>
>  
>
> <?xml version="1.0" encoding="utf-8"?>
>
>  
>
> . . .
>
>  
>
> My test bean look like this:
>
> * *
>
> *public* *class* TestXSLTModelBean *extends* Object {
>
>      
>
>       *private* Integer id = 101;
>
>       *private* String string= *this*.getClass().getName();
>
>      
>
>       *public* Integer getId() {
>
>             *return* id;
>
>       }
>
>       *public* *void* setId(Integer id) {
>
>             *this*.id = id;
>
>       }
>
>       *public* String getString() {
>
>             *return* string;
>
>       }
>
>       *public* *void* setString(String string) {
>
>             *this*.string = string;
>
>       }
>
> }
>
>  
>
> I think that the issue is that the top level 
> DocumentAdapter.getChildNodes() doesn't exist... if I change this in 
> the source to and implement getChildNodes() to return 
> root.getChildNodes() then when I do the serialization I get.:
>
>  
>
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>
> <item key="model" type="com.visitlondon.test.xslt.TestXSLTModelBean">
>
> <id>101</id>
>
> <string>com.visitlondon.test.xslt.TestXSLTModelBean</string>
>
> </item>
>
> <item key="model2" type="com.visitlondon.test.xslt.TestXSLTModelBean">
>
> <id>101</id>
>
> <string>com.visitlondon.test.xslt.TestXSLTModelBean</string>
>
> </item>
>
>  
>
> But this xml is not well formed - there needs to be an enclosing 
> <items> tag which encloses the <item> tags.. so should look like this:
>
>  
>
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>
> <items>
>
> <item key="model" type="com.visitlondon.test.xslt.TestXSLTModelBean">
>
> <id>101</id>
>
> <string>com.visitlondon.test.xslt.TestXSLTModelBean</string>
>
> </item>
>
> <item key="model2" type="com.visitlondon.test.xslt.TestXSLTModelBean">
>
> <id>101</id>
>
> <string>com.visitlondon.test.xslt.TestXSLTModelBean</string>
>
> </item>
>
> </items>
>
>  
>
> Any ideas???
>
>  
>
> Thanks,
>
> Jahanzeb
>
>  
>
>  
>
>  
> Jahanzeb Abdur-Rahman
>
> Visit London
> 6th Floor,
> 2 More London Riverside, London SE1 2RR
>  
> Tel: 
> Fax: +44 (0)20 7234 5752
>  
> www.visitlondon.com <http://www.visitlondon.com> 
>  
>   Please don't print this e-mail unless you really need to.
>  
> 'Visit London Limited' is registered in England under No.761149;
> Registered Office: Visit London, 2 More London Riverside, London SE1 2RR.
>  
> Visit London is the official visitor organisation for London. Visit 
> London is partly funded by Partnership, the Mayor's London Development 
> Agency and London Councils.
> The information contained in this e-mail is confidential and intended 
> for the named recipient(s) only.  If you have received it in error, 
> please notify the sender immediately and then delete the message.  If 
> you are not the intended recipient, you must not use, disclose, copy 
> or distribute this email. The views expressed in this e-mail are those 
> of the individual and not of Visit London. We reserve the right to 
> read and monitor any email or attachment entering or leaving our 
> systems without prior notice.
>
>------------------------------------------------------------------------
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Microsoft
>Defy all challenges. Microsoft(R) Visual Studio 2005.
>http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Domify-interest mailing list
>Dom...@li...
>https://lists.sourceforge.net/lists/listinfo/domify-interest
>  
>

-- 
Geoffrey Mitchell
Programmer/Analyst
Home Decorator's Collection
314-684-1062

[Domify-interest] domify tests not working!

[Jahanzeb Abdur-R. <jah...@vi...>]

Hello Chaps,=20
Man, its been a looooong time since anyone posted here! I'm hoping that
this is still being monitored!

I'm unsuccessfully trying to use domify to convert my beans to xml -
what I get is a top level element but when I try and get some xml spit
out all I get is the xml header...=20

<?xml version=3D"1.0" encoding=3D"utf-8"?>

When I run the domify tests included with the domify 1.1.1 source code I
get the same thing.. what gives??

Thanks,
Jay
=20
Jahanzeb Abdur-Rahman

Visit London
6th Floor,
2 More London Riverside, London SE1 2RR
=20
Tel: =20
Fax: +44 (0)20 7234 5752

=20
www.visitlondon.com=20
=20
  Please don't print this e-mail unless you really need to.
=20
'Visit London Limited' is registered in England under No.761149;
Registered Office: Visit London, 2 More London Riverside, London SE1 =
2RR.
=20
Visit London is the official visitor organisation for London. Visit =
London is partly funded by Partnership, the Mayor's London Development =
Agency and London Councils.
The information contained in this e-mail is confidential and intended =
for the named recipient(s) only.  If you have received it in error, =
please notify the sender immediately and then delete the message.  If =
you are not the intended recipient, you must not use, disclose, copy or =
distribute this email. The views expressed in this e-mail are those of =
the individual and not of Visit London. We reserve the right to read and =
monitor any email or attachment entering or leaving our systems without =
prior notice.

Re: [Domify-interest] Domify & Xalan

[Constantin, S. (S. - c. <SCo...@ex...>]

This is not a problem with Domify itself but with Xalan.  The issue is
Xalan traverses the entire DOM before transforming the object using the
XSL.  This will cause Domify to visit every variable in the object even
if the XSL does not reference it.  If the object you are adapting with
Domify has many variables that has the potential to be very
innefficient.  I was hoping someone else has come across this issue and
found a solution.
=20
Steve

  _____ =20

From: dom...@li...
[mailto:dom...@li...] On Behalf Of
Geoffrey Mitchell
Sent: Thursday, October 19, 2006 2:28 PM
To: dom...@li...
Subject: Re: [Domify-interest] Domify & Xalan


Hi Steve.  Believe it or not, someone *is* listening.  :-)

>From the referenced bug report, I'm unclear exactly what the issue is
as it pertains to domify.  In the example in the bug report, the tree
hierearchy appears to contain a circular reference.  There is a known
limitation with domify that object trees containing circular references
will not work.  I have not addressed it because nobody has really
complained and I've always been able to work around it in my own code.

Is this the problem you are having, or is it something else?

Constantin, Steve (STL) - contr wrote:=20

	It has been a couple of years since someone has posted to this
mailing list so I hope there are still people paying attention to it.  I
am very interested in using domify in my XML/XSLT based application but
I have come across an issue that is documented here:
http://issues.apache.org/bugzilla/show_bug.cgi?id=3D13579
<http://issues.apache.org/bugzilla/show_bug.cgi?id=3D13579> .  Xalan
traverses the complete DOM tree which effectively makes the lazy
instantiation domify provides useless.  I am looking into DOM2DTM2 but
it appears that effort has been abandoned. Has anyone else come across
this issue and did you find any solution?

	Thanks,=20

	Steve=20
******* Confidentiality Notice *******
This email, its electronic document attachments, and the contents of its =
website linkages may contain confidential health information.  This =
information is intended solely for use by the individual or entity to =
whom it is addressed.  If you have received this information in error, =
please notify the sender immediately and arrange for the prompt =
destruction of the material and any accompanying attachments.

[Domify-interest] Domify & Xalan

[Constantin, S. (S. - c. <SCo...@ex...>]

It has been a couple of years since someone has posted to this mailing
list so I hope there are still people paying attention to it.  I am very
interested in using domify in my XML/XSLT based application but I have
come across an issue that is documented here:
http://issues.apache.org/bugzilla/show_bug.cgi?id=3D13579.  Xalan
traverses the complete DOM tree which effectively makes the lazy
instantiation domify provides useless.  I am looking into DOM2DTM2 but
it appears that effort has been abandoned. Has anyone else come across
this issue and did you find any solution?

Thanks,

Steve
******* Confidentiality Notice *******
This email, its electronic document attachments, and the contents of its =
website linkages may contain confidential health information.  This =
information is intended solely for use by the individual or entity to =
whom it is addressed.  If you have received this information in error, =
please notify the sender immediately and arrange for the prompt =
destruction of the material and any accompanying attachments.

[Domify-interest] will domify work with Personal Profile?

[Nikita <ni...@wo...>]

Hi,

I just came accross Domify and I'd like to use it in a Personal Profile 
application that will run on a J9 VM (on Dell Axim most likely). Could 
you please tell me whether domify depends on any packages that are *not* 
found in Personal Profile (which is kind of j2se 1.2/1.3 hybrid w/ no 
Swing)?

thanks a lot

-nikita