xmlceclipse-development — Discussions and questions related to the development of xmlceclipse

[XmlcEclipse-development] Ok, Please Try 0.0.4

[David C. <dc...@ma...>]

Thanks.

Re: [XmlcEclipse-development] XmlcEclipse 0.0.2

[Garth D. <ga...@ut...>]

It's getting better...  I got all the files I needed... 

When I opened my project I got an "Errors during build." exception
and when I went to the properties page I got a 
"Unable to create selected properties page 
Reason:
Plug-in net.sourceforge.xmlceclipse.core was unable to load class
net.sourceforge.xmleclipse.ui.properties.ProjectPropertiesPage."

Sounds like you missed a class in the xmlceclipse.jar or the jar's not in 
the plugin.xml...

I'll have closer look tomorrow, gotta go to work.

-G


On Wed, 15 Jan 2003 19:03:22 -0500 David Corbin wrote:

> I've release a new version for installation using the Update Manager.  
> There are no new features in 0.0.3, but it should be built correctly ;)  
> Would someon please test it and tell me I did it right.  Thanks.
> 
> 
> Garth Dahlstrom wrote:
> 
> >On Mon, 13 Jan 2003 20:29:19 -0500 David Corbin wrote:
> >
> >  
> >
> >>I'm pleased to announce a new release of XmlcEclipse, version 0.0.2.  
> >>The best way to install it is using the Eclipse Update Manager.  The 
> >>install URL is http://xmlceclipse.sourceforge.net/site.  Alternatively, 
> >>you can download the file from http://xmlceclipse.sourceforge.net
> >>
> >>David Corbin
> >>    
> >>
> >
> >It is still broken... 
> >
> >C:\Java\eclipse\plugins>dir xmlc*.* /s
> > Volume in drive C has no label.
> > Volume Serial Number is 54CF-1037
> >
> > Directory of
> C:\Java\eclipse\plugins\net.sourceforge.xmlceclipse.core_0.0.2
> >
> >01/14/2003  12:56 AM            47,759 xmlceclipse.jar
> >               1 File(s)         47,759 bytes
> >
> >There is no plugin.xml, there is also no \libs directory.  Eclipse
> >totally ingores it when I start up, no "enable XMLC", no properties
> >pages...
> >
> >I'll see if I can build a working one from the CVS and post 
> >it on the Wiki.
> >
> >Northern.CA ===--
> >http://www.northern.ca 
> >Canada's Search Engine
> >
> >
> >
> >
> >-------------------------------------------------------
> >This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
> >are you planning your Web Server Security? Click here to get a FREE
> >Thawte SSL guide and find the answers to all your  SSL security issues.
> >http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
> >_______________________________________________
> >Xmlceclipse-development mailing list
> >Xml...@li...
> >https://lists.sourceforge.net/lists/listinfo/xmlceclipse-development
> >
> >  
> >
> 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by: A Thawte Code Signing Certificate 
> is essential in establishing user confidence by providing assurance of 
> authenticity and code integrity. Download our Free Code Signing guide:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en
> _______________________________________________
> Xmlceclipse-development mailing list
> Xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlceclipse-development
> 



Northern.CA ===--
http://www.northern.ca 
Canada's Search Engine

Re: [XmlcEclipse-development] XmlcEclipse 0.0.2

[David C. <dc...@ma...>]

I've release a new version for installation using the Update Manager.  
There are no new features in 0.0.3, but it should be built correctly ;)  
Would someon please test it and tell me I did it right.  Thanks.


Garth Dahlstrom wrote:

>On Mon, 13 Jan 2003 20:29:19 -0500 David Corbin wrote:
>
>  
>
>>I'm pleased to announce a new release of XmlcEclipse, version 0.0.2.  
>>The best way to install it is using the Eclipse Update Manager.  The 
>>install URL is http://xmlceclipse.sourceforge.net/site.  Alternatively, 
>>you can download the file from http://xmlceclipse.sourceforge.net
>>
>>David Corbin
>>    
>>
>
>It is still broken... 
>
>C:\Java\eclipse\plugins>dir xmlc*.* /s
> Volume in drive C has no label.
> Volume Serial Number is 54CF-1037
>
> Directory of C:\Java\eclipse\plugins\net.sourceforge.xmlceclipse.core_0.0.2
>
>01/14/2003  12:56 AM            47,759 xmlceclipse.jar
>               1 File(s)         47,759 bytes
>
>There is no plugin.xml, there is also no \libs directory.  Eclipse
>totally ingores it when I start up, no "enable XMLC", no properties
>pages...
>
>I'll see if I can build a working one from the CVS and post 
>it on the Wiki.
>
>Northern.CA ===--
>http://www.northern.ca 
>Canada's Search Engine
>
>
>
>
>-------------------------------------------------------
>This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
>are you planning your Web Server Security? Click here to get a FREE
>Thawte SSL guide and find the answers to all your  SSL security issues.
>http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
>_______________________________________________
>Xmlceclipse-development mailing list
>Xml...@li...
>https://lists.sourceforge.net/lists/listinfo/xmlceclipse-development
>
>  
>

Re: [XmlcEclipse-development] XmlcEclipse 0.0.2

[Garth D. <ga...@ut...>]

On Tue, 14 Jan 2003 08:03:45 -0500 David Corbin wrote:

> Did you download it, or use the install manager?  I used the install 
> manager and it all seems to be working fine for me, though having looked 
> deeper, I have to admit I don't know why....
> 

I used the install manager, but the sf downloads page is the same
thing...   I don't know why it works for you (maybe your build
environment is hooked into your classpath somehow), without a plugin.xml
file and libs\*.* there's no way it will work for some one that has a
fresh install of eclipse.  Mind you installing just the .jar file would
work fine as an upgrade (at least until the UI events get changed in
plugin.xml -  i.e. next time a new properties page is added or something) 
cuz you'd already have an old copy of the eclipse stuff in there...

I deleted my \plugins\xmlceclipse folder before I started the updates
manager going...

Northern.CA ===--
http://www.northern.ca 
Canada's Search Engine

Re: [XmlcEclipse-development] XmlcEclipse 0.0.2

[David C. <dc...@ma...>]

Did you download it, or use the install manager?  I used the install 
manager and it all seems to be working fine for me, though having looked 
deeper, I have to admit I don't know why....

Garth Dahlstrom wrote:

>On Mon, 13 Jan 2003 20:29:19 -0500 David Corbin wrote:
>
>  
>
>>I'm pleased to announce a new release of XmlcEclipse, version 0.0.2.  
>>The best way to install it is using the Eclipse Update Manager.  The 
>>install URL is http://xmlceclipse.sourceforge.net/site.  Alternatively, 
>>you can download the file from http://xmlceclipse.sourceforge.net
>>
>>David Corbin
>>    
>>
>
>It is still broken... 
>
>C:\Java\eclipse\plugins>dir xmlc*.* /s
> Volume in drive C has no label.
> Volume Serial Number is 54CF-1037
>
> Directory of C:\Java\eclipse\plugins\net.sourceforge.xmlceclipse.core_0.0.2
>
>01/14/2003  12:56 AM            47,759 xmlceclipse.jar
>               1 File(s)         47,759 bytes
>
>There is no plugin.xml, there is also no \libs directory.  Eclipse
>totally ingores it when I start up, no "enable XMLC", no properties
>pages...
>
>I'll see if I can build a working one from the CVS and post 
>it on the Wiki.
>
>Northern.CA ===--
>http://www.northern.ca 
>Canada's Search Engine
>
>
>
>
>-------------------------------------------------------
>This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
>are you planning your Web Server Security? Click here to get a FREE
>Thawte SSL guide and find the answers to all your  SSL security issues.
>http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
>_______________________________________________
>Xmlceclipse-development mailing list
>Xml...@li...
>https://lists.sourceforge.net/lists/listinfo/xmlceclipse-development
>
>  
>

Re: [XmlcEclipse-development] XmlcEclipse 0.0.2

[Garth D. <ga...@ut...>]

On Mon, 13 Jan 2003 20:29:19 -0500 David Corbin wrote:
> you can download the file from http://xmlceclipse.sourceforge.net

Further details:
Get the unoffical plugin.xml fix from the link off
http://xmlceclipse.sourceforge.net or directly from 
http://www.northern.ca/forums/getfile.php?id=23

Extract to plugins\net.sourceforge.xmlceclipse.core_0.0.2\

Install xmlc 2.1 into the \libs folder under the that folder
(read the plugin readme.txt for details)

Restart Eclipse and you should be golden.

Northern.CA ===--
http://www.northern.ca 
Canada's Search Engine

Re: [XmlcEclipse-development] XmlcEclipse 0.0.2

[Garth D. <ga...@ut...>]

On Mon, 13 Jan 2003 20:29:19 -0500 David Corbin wrote:

> I'm pleased to announce a new release of XmlcEclipse, version 0.0.2.  
> The best way to install it is using the Eclipse Update Manager.  The 
> install URL is http://xmlceclipse.sourceforge.net/site.  Alternatively, 
> you can download the file from http://xmlceclipse.sourceforge.net
> 
> David Corbin

It is still broken... 

C:\Java\eclipse\plugins>dir xmlc*.* /s
 Volume in drive C has no label.
 Volume Serial Number is 54CF-1037

 Directory of C:\Java\eclipse\plugins\net.sourceforge.xmlceclipse.core_0.0.2

01/14/2003  12:56 AM            47,759 xmlceclipse.jar
               1 File(s)         47,759 bytes

There is no plugin.xml, there is also no \libs directory.  Eclipse
totally ingores it when I start up, no "enable XMLC", no properties
pages...

I'll see if I can build a working one from the CVS and post 
it on the Wiki.

Northern.CA ===--
http://www.northern.ca 
Canada's Search Engine

[XmlcEclipse-development] XmlcEclipse 0.0.2

[David C. <dc...@ma...>]

I'm pleased to announce a new release of XmlcEclipse, version 0.0.2.  
The best way to install it is using the Eclipse Update Manager.  The 
install URL is http://xmlceclipse.sourceforge.net/site.  Alternatively, 
you can download the file from http://xmlceclipse.sourceforge.net

David Corbin

Re: [XmlcEclipse-development] Changes.

[David C. <dc...@ma...>]

Yes it is,  I'll apply them today.

Garth Dahlstrom wrote:

>>>Garth - I took a look at your patches, and it would be a WHOLE lot 
>>>easier if they were submitted as actualy "patch" files.
>>>      
>>>
>>Hmm... strange... before I was not able to get view the repository
>>anonymously through eclipse -> hence one of the reasons I didn't do patch 
>>format files...  I will try to figure out how to use this for diffs now
>>that it works...
>>    
>>
>
>Turns out Eclipse is quite good at this stuff, it was a whole lot easier
>then I thought, so now all the patches I submitted before have diffs.
>
>TTYL,
>
>-Garth
>
>Northern.CA ===--
>http://www.northern.ca 
>Canada's Search Engine
>
>
>
>
>-------------------------------------------------------
>This SF.NET email is sponsored by:
>SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
>http://www.vasoftware.com
>_______________________________________________
>Xmlceclipse-development mailing list
>Xml...@li...
>https://lists.sourceforge.net/lists/listinfo/xmlceclipse-development
>
>  
>

Re: [XmlcEclipse-development] Tried to build the CVS, Implements class is missing...

[David C. <dc...@ma...>]

Ach!  It's there now.  I fell pray to a CVS plugin "bug".  I renamed a 
class after "Add to source control".  I ususally use perforce for source 
control, and it would have kept the new file under source control.

Garth Dahlstrom wrote:

>I checked out the CVS and tried to build it, I get a fatal on the 
>
>addWidget(new Implements());
>
>In ResourcePropertyPage.java
>
>Where is Implements imported from? (or is it a new class that hasn't been 
>added to the CVS yet?)
>
>Cheers,
>
>-Garth
>
>Northern.CA ===--
>http://www.northern.ca 
>Canada's Search Engine
>
>
>
>
>-------------------------------------------------------
>This SF.NET email is sponsored by:
>SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
>http://www.vasoftware.com
>_______________________________________________
>Xmlceclipse-development mailing list
>Xml...@li...
>https://lists.sourceforge.net/lists/listinfo/xmlceclipse-development
>
>  
>

[XmlcEclipse-development] Tried to build the CVS, Implements class is missing...

[Garth D. <ga...@ut...>]

I checked out the CVS and tried to build it, I get a fatal on the 

addWidget(new Implements());

In ResourcePropertyPage.java

Where is Implements imported from? (or is it a new class that hasn't been 
added to the CVS yet?)

Cheers,

-Garth

Northern.CA ===--
http://www.northern.ca 
Canada's Search Engine

Re: [XmlcEclipse-development] Changes.

[Garth D. <ga...@ut...>]

> > Garth - I took a look at your patches, and it would be a WHOLE lot 
> > easier if they were submitted as actualy "patch" files.
> 
> Hmm... strange... before I was not able to get view the repository
> anonymously through eclipse -> hence one of the reasons I didn't do patch 
> format files...  I will try to figure out how to use this for diffs now
> that it works...

Turns out Eclipse is quite good at this stuff, it was a whole lot easier
then I thought, so now all the patches I submitted before have diffs.

TTYL,

-Garth

Northern.CA ===--
http://www.northern.ca 
Canada's Search Engine

Re: [XmlcEclipse-development] Changes.

[Garth D. <ga...@ut...>]

> Finally! I got my code working again, and I've committed them.  Two >
new features:
> 
> 1) You can now specify "Implements" in the properties (should be fully 
> qualified class name), or leave it blank.
> 2) You can now have different properties on differnt folders underneath 
> an Xmlc source folder.

That is good news indeed! 
 
> Garth - I took a look at your patches, and it would be a WHOLE lot 
> easier if they were submitted as actualy "patch" files.

Hmm... strange... before I was not able to get view the repository
anonymously through eclipse -> hence one of the reasons I didn't do patch 
format files...  I will try to figure out how to use this for diffs now
that it works...

> I'll probably build a new release either Sunday or Monday.

That's great news.   I'm going to fetch down what you just did and see if 
it helps me in what I'm trying to do (import a Barracuda sample project
using Eclipse without relying on Ant to build it).

> The next "big feature" I'll look into will be proper error 
> handling/reporting.

Good stuff.


Northern.CA ===--
http://www.northern.ca 
Canada's Search Engine

[XmlcEclipse-development] Changes.

[David C. <dc...@ma...>]

Finally! I got my code working again, and I've committed them.  Two new 
features:

1) You can now specify "Implements" in the properties (should be fully 
qualified class name), or leave it blank.
2) You can now have different properties on differnt folders underneath 
an Xmlc source folder.

Garth - I took a look at your patches, and it would be a WHOLE lot 
easier if they were submitted as actualy "patch" files.

I'll probably build a new release either Sunday or Monday.

The next "big feature" I'll look into will be proper error 
handling/reporting.

David

Re: [XmlcEclipse-development] So how goes...

[David C. <dc...@ma...>]

I thought I was going to make "one simple change", but it seems to not 
be so simple.  I'm reluctant to back out my work.  Hopefully I'll make 
some progress tonight...

Garth Dahlstrom wrote:

>Wondering how it's going?  
>
>Since I posted it to your Wiki (Jan 7), the CVS version of 
>your plug-in has been downloaded 41 times, and about 7 folks 
>downloaded the broken 0.0.1 release off of SF.
>
>Anyway, if you commit some changes to your archive, let me know
>and I'll give it a good through testing...
>
>-Garth
>
>Northern.CA ===--
>http://www.northern.ca 
>Canada's Search Engine
>
>
>
>
>-------------------------------------------------------
>This SF.NET email is sponsored by:
>SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
>http://www.vasoftware.com
>_______________________________________________
>Xmlceclipse-development mailing list
>Xml...@li...
>https://lists.sourceforge.net/lists/listinfo/xmlceclipse-development
>
>  
>

[XmlcEclipse-development] So how goes...

[Garth D. <ga...@ut...>]

Wondering how it's going?  

Since I posted it to your Wiki (Jan 7), the CVS version of 
your plug-in has been downloaded 41 times, and about 7 folks 
downloaded the broken 0.0.1 release off of SF.

Anyway, if you commit some changes to your archive, let me know
and I'll give it a good through testing...

-Garth

Northern.CA ===--
http://www.northern.ca 
Canada's Search Engine

Re: [XmlcEclipse-development] XMLC not generating .java files

[David C. <dc...@ma...>]

Garth Dahlstrom wrote:

>On Mon, 06 Jan 2003 18:14:47 -0500 David Corbin wrote:
>
>  
>
>>>popup with error messages that tell the user the problem...
>>> 
>>>
>>>      
>>>
>>That can be done too.  Let me know when you have a patch :)
>>    
>>
>
>I submitted a bunch of patches...  I think they are all crapily 
>done, but then I don't know java very well yet :)
>  
>
I'll look at them once I finish the current one I'm working on....

>  
>
>>>My problems were parser related... (maybe a drop down box with available
>>>parsers would be cool along with a label suggesting HTML or XML)...
>>>
>>>      
>>>
>>That was planned, but my first step has always been capabilities (usage) 
>>and second is UI (ease of use)
>>
>>    
>>
>
>I hope you get a chance do a little gui improving for the next release,
>or the release after...
>  
>
Probably the release after...

>  
>
>>>This was caused by having my parser set as xerces, when it should have
>>>been jtidy or swing:
>>>      
>>>
>
>I hopefully got this one too, should pop an error dialog 
>in addition to doing a printstacktrace (fingers crossed) if it
>craps out anywhere in XMLCCompiler.java
>
Actually, I've done that one.

>
>  
>
>>>>This was caused by having my parser setting my parser as jtidy (the UI
>>>>        
>>>>
>>>does not accept tidy):
>>>      
>>>
>
>One of my patches fixes this...
>
>
>Northern.CA ===--
>http://www.northern.ca 
>Canada's Search Engine
>
>
>
>
>-------------------------------------------------------
>This SF.NET email is sponsored by:
>SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
>http://www.vasoftware.com
>_______________________________________________
>Xmlceclipse-development mailing list
>Xml...@li...
>https://lists.sourceforge.net/lists/listinfo/xmlceclipse-development
>
>  
>

Re: [XmlcEclipse-development] XMLC not generating .java files

[Garth D. <ga...@ut...>]

On Mon, 06 Jan 2003 18:14:47 -0500 David Corbin wrote:

> >popup with error messages that tell the user the problem...
> >  
> >
> That can be done too.  Let me know when you have a patch :)

I submitted a bunch of patches...  I think they are all crapily 
done, but then I don't know java very well yet :)

> >My problems were parser related... (maybe a drop down box with available
> >parsers would be cool along with a label suggesting HTML or XML)...
> >
> That was planned, but my first step has always been capabilities (usage) 
> and second is UI (ease of use)
> 

I hope you get a chance do a little gui improving for the next release,
or the release after...

> >This was caused by having my parser set as xerces, when it should have
> >been jtidy or swing:

I hopefully got this one too, should pop an error dialog 
in addition to doing a printstacktrace (fingers crossed) if it
craps out anywhere in XMLCCompiler.java

> > >This was caused by having my parser setting my parser as jtidy (the UI
> >does not accept tidy):

One of my patches fixes this...


Northern.CA ===--
http://www.northern.ca 
Canada's Search Engine

Re: [XmlcEclipse-development] XMLC not generating .java files

[David C. <dc...@ma...>]

Garth Dahlstrom wrote:

>On Mon, 06 Jan 2003 17:06:42 EST Garth Dahlstrom wrote:
>
>  
>
>>Any ideas as to what might be causing the xmlc compiler not 
>>to generate the .java output files (it makes the directory output
>>directory and the package name subdir ok)... 
>>    
>>
>
>I figured out how to debug the UI, its too bad that the exceptions don't
>popup with error messages that tell the user the problem...
>  
>
That can be done too.  Let me know when you have a patch :)

>But setting the parser to Swing seems to get me some .java files... Yay!
>
>My problems were parser related... (maybe a drop down box with available
>parsers would be cool along with a label suggesting HTML or XML)...
>
That was planned, but my first step has always been capabilities (usage) 
and second is UI (ease of use)

>This was caused by having my parser set as xerces, when it should have
>been jtidy or swing:
>
>-class xmlc-debug.helloHtml -keep -nocompile -sourceout
>C:\Java\eclipse\runtime-workspace\xmlc-debug\xmlc-java -parser xerces
>-domfactory org.enhydra.xml.xhtml.XHTMLDomFactory
>C:\Java\eclipse\runtime-workspace\xmlc-debug\xmlc\hello.html 
>org.enhydra.xml.xmlc.XMLCException: Document appears to be an HTML
>document; the xerces parser only supports XML (does the document start
>with `<?xml ... ?>'?):
>C:\Java\eclipse\runtime-workspace\xmlc-debug\xmlc\hello.html
>	at org.enhydra.xml.xmlc.compiler.Parse.setupParser(Parse.java:108)
>	at org.enhydra.xml.xmlc.compiler.Parse.parse(Parse.java:222)
>	at org.enhydra.xml.xmlc.compiler.Compiler.parsePage(Compiler.java:109)
>	at org.enhydra.xml.xmlc.compiler.Compiler.compile(Compiler.java:218)
>	at org.enhydra.xml.xmlc.commands.xmlc.XMLC.compile(XMLC.java:132)
>	at net.sourceforge.xmlceclipse.core.XmlcBuilder.build(XmlcBuilder.java:182)
>	at net.sourceforge.xmlceclipse.core.XmlcBuilder.access$0(XmlcBuilder.java:165)
>	at
>net.sourceforge.xmlceclipse.core.XmlcBuilder$MyBuildVisitor.visit(XmlcBuil
>der.java:235)
>	at
>org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:71)
>	at
>org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
>	at
>org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
>	at
>org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:52)
>	at
>net.sourceforge.xmlceclipse.core.XmlcBuilder.incrementalBuild(XmlcBuilder.
>java:275)
>	at net.sourceforge.xmlceclipse.core.XmlcBuilder.build(XmlcBuilder.java:257)
>	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:384)
>	at
>org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.ja
>va:852)
>	at org.eclipse.core.runtime.Platform.run(Platform.java:413)
>	at
>org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:120)
>	at
>org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:176)
>	at
>org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:186)
>	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:146)
>	at
>org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.ja
>va:852)
>	at org.eclipse.core.runtime.Platform.run(Platform.java:413)
>	at
>org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:160)
>	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:211)
>	at
>org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:861)
>	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1569)
>	at
>org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperati
>on.java:79)
>	at
>org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalConte
>xt.java:95)
>
>This was caused by having my parser setting my parser as jtidy (the UI
>does not accept tidy):
>
>-class xmlc-debug.hello -keep -nocompile -sourceout
>C:\Java\eclipse\runtime-workspace\xmlc-debug\xmlc-java -parser jtidy
>-domfactory org.enhydra.xml.xmlc.dom.lazydom.LazyHTMLDomFactory
>C:\Java\eclipse\runtime-workspace\xmlc-debug\xmlc\hello.html 
>org.enhydra.xml.xmlc.XMLCException: Invalid ParserType: "jtidy", expected 
>of "xerces", "tidy", or "swing"
>	at
>org.enhydra.xml.xmlc.commands.xmlc.ParserCmdOptions$ParserOption.parse(Par
>serCmdOptions.java:58)
>	at
>org.enhydra.xml.xmlc.commands.options.OptionsParser.parseCmdOption(Options
>Parser.java:156)
>	at
>org.enhydra.xml.xmlc.commands.options.OptionsParser.parseOptions(OptionsPa
>rser.java:169)
>	at
>org.enhydra.xml.xmlc.commands.options.OptionsParser.parse(OptionsParser.ja
>va:323)
>	at
>org.enhydra.xml.xmlc.commands.xmlc.XMLCOptionsParser.parse(XMLCOptionsPars
>er.java:75)
>	at org.enhydra.xml.xmlc.commands.xmlc.XMLC.parseArgs(XMLC.java:101)
>	at org.enhydra.xml.xmlc.commands.xmlc.XMLC.compile(XMLC.java:121)
>	at net.sourceforge.xmlceclipse.core.XmlcBuilder.build(XmlcBuilder.java:182)
>	at net.sourceforge.xmlceclipse.core.XmlcBuilder.access$0(XmlcBuilder.java:165)
>	at
>net.sourceforge.xmlceclipse.core.XmlcBuilder$MyBuildVisitor.visit(XmlcBuil
>der.java:231)
>	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:56)
>	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:72)
>	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:72)
>	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:38)
>	at
>net.sourceforge.xmlceclipse.core.XmlcBuilder.fullBuild(XmlcBuilder.java:267)
>	at net.sourceforge.xmlceclipse.core.XmlcBuilder.build(XmlcBuilder.java:246)
>	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:384)
>	at
>org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.ja
>va:852)
>	at org.eclipse.core.runtime.Platform.run(Platform.java:413)
>	at
>org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:120)
>	at
>org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:176)
>	at
>org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:186)
>	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:146)
>	at
>org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.ja
>va:852)
>	at org.eclipse.core.runtime.Platform.run(Platform.java:413)
>	at
>org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:160)
>	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:232)
>	at org.eclipse.core.internal.resources.Project.build(Project.java:87)
>	at org.eclipse.ui.actions.BuildAction.invokeOperation(BuildAction.java:156)
>	at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:111)
>	at org.eclipse.ui.actions.WorkspaceAction$1.execute(WorkspaceAction.java:268)
>	at
>org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOpera
>tion.java:65)
>	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1564)
>	at
>org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperati
>on.java:79)
>	at
>org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalConte
>xt.java:95)
>Caused by: java.lang.IllegalArgumentException: Invalid ParserType:
>"jtidy", expected of "xerces", "tidy", or "swing"
>	at org.enhydra.xml.xmlc.metadata.ParserType.getType(ParserType.java:66)
>	at
>org.enhydra.xml.xmlc.commands.xmlc.ParserCmdOptions$ParserOption.parse(Par
>serCmdOptions.java:56)
>	... 34 more
>
>
>Northern.CA ===--
>http://www.northern.ca 
>Canada's Search Engine
>
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>Xmlceclipse-development mailing list
>Xml...@li...
>https://lists.sourceforge.net/lists/listinfo/xmlceclipse-development
>
>  
>

Re: [XmlcEclipse-development] XMLC not generating .java files

[Garth D. <ga...@ut...>]

On Mon, 06 Jan 2003 17:06:42 EST Garth Dahlstrom wrote:

> Any ideas as to what might be causing the xmlc compiler not 
> to generate the .java output files (it makes the directory output
> directory and the package name subdir ok)... 

I figured out how to debug the UI, its too bad that the exceptions don't
popup with error messages that tell the user the problem...

But setting the parser to Swing seems to get me some .java files... Yay!

My problems were parser related... (maybe a drop down box with available
parsers would be cool along with a label suggesting HTML or XML)...

This was caused by having my parser set as xerces, when it should have
been jtidy or swing:

-class xmlc-debug.helloHtml -keep -nocompile -sourceout
C:\Java\eclipse\runtime-workspace\xmlc-debug\xmlc-java -parser xerces
-domfactory org.enhydra.xml.xhtml.XHTMLDomFactory
C:\Java\eclipse\runtime-workspace\xmlc-debug\xmlc\hello.html 
org.enhydra.xml.xmlc.XMLCException: Document appears to be an HTML
document; the xerces parser only supports XML (does the document start
with `<?xml ... ?>'?):
C:\Java\eclipse\runtime-workspace\xmlc-debug\xmlc\hello.html
	at org.enhydra.xml.xmlc.compiler.Parse.setupParser(Parse.java:108)
	at org.enhydra.xml.xmlc.compiler.Parse.parse(Parse.java:222)
	at org.enhydra.xml.xmlc.compiler.Compiler.parsePage(Compiler.java:109)
	at org.enhydra.xml.xmlc.compiler.Compiler.compile(Compiler.java:218)
	at org.enhydra.xml.xmlc.commands.xmlc.XMLC.compile(XMLC.java:132)
	at net.sourceforge.xmlceclipse.core.XmlcBuilder.build(XmlcBuilder.java:182)
	at net.sourceforge.xmlceclipse.core.XmlcBuilder.access$0(XmlcBuilder.java:165)
	at
net.sourceforge.xmlceclipse.core.XmlcBuilder$MyBuildVisitor.visit(XmlcBuil
der.java:235)
	at
org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:71)
	at
org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
	at
org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
	at
org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:52)
	at
net.sourceforge.xmlceclipse.core.XmlcBuilder.incrementalBuild(XmlcBuilder.
java:275)
	at net.sourceforge.xmlceclipse.core.XmlcBuilder.build(XmlcBuilder.java:257)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:384)
	at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.ja
va:852)
	at org.eclipse.core.runtime.Platform.run(Platform.java:413)
	at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:120)
	at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:176)
	at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:186)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:146)
	at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.ja
va:852)
	at org.eclipse.core.runtime.Platform.run(Platform.java:413)
	at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:160)
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:211)
	at
org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:861)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1569)
	at
org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperati
on.java:79)
	at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalConte
xt.java:95)

This was caused by having my parser setting my parser as jtidy (the UI
does not accept tidy):

-class xmlc-debug.hello -keep -nocompile -sourceout
C:\Java\eclipse\runtime-workspace\xmlc-debug\xmlc-java -parser jtidy
-domfactory org.enhydra.xml.xmlc.dom.lazydom.LazyHTMLDomFactory
C:\Java\eclipse\runtime-workspace\xmlc-debug\xmlc\hello.html 
org.enhydra.xml.xmlc.XMLCException: Invalid ParserType: "jtidy", expected 
of "xerces", "tidy", or "swing"
	at
org.enhydra.xml.xmlc.commands.xmlc.ParserCmdOptions$ParserOption.parse(Par
serCmdOptions.java:58)
	at
org.enhydra.xml.xmlc.commands.options.OptionsParser.parseCmdOption(Options
Parser.java:156)
	at
org.enhydra.xml.xmlc.commands.options.OptionsParser.parseOptions(OptionsPa
rser.java:169)
	at
org.enhydra.xml.xmlc.commands.options.OptionsParser.parse(OptionsParser.ja
va:323)
	at
org.enhydra.xml.xmlc.commands.xmlc.XMLCOptionsParser.parse(XMLCOptionsPars
er.java:75)
	at org.enhydra.xml.xmlc.commands.xmlc.XMLC.parseArgs(XMLC.java:101)
	at org.enhydra.xml.xmlc.commands.xmlc.XMLC.compile(XMLC.java:121)
	at net.sourceforge.xmlceclipse.core.XmlcBuilder.build(XmlcBuilder.java:182)
	at net.sourceforge.xmlceclipse.core.XmlcBuilder.access$0(XmlcBuilder.java:165)
	at
net.sourceforge.xmlceclipse.core.XmlcBuilder$MyBuildVisitor.visit(XmlcBuil
der.java:231)
	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:56)
	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:72)
	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:72)
	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:38)
	at
net.sourceforge.xmlceclipse.core.XmlcBuilder.fullBuild(XmlcBuilder.java:267)
	at net.sourceforge.xmlceclipse.core.XmlcBuilder.build(XmlcBuilder.java:246)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:384)
	at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.ja
va:852)
	at org.eclipse.core.runtime.Platform.run(Platform.java:413)
	at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:120)
	at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:176)
	at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:186)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:146)
	at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.ja
va:852)
	at org.eclipse.core.runtime.Platform.run(Platform.java:413)
	at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:160)
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:232)
	at org.eclipse.core.internal.resources.Project.build(Project.java:87)
	at org.eclipse.ui.actions.BuildAction.invokeOperation(BuildAction.java:156)
	at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:111)
	at org.eclipse.ui.actions.WorkspaceAction$1.execute(WorkspaceAction.java:268)
	at
org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOpera
tion.java:65)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1564)
	at
org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperati
on.java:79)
	at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalConte
xt.java:95)
Caused by: java.lang.IllegalArgumentException: Invalid ParserType:
"jtidy", expected of "xerces", "tidy", or "swing"
	at org.enhydra.xml.xmlc.metadata.ParserType.getType(ParserType.java:66)
	at
org.enhydra.xml.xmlc.commands.xmlc.ParserCmdOptions$ParserOption.parse(Par
serCmdOptions.java:56)
	... 34 more


Northern.CA ===--
http://www.northern.ca 
Canada's Search Engine

Re: [XmlcEclipse-development] XMLC not generating .java files

[David C. <dc...@ma...>]

Nothing concise.  I'm going to spend a few hours on it tonight.  Let me 
see what I find...

Garth Dahlstrom wrote:

>Any ideas as to what might be causing the xmlc compiler not 
>to generate the .java output files (it makes the directory output
>directory and the package name subdir ok)... 
>
>Any suggestions for debugging it?
>What class should I look in, in the plug-in code...  
>
>-G
>
>Northern.CA ===--
>http://www.northern.ca 
>Canada's Search Engine
>
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>Xmlceclipse-development mailing list
>Xml...@li...
>https://lists.sourceforge.net/lists/listinfo/xmlceclipse-development
>
>  
>

[XmlcEclipse-development] XMLC not generating .java files

[Garth D. <ga...@ut...>]

Any ideas as to what might be causing the xmlc compiler not 
to generate the .java output files (it makes the directory output
directory and the package name subdir ok)... 

Any suggestions for debugging it?
What class should I look in, in the plug-in code...  

-G

Northern.CA ===--
http://www.northern.ca 
Canada's Search Engine

[XmlcEclipse-development] Re: How do I use XMLCeclipse?

[Garth D. <ga...@ut...>]

On Mon, 06 Jan 2003 06:50:48 -0500 David Corbin wrote:

> OK  Please join the xmlceclipse-development.  Let's see if we can crank 
> this project back up.  I'll try and see if I can make the latest work 
> (build) in at least one environment, and if I can, I'll build and 
> release 0.0.2.

Ok, sure...  My unix user id on SF is ironstorm, I beleive you have
to add me in the admin screen.

I've done some docs and linked them to the Wiki, the autogenerate
doesn't actually yeild anything for me but I doctored the screen 
shots based on the description...

> I know about Barracuda, but I've never even downloaded it. 

Barracuda is very cool, it involves hooking events/data components 
to the id attributes used by XMLC.  Supposed to be sort of like how 
swing seperates logic from presentation while encourage reuse.

You can find out more about it at http://barracudamvs.org/ or you 
can look at the running CVS version on my web home computer's web 
server http://dx.northern.ca/Barracuda/ (the examples work on mine, 
however they appear broken on the official site)...

Cheers,

-G

Northern.CA ===--
http://www.northern.ca 
Canada's Search Engine

[XmlcEclipse-development] Re: How do I use XMLCeclipse?

[David C. <dc...@ma...>]

OK  Please join the xmlceclipse-development.  Let's see if we can crank 
this project back up.  I'll try and see if I can make the latest work 
(build) in at least one environment, and if I can, I'll build and 
release 0.0.2.

I know about Barracuda, but I've never even downloaded it. 

Garth Dahlstrom wrote:

>>I'm not really sure what state it was left in.  I honestly 
>>thought 0.0.1 worked (in a very narrow configuration).  
>>    
>>
>
>No worries, it was interesting for me to figure out why...  I learned
>about plugins. :)
>
>The plugin.xml file wasn't in the 0.0.1 Jar, eclipse doesn't know it's a
>plugin or what events tie to what classes in the jar. (kinda  neat how
>they make the plugins)
>
>Cool, now I got how it works... 
>I set my classNameTemplate to @HTML and dropped my HelloWorld1.html 
>file into /xmlc and then closed/reopened my project. 
>
>It doesn't seem to produce any .java files for me yet, but I think it is
>getting run because now I have a an empty /xmlc-java/oss-reg/ 
>directory that wasn't there before.
>
>  
>
>>I know people that users of interfaces with xmlc will need such.
>>    
>>
>
>Yup, I think it's espeically useful for Barracuda projects that 
>might get too big to manage with just notepad.
>
>  
>
>>If I've actually got someone interested in using it, I may have to 
>>get back to working on it.  
>>    
>>
>
>http://eclipse-plugins.2y.net/eclipse/plugin_details.jsp?id=158
>clicks:   	
>24H 	week 	month 	all
>10 	44 	1449 	1449
>
>  
>
>>Of course, contributions (in any form, code, suggestions, 
>>documentation, etc.) are very welcome.
>>    
>>
>
>I'm just starting to pick up java (I've done Delphi, PHP, Perl 
>and lots of other stuff), but I've already put a patch into the
>patch system to get rid of the "access in a static way" warning. :)
>
>I'd also be happy to help with testing and documentation...  
>I'll write a quick how-to use it based on what you've told me...  
>but we should put out a 0.0.2 release that works, even if you just grab
>the build I made from CVS off
>http://www.northern.ca/forums/getfile.php?id=20 and release it...
>
>Cheers,
>
>-Garth
>
>Northern.CA ===--
>http://www.northern.ca 
>Canada's Search Engine
>
>
>  
>

[XmlcEclipse-development] Update

[David C. <dc...@im...>]

I've reorganized the CVS repository a bit.  There are two modules that
should be used.

net.sourceforge.xmlceclispe  is the feature required to support Update
manager
net.sourceforge.xmlceclipse.core is the existing code that really does
something.

The latter makes use of a classpath variable to refer to the XMLC
installation.  I've also included in CVS a "lib" folder which contains
the jars necessary for building.  (You'll still need to set your
classpath variable in eclipse)

Also, I've release version 0.0.1 of the plugin.

David