You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Michele Mazzucco (JIRA)" <ji...@apache.org> on 2006/09/20 11:14:22 UTC

[jira] Created: (AXIS2-1200) org.apache.axis2.engine.Service interface broken

org.apache.axis2.engine.Service interface broken
------------------------------------------------

                 Key: AXIS2-1200
                 URL: http://issues.apache.org/jira/browse/AXIS2-1200
             Project: Apache Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: core
         Environment: win XP sp2, java 1.5.0_03
            Reporter: Michele Mazzucco
            Priority: Blocker
         Attachments: MyService.java, services.xml

I'm facing against serious problems with the eager service initialization features provided by the Service interface (the service is deployed in application scope everything is correct in services.xml). I'm using the latest nightly build.

1 - the 'init' method is called *only* if there's a static initialization elsewhere (i.e. a static block) -- so I guess the init() method is called *only* when the first request comes, and not at system startup as described into the documentation (and a service instance is created)
2 - the startUp() method is *never* called, even if the <parameter name="load-on-startup" locked="false">true</parameter>
parameter is set into services.xml.
Furthermore, if you set this argument, *2* service instances are created at system startup!. Again, if a static block is not present, nothing
happens.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Commented: (AXIS2-1200) org.apache.axis2.engine.Service interface broken

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/AXIS2-1200?page=comments#action_12439697 ] 
            
Davanum Srinivas commented on AXIS2-1200:
-----------------------------------------

Need to at least doc current design / behavior to downgrade this bug.

thanks,
dims

> org.apache.axis2.engine.Service interface broken
> ------------------------------------------------
>
>                 Key: AXIS2-1200
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1200
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: core
>         Environment: win XP sp2, java 1.5.0_03
>            Reporter: Michele Mazzucco
>         Assigned To: Deepal Jayasinghe
>            Priority: Blocker
>         Attachments: MyService.java, services.xml
>
>
> I'm facing against serious problems with the eager service initialization features provided by the Service interface (the service is deployed in application scope everything is correct in services.xml). I'm using the latest nightly build.
> 1 - the 'init' method is called *only* if there's a static initialization elsewhere (i.e. a static block) -- so I guess the init() method is called *only* when the first request comes, and not at system startup as described into the documentation (and a service instance is created)
> 2 - the startUp() method is *never* called, even if the <parameter name="load-on-startup" locked="false">true</parameter>
> parameter is set into services.xml.
> Furthermore, if you set this argument, *2* service instances are created at system startup!. Again, if a static block is not present, nothing
> happens.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Updated: (AXIS2-1200) org.apache.axis2.engine.Service interface broken

Posted by "Michele Mazzucco (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2-1200?page=all ]

Michele Mazzucco updated AXIS2-1200:
------------------------------------

    Attachment: services.xml
                MyService.java

Please find attached the sample which shows what described (it's the sample service
slightly modified) together with the configuration file.

> org.apache.axis2.engine.Service interface broken
> ------------------------------------------------
>
>                 Key: AXIS2-1200
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1200
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: core
>         Environment: win XP sp2, java 1.5.0_03
>            Reporter: Michele Mazzucco
>            Priority: Blocker
>         Attachments: MyService.java, services.xml
>
>
> I'm facing against serious problems with the eager service initialization features provided by the Service interface (the service is deployed in application scope everything is correct in services.xml). I'm using the latest nightly build.
> 1 - the 'init' method is called *only* if there's a static initialization elsewhere (i.e. a static block) -- so I guess the init() method is called *only* when the first request comes, and not at system startup as described into the documentation (and a service instance is created)
> 2 - the startUp() method is *never* called, even if the <parameter name="load-on-startup" locked="false">true</parameter>
> parameter is set into services.xml.
> Furthermore, if you set this argument, *2* service instances are created at system startup!. Again, if a static block is not present, nothing
> happens.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Assigned: (AXIS2-1200) org.apache.axis2.engine.Service interface broken

Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2-1200?page=all ]

Eran Chinthaka reassigned AXIS2-1200:
-------------------------------------

    Assignee: Deepal Jayasinghe

> org.apache.axis2.engine.Service interface broken
> ------------------------------------------------
>
>                 Key: AXIS2-1200
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1200
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: core
>         Environment: win XP sp2, java 1.5.0_03
>            Reporter: Michele Mazzucco
>         Assigned To: Deepal Jayasinghe
>            Priority: Blocker
>         Attachments: MyService.java, services.xml
>
>
> I'm facing against serious problems with the eager service initialization features provided by the Service interface (the service is deployed in application scope everything is correct in services.xml). I'm using the latest nightly build.
> 1 - the 'init' method is called *only* if there's a static initialization elsewhere (i.e. a static block) -- so I guess the init() method is called *only* when the first request comes, and not at system startup as described into the documentation (and a service instance is created)
> 2 - the startUp() method is *never* called, even if the <parameter name="load-on-startup" locked="false">true</parameter>
> parameter is set into services.xml.
> Furthermore, if you set this argument, *2* service instances are created at system startup!. Again, if a static block is not present, nothing
> happens.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Commented: (AXIS2-1200) org.apache.axis2.engine.Service interface broken

Posted by "Michele Mazzucco (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/AXIS2-1200?page=comments#action_12436272 ] 
            
Michele Mazzucco commented on AXIS2-1200:
-----------------------------------------

Some more details: the init() method is called after creating the service instance (does it make any sense??), while the destroy() method works properly.

> org.apache.axis2.engine.Service interface broken
> ------------------------------------------------
>
>                 Key: AXIS2-1200
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1200
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: core
>         Environment: win XP sp2, java 1.5.0_03
>            Reporter: Michele Mazzucco
>            Priority: Blocker
>         Attachments: MyService.java, services.xml
>
>
> I'm facing against serious problems with the eager service initialization features provided by the Service interface (the service is deployed in application scope everything is correct in services.xml). I'm using the latest nightly build.
> 1 - the 'init' method is called *only* if there's a static initialization elsewhere (i.e. a static block) -- so I guess the init() method is called *only* when the first request comes, and not at system startup as described into the documentation (and a service instance is created)
> 2 - the startUp() method is *never* called, even if the <parameter name="load-on-startup" locked="false">true</parameter>
> parameter is set into services.xml.
> Furthermore, if you set this argument, *2* service instances are created at system startup!. Again, if a static block is not present, nothing
> happens.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Error while in WSDL running a simple HelloWorld program.

Posted by "Reddy, Sanket (US - Hyderabad)" <sa...@deloitte.com>.
Hi friends 

This is the first time I am trying axis2. And I am trying to run a simple helloworld program 

public class HelloWorld {
   public String sayHello(String str) {
      return "Hello :"+str ;
   }
}

Services.xml

<service>
   <description>
      This is my first service, which says hello
   </description>
   <parameter name="ServiceClass" locked="false">HelloWorld</parameter>
   <operation name="sayHello">
      <messageReceiver class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
   </operation>
</service>


I have created a HelloWorld.jar and renamed it to HelloWorld.aar and put in the repo\services directory and I start the http-server.bat  with repository location as a parameters. I can find the deployed WS and also the WSDL but when I try to use this WSLD to call the WS using the ALTOVA XML SPY (which creates the SOAP request and also gets the response.)

WSDL file:-
http://localhost:8080/axis2/services/HelloWorld?wsdl

I get an error in SOAP response and mainly I don't see the input field in the SOAP request. To enter the parameter for the sayHello(String str).

Can u please guide me through it.?? Am I doing something wrong ?? Isn't it possible to call the WS using ALTOVA XMY SPY àMENUà SOAPàcreate new soap request.

Can anyone pass the Client code for a simple WS HelloWorld.sayHello(String str) ??

Regards
Sanket 


This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, you should delete this message. 


Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Resolved: (AXIS2-1200) org.apache.axis2.engine.Service interface broken

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2-1200?page=all ]

Davanum Srinivas resolved AXIS2-1200.
-------------------------------------

    Resolution: Fixed

Please see the updates:
http://svn.apache.org/viewvc?view=rev&revision=453202

-- dims

> org.apache.axis2.engine.Service interface broken
> ------------------------------------------------
>
>                 Key: AXIS2-1200
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1200
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: core
>         Environment: win XP sp2, java 1.5.0_03
>            Reporter: Michele Mazzucco
>         Assigned To: Deepal Jayasinghe
>            Priority: Blocker
>         Attachments: MyService.java, services.xml
>
>
> I'm facing against serious problems with the eager service initialization features provided by the Service interface (the service is deployed in application scope everything is correct in services.xml). I'm using the latest nightly build.
> 1 - the 'init' method is called *only* if there's a static initialization elsewhere (i.e. a static block) -- so I guess the init() method is called *only* when the first request comes, and not at system startup as described into the documentation (and a service instance is created)
> 2 - the startUp() method is *never* called, even if the <parameter name="load-on-startup" locked="false">true</parameter>
> parameter is set into services.xml.
> Furthermore, if you set this argument, *2* service instances are created at system startup!. Again, if a static block is not present, nothing
> happens.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org