-
1. Re: Problem with Dukes Bank section 5.2
rogera May 12, 2005 5:30 AM (in response to rogera)Jboss 4.0.2 was binary install
-
2. Re: Problem with Dukes Bank section 5.2
l3sad0 May 13, 2005 4:20 AM (in response to rogera)got the same error:
windows xp sp2
sun jdk 1.5.0_02-b09
jboss-4.0.2
j2ee tutorial update 4
altough this error did not ocurred while using jboss-4.0.1 -
3. Re: Problem with Dukes Bank section 5.2
norman.richards May 13, 2005 10:02 AM (in response to rogera)The getting started guide you are using is for 4.0.1. There were changes in web services in 4.0.2 that make things not work. There should be a 4.0.2 version shortly.
-
4. Re: Problem with Dukes Bank section 5.2
lm28ness May 13, 2005 11:18 AM (in response to rogera)I too am having problems with chapter 5 but when I try to build the web service with the ant command i get this instead
[java] log4j:WARN No appenders could be found for logger (org.apache.axis.i18n.ProjectResourceBundle).
[java] log4j:WARN Please initialize the log4j system properly.
And the wsdl is not created, not familiar with log4j.
Thanks -
5. Re: Problem with Dukes Bank section 5.2
sosoict1 Jun 1, 2005 1:55 AM (in response to rogera)The problem occurs because there isn't axis.jar in the "lib" dir. Just copy it from Axis/lib dir that you installed your Axis.
to lm28ness: you can copy log4j-1.2.8.jar and log4j.properties from the Axis installing dir to default/lib dir. If the problem still occurs, copy commons-logging.jar and commons-discovery.jar. -
6. Re: Problem with Dukes Bank section 5.2
rogera Jun 5, 2005 7:30 AM (in response to rogera)Copied axis.jar to jboss-4.0.2/lib directory as you suggested but still get error on wsdl build target.
Have checked that axis.jar does contain the class org.apache.axis.wsdl.Java2WSDL
Any further ideas on this?
Thanks -
7. Re: Problem with Dukes Bank section 5.2
clairecostello Jun 7, 2005 12:55 PM (in response to rogera)A long shot but try copying axis.jar to lib directory of appropriate server configuration rather than root lib.
HTH, Claire -
8. Re: Problem with Dukes Bank section 5.2
rogera Jun 24, 2005 9:57 AM (in response to rogera)Hi Claire.
Tried that too but to no avail
Thanks anyway for suggestion. I think problem is as suggested by norman in post on this topic above
Roger -
9. Re: Problem with Dukes Bank section 5.2
rathorev Aug 13, 2005 2:17 PM (in response to rogera)Here is the woraround that I performed to make the web services in chapter 5 to work:
1. Since jboss-build.xml is including the entire jars in jboss-4.0.2\client to the classpath, I renamed the existing axis-ws4ee.jar to z_axis-ws4ee.jar, so that it is loaded at last. This file has the timestamp of May' 2005
2. Then I copied jboss-4.0.2\server\all\deploy\jboss-ws4ee.sar\axis-ws4ee.jar to jboss-4.0.2\client. This had the timestamp of Sep' 2005.
3. execute the ant -f jboss-build.xml compile. This should work fine with old axis-ws4ee.jar.
In simple terms I replaced the new axis-ws4ee.jar with an old copy of axis-ws4ee.jar.
You can add the log4j related classes also to the classpath so that the Log4j related warnings do not appear after compiling as mentioned earlier in other post.
Good Luck...
Rathore, Vijay S. -
10. Re: Problem with Dukes Bank section 5.2
rathorev Aug 13, 2005 2:19 PM (in response to rogera)Here is the workaround that I performed to make the web services in chapter 5 to work:
1. Since jboss-build.xml is including the entire jars in jboss-4.0.2\client to the classpath, I renamed the existing axis-ws4ee.jar to z_axis-ws4ee.jar, so that it is loaded at last. This file has the timestamp of May' 2005
2. Then I copied jboss-4.0.2\server\all\deploy\jboss-ws4ee.sar\axis-ws4ee.jar to jboss-4.0.2\client. This had the timestamp of Sep' 2005.
3. execute the ant -f jboss-build.xml compile. This should work fine with old axis-ws4ee.jar.
In simple terms I replaced the new axis-ws4ee.jar with an old copy of axis-ws4ee.jar.
You can add the log4j related classes also to the classpath so that the Log4j related warnings do not appear after compiling as mentioned earlier in other post.
Good Luck...
Rathore, Vijay S. -
11. Re: Problem with Dukes Bank section 5.2
kjeldsen Aug 19, 2005 9:39 AM (in response to rogera)I get the samme error:
wsdl: [java] log4j:WARN No appenders could be found for logger (org.jboss.axis.i18n.ProjectResourceBundle). [java] log4j:WARN Please initialize the log4j system properly.
I am using JBoss 4.0.1 and have tried all of the above solutions with no luck.
Any other ideas anyone? -
12. Re: Problem with Dukes Bank section 5.2
duane5000 Sep 21, 2005 12:45 PM (in response to rogera)In the jar for axis (axis-w4ee.jar),
the java2WSDL class has org/apache/.. as its path, the build complains that /org/jboss/.../java2WSDL does not exist.
java.lang.NoClassDefFoundError: org/jboss/axis/wsdl/Java2WSDL
Changing the path in the jboss-build.xml (wsdl target)
from
to
gets us past the complaint that the class is not found.
From there the only complaint is that log4j appenders were not found. But this should have no adverse affect on the rest of the build. -
13. Re: Problem with Dukes Bank section 5.2
duane5000 Sep 21, 2005 12:48 PM (in response to rogera)Sorry about that. The greaterThan lessThan tags were rendered as html. My bad. Here's the missing info:
java classname="org.jboss.axis.wsdl.Java2WSDL"
classpathref="build.classpath" fork="yes"
should be...
java classname="org.apache.axis.wsdl.Java2WSDL"
classpathref="build.classpath" fork="yes" -
14. Re: Problem with Dukes Bank section 5.2
uisys26 Nov 8, 2005 2:43 PM (in response to rogera)I found that the jboss-buid.xml, in the "wsdl" target, specified the classname as folows:
<java classname="org.apache.axis.wsdl.Java2WSDL" ...
whereas the jar axis-ws4ee.jar that I have (May 5th) contains classes with
the path "org.jboss" not "org.apache".
I found changing the classname to "org.jboss.axis.wsdl.Java2WSDL"
eliminated the run time error, allowed the teller.wsdl file to be created
but then gave the log4j warnings.
The other steps worked although the log4j error reoccured when the
ws was run.