1 2 Previous Next 20 Replies Latest reply on Apr 24, 2006 6:16 AM by alancui Go to original post
      • 15. Re: using WSEE doclet
        rlj
        rlj Jul 22, 2005 11:48 AM (in response to dhartford)

         

        "dhartford" wrote:
        I don't quite remember, but I do recall some of the issues were resolved with WSCOMPILE when you used fork="true".


        OK I'll try that monday morning.

        I've been using the commandline version for the day. My other problem is that I get an error from wscompile regarding some of my custom types used as paramters. These custom types are all interfaces. It's Java, so every method in the bean I'm exposing as a WS is using interfaces. Anyone know if this is the actual problem ie. one cannot expose methods which returns or accepts interfaces as parameters?

          • Actions
        • 16. Re: using WSEE doclet
          thomas.diesler
          thomas.diesler Jul 22, 2005 1:39 PM (in response to dhartford)

          When you want to know when features become available, have a look at the raodmap

          http://jira.jboss.org/jira/browse/JBWS?report=com.atlassian.jira.plugin.system.project:roadmap-panel

            • Actions
          • 17. Re: using WSEE doclet
            erik777
            erik777 Jul 27, 2005 6:11 PM (in response to dhartford)

            Does anyone else get

            compileWS:
[wscompile] error: class java.lang.StackTraceElement does not have a public accessible empty constructor


            when they run wscompile. I get this error when I run it from Ant or command line, and when I use JDK 1.4 or JDK 1.5.


              • Actions
            • 18. Re: using WSEE doclet
              adam.nowotny
              adam.nowotny Dec 18, 2005 11:01 AM (in response to dhartford)

               

              "adammeghji" wrote:
              If your service endpoint isn't getting added to your ejb-jar.xml, make sure you're:
              - building a deployment descriptor with ejbSpec="2.1"
              - add this to your session bean:
              @ejb.interface service-endpoint-class="arm.carrier.interfaces.CarrierFacadeService"

              I was manually doing merges until I did this, and it started adding the service endpoint tag to ejb-jar.xml

              Hope this helps!

              One more thing: set @ejb.bean view-type to "all" ("both" is not enough, as it means only the local and remote, but not service-endpoint).

                • Actions
              • 19. Re: using WSEE doclet
                ashokkumarv
                ashokkumarv Dec 30, 2005 5:05 AM (in response to dhartford)

                 

                "erik777" wrote:
                Does anyone else get

                compileWS:
[wscompile] error: class java.lang.StackTraceElement does not have a public accessible empty constructor


                when they run wscompile. I get this error when I run it from Ant or command line, and when I use JDK 1.4 or JDK 1.5.


                  • Actions
                • 20. Re: using WSEE doclet
                  alancui
                  alancui Apr 24, 2006 6:16 AM (in response to dhartford)

                   

                  "adam.nowotny" wrote:

                  One more thing: set @ejb.bean view-type to "all" ("both" is not enough, as it means only the local and remote, but not service-endpoint).


                  Refering to XDoclet website, we can set @ejb.bean view-type to "local-service-endpoint". By doing this, we can get a local and a serice-endpoint

                    • Actions
                  1 2 Previous Next