3 Replies Latest reply on Jun 15, 2004 5:25 PM by khelenek

    non-primitive object as method param

    khelenek Newbie

      Hi,
      So I successfully deployed my ejb as a web service, but when I generated my axis client classes (using wsdl2java) the Boolean parameter in my method is now a boolean primitive in the client stub.

      I looked at the wsdl that jboss-net creates and it does not denote anywhere that the parameter should be nillable. I assumed it would figure this out itself - is there a way to denote this in xdoclet or something?

      Also, does anyone have a way to generate client code without deploying the web service first to generate the wsdl. Like using java2wsdl then wsdl2java? (I'm working on that but I can't get it to work.. wondering if it was possible before I spend a day on that..)

      Thanks,
      Kris

        • 1. Re: non-primitive object as method param
          Jason Greene Master

           

          "khelenek" wrote:
          Hi,
          I looked at the wsdl that jboss-net creates and it does not denote anywhere that the parameter should be nillable. I assumed it would figure this out itself - is there a way to denote this in xdoclet or something?
          [/quate]

          This looks like a bug, there is no way to denote this in xdoclet becuase the EJBProvider generates the type information at runtime. I would try the 3.2.4 release candidate, and open a bug if it still happens


          Also, does anyone have a way to generate client code without deploying the web service first to generate the wsdl.


          No, since the EJB provider is generated at runtime, there is no way to do this. If this really is a problem, you may want to write the webservice yourself as the standard rpc provider, and just call your session bean methods

          -Jason


          • 2. Re: non-primitive object as method param
            Jason Greene Master

            Sorry errors in my last post...


            Hi,
            I looked at the wsdl that jboss-net creates and it does not denote anywhere that the parameter should be nillable. I assumed it would figure this out itself - is there a way to denote this in xdoclet or something?


            This looks like a bug, there is no way to denote this in xdoclet becuase the EJBProvider generates the type information at runtime. I would try the 3.2.4 release candidate, and open a bug if it still happens


            Also, does anyone have a way to generate client code without deploying the web service first to generate the wsdl.


            No, since the EJB provider is generated at runtime, there is no way to do this. If this really is a problem, you may want to write the webservice yourself as the standard rpc provider, and just call your session bean methods

            -Jason

            • 3. Re: non-primitive object as method param
              khelenek Newbie

              Jason - thanks very much.

              I tried the 3.2.4 edition w/o luck, so I submitted this as a bug.