Just released on sf version 1.0.1. It works with JBossWS 2.0.1. From the changelog:
******* Wise 1.0.1 ********
* This is a minor release, just adding support to JBossWS 2.0.1; this version 1.0.1 works with JBossWS 2.0.1.
If you are using JbossWS 2.0.0 please use Wise 1.0.
Some difference in JBossWS libs force us to have two different version of Wise strictly
coupled with JBossWS version deployed on the server.
Does WISE support Sun JAX-WS 2.1.2 RI?
I’m using JAX-WS RI on glassfish.
depends on what you mean with “support”.
If you mean if it can be used as client against glassfish server the answer is yes.
If you are asking if you can deploy it on glassfish/RI the answer is no. It is thought and tested using jbossws.
We will support next versions of jbossws with all stack implemented in (metro is one of them), but at the moment there isn’t any plan to support directly glassfish/RI as deployment environment.
thanks for the interest
Hi and thx for this tool.
We are using it to test some webservices internally and encountered two problems:
- support for enumeration (always ***NIL*** in the result tree), seems to be a known limitation
(http://jax-wise.svn.sourceforge.net/viewvc/jax-wise?view=rev&revision=17) but it could be very useful
xsd:simpleType name=”Flag”
xsd:restriction base=”xsd:string”
xsd:enumeration value=”Y”/xsd:enumeration
xsd:enumeration value=”N”/xsd:enumeration
/xsd:restriction
/xsd:simpleType
- a strange issue with a (mandatory) boolean field
xsd:element name=”isDriver” nillable=”false” type=”xsd:boolean”/xsd:element
causing an exception when the service is called
…
Caused by: it.javalinux.wise.exceptions.WiseRuntimeException: Error converting element to object
at it.javalinux.wise.exceptions.WiseRuntimeException.rethrow(WiseRuntimeException.java:44)
at it.javalinux.wise.seam.entities.treeElement.ComplexWiseTreeElement.toObject(ComplexWiseTreeElement.java:112)
at it.javalinux.wise.seam.entities.treeElement.ComplexWiseTreeElement.toObject(ComplexWiseTreeElement.java:88)
at it.javalinux.wise.seam.actions.WSDLManagerBean.doCall(WSDLManagerBean.java:224)
… 115 more
Caused by: java.lang.NoSuchMethodException: it.javalinux.ws.ComplainantVO.setIsDriver(java.lang.Boolean)
at java.lang.Class.getMethod(Class.java:1581)
at it.javalinux.wise.seam.entities.treeElement.ComplexWiseTreeElement.toObject(ComplexWiseTreeElement.java:101)
even if the generated “ComplainantVO” class contains the method
/**
* Sets the value of the isDriver property.
*
*/
public void setIsDriver(boolean value) {
this.isDriver = value;
}
We hope you’ll be able to fix those soon.
Keep up with the good work.
Claude
I’ve just created two issues for the problems you wrote us.
https://sourceforge.net/tracker/index.php?func=detail&aid=1813703&group_id=202353&atid=981242
https://sourceforge.net/tracker/index.php?func=detail&aid=1813705&group_id=202353&atid=981242
If you can, feel free to attach them a minimal test case (the WS implementation), so that we can easily reproduce and fix the problem.
Thank you
DONE!
This patched version would solve both problems:
http://www.javalinuxlabs.org/Wise-1.0.1SP1.tgz
Please make some tests and let us know if it is working for you. If we would have a good feedback we will publish this SP1 on sourceforge.
Thanks for your feedbacks
Installed JBoss 4.2.1 on a Windows Vista, tried out WISE so that I can use JBoss with good features as those who come with Glassfish ( thinking of ‘Tester’ ).
I have not installed JBossWS, something went wrong there,
is that necessary for WISE ?
Adding a WebService which I have tried out in Glassfish:
It is this small one:
Code:
@Stateless()
@WebService()
public class ProjectManagerWs {
@WebMethod
public String version() {
return “ProjectManager version 0.1″;
}
}
Surfing to:
http://127.0.0.1:8080/ProjectManagerWsService/ProjectManagerWs?wsdl
I am able to see the WSDL in my browser, so the wsdl is OK.
But adding it to wise and clicking the link which I have created gives me the following error:
16:47:48,421 INFO [WSDLManagerBean] *** Beginning conversation, savedWsdl = null
16:47:48,426 ERROR [WSDLManagerBean] An unexpected exception occurred while selecting the wsdl.
Code:
java.lang.NoClassDefFoundError: org/jboss/wsf/spi/tools/WSContractConsumer
at it.javalinux.wise.seam.actions.WSDLManagerBean.selectWsdl(WSDLManagerBean.java:116)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Am I forgetting something ?
the mysql says:
mysql> select * from savedwsdl;
+————-+———————————————————————+———-+————+——————-+
| idSavedWSDL | wsdlLink | wsdlText | savingDate | idUserInformation |
+————-+———————————————————————+———-+————+——————-+
| 2 | http://127.0.0.1:8080/ProjectManagerWsService/ProjectManagerWs?wsdl | tt | 2007-10-21 | 3 |
+————-+———————————————————————+———-+————+——————-+
regards, i
Wise 1.0.1 needs jbossws 2.0.1 installed.
have a look to pdf manual distributed with wise binaries or to http://www.javalinuxlabs.org/wise/download.html
for installation notes.
Thanks for the interest.
Stefano
Hello,
Did install the JBossws 2.0.1.
Seem to be working.
starting jboss and launching my webservice – a webservice I run in Glassfish.
This is the reply from JBoss:
23:11:57,035 INFO [SessionFactoryObjectFactory] Factory name: persistence.units:jar=ProjectManagerJBoss.jar,unitName=company
23:11:57,035 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
23:11:57,037 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name: persistence.units:jar=ProjectManagerJBoss.jar,unitName=company
23:11:57,037 WARN [SessionFactoryObjectFactory] InitialContext did not implement EventContext
23:11:57,037 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
23:11:57,047 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
23:11:57,047 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=ProjectManagerJBoss.jar,name=TitanWS,service=EJB3 with dependencies:
23:11:57,047 INFO [JmxKernelAbstraction] persistence.units:jar=ProjectManagerJBoss.jar,unitName=company
23:11:57,057 INFO [EJBContainer] STARTED EJB: ws.TitanWS ejbName: TitanWS
23:11:57,063 INFO [EJB3Deployer] Deployed: file:/C:/app/jboss-4.2.1.GA/server/default/deploy/ProjectManagerJBoss.jar
23:11:57,080 INFO [DefaultEndpointRegistry] register: jboss.ws:context=ProjectManagerJBoss,endpoint=TitanWS
23:11:57,370 INFO [WSDLFilePublisher] WSDL published to: file:/C:/app/jboss-4.2.1.GA/server/default/data/wsdl/ProjectManagerJBoss.jar/TitanWSService16783.wsdl
23:11:57,459 INFO [TomcatDeployer] deploy, ctxPath=/ProjectManagerJBoss, warUrl=…/tmp/deploy/ProjectManagerJBoss.jar16782.war/
Using Wise, and I write:
http://localhost:8080/TitanWSService/TitanWS?wsdl
choosing the one, I am once again prompted to put in the password.
I do so.
this is the reply from wise:
# Cannot download wsdl; please check host address, username and password. …..
….
…..
…..
Do you mean, If I succeed, that I am able to test the methods in the service as I do in Glassfish ?
regards, i
As far as I understand you didn’t provide correct user/password credential. Note that you have to provide user/passwrod set in the wsdl not wise’s ones.
Hello Stefano,
Do you mean that my wsdl has a user/password ?
I am quite new to this.
Glassfish did not ask for a psw concerning the WSDL.
I created a user in wise and thought it was that user/psw.
regards, i
Hello Stefano,
Do you mean that my wsdl has a user/password ?
I am quite new to this.
Glassfish did not ask for a psw concerning the WSDL.
I created a user in wise and thought it was that user/psw.
regards, i
Hi, I’m using jboss4.2.2.GA and the jbossws2.0.2 Release, everything works (can read wsdls and can enter parameters and endpoints) the problem is, when I execute the call, I always get: Result is null – and no debug messages……
Hi Stocki,
what is your invoked operation supposed to return? do you get any exception in the log file (please check the log4j conf to be sure the it.javalinux category is not filtered). Please give us some more information about your issue. Otherwise you could open an issue on the tracker (http://sourceforge.net/tracker/?group_id=202353) attaching a minimal example reproducing your issue, so that we can analyze and perhaps fix it.
Hi
I’m trying to use wise 1.0.1 to test our web services, but there is a problem when a complex type is returned: All String fields turn up as e.g. it.javalinux.wise.seam.entities.treeElement.ParameterizedWiseTreeElement@1658b53
I.e. they don’t show the value. Integers, booleans, etc. work fine.
I’m using jboss-4.2.2, wise-1.0.1, jdk1.5.0_13, and jbossws-2.0.1 (I’ve also tried 2.0.2 and 2.0.3 without luck). No errors appear in the log. Do you have any idea of what could be wrong?
Thanks
- taf
Hi taf,
the issue you described might have already been solved (but after the 1.0.1 release). Could you please try using a Wise binary obtained compiling the trunk src from SVN or send us the wsdl contract you’re having problem with?
Thank you
Alessio