Need some clarification for the createOrder Service

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Need some clarification for the createOrder Service

cjhorton
Hi Everyone,

I would appreciate if someone could clear up some confusion for me.

The createOrder service located in orderservices.java isn't defined as a typical service in the order/servicedef/services.xml file.  

Is this an older pattern that has just remained or what?

Thanks for your clarification!

-CJ
Reply | Threaded
Open this post in threaded view
|

Re: Need some clarification for the createOrder Service

BJ Freeman
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

this is normal.
it is referenced the minilan in
location="org.ofbiz.order.order.OrderServices" invoke="createOrder

you can see this in
<service name="storeOrder" engine="java" validate="true" auth="true"


cjhorton sent the following on 1/12/2009 3:22 PM:

> Hi Everyone,
>
> I would appreciate if someone could clear up some confusion for me.
>
> The createOrder service located in orderservices.java isn't defined as a
> typical service in the order/servicedef/services.xml file.  
>
> Is this an older pattern that has just remained or what?
>
> Thanks for your clarification!
>
> -CJ
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJa+a9rP3NbaWWqE4RAkFDAJ0SM5ZMOBkcChT3N561HvcVFwvETwCgnEr8
VS2NM5bJ4YXaCnvfDyFZiWY=
=zZvI
-----END PGP SIGNATURE-----
Reply | Threaded
Open this post in threaded view
|

Re: Need some clarification for the createOrder Service

Tushar Abhyankar
In reply to this post by cjhorton
Hi CJ,
       In servicedef files we can have a different name and invoke  
attribute. for eg  in the service definition of "createOrder" is

  <service name="storeOrder" engine="java" validate="true" auth="true"  
location="org.ofbiz.order.order.OrderServices" invoke="createOrder">

here we can have different name and invoke attribute. The  
name="storeOrder" and
invoke="createOrder".

This is not an Older Pattern.According to convention it is preferable  
to have name and invoke attribute same, especially for CRUD  
operation.But we can have name and invoke attribute different.

Regards,
Tushar Abhyankar
Amicon Technologies Pvt. Ltd. Mumbai, India.
India's No. 1 Ofbiz service provider.




Quoting cjhorton <[hidden email]>:

>
> Hi Everyone,
>
> I would appreciate if someone could clear up some confusion for me.
>
> The createOrder service located in orderservices.java isn't defined as a
> typical service in the order/servicedef/services.xml file.
>
> Is this an older pattern that has just remained or what?
>
> Thanks for your clarification!
>
> -CJ
> --
> View this message in context:  
> http://www.nabble.com/Need-some-clarification-for-the-createOrder-Service-tp21426261p21426261.html
> Sent from the OFBiz - User mailing list archive at Nabble.com.
>
>



Reply | Threaded
Open this post in threaded view
|

Re: Need some clarification for the createOrder Service

cjhorton
Thank you BJ and Tushar for the clarification!

On Mon, Jan 12, 2009 at 10:17 PM, <[hidden email]> wrote:

> Hi CJ,
>      In servicedef files we can have a different name and invoke attribute.
> for eg  in the service definition of "createOrder" is
>
>  <service name="storeOrder" engine="java" validate="true" auth="true"
> location="org.ofbiz.order.order.OrderServices" invoke="createOrder">
>
> here we can have different name and invoke attribute. The name="storeOrder"
> and
> invoke="createOrder".
>
> This is not an Older Pattern.According to convention it is preferable to
> have name and invoke attribute same, especially for CRUD operation.But we
> can have name and invoke attribute different.
>
> Regards,
> Tushar Abhyankar
> Amicon Technologies Pvt. Ltd. Mumbai, India.
> India's No. 1 Ofbiz service provider.
>
>
>
>
>
> Quoting cjhorton <[hidden email]>:
>
>
>> Hi Everyone,
>>
>> I would appreciate if someone could clear up some confusion for me.
>>
>> The createOrder service located in orderservices.java isn't defined as a
>> typical service in the order/servicedef/services.xml file.
>>
>> Is this an older pattern that has just remained or what?
>>
>> Thanks for your clarification!
>>
>> -CJ
>> --
>> View this message in context:
>> http://www.nabble.com/Need-some-clarification-for-the-createOrder-Service-tp21426261p21426261.html
>> Sent from the OFBiz - User mailing list archive at Nabble.com.
>>
>>
>>
>
>
>