This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
Hi, I'm totally new to Web Services can have a problem with JBuilder trying to generate a file named int.java from the WSDL. The WSDL is supplied by a TDA in my company and I've noticed that it has a few descriptions that include <restriction base="int"/>. When I import the WSDL and select the option to Generate Local Server Implementation (which seems the next logical step) and try to compile from the default generated files, it's looking for String.java (that's OK, even though it doesn't find it) and also int.java...which doesn't make sense to me, so it FAILS to compile properly. I've also noticed that there is a deployment file WSDD that has a type of "java:int" in it.
This may be a basic issue, but I'm new to Web Services this week so any help would be appreciated.
Could you please provide more information? The <restriction base="int"/> means it is a restricted interger( You can restrict the value range , set it to an enumeration type etc...). However I do not understand what do you mean it is looking for String.java and int.java. Do you have those types (String ,int ) defined in your wsdl? Usually it would be pretty straight forward to develop a web service if you already have a wsdl file and you are using a wizard.
Joined: Feb 22, 2005
Hi Lin. Thanks for the response. Not sure I can expand anymore. I think we may have some sort of configuration issue. Basically we have restriction base="int" within our WSDL. We follow the steps for creating Web Services within JBuilder, i.e. new project, new file (Web Configuration), Drag the WSDL into JBuilder, right click and generate local server which fails, because it's looking for String.java and int.java. There must be something not quite right here, because it shouldn't be looking for int.java, it wouldn't be possible to create a class with a name of "int". Nothing else to add really.
try to first validate the wsdl given by some third party which may be another unit in ur company then find whether ur jbuilder's web service toolkit supports all types of web service styles like rpc/encoded, document/literal, document/wrapped etc. and try to isolate the problem and go step by step may be first trying to consume the wsdl with other web service toolkits like apache axis etc.
all the above stuff is just a suggestion but may not necessarily work for you. u need to apply divide N conquer rule to find solutions to ur problem :-)
Joined: Feb 22, 2005
Hi. Ive been told that this issue maybe down to the a mismatch of Apache Toolkit version and WSDL standard version.
This problem seems to be more related to JBuilder and how it generates WSDL files and not that much to the certification itself.
Moreover, we would be grateful if you do not crosspost the same topic in multiple forums. I'm closing this topic now. You can continue this discussion in the other topic you opened in the web services forum.