[OpenVPMS Developers] [JIRA] Created: (OVPMS-933) Simple Ordering services
Key: OVPMS-933 URL: https://openvpms.atlassian.net/browse/OVPMS-933 Project: VPMS Web Application Issue Type: Sub-task Components: Supplier Reporter: Tony De Keizer Assignee: Tim Anderson
The simple ordering services provide interface definitions and default implementations to allow client applications to send orders to supply chain partners and receive simple order responses.
The OrderService interface is defined as follows:
@WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
OrderResponseSimpleType createOrder(OrderType order);
}
The createOrder method will accept a UBL order from a client application and dispatch this order via SOAP to a service provided by the supply chain partner. As each supplier will have a different URL for their SOAP service the implementation will need to provide a mechanism to allow this URL to be defined as either part of the createOrder call or by finding this information utilising the unique supplier identifier found in the UBL Order document. The createOrder method will support synchronous responses and return a simple UBL OrderResponseSimple document or return null if no synchronous response was returned by the Supply Chain partner.
The OrderResponseService is defined as follows:
WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
OrderResponseSimpleType getOrderResponse(OrderType order);
}
The orderResponse method allows client applications to submit OrrdeResponseSimple UBL documents and process these documents. The default implementation will provide a SOAP web service to accept these responses.
The getOrderResponse method allows the client application to request a OrderResponseSimple for the Order specified in the parameter from the supply chain partner. The default implementation will utilise a SOAP web service call to a supplier specific URL.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf
[OpenVPMS Developers] [JIRA] Updated: (OVPMS-933) Simple Orderin
Tim Anderson updated OVPMS-933: -------------------------------
Description: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
Orders and their corresponding responses will be UBL messages, sent using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
OrderResponseSimpleType createOrder(OrderType order);
OrderResponseSimpleType getOrderResponse(String orderId);
} {code}
A client uses createOrder() to submit a new order. The supplier can return an OrderResponseSimpleType to indicate that the order has been accepted, or return null to indicate that the order will be processed asynchronously. Ideally, responses will be sent via OrderReponseService. If the supplier cannot call back the client, the getOrderResponse() method is provided to enable the client to poll the supplier for the order response. It is a configuration issue as to which means of obtaining responses is used.
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
was: The simple ordering services provide interface definitions and default implementations to allow client applications to send orders to supply chain partners and receive simple order responses.
The OrderService interface is defined as follows:
@WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
OrderResponseSimpleType createOrder(OrderType order);
}
The createOrder method will accept a UBL order from a client application and dispatch this order via SOAP to a service provided by the supply chain partner. As each supplier will have a different URL for their SOAP service the implementation will need to provide a mechanism to allow this URL to be defined as either part of the createOrder call or by finding this information utilising the unique supplier identifier found in the UBL Order document. The createOrder method will support synchronous responses and return a simple UBL OrderResponseSimple document or return null if no synchronous response was returned by the Supply Chain partner.
The OrderResponseService is defined as follows:
WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
OrderResponseSimpleType getOrderResponse(OrderType order);
}
The orderResponse method allows client applications to submit OrrdeResponseSimple UBL documents and process these documents. The default implementation will provide a SOAP web service to accept these responses.
The getOrderResponse method allows the client application to request a OrderResponseSimple for the Order specified in the parameter from the supply chain partner. The default implementation will utilise a SOAP web service call to a supplier specific URL.
> Simple Ordering services > ------------------------ > > Key: OVPMS-933 > URL: https://openvpms.atlassian.net/browse/OVPMS-933 > Project: VPMS Web Application > Issue Type: Sub-task > Components: Supplier > Reporter: Tony De Keizer > Assignee: Tim Anderson > > The ordering services provide interface definitions and stub implementations to allow applications to: > * send orders to supply chain partners > * receive order responses from supply chain partners > Orders and their corresponding responses will be UBL messages, sent using SOAP. > Two web services will be defined, using JAX-WS: > * OrderService - enables an application to submit an order to a supplier > * OrderResponseService - enables a supplier to send a response to an order back to the application. > The OrderService interface might be defined as follows: > {code} > @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderService { > OrderResponseSimpleType createOrder(OrderType order); > > OrderResponseSimpleType getOrderResponse(String orderId); > } > {code} > A client uses createOrder() to submit a new order. The supplier can return an OrderResponseSimpleType to indicate that the order has been accepted, or return null to indicate that the order will be processed asynchronously. > Ideally, responses will be sent via OrderReponseService. > If the supplier cannot call back the client, the getOrderResponse() method is provided to enable the client to poll the supplier for the order response. > It is a configuration issue as to which means of obtaining responses is used. > The OrderResponseService might look something like: > {code} > WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderResponseService { > > void orderReponse(OrderResponseSimpleType response); > > } > {code}-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf
[OpenVPMS Developers] [JIRA] Updated: (OVPMS-933) Simple Orderin
Tony De Keizer updated OVPMS-933: ---------------------------------
Description: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
Orders and their corresponding responses will be UBL messages, sent using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
OrderResponseSimpleType createOrder(OrderType order);
OrderResponseSimpleType getOrderResponse(String orderId);
} {code}
A client uses createOrder() to submit a new order. The supplier can return an OrderResponseSimpleType to indicate that the order has been accepted, or return null to indicate that the order will be processed asynchronously. Ideally, responses will be sent via OrderReponseService. If the supplier cannot call back the client, the getOrderResponse() method is provided to enable the client to poll the supplier for the order response. It is a configuration issue as to which means of obtaining responses is used.
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
The development will include the following tasks:
* Define and supply the schematron and xsl definitions for the Order and OrderResponseSimple UBL documents. This will allow the interface and supply chain partners to validate UBL documents. * Develop and test interfaces and stub implementations. * Develop and test a java test client which allows interactive testing of the new services, The client will be command line driven and allow xml files containing UBL Order and OrderResponse documents to be submitted to the interface for testing purposes. The client will allow interface responses and errors to be displayed and logged. Configuration information will be provided to the client via a property file.
was: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
Orders and their corresponding responses will be UBL messages, sent using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
OrderResponseSimpleType createOrder(OrderType order);
OrderResponseSimpleType getOrderResponse(String orderId);
} {code}
A client uses createOrder() to submit a new order. The supplier can return an OrderResponseSimpleType to indicate that the order has been accepted, or return null to indicate that the order will be processed asynchronously. Ideally, responses will be sent via OrderReponseService. If the supplier cannot call back the client, the getOrderResponse() method is provided to enable the client to poll the supplier for the order response. It is a configuration issue as to which means of obtaining responses is used.
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
> Simple Ordering services > ------------------------ > > Key: OVPMS-933 > URL: https://openvpms.atlassian.net/browse/OVPMS-933 > Project: VPMS Web Application > Issue Type: Sub-task > Components: Supplier > Reporter: Tony De Keizer > Assignee: Tim Anderson > > The ordering services provide interface definitions and stub implementations to allow applications to: > * send orders to supply chain partners > * receive order responses from supply chain partners > Orders and their corresponding responses will be UBL messages, sent using SOAP. > Two web services will be defined, using JAX-WS: > * OrderService - enables an application to submit an order to a supplier > * OrderResponseService - enables a supplier to send a response to an order back to the application. > The OrderService interface might be defined as follows: > {code} > @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderService { > OrderResponseSimpleType createOrder(OrderType order); > > OrderResponseSimpleType getOrderResponse(String orderId); > } > {code} > A client uses createOrder() to submit a new order. The supplier can return an OrderResponseSimpleType to indicate that the order has been accepted, or return null to indicate that the order will be processed asynchronously. > Ideally, responses will be sent via OrderReponseService. > If the supplier cannot call back the client, the getOrderResponse() method is provided to enable the client to poll the supplier for the order response. > It is a configuration issue as to which means of obtaining responses is used. > The OrderResponseService might look something like: > {code} > WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderResponseService { > > void orderReponse(OrderResponseSimpleType response); > > } > {code} > The development will include the following tasks: > * Define and supply the schematron and xsl definitions for the Order and OrderResponseSimple UBL documents. This will allow the interface and supply chain partners to validate UBL documents. > * Develop and test interfaces and stub implementations. > * Develop and test a java test client which allows interactive testing of the new services, The client will be command line driven and allow xml files containing UBL Order and OrderResponse documents to be submitted to the interface for testing purposes. The client will allow interface responses and errors to be displayed and logged. Configuration information will be provided to the client via a property file.-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf
[OpenVPMS Developers] [JIRA] Updated: (OVPMS-933) Simple Orderin
Tim Anderson updated OVPMS-933: -------------------------------
Original Estimate: 5 days, 20 hours Remaining Estimate: 5 days, 20 hours Description: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
OrderResponseSimpleType createOrder(OrderType order);
OrderResponseSimpleType getOrderResponse(String orderId);
} {code}
A client uses createOrder() to submit a new order. The supplier can return an OrderResponseSimpleType to indicate that the order has been accepted, or return null to indicate that the order will be processed asynchronously. Ideally, responses will be sent via OrderReponseService. If the supplier cannot call back the client, the getOrderResponse() method is provided to enable the client to poll the supplier for the order response. It is a configuration issue as to which means of obtaining responses is used.
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
The development will include the following tasks:
* Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService * Develop classes to adapt UBL documents received from OrderResponseService (or polled from OrderService) and update the corresponding act.supplierOrder act * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier * Define and supply the schematron and xsl definitions for the Order and OrderResponseSimple UBL documents. This will allow the interface and supply chain partners to validate UBL documents. * Develop and test interfaces and stub implementations. * Develop and test a java test client which allows interactive testing of the new services, The client will be command line driven and allow xml files containing UBL Order and OrderResponse documents to be submitted to the interface for testing purposes. The client will allow interface responses and errors to be displayed and logged. Configuration information will be provided to the client via a property file.
was: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
Orders and their corresponding responses will be UBL messages, sent using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
OrderResponseSimpleType createOrder(OrderType order);
OrderResponseSimpleType getOrderResponse(String orderId);
} {code}
A client uses createOrder() to submit a new order. The supplier can return an OrderResponseSimpleType to indicate that the order has been accepted, or return null to indicate that the order will be processed asynchronously. Ideally, responses will be sent via OrderReponseService. If the supplier cannot call back the client, the getOrderResponse() method is provided to enable the client to poll the supplier for the order response. It is a configuration issue as to which means of obtaining responses is used.
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
The development will include the following tasks:
* Define and supply the schematron and xsl definitions for the Order and OrderResponseSimple UBL documents. This will allow the interface and supply chain partners to validate UBL documents. * Develop and test interfaces and stub implementations. * Develop and test a java test client which allows interactive testing of the new services, The client will be command line driven and allow xml files containing UBL Order and OrderResponse documents to be submitted to the interface for testing purposes. The client will allow interface responses and errors to be displayed and logged. Configuration information will be provided to the client via a property file.
> Simple Ordering services > ------------------------ > > Key: OVPMS-933 > URL: https://openvpms.atlassian.net/browse/OVPMS-933 > Project: VPMS Web Application > Issue Type: Sub-task > Components: Supplier > Reporter: Tony De Keizer > Assignee: Tim Anderson > Original Estimate: 5 days, 20 hours > Remaining Estimate: 5 days, 20 hours > > The ordering services provide interface definitions and stub implementations to allow applications to: > * send orders to supply chain partners > * receive order responses from supply chain partners > The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP. > Two web services will be defined, using JAX-WS: > * OrderService - enables an application to submit an order to a supplier > * OrderResponseService - enables a supplier to send a response to an order back to the application. > The OrderService interface might be defined as follows: > {code} > @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderService { > OrderResponseSimpleType createOrder(OrderType order); > > OrderResponseSimpleType getOrderResponse(String orderId); > } > {code} > A client uses createOrder() to submit a new order. The supplier can return an OrderResponseSimpleType to indicate that the order has been accepted, or return null to indicate that the order will be processed asynchronously. > Ideally, responses will be sent via OrderReponseService. > If the supplier cannot call back the client, the getOrderResponse() method is provided to enable the client to poll the supplier for the order response. > It is a configuration issue as to which means of obtaining responses is used. > The OrderResponseService might look something like: > {code} > WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderResponseService { > > void orderReponse(OrderResponseSimpleType response); > > } > {code} > The development will include the following tasks: > * Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService > * Develop classes to adapt UBL documents received from OrderResponseService (or polled from OrderService) and update the corresponding act.supplierOrder act > * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier > * Define and supply the schematron and xsl definitions for the Order and OrderResponseSimple UBL documents. This will allow the interface and supply chain partners to validate UBL documents. > * Develop and test interfaces and stub implementations. > * Develop and test a java test client which allows interactive testing of the new services, The client will be command line driven and allow xml files containing UBL Order and OrderResponse documents to be submitted to the interface for testing purposes. The client will allow interface responses and errors to be displayed and logged. Configuration information will be provided to the client via a property file.-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf
[OpenVPMS Developers] [JIRA] Moved: (ESCI-2) Simple Ordering ser
Tim Anderson moved OVPMS-933 to ESCI-2: ---------------------------------------
Project: OpenVPMS e-Supply Chain Interface (was: VPMS Web Application) Key: ESCI-2 (was: OVPMS-933)
> Simple Ordering services > ------------------------ > > Key: ESCI-2 > URL: https://openvpms.atlassian.net/browse/ESCI-2 > Project: e-Supply Chain Interface > Issue Type: Sub-task > Components: Supplier > Reporter: Tony De Keizer > Assignee: Tim Anderson > Original Estimate: 5 days, 20 hours > Remaining Estimate: 5 days, 20 hours > > The ordering services provide interface definitions and stub implementations to allow applications to: > * send orders to supply chain partners > * receive order responses from supply chain partners > The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP. > Two web services will be defined, using JAX-WS: > * OrderService - enables an application to submit an order to a supplier > * OrderResponseService - enables a supplier to send a response to an order back to the application. > The OrderService interface might be defined as follows: > {code} > @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderService { > OrderResponseSimpleType createOrder(OrderType order); > > OrderResponseSimpleType getOrderResponse(String orderId); > } > {code} > A client uses createOrder() to submit a new order. The supplier can return an OrderResponseSimpleType to indicate that the order has been accepted, or return null to indicate that the order will be processed asynchronously. > Ideally, responses will be sent via OrderReponseService. > If the supplier cannot call back the client, the getOrderResponse() method is provided to enable the client to poll the supplier for the order response. > It is a configuration issue as to which means of obtaining responses is used. > The OrderResponseService might look something like: > {code} > WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderResponseService { > > void orderReponse(OrderResponseSimpleType response); > > } > {code} > The development will include the following tasks: > * Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService > * Develop classes to adapt UBL documents received from OrderResponseService (or polled from OrderService) and update the corresponding act.supplierOrder act > * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier > * Define and supply the schematron and xsl definitions for the Order and OrderResponseSimple UBL documents. This will allow the interface and supply chain partners to validate UBL documents. > * Develop and test interfaces and stub implementations. > * Develop and test a java test client which allows interactive testing of the new services, The client will be command line driven and allow xml files containing UBL Order and OrderResponse documents to be submitted to the interface for testing purposes. The client will allow interface responses and errors to be displayed and logged. Configuration information will be provided to the client via a property file.-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf
[OpenVPMS Developers] [JIRA] Updated: (ESCI-2) Simple Ordering s
Tim Anderson updated ESCI-2: ----------------------------
Description: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
OrderResponseSimpleType createOrder(OrderType order);
OrderResponseSimpleType getOrderResponse(String orderId);
} {code}
A client uses createOrder() to submit a new order. The supplier can return an OrderResponseSimpleType to indicate that the order has been accepted, or return null to indicate that the order will be processed asynchronously. Ideally, responses will be sent via OrderReponseService. If the supplier cannot call back the client, the getOrderResponse() method is provided to enable the client to poll the supplier for the order response. It is a configuration issue as to which means of obtaining responses is used.
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
The development will include the following tasks:
* Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService * Develop classes to adapt UBL documents received from OrderResponseService (or polled from OrderService) and update the corresponding act.supplierOrder act * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier * Define and supply the schematron and xsl definitions for the Order and OrderResponseSimple UBL documents. This will allow the interface and supply chain partners to validate UBL documents. * Develop and test interfaces and stub implementations. * Develop and test a java test client which allows interactive testing of the new services, The client will be command line driven and allow xml files containing UBL Order and OrderResponse documents to be submitted to the interface for testing purposes. The client will allow interface responses and errors to be displayed and logged. Configuration information will be provided to the client via a property file.
NOTE: Order cancellation and amendment will be supported at a later date.
was: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
OrderResponseSimpleType createOrder(OrderType order);
OrderResponseSimpleType getOrderResponse(String orderId);
} {code}
A client uses createOrder() to submit a new order. The supplier can return an OrderResponseSimpleType to indicate that the order has been accepted, or return null to indicate that the order will be processed asynchronously. Ideally, responses will be sent via OrderReponseService. If the supplier cannot call back the client, the getOrderResponse() method is provided to enable the client to poll the supplier for the order response. It is a configuration issue as to which means of obtaining responses is used.
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
The development will include the following tasks:
* Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService * Develop classes to adapt UBL documents received from OrderResponseService (or polled from OrderService) and update the corresponding act.supplierOrder act * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier * Define and supply the schematron and xsl definitions for the Order and OrderResponseSimple UBL documents. This will allow the interface and supply chain partners to validate UBL documents. * Develop and test interfaces and stub implementations. * Develop and test a java test client which allows interactive testing of the new services, The client will be command line driven and allow xml files containing UBL Order and OrderResponse documents to be submitted to the interface for testing purposes. The client will allow interface responses and errors to be displayed and logged. Configuration information will be provided to the client via a property file.
Component/s: (was: Supplier)
> Simple Ordering services > ------------------------ > > Key: ESCI-2 > URL: https://openvpms.atlassian.net/browse/ESCI-2 > Project: e-Supply Chain Interface > Issue Type: Sub-task > Reporter: Tony De Keizer > Assignee: Tim Anderson > Original Estimate: 140h > Remaining Estimate: 140h > > The ordering services provide interface definitions and stub implementations to allow applications to: > * send orders to supply chain partners > * receive order responses from supply chain partners > The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP. > Two web services will be defined, using JAX-WS: > * OrderService - enables an application to submit an order to a supplier > * OrderResponseService - enables a supplier to send a response to an order back to the application. > The OrderService interface might be defined as follows: > {code} > @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderService { > OrderResponseSimpleType createOrder(OrderType order); > > OrderResponseSimpleType getOrderResponse(String orderId); > } > {code} > A client uses createOrder() to submit a new order. The supplier can return an OrderResponseSimpleType to indicate that the order has been accepted, or return null to indicate that the order will be processed asynchronously. > Ideally, responses will be sent via OrderReponseService. > If the supplier cannot call back the client, the getOrderResponse() method is provided to enable the client to poll the supplier for the order response. > It is a configuration issue as to which means of obtaining responses is used. > The OrderResponseService might look something like: > {code} > WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderResponseService { > > void orderReponse(OrderResponseSimpleType response); > > } > {code} > The development will include the following tasks: > * Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService > * Develop classes to adapt UBL documents received from OrderResponseService (or polled from OrderService) and update the corresponding act.supplierOrder act > * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier > * Define and supply the schematron and xsl definitions for the Order and OrderResponseSimple UBL documents. This will allow the interface and supply chain partners to validate UBL documents. > * Develop and test interfaces and stub implementations. > * Develop and test a java test client which allows interactive testing of the new services, The client will be command line driven and allow xml files containing UBL Order and OrderResponse documents to be submitted to the interface for testing purposes. The client will allow interface responses and errors to be displayed and logged. Configuration information will be provided to the client via a property file. > NOTE: Order cancellation and amendment will be supported at a later date.-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf
[OpenVPMS Developers] [JIRA] Updated: (ESCI-2) Simple Ordering s
Tim Anderson updated ESCI-2: ----------------------------
Original Estimate: 120h (was: 140h) Remaining Estimate: 120h (was: 140h) Description: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
void createOrder(OrderType order);
} {code}
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
The development will include the following tasks:
* Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService * Develop classes to adapt UBL documents received from OrderResponseService and update the corresponding act.supplierOrder act * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier * Define a UBL profile for OpenVPMS using schematron and xsl definitions for the Order and OrderResponseSimple UBL documents. This will allow the interface and supply chain partners to validate UBL documents as per the OpenVPMS eSCI requirements. * Develop command line client that enables orders to be submitted to the OrderService from a file. This is provided for suppliers that don't have the facility to invoke the SOAP service directly. * Develop command line client that enables order responses to be submitted to the OrderResponseService from a file. This is provided for suppliers that don't have the facility to invoke the SOAP service directly. * Develop test implementation of the OrderService that accepts, validates and logs orders. * Develop test implementation of the OrderResponseService that accepts, validates and logs order responses.
NOTE: Order cancellation and amendment will be supported at a later date.
was: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
OrderResponseSimpleType createOrder(OrderType order);
OrderResponseSimpleType getOrderResponse(String orderId);
} {code}
A client uses createOrder() to submit a new order. The supplier can return an OrderResponseSimpleType to indicate that the order has been accepted, or return null to indicate that the order will be processed asynchronously. Ideally, responses will be sent via OrderReponseService. If the supplier cannot call back the client, the getOrderResponse() method is provided to enable the client to poll the supplier for the order response. It is a configuration issue as to which means of obtaining responses is used.
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
The development will include the following tasks:
* Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService * Develop classes to adapt UBL documents received from OrderResponseService (or polled from OrderService) and update the corresponding act.supplierOrder act * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier * Define and supply the schematron and xsl definitions for the Order and OrderResponseSimple UBL documents. This will allow the interface and supply chain partners to validate UBL documents. * Develop and test interfaces and stub implementations. * Develop and test a java test client which allows interactive testing of the new services, The client will be command line driven and allow xml files containing UBL Order and OrderResponse documents to be submitted to the interface for testing purposes. The client will allow interface responses and errors to be displayed and logged. Configuration information will be provided to the client via a property file.
NOTE: Order cancellation and amendment will be supported at a later date.
> Simple Ordering services > ------------------------ > > Key: ESCI-2 > URL: https://openvpms.atlassian.net/browse/ESCI-2 > Project: e-Supply Chain Interface > Issue Type: Sub-task > Reporter: Tony De Keizer > Assignee: Tim Anderson > Original Estimate: 120h > Remaining Estimate: 120h > > The ordering services provide interface definitions and stub implementations to allow applications to: > * send orders to supply chain partners > * receive order responses from supply chain partners > The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP. > Two web services will be defined, using JAX-WS: > * OrderService - enables an application to submit an order to a supplier > * OrderResponseService - enables a supplier to send a response to an order back to the application. > The OrderService interface might be defined as follows: > {code} > @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderService { > void createOrder(OrderType order); > > } > {code} > The OrderResponseService might look something like: > {code} > WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderResponseService { > > void orderReponse(OrderResponseSimpleType response); > > } > {code} > The development will include the following tasks: > * Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService > * Develop classes to adapt UBL documents received from OrderResponseService and update the corresponding act.supplierOrder act > * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier > * Define a UBL profile for OpenVPMS using schematron and xsl definitions for the Order and OrderResponseSimple UBL documents. > This will allow the interface and supply chain partners to validate UBL documents as per the OpenVPMS eSCI requirements. > * Develop command line client that enables orders to be submitted to the OrderService from a file. > This is provided for suppliers that don't have the facility to invoke the SOAP service directly. > * Develop command line client that enables order responses to be submitted to the OrderResponseService from a file. > This is provided for suppliers that don't have the facility to invoke the SOAP service directly. > * Develop test implementation of the OrderService that accepts, validates and logs orders. > * Develop test implementation of the OrderResponseService that accepts, validates and logs order responses. > NOTE: Order cancellation and amendment will be supported at a later date.-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf
[OpenVPMS Developers] [JIRA] Updated: (ESCI-2) Simple Ordering s
Tim Anderson updated ESCI-2: ----------------------------
Description: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
void createOrder(OrderType order);
} {code}
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
The development will include the following tasks:
* Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService * Develop classes to adapt UBL documents received from OrderResponseService and update the corresponding act.supplierOrder act * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier * Develop command line client that enables orders to be submitted to the OrderService from a file. This is provided for suppliers that don't have the facility to invoke the SOAP service directly. * Develop command line client that enables order responses to be submitted to the OrderResponseService from a file. This is provided for suppliers that don't have the facility to invoke the SOAP service directly. * Develop test implementation of the OrderService that accepts, validates and logs orders. * Develop test implementation of the OrderResponseService that accepts, validates and logs order responses.
NOTE: Order cancellation and amendment will be supported at a later date.
was: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
void createOrder(OrderType order);
} {code}
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
The development will include the following tasks:
* Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService * Develop classes to adapt UBL documents received from OrderResponseService and update the corresponding act.supplierOrder act * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier * Define a UBL profile for OpenVPMS using schematron and xsl definitions for the Order and OrderResponseSimple UBL documents. This will allow the interface and supply chain partners to validate UBL documents as per the OpenVPMS eSCI requirements. * Develop command line client that enables orders to be submitted to the OrderService from a file. This is provided for suppliers that don't have the facility to invoke the SOAP service directly. * Develop command line client that enables order responses to be submitted to the OrderResponseService from a file. This is provided for suppliers that don't have the facility to invoke the SOAP service directly. * Develop test implementation of the OrderService that accepts, validates and logs orders. * Develop test implementation of the OrderResponseService that accepts, validates and logs order responses.
NOTE: Order cancellation and amendment will be supported at a later date.
Definition of an OpenVPMS UBL profile now out of the scope of this project
> Simple Ordering services > ------------------------ > > Key: ESCI-2 > URL: https://openvpms.atlassian.net/browse/ESCI-2 > Project: e-Supply Chain Interface > Issue Type: Sub-task > Reporter: Tony De Keizer > Assignee: Tim Anderson > Original Estimate: 120h > Time Spent: 62h > Remaining Estimate: 58h > > The ordering services provide interface definitions and stub implementations to allow applications to: > * send orders to supply chain partners > * receive order responses from supply chain partners > The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP. > Two web services will be defined, using JAX-WS: > * OrderService - enables an application to submit an order to a supplier > * OrderResponseService - enables a supplier to send a response to an order back to the application. > The OrderService interface might be defined as follows: > {code} > @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderService { > void createOrder(OrderType order); > > } > {code} > The OrderResponseService might look something like: > {code} > WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderResponseService { > > void orderReponse(OrderResponseSimpleType response); > > } > {code} > The development will include the following tasks: > * Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService > * Develop classes to adapt UBL documents received from OrderResponseService and update the corresponding act.supplierOrder act > * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier > * Develop command line client that enables orders to be submitted to the OrderService from a file. > This is provided for suppliers that don't have the facility to invoke the SOAP service directly. > * Develop command line client that enables order responses to be submitted to the OrderResponseService from a file. > This is provided for suppliers that don't have the facility to invoke the SOAP service directly. > * Develop test implementation of the OrderService that accepts, validates and logs orders. > * Develop test implementation of the OrderResponseService that accepts, validates and logs order responses. > NOTE: Order cancellation and amendment will be supported at a later date.-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf
[OpenVPMS Developers] [JIRA] Updated: (ESCI-2) Simple Ordering s
Tim Anderson updated ESCI-2: ----------------------------
Remaining Estimate: 42h (was: 58h) Description: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
void createOrder(OrderType order);
} {code}
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
The development will include the following tasks:
* Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService * Develop classes to adapt UBL documents received from OrderResponseService and update the corresponding act.supplierOrder act * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier * Develop test implementation of the OrderService that accepts, validates and logs orders. * Develop test implementation of the OrderResponseService that accepts, validates and logs order responses.
NOTE: Order cancellation and amendment will be supported at a later date.
was: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
void createOrder(OrderType order);
} {code}
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
The development will include the following tasks:
* Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService * Develop classes to adapt UBL documents received from OrderResponseService and update the corresponding act.supplierOrder act * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier * Develop command line client that enables orders to be submitted to the OrderService from a file. This is provided for suppliers that don't have the facility to invoke the SOAP service directly. * Develop command line client that enables order responses to be submitted to the OrderResponseService from a file. This is provided for suppliers that don't have the facility to invoke the SOAP service directly. * Develop test implementation of the OrderService that accepts, validates and logs orders. * Develop test implementation of the OrderResponseService that accepts, validates and logs order responses.
NOTE: Order cancellation and amendment will be supported at a later date.
Removed from scope: * Develop command line client that enables orders to be submitted to the OrderService from a file. This is provided for suppliers that don't have the facility to invoke the SOAP service directly. * Develop command line client that enables order responses to be submitted to the OrderResponseService from a file. This is provided for suppliers that don't have the facility to invoke the SOAP service directly.
> Simple Ordering services > ------------------------ > > Key: ESCI-2 > URL: https://openvpms.atlassian.net/browse/ESCI-2 > Project: e-Supply Chain Interface > Issue Type: Sub-task > Reporter: Tony De Keizer > Assignee: Tim Anderson > Original Estimate: 120h > Time Spent: 62h > Remaining Estimate: 42h > > The ordering services provide interface definitions and stub implementations to allow applications to: > * send orders to supply chain partners > * receive order responses from supply chain partners > The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP. > Two web services will be defined, using JAX-WS: > * OrderService - enables an application to submit an order to a supplier > * OrderResponseService - enables a supplier to send a response to an order back to the application. > The OrderService interface might be defined as follows: > {code} > @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderService { > void createOrder(OrderType order); > > } > {code} > The OrderResponseService might look something like: > {code} > WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderResponseService { > > void orderReponse(OrderResponseSimpleType response); > > } > {code} > The development will include the following tasks: > * Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService > * Develop classes to adapt UBL documents received from OrderResponseService and update the corresponding act.supplierOrder act > * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier > * Develop test implementation of the OrderService that accepts, validates and logs orders. > * Develop test implementation of the OrderResponseService that accepts, validates and logs order responses. > NOTE: Order cancellation and amendment will be supported at a later date.-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf
[OpenVPMS Developers] [JIRA] Updated: (ESCI-2) Simple Ordering s
Tim Anderson updated ESCI-2: ----------------------------
Description: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
void createOrder(OrderType order);
} {code}
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
The development will include the following tasks:
* Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService * Develop classes to adapt UBL documents received from OrderResponseService and update the corresponding act.supplierOrder act * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier * Develop test implementation of the OrderService that accepts, validates and logs orders. * Develop test implementation of the OrderResponseService that accepts, validates and logs order responses. * Document mapping of act.supplierOrder to UBL Order * Document mandatory fields of UBL OrderResponseSimple
NOTE: Order cancellation and amendment will be supported at a later date.
was: The ordering services provide interface definitions and stub implementations to allow applications to: * send orders to supply chain partners * receive order responses from supply chain partners
The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP.
Two web services will be defined, using JAX-WS: * OrderService - enables an application to submit an order to a supplier * OrderResponseService - enables a supplier to send a response to an order back to the application.
The OrderService interface might be defined as follows:
{code} @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderService {
void createOrder(OrderType order);
} {code}
The OrderResponseService might look something like:
{code} WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @Addressing(enabled = true, required = true) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) public interface OrderResponseService {
void orderReponse(OrderResponseSimpleType response);
} {code}
The development will include the following tasks:
* Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService * Develop classes to adapt UBL documents received from OrderResponseService and update the corresponding act.supplierOrder act * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier * Develop test implementation of the OrderService that accepts, validates and logs orders. * Develop test implementation of the OrderResponseService that accepts, validates and logs order responses.
NOTE: Order cancellation and amendment will be supported at a later date.
> Simple Ordering services > ------------------------ > > Key: ESCI-2 > URL: https://openvpms.atlassian.net/browse/ESCI-2 > Project: e-Supply Chain Interface > Issue Type: Sub-task > Reporter: Tony De Keizer > Assignee: Tim Anderson > Original Estimate: 120h > Time Spent: 62h > Remaining Estimate: 42h > > The ordering services provide interface definitions and stub implementations to allow applications to: > * send orders to supply chain partners > * receive order responses from supply chain partners > The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP. > Two web services will be defined, using JAX-WS: > * OrderService - enables an application to submit an order to a supplier > * OrderResponseService - enables a supplier to send a response to an order back to the application. > The OrderService interface might be defined as follows: > {code} > @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderService { > void createOrder(OrderType order); > > } > {code} > The OrderResponseService might look something like: > {code} > WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderResponseService { > > void orderReponse(OrderResponseSimpleType response); > > } > {code} > The development will include the following tasks: > * Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService > * Develop classes to adapt UBL documents received from OrderResponseService and update the corresponding act.supplierOrder act > * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier > * Develop test implementation of the OrderService that accepts, validates and logs orders. > * Develop test implementation of the OrderResponseService that accepts, validates and logs order responses. > * Document mapping of act.supplierOrder to UBL Order > * Document mandatory fields of UBL OrderResponseSimple > NOTE: Order cancellation and amendment will be supported at a later date.-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf
[OpenVPMS Developers] [JIRA] Updated: (ESCI-2) Simple Ordering s
Tony De Keizer updated ESCI-2: ------------------------------
Affects Version/s: 1.5 Fix Version/s: 1.5 Component/s: Ordering
> Simple Ordering services > ------------------------ > > Key: ESCI-2 > URL: https://openvpms.atlassian.net/browse/ESCI-2 > Project: e-Supply Chain Interface > Issue Type: Sub-task > Components: Ordering > Affects Versions: 1.5 > Reporter: Tony De Keizer > Assignee: Tim Anderson > Fix For: 1.5 > > Original Estimate: 120h > Time Spent: 62h > Remaining Estimate: 42h > > The ordering services provide interface definitions and stub implementations to allow applications to: > * send orders to supply chain partners > * receive order responses from supply chain partners > The default implementation will convert act.supplierOrder acts to UBL Order messages and send them using SOAP. > Two web services will be defined, using JAX-WS: > * OrderService - enables an application to submit an order to a supplier > * OrderResponseService - enables a supplier to send a response to an order back to the application. > The OrderService interface might be defined as follows: > {code} > @WebService(name = "OrderService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderService { > void createOrder(OrderType order); > > } > {code} > The OrderResponseService might look something like: > {code} > WebService(name = "OrderResponseService", targetNamespace = "http://openvpms.org/esci") > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) > @Addressing(enabled = true, required = true) > @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING) > public interface OrderResponseService { > > void orderReponse(OrderResponseSimpleType response); > > } > {code} > The development will include the following tasks: > * Develop classes to adapt act.supplierOrder acts to UBL and submit them to the appropriate supplier via OrderService > * Develop classes to adapt UBL documents received from OrderResponseService and update the corresponding act.supplierOrder act > * Define an interface to enable notification when act.supplierOrder acts are updated by a supplier, or an error occurs communicating with the supplier > * Develop test implementation of the OrderService that accepts, validates and logs orders. > * Develop test implementation of the OrderResponseService that accepts, validates and logs order responses. > * Document mapping of act.supplierOrder to UBL Order > * Document mandatory fields of UBL OrderResponseSimple > NOTE: Order cancellation and amendment will be supported at a later date.-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf