11 Replies Latest reply on Jan 20, 2006 12:33 AM by Thomas Diesler

    Clarification - is anybody successfully using JSR-181 annota

    Thomas Diesler Master

      It's not too early. If HEAD is not working for you, I shall hit whoever broke it with a large trout.

      The tagged EA release is a defined starting point.

      cvs co -r JBossWS_1_0EA jboss-head-old
      


      Do you compile with jdk1.5?

      tdiesler@TDDELL /cygdrive/d/projects/jboss-archive/jbossws-1.0EA/build/output/jboss-5.0.0alpha
      $ bin/run.sh
      =========================================================================
      
       JBoss Bootstrap Environment
      
       JBOSS_HOME: d:\projects\jboss-archive\jbossws-1.0EA\build\output\jboss-5.0.0alpha
      
       JAVA: /cygdrive/d/java/sun/jdk1.5.0_04/bin/java
      
       JAVA_OPTS: -server -Xms128m -Xmx128m -Dprogram.name=run.sh
      
       CLASSPATH: d:\projects\jboss-archive\jbossws-1.0EA\build\output\jboss-5.0.0alpha\bin\run.jar;d:\java\sun\jdk1.5.0_04\l
      ib\tools.jar
      
      =========================================================================
      
      13:32:39,625 INFO [Server] Starting JBoss (MX MicroKernel)...
      13:32:39,625 INFO [Server] Release ID: JBoss [TheOne] 5.0.0alpha (build: CVSTag=HEAD date=200508111328)
      13:32:39,640 INFO [Server] Home Dir: D:\projects\jboss-archive\jbossws-1.0EA\build\output\jboss-5.0.0alpha
      13:32:39,640 INFO [Server] Home URL: file:/D:/projects/jboss-archive/jbossws-1.0EA/build/output/jboss-5.0.0alpha/
      13:32:39,640 INFO [Server] Patch URL: null
      13:32:39,640 INFO [Server] Server Name: default
      13:32:39,640 INFO [Server] Server Home Dir: D:\projects\jboss-archive\jbossws-1.0EA\build\output\jboss-5.0.0alpha\serve
      r\default
      13:32:39,640 INFO [Server] Server Home URL: file:/D:/projects/jboss-archive/jbossws-1.0EA/build/output/jboss-5.0.0alpha
      /server/default/
      13:32:39,640 INFO [Server] Server Temp Dir: D:\projects\jboss-archive\jbossws-1.0EA\build\output\jboss-5.0.0alpha\serve
      r\default\tmp
      13:32:39,640 INFO [Server] Root Deployment Filename: jboss-service.xml
      13:32:40,125 INFO [ServerInfo] Java version: 1.5.0_04,Sun Microsystems Inc.
      13:32:40,125 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_04-b05,Sun Microsystems Inc.
      13:32:40,125 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
      13:32:40,828 INFO [Server] Core system initialized
      13:32:51,312 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
      13:32:51,500 INFO [WebService] Using RMI server codebase: http://TDDELL:8083/
      13:32:51,796 WARN [MarshalFactory] Could not find marshaller for data type 'invocation'. Object in collection is null
      13:32:52,093 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0.0:1098, backlog=50, no client SocketFact
      ory, Server SocketFactory=class org.jboss.net.sockets.DefaultSocketFactory
      13:32:52,531 INFO [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://192.168.2.101:4446/?marsh
      aller=org.jboss.invocation.unified.marshall.InvocationMarshaller&dataType=invocation&unmarshaller=org.jboss.invocation.u
      nified.marshall.InvocationUnMarshaller]
      13:32:56,875 INFO [EJB3Deployer] Default persistence.properties: {hibernate.transaction.flush_before_completion=false,
      hibernate.jndi.java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces, hibernate.transaction.auto_close_sessio
      n=false, hibernate.jndi.java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, hibernate.cache.provider_cl
      ass=org.hibernate.cache.HashtableCacheProvider, hibernate.transaction.manager_lookup_class=org.hibernate.transaction.JBo
      ssTransactionManagerLookup, hibernate.dialect=org.hibernate.dialect.HSQLDialect, hibernate.query.factory_class=org.hiber
      nate.hql.ast.ASTQueryTranslatorFactory, hibernate.hbm2ddl.auto=create-drop, hibernate.connection.datasource=java:/Defaul
      tDS, hibernate.connection.release_mode=after_statement}
      13:32:56,890 INFO [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://192.168.2.101:3873/]
      13:32:57,937 INFO [AspectDeployer] Deployed AOP: file:/D:/projects/jboss-archive/jbossws-1.0EA/build/output/jboss-5.0.0
      alpha/server/default/deploy/ejb3-interceptors-aop.xml
      13:33:00,406 INFO [Embedded] Catalina naming disabled
      13:33:00,828 INFO [AprLifecycleListener] The Apache Portable Runtime which allows optimal performance in production env
      ironments was not found on the java.library.path: d:\java\sun\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;d:\java\s
      un\jdk1.5.0_04\bin;C:\cygwin\usr\local\bin;C:\cygwin\bin;C:\cygwin\bin;C:\cygwin\usr\X11R6\bin;c:\oracle\ora92\bin;c:\WI
      NDOWS\system32;c:\WINDOWS;c:\WINDOWS\System32\Wbem;c:\Program Files\Common Files\Adaptec Shared\System;c:\Program Files\
      Sysinternals;c:\Program Files\cvsnt;d:\java\sun\jwsdp-1.5\jwsdp-shared\bin;d:\java\sun\jwsdp-1.4\jwsdp-shared\bin;d:\jav
      a\sun\jdk1.5.0_04\bin;d:\java\apache\apache-ant-1.6.5\bin;d:\java\yjp-3.1.1-build449\bin\win32;d:\java\sun\j2eeri-1_4_1\
      bin;d:\projects\j2eetck\bin;c:\Program Files\SSH Secure Shell
      13:33:00,937 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
      13:33:00,953 INFO [Catalina] Initialization processed in 453 ms
      13:33:00,953 INFO [StandardService] Starting service jboss.web
      13:33:00,953 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.10
      13:33:01,000 INFO [StandardHost] XML validation disabled
      13:33:01,031 INFO [Catalina] Server startup in 78 ms
      13:33:01,187 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
      13:33:01,625 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
      13:33:02,218 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
      13:33:03,203 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp38636jbossws-exp.war/
      13:33:03,703 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-ht
      tpil.war/
      13:33:05,390 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://TDDELL/jndi/rmi://TDDELL:1090/jmx
      connector
      13:33:07,828 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-conso
      le.war/
      13:33:09,046 INFO [MailService] Mail Service bound to java:/Mail
      13:33:09,828 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.
      rar
      13:33:10,062 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
      
      13:33:10,296 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
      
      13:33:10,531 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
      13:33:10,828 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
      13:33:10,984 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
      13:33:12,125 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss
      .jca:service=DataSourceBinding,name=DefaultDS to JNDI name 'java:DefaultDS'
      13:33:12,859 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
      13:33:12,937 INFO [DLQ] Bound to JNDI name: queue/DLQ
      13:33:13,250 INFO [ConnectionFactoryBindingService] Bound connection factory for resource adapter for ConnectionManager
       'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA to JNDI name 'java:JmsXA'
      13:33:13,328 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
      13:33:14,093 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
      13:33:14,828 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
      13:33:14,859 INFO [JkMain] Jk running ID=0 time=0/94 config=null
      13:33:14,875 INFO [Server] JBoss (MX MicroKernel) [5.0.0alpha (build: CVSTag=HEAD date=200508111328)] Started in 35s:23
      5ms
      





        • 1. Re: Clarification - is anybody successfully using JSR-181 an
          Thomas Diesler Master

          tdiesler@TDDELL /cygdrive/d/projects/jboss-archive/jbossws-1.0EA/webservice/test
          $ ant -Dtest=jsr181 test

          tests-main:
          [junit] Running org.jboss.test.ws.jsr181.webservice.JSR181WebServiceEJB21TestCase
          [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 10.062 sec
          [junit] Running org.jboss.test.ws.jsr181.webservice.JSR181WebServiceEJB3TestCase
          [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 7.437 sec
          [junit] Running org.jboss.test.ws.jsr181.webservice.JSR181WebServiceJSETestCase
          [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 5.579 sec

          BUILD SUCCESSFUL
          Total time: 40 seconds

          • 2. Re: Clarification - is anybody successfully using JSR-181 an
            Travis Hubbard Newbie

            Not sure if this will be of any help, but I've been using http://incubator.apache.org/beehive/index.html with a great deal of success.

            regards,
            Travis

            • 3. Re: Clarification - is anybody successfully using JSR-181 an
              Matthew Sell Newbie

              It seems as if the JUnit tests are not able to execute, at least with the posted instructions:

              @lincoln:[test] (0) $ /usr/development/ant/bin/ant -Dtest=jsr181 test
              Buildfile: build.xml

              init:
              [echo] -----------------------------------------------
              [echo] java.home = /usr/java/jdk1.5.0_03/jre
              [echo] jboss.home = ../../build/output/jboss-5.0.0alpha
              [echo] -----------------------------------------------

              check-jbossws:

              compile:

              build:

              build-jars:

              test:

              init:
              [echo] -----------------------------------------------
              [echo] java.home = /usr/java/jdk1.5.0_03/jre
              [echo] jboss.home = ../../build/output/jboss-5.0.0alpha
              [echo] -----------------------------------------------

              check-jbossws:

              compile:

              build:

              build-jars:

              tests-main:

              BUILD FAILED
              /usr/development/jboss-alpha-5.0/jboss-head/webservice/test/build.xml:163: The following error occurred while executing this line:
              /usr/development/jboss-alpha-5.0/jboss-head/webservice/test/build.xml:174: Could not create task or type of type: junit.

              Ant could not find the task or a class this task relies upon.

              This is common and has a number of causes; the usual
              solutions are to read the manual pages then download and
              install needed JAR files, or fix the build file:
              - You have misspelt 'junit'.
              Fix: check your spelling.
              - The task needs an external JAR file to execute
              and this is not found at the right place in the classpath.
              Fix: check the documentation for dependencies.
              Fix: declare the task.
              - The task is an Ant optional task and the JAR file and/or libraries
              implementing the functionality were not found at the time you
              yourself built your installation of Ant from the Ant sources.
              Fix: Look in the ANT_HOME/lib for the 'ant-' JAR corresponding to the
              task and make sure it contains more than merely a META-INF/MANIFEST.MF.
              If all it contains is the manifest, then rebuild Ant with the needed
              libraries present in ${ant.home}/lib/optional/ , or alternatively,
              download a pre-built release version from apache.org
              - The build file was written for a later version of Ant
              Fix: upgrade to at least the latest release version of Ant
              - The task is not an Ant core or optional task
              and needs to be declared using .
              - You are attempting to use a task defined using
              or but have spelt wrong or not
              defined it at the point of use

              Remember that for JAR files to be visible to Ant tasks implemented
              in ANT_HOME/lib, the files must be in the same directory or on the
              classpath

              Please neither file bug reports on this problem, nor email the
              Ant mailing lists, until all of these causes have been explored,
              as this is not an Ant bug.

              Total time: 14 seconds


              Looking through "build.xml" - it appears as if the JUnit deps are included in the source distribution. I do have JUnit located in another directory on this computer, but do not yet have any references to it in the form of PATH or CLASSPATH definitions.

              The JBoss build was successful, and started successfully without any errors:

              @lincoln:[bin] (0) $ ./run.sh
              =========================================================================

              JBoss Bootstrap Environment

              JBOSS_HOME: /usr/development/jboss-alpha-5.0/jboss-head/build/output/jboss-5.0.0alpha

              JAVA: /usr/java/jdk1.5.0_03/bin/java

              JAVA_OPTS: -server -Xms128m -Xmx128m -Dprogram.name=run.sh

              CLASSPATH: /usr/development/jboss-alpha-5.0/jboss-head/build/output/jboss-5.0.0alpha/bin/run.jar:/usr/java/jdk1.5.0_03/lib/tools.jar

              =========================================================================

              09:04:17,373 INFO [Server] Starting JBoss (MX MicroKernel)...
              09:04:17,380 INFO [Server] Release ID: JBoss [TheOne] 5.0.0alpha (build: CVSTag=HEAD date=200508110822)
              09:04:17,391 INFO [Server] Home Dir: /usr/development/jboss-alpha-5.0/jboss-head/build/output/jboss-5.0.0alpha
              09:04:17,392 INFO [Server] Home URL: file:/usr/development/jboss-alpha-5.0/jboss-head/build/output/jboss-5.0.0alpha/
              09:04:17,398 INFO [Server] Patch URL: null
              09:04:17,399 INFO [Server] Server Name: default
              09:04:17,400 INFO [Server] Server Home Dir: /usr/development/jboss-alpha-5.0/jboss-head/build/output/jboss-5.0.0alpha/server/default
              09:04:17,402 INFO [Server] Server Home URL: file:/usr/development/jboss-alpha-5.0/jboss-head/build/output/jboss-5.0.0alpha/server/default/
              09:04:17,404 INFO [Server] Server Temp Dir: /usr/development/jboss-alpha-5.0/jboss-head/build/output/jboss-5.0.0alpha/server/default/tmp
              09:04:17,407 INFO [Server] Root Deployment Filename: jboss-service.xml
              09:04:20,129 INFO [ServerInfo] Java version: 1.5.0_03,Sun Microsystems Inc.
              09:04:20,131 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_03-b07,Sun Microsystems Inc.
              09:04:20,133 INFO [ServerInfo] OS-System: Linux 2.6.11-1.27_FC3smp,i386
              09:04:23,514 INFO [Server] Core system initialized
              09:04:39,487 INFO [WebService] Using RMI server codebase: http://lincoln:8083/
              09:04:39,634 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
              09:04:41,388 WARN [MarshalFactory] Could not find marshaller for data type 'invocation'. Object in collection is null
              09:04:43,409 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0.0:1098, backlog=50, no client SocketFactory, Server SocketFactory=class org.jboss.net.sockets.DefaultSocketFactory
              09:04:47,749 INFO [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://127.0.0.1:4446/?marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller&dataType=invocation&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller]
              09:05:08,053 INFO [EJB3Deployer] Default persistence.properties: {hibernate.transaction.flush_before_completion=false, hibernate.jndi.java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces, hibernate.transaction.auto_close_session=false, hibernate.jndi.java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, hibernate.cache.provider_class=org.hibernate.cache.HashtableCacheProvider, hibernate.transaction.manager_lookup_class=org.hibernate.transaction.JBossTransactionManagerLookup, hibernate.dialect=org.hibernate.dialect.HSQLDialect, hibernate.query.factory_class=org.hibernate.hql.ast.ASTQueryTranslatorFactory, hibernate.hbm2ddl.auto=create-drop, hibernate.connection.datasource=java:/DefaultDS, hibernate.connection.release_mode=after_statement}
              09:05:08,073 INFO [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://127.0.0.1:3873/0.0.0.0:3873]
              09:05:12,059 INFO [AspectDeployer] Deployed AOP: file:/usr/development/jboss-alpha-5.0/jboss-head/build/output/jboss-5.0.0alpha/server/default/deploy/ejb3-interceptors-aop.xml
              09:05:23,347 INFO [Embedded] Catalina naming disabled
              09:05:25,087 INFO [AprLifecycleListener] The Apache Portable Runtime which allows optimal performance in production environments was not found on the java.library.path: /usr/java/jdk1.5.0_03/jre/lib/i386/server:/usr/java/jdk1.5.0_03/jre/lib/i386:/usr/java/jdk1.5.0_03/jre/../lib/i386
              09:05:27,298 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
              09:05:27,310 INFO [Catalina] Initialization processed in 3545 ms
              09:05:27,315 INFO [StandardService] Starting service jboss.web
              09:05:27,339 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.10
              09:05:27,888 INFO [StandardHost] XML validation disabled
              09:05:28,017 INFO [Catalina] Server startup in 706 ms
              09:05:29,114 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
              09:05:31,314 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
              09:05:35,494 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
              09:05:38,722 INFO [TomcatDeployer] deploy, ctxPath=/jboss-faces, warUrl=.../deploy/jbossweb-tomcat55.sar/jboss-faces.war/
              09:05:39,313 INFO [ContextConfig] Missing application web.xml, using defaults only StandardEngine[jboss.web].StandardHost[localhost].StandardContext[/jboss-faces]
              09:05:48,343 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp7280jbossws-exp.war/
              09:05:51,670 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://lincoln/jndi/rmi://lincoln:1090/jmxconnector
              09:06:02,562 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
              09:06:04,520 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
              09:06:11,584 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
              09:06:15,449 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
              09:06:20,393 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
              09:06:21,453 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
              09:06:21,515 INFO [JkMain] Jk running ID=0 time=0/267 config=null
              09:06:21,555 INFO [Server] JBoss (MX MicroKernel) [5.0.0alpha (build: CVSTag=HEAD date=200508110822)] Started in 2m:4s:131ms


              I have the ability to checkout various versions of JBoss and perform tests if you would like me to try various versions or commands. Please let me know if there is anything I can do to help your efforts.

              • 4. Re: Clarification - is anybody successfully using JSR-181 an
                Anil Saldanha Master

                Try to get junit.jar in your test build path

                 <!-- XML security uses commons logging -->
                 <pathelement location="../../thirdparty/apache-commons/lib/commons-logging.j
                ar"/>
                 <pathelement location="../../thirdparty/junit-junit/lib/junit.jar"/>
                 </path>
                


                If you have the whole sourcecodebase, then junit.jar is available in the thirdparty directory

                • 5. Re: Clarification - is anybody successfully using JSR-181 an
                  rpochet Newbie

                  I downloaded jboss-head using "cvs co jboss-head", build successfully but I couldn't find @WebService class. I try "cvs co -r JBossWS_1_0EA jboss-head" but cvs couldn't find file on server?

                  • 6. Re: Clarification - is anybody successfully using JSR-181 an
                    Thomas Diesler Master

                    It should work. Is this an anonymous access problem?

                    • 7. Re: Clarification - is anybody successfully using JSR-181 an
                      rpochet Newbie

                      I finally checked out the HEAD version of jboss-5.0.0alpha. It also build successfully. Now I try to test the @WebService annotation as follow:

                      @Stateless
                      public class TestBean implements Test
                      {
                       public String hello()
                       {
                       return "Hello world";
                       }
                      }


                      @WebService
                      @Remote
                      public interface Test
                      {
                       @WebMethod
                       public String hello();
                      }


                      But Jboss does not see the @WebService annotation. When I set it in the TestBean, it tries to deploy the web service but it complaints about a missing URI. Is there any documentation about using JSR-181 annotations?

                      Thanks,

                      • 8. Re: Clarification - is anybody successfully using JSR-181 an
                        Thomas Diesler Master

                        Have a look at

                        cd webservice/test
                        ant -Dtest=jsr181 test
                        
                        tests-main:
                         [junit] Running org.jboss.test.ws.jsr181.webservice.JSR181WebServiceEJB21TestCase
                         [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 18.326 sec
                         [junit] Running org.jboss.test.ws.jsr181.webservice.JSR181WebServiceEJB3TestCase
                         [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 9.003 sec
                         [junit] Running org.jboss.test.ws.jsr181.webservice.JSR181WebServiceJSETestCase
                         [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 6.579 sec
                        


                        • 9. Re: Clarification - is anybody successfully using JSR-181 an
                          rpochet Newbie

                          I had to check out again to get these test cases. Everything is working fine but I still have a question: war file are generated, containing web.xml file. Is it possible to deploy web service without defining such file, only by annotating the class files as described in JCP?

                          thanks in advance

                          • 10. Re: Clarification - is anybody successfully using JSR-181 an
                            aung zay Newbie

                             

                            "msell" wrote:
                            Sorry for the "duplicate" topic - adding a reply to my previous topic is producing an error.


                            Is it too soon to attempt testing of JSR-181 annotations? The "EJB3Bean01" example listed in the blog generates a WSDL, but does not service requests from SOAP clients.

                            Deploying an *.EJB3 with the example produces several errors such as "Unable to find operation addOperationInterceptor", class cast exception (Stateless container).

                            I would *really* like to get started on a test application using JSR-181; is it a bit too early for this?


                            • 11. Re: Clarification - is anybody successfully using JSR-181 an
                              Thomas Diesler Master

                              It's not too early if you are happy with working with jboss-head. There are just a couple of issues that need to be resloved for jbossws-1.0 final

                              We also have a packport of jboss-1.0RC1 available for jboss-4.0.x. You can get it by checking out the latest from Branch_4_0