You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jaxme-dev@ws.apache.org by Dean Hiller <de...@xsoftware.biz> on 2004/11/27 22:38:28 UTC
importing into eclipse to look at source???
I wanted to start looking at the jaxme source. I followed the typical steps for creating a project in eclipse, but jaxme appears to be missing some jar files or is missing me doing some kind of build step where java files are generated??? I did an "ant -projecthelp" but it didn't look like there were any targets for generating source files that might be missing. I am working some other open source projects and didn't really have the time to spend alot of time getting set up so I am kind of being lazy here, but could someone let me know a quick few steps. I did check the e-mail archives and a reply to this might benefit the next person :)
Some of the errors in eclipse are
2 Address cannot be resolved to a type AddressCreator.java jaxme/src/jaxme/org/apache/ws/jaxme/examples/misc/address line 42 November 27, 2004 2:28:13 PM
2 AddressImpl cannot be resolved to a type AddressCreator.java jaxme/src/jaxme/org/apache/ws/jaxme/examples/misc/address line 42 November 27, 2004 2:28:13 PM
2 AttributeSGImpl cannot be resolved to a type JAXBComplexTypeSG.java jaxme/src/jaxme/org/apache/ws/jaxme/generator/sg/impl line 147 November 27, 2004 2:28:13 PM
2 SimpleContentSGChain cannot be resolved to a type JAXBComplexTypeSG.java jaxme/src/jaxme/org/apache/ws/jaxme/generator/sg/impl line 165 November 27, 2004 2:28:13 PM
thanks,
dean
Re: building from 0.3.1, building from head
Posted by Dean Hiller <de...@xsoftware.biz>.
sweet, thanks for the quick response. Will try again tonight.
thanks,
dean
----- Original Message -----
From: "Jochen Wiedmann" <jo...@freenet.de>
To: "Dean Hiller" <de...@xsoftware.biz>
Cc: <ja...@ws.apache.org>
Sent: Monday, November 29, 2004 1:59 PM
Subject: Re: building from 0.3.1, building from head
>
> Hi, Dean,
>
> Dean Hiller wrote:
>
> > C:\ROOT\views\jakartaviews\jaxmehead\ant\macros.xml:72: Test
> > org.apache.ws.jaxme.js.junit.VersionTest failed
>
> unfortunately, you do not post the full error message. Most possibly,
> the error message indicates, that the database is in use.
>
> This is a problem, that I still cannot explain. In order to proceed,
> simply change "failOnError" to "false" in js.xml, line 169. (I hope,
> that we'll be able to use Derby in the near future, which will hopefully
> make the problem vanish.)
>
>
> > I try to import it into eclipse and get the following error
> > The import org.apache.ws.jaxme.test cannot be resolved
AddressCreator.java
>
> You need to run the complete "make test". (That's why the above change
> is required.)
>
>
> > C:\ROOT\views\sfviews\all2\ws-jaxme-0.3.1\buildjs.xml:143: Class Not
Found:
> > JDBC driver org.hsqldb.jdbcDriver could not be loaded
>
> I have no explanation for that, besides, that the hsqldb.jar file was
> possibly checked into the CVS after branching the 0.3 branch. (There
> have been license issues.) If so, simply copy the jar file from the HEAD
> branch.)
>
>
> Sorry for the hazzle,
>
> Jochen
>
> --
> http://lilypie.com/baby1/050423/1/5/1/+1
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
Re: building from 0.3.1, building from head
Posted by Dean Hiller <de...@xsoftware.biz>.
There was no failOnError property nor did "runtests" element allow one. I
just commented out runtests to proceed with using "ant test". Once I did
that, the build was successful, and the eclipse errors went down alot, but
there are still 93 errors left. Could it be commenting out the runtests
element or do I need a jar?
as far as I can tell, this is the one error which covers all 93 other
errors.
The import com.softwareag cannot be
resolved.............DocumentDefaultHandler.java
(side question...why use runtests instead of JUnit?....I have seen many just
hide all their tests wether scripts or not under JUnit tests...ant does
this. Ant's testing is pretty funky as you feed it real scripts under the
look of a JUnit test).
Also, the previous error when I have runtests is just this(I am not sure if
there is any extra helpful info here though, is there a special option like
verbose or something or do I just have to run the test in eclipse which I
worry about because that can be a different beast with different results as
the classpath is different)....
----------------------------------------------------------------------------
-------------
JS.generate:
JS.test:
[junit] Running org.apache.ws.jaxme.js.junit.BasicTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.13 sec
[junit] Running org.apache.ws.jaxme.js.junit.MultipleInheritanceTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.02 sec
[junit] Running org.apache.ws.jaxme.js.junit.TypesafeEnumerationTest
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.02 sec
[junit] Running org.apache.ws.jaxme.js.junit.VersionTest
[junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 6.059 sec
BUILD FAILED
C:\ROOT\views\jakartaviews\jaxmehead\ant\js.xml:169: The following error
occurre
d while executing this line:
C:\ROOT\views\jakartaviews\jaxmehead\ant\macros.xml:72: Test
org.apache.ws.jaxme
.js.junit.VersionTest failed
Total time: 11 seconds
----------------------------------------------------------------------------
-----------------
thanks,
dean
----- Original Message -----
From: "Jochen Wiedmann" <jo...@freenet.de>
To: "Dean Hiller" <de...@xsoftware.biz>
Cc: <ja...@ws.apache.org>
Sent: Monday, November 29, 2004 1:59 PM
Subject: Re: building from 0.3.1, building from head
>
> Hi, Dean,
>
> Dean Hiller wrote:
>
> > C:\ROOT\views\jakartaviews\jaxmehead\ant\macros.xml:72: Test
> > org.apache.ws.jaxme.js.junit.VersionTest failed
>
> unfortunately, you do not post the full error message. Most possibly,
> the error message indicates, that the database is in use.
>
> This is a problem, that I still cannot explain. In order to proceed,
> simply change "failOnError" to "false" in js.xml, line 169. (I hope,
> that we'll be able to use Derby in the near future, which will hopefully
> make the problem vanish.)
>
>
> > I try to import it into eclipse and get the following error
> > The import org.apache.ws.jaxme.test cannot be resolved
AddressCreator.java
>
> You need to run the complete "make test". (That's why the above change
> is required.)
>
>
> > C:\ROOT\views\sfviews\all2\ws-jaxme-0.3.1\buildjs.xml:143: Class Not
Found:
> > JDBC driver org.hsqldb.jdbcDriver could not be loaded
>
> I have no explanation for that, besides, that the hsqldb.jar file was
> possibly checked into the CVS after branching the 0.3 branch. (There
> have been license issues.) If so, simply copy the jar file from the HEAD
> branch.)
>
>
> Sorry for the hazzle,
>
> Jochen
>
> --
> http://lilypie.com/baby1/050423/1/5/1/+1
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: jaxme-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
Re: building from 0.3.1, building from head
Posted by Jochen Wiedmann <jo...@freenet.de>.
Hi, Dean,
Dean Hiller wrote:
> C:\ROOT\views\jakartaviews\jaxmehead\ant\macros.xml:72: Test
> org.apache.ws.jaxme.js.junit.VersionTest failed
unfortunately, you do not post the full error message. Most possibly,
the error message indicates, that the database is in use.
This is a problem, that I still cannot explain. In order to proceed,
simply change "failOnError" to "false" in js.xml, line 169. (I hope,
that we'll be able to use Derby in the near future, which will hopefully
make the problem vanish.)
> I try to import it into eclipse and get the following error
> The import org.apache.ws.jaxme.test cannot be resolved AddressCreator.java
You need to run the complete "make test". (That's why the above change
is required.)
> C:\ROOT\views\sfviews\all2\ws-jaxme-0.3.1\buildjs.xml:143: Class Not Found:
> JDBC driver org.hsqldb.jdbcDriver could not be loaded
I have no explanation for that, besides, that the hsqldb.jar file was
possibly checked into the CVS after branching the 0.3 branch. (There
have been license issues.) If so, simply copy the jar file from the HEAD
branch.)
Sorry for the hazzle,
Jochen
--
http://lilypie.com/baby1/050423/1/5/1/+1
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
building from 0.3.1, building from head
Posted by Dean Hiller <de...@xsoftware.biz>.
I don't care as much about building 0.3.1 as I do about building from the
head so I will start with my problems with building from the head and
running in eclipse.
I check out ws-jaxme from /home/cvspublic cvsroot. I then run "ant test"
and get the following error
-----------------------------------------------------------------
BUILD FAILED
C:\ROOT\views\jakartaviews\jaxmehead\ant\js.xml:169: The following error
occurred while executing this line:
C:\ROOT\views\jakartaviews\jaxmehead\ant\macros.xml:72: Test
org.apache.ws.jaxme.js.junit.VersionTest failed
-----------------------------------------------------------------
I try to import it into eclipse and get the following error
The import org.apache.ws.jaxme.test cannot be resolved AddressCreator.java
I look in ws-jaxme and can't find a folder called test that has a parent
folder of jaxme anywhere. I must be missing some jars or something???
Building 0.3.1 from source resulted in different errors....
-------------------------------------------------------------------
BUILD FAILED
C:\ROOT\views\sfviews\all2\ws-jaxme-0.3.1\build.xml:259: The following
erroroccurred while executing this line:
C:\ROOT\views\sfviews\all2\ws-jaxme-0.3.1\buildjs.xml:143: Class Not Found:
JDBC driver org.hsqldb.jdbcDriver could not be loaded
-------------------------------------------------------------------
Just trying to get a quick start and step through the source code with my
application to understand the init method better(and understand the
suggestion that was given me)
thanks,
dean
----- Original Message -----
From: "Jochen Wiedmann" <jo...@freenet.de>
To: "Dean Hiller" <de...@xsoftware.biz>
Cc: <ja...@ws.apache.org>
Sent: Saturday, November 27, 2004 2:59 PM
Subject: Re: importing into eclipse to look at source???
> Dean Hiller wrote:
>
> > I wanted to start looking at the jaxme source. I followed the typical
> > steps for creating a project in eclipse, but jaxme appears to be missing
> > some jar files or is missing me doing some kind of build step where java
> > files are generated???
>
> Simply run the "test" target in Ant, followed by a refresh in Eclipse.
>
> I admit, that this is nonobvious. Hints for how to let the user know are
> welcome. So are patches or FAQ entries.
>
>
> Jochen
>
> --
> http://lilypie.com/baby1/050423/1/5/1/+1
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
Re: importing into eclipse to look at source???
Posted by Jochen Wiedmann <jo...@freenet.de>.
Dean Hiller wrote:
> I wanted to start looking at the jaxme source. I followed the typical
> steps for creating a project in eclipse, but jaxme appears to be missing
> some jar files or is missing me doing some kind of build step where java
> files are generated???
Simply run the "test" target in Ant, followed by a refresh in Eclipse.
I admit, that this is nonobvious. Hints for how to let the user know are
welcome. So are patches or FAQ entries.
Jochen
--
http://lilypie.com/baby1/050423/1/5/1/+1
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org