5 Replies Latest reply on Dec 1, 2007 12:43 PM by jsolderitsch

    No session context for @WebMethod-call

    gena777

      Hello

      i'm trying the @WebService example from the reference-documentation but i'm getting following exception on Identity.instance() call:

      Caused by: java.lang.IllegalStateException: No active session context
       at org.jboss.seam.security.Identity.instance(Identity.java:157)
      


      what am i doing wrong?

      Thanks,
      Gena




        • 1. Re: No session context for @WebMethod-call
          shane.bryzak

          Do you have the SOAPRequestHandler configured in standard-jaxws-endpoint-config.xml, as described by the docs?

          • 2. Re: No session context for @WebMethod-call
            gena777

            Sorry, configured, but didn't deploy.

            Thank you for the hint!

            Gena

            • 3. Re: No session context for @WebMethod-call
              jsolderitsch

               

              "gena777" wrote:
              Sorry, configured, but didn't deploy.

              Thank you for the hint!

              Gena


              I just ran into the same problem but it appears that this file is deployed to my JBoss install.

              And I am seeing the error you reported still.

              Running with Seam 2.0.0GA and Jboss 4.2.2.

              What do I need to deploy? How to make the deployment?



              • 4. Re: No session context for @WebMethod-call
                shane.bryzak

                You need a file called standard-jaxws-endpoint-config.xml deployed in the meta-inf directory of the jar file containing your web service classes. The contents of this file are described in the Web Services chapter of the reference docs.

                • 5. Re: No session context for @WebMethod-call
                  jsolderitsch

                   

                  "shane.bryzak@jboss.com" wrote:
                  You need a file called standard-jaxws-endpoint-config.xml deployed in the meta-inf directory of the jar file containing your web service classes. The contents of this file are described in the Web Services chapter of the reference docs.


                  I thought I was clear on this -- I did have this endpoint file included where it was supposed to be.

                  But as you pointed out in your reply to my new topic related to this subject, the problem turned out to be the service endpoint URL being wrong. Instead of AuctionServiceService, I needed to use jboss-seam-bay-jboss-seam-bay.

                  This usage was unexpected and not documented anywhere that I could see.

                  But with this information, I am able to get the demo seam-bay web service to act as expected.