6 Replies Latest reply on Oct 21, 2007 4:23 PM by asoldano

    JBossWS vs Glassfish, do we a 'Tester' ?

    iner

      Hello,

      Using JBoss frequently, checked out the features for WS
      in Glassfish and saw that they have this Tester-feature in the AS.
      This gives me the opportunity to test the WS without writing a client.

      Does JBoss have something similar ?

      I am running JBoss 4.2.1 now, do I need any addition to that
      regarding WS ? And I am running mysql as my rdbms.

      regards, i

        • 1. Re: JBossWS vs Glassfish, do we a 'Tester' ?
          asoldano

          Hi,
          JBoss currently lacks something similar to the Glassfish ws Tester, however we're working on this. For further information, take a look at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121127
          Feel free to comment!

          In the meantime you might evaluate Wise http://www.javalinuxlabs.org/wise/, a tool to test ws through a web interface almost like the Glassfish tester.

          • 2. Re: JBossWS vs Glassfish, do we a 'Tester' ?

            Hi,

            have a look at soapUI (http://www.soapui.org), which is an extremely popular free open-source desktop app for invoking, testing and simulating any web-service. It even has built-in support for the jbossws wsconsume toolset and there are plugins for eclipse, netbeans and IDEA..

            Previously there was also a dedicated plug-in for JBossIDE, put it has not yet made it into the new JBoss Tools stack..

            Good Luck!

            /Ole
            eviware.com

            • 3. Re: JBossWS vs Glassfish, do we a 'Tester' ?
              iner

              Thanks !!

              I will put a side saturday for this
              and get back to you!

              regards, Inkimar

              • 4. Re: JBossWS vs Glassfish, do we a 'Tester' ?
                iner

                Hello Alessio,

                Trying the WISE.
                Using JBoss 4.2.1.
                Did not install JBossWS though - is that necessary ?

                When surfing to:
                http://localhost:8080/Wise/

                I get the following error in the JBoss-console:

                15:35:12,680 INFO [EJBContainer] STARTED EJB: org.jboss.seam.transaction.EjbTransaction ejbName: EjbTransaction
                15:35:12,713 INFO [EJB3Deployer] Deployed: file:/C:/app/jboss-4.2.1.GA/server/default/tmp/deploy/tmp39865Wise.ear-contents/jboss-seam.jar
                15:35:12,717 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.entity.PersistenceUnitDeployment
                15:35:12,720 INFO [JmxKernelAbstraction] installing MBean: persistence.units:ear=Wise.ear,jar=Wise.ejb3.jar,unitName=Wise with dependencies:
                15:35:12,722 INFO [JmxKernelAbstraction] jboss.jca:name=WiseDatasource,service=DataSourceBinding
                15:35:12,725 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:ear=Wise.ear,jar=Wise.ejb3.jar,unitName=Wise
                15:35:12,762 INFO [Ejb3Configuration] found EJB3 Entity bean: it.javalinux.wise.seam.entities.SavedWsdl
                15:35:12,766 INFO [Ejb3Configuration] found EJB3 Entity bean: it.javalinux.wise.seam.entities.UserInformation
                15:35:12,792 INFO [Configuration] Reading mappings from resource : META-INF/orm.xml
                15:35:12,794 INFO [Ejb3Configuration] [PersistenceUnit: Wise] no META-INF/orm.xml found
                15:35:12,800 INFO [AnnotationBinder] Binding entity from annotated class: it.javalinux.wise.seam.entities.SavedWsdl
                15:35:12,803 INFO [EntityBinder] Bind entity it.javalinux.wise.seam.entities.SavedWsdl on table SavedWSDL
                15:35:12,826 INFO [AnnotationBinder] Binding entity from annotated class: it.javalinux.wise.seam.entities.UserInformation
                15:35:12,828 INFO [EntityBinder] Bind entity it.javalinux.wise.seam.entities.UserInformation on table UserInformation
                15:35:12,839 INFO [CollectionBinder] Mapping collection: it.javalinux.wise.seam.entities.UserInformation.savedWsdls -> SavedWSDL
                15:35:12,986 INFO [ConnectionProviderFactory] Initializing connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
                15:35:12,989 INFO [InjectedDataSourceConnectionProvider] Using provided datasource
                15:35:12,999 WARN [JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
                org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Access denied for user 'root'@'loc
                alhost' (using password: NO))
                 at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:179)
                 at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:577)
                


                When using 'MySQL Administrator' and going to 'Server Connection'
                Then I am able to see all the connection made in my mysql-ds.xml within JBoss but not the connection in 'wise-ds.xml'

                I am not able to register a new user ....

                I am running on a windows vista at the moment, that is
                my working machine - the installation-routine for JBossWS seems
                a bit complicated.

                Could you give me further advice.

                regards, i




                • 5. Re: JBossWS vs Glassfish, do we a 'Tester' ?
                  iner

                  Hello,

                  My mistake with Wise, sorry for that.
                  changed the login in 'wise-ds.xml' and able to create a new user and to log in ( shame that I cannot erase the last post )

                  Adding a WebService which I have tried out in Glassfish:
                  It is this small one:

                  @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.

                  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.
                  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

                  • 6. Re: JBossWS vs Glassfish, do we a 'Tester' ?
                    asoldano

                    I'm sorry, this is not the right forum for Wise issues. Please post your requests for assistance (including any follow-up to this thread) here:
                    http://www.javalinux.it/blogs/index.php?title=wise_1_0_1_released&more=1&c=1&tb=1&pb=1#comments
                    Anyway, you need of course to upgrade the JBossWS that ships with JBoss 4.2.1 and this is most likely the cause of your problem.