订单信息管理：查看订单清单，更新订单付款，出货状态。
Orders for information management: View a list of orders, updating of payment orders, shipping status.
清单3是一个上述订单消息的扩展示例。
Listing 3 is an extended example of the above order message.
对于订单表(参见清单2)，只需要将其绑定与一位客户和一个日期相关联，并允许折扣。
For the Order table (see Listing 2), you just want to tie it to a customer and a date and allow for a discount.
在该文件内，您应该仅看到符合您的ILOG规则的订单，如清单7中所示。
Within that file, you should only see orders that conform to your ILOG rule, as shown in Listing 7.
我们可以做一个很长的清单，不许伪造订单等。
清单1中的JDBC代码没有包含任何事务逻辑，它只是在数据库中保存TRADE表中的交易订单。
The JDBC code in Listing 1 includes no transaction logic, yet it persists the trade order in the TRADE table in the database.
利用带新的客户端构件的同一客户端实现请求订单，清单6显示了响应结果。
Using the same client implementation with the new client artifacts to request an order produces the response shown in Listing 6.
清单2给出了CAM如何定义一个简单购买订单的结构。
Listing 2 shows how CAM defines the structure for a simple purchase order.
现在，您只需关心获得足够的客户信息来交付和确认订单，如清单1所示。
Right now, you only care about enough customer information to be able to deliver and confirm the orders, as Listing 1 shows.
清单8.1中的示例的第一个部分定义了一个处理新客户的新订单的过程。
The first part of the example in Listing 8.1 defines a procedure for processing a new order for a new customer.
在清单5中，当用户确认订单的时间超过一分钟，应用程序就会超时。
In Listing 5, when a user takes more than a minute to confirm an order, the application has to time out.
清单7显示了购买订单的模式。
清单8显示了订单汇总的模式。
在清单5中，您有一个称为PO_ID的标准主键列(即订单id)。
In Listing 5, you have a standard primary key column called PO_ID (that is, purchase order ID).
然后使用订单和地址设置表单中的元素值，清单16给出了更新显示内容的代码。
The order and address are both then used to set values of elements on the form; Listing 16 shows the code that updates the display.
清单1显示了表示CICS订单验证程序的WSDL文件。
Listing 1 shows the WSDL file that represents the CICS order validation program.
例如，清单6显示了如何用正则表达式从顾客的订单历史中提取第一笔订单的日期。
For instance, Listing 6 shows how a regular expression can be used to extract the date of the first order in a customer's order History.
在清单8中，订单条目直接嵌入在订单文档中，使得以后查询文档时检索信息快得多。
In Listing 8, the order items have been embedded directly into the order document, making it faster to retrieve this information when querying on the document later.
现在，使用清单14中的代码将包含购买订单的消息发送到AmazonSQS队列。
Now, send the message containing the purchase order to the Amazon SQS queue using the code in Listing 14.
清单5显示了用来添加新订单的client类。
清单3所示的MockupDB是个单体类，模拟客户订单的数据库。
MockupDB, illustrated in Listing 3, is singleton class that simulates a database of customer orders.
使用清单13，这意味着，如果在执行updateacct方法期间抛出受控异常，就会保存交易订单，但不会更新帐户来反映交易情况。
Using Listing 13, this means that if a checked exception occurs during the updateAcct method, the trade order is persisted, but the account isn't updated to reflect the trade.
清单2显示了使用HumanTaskManager通过订单号过滤任务的代码片段。
Listing 2 shows the code snippet to filter the task by the order number using the Human task Manager.
在清单6中，batch块中的多个API调用确保与一个购物订单相关的所有信息将在一个事务中得到更新。
In Listing 6, your multiple API calls inside the batch block guarantee that all the information relative to a purchase order will be updated in a single transaction.
清单5.XMLBeans生成的订单代码。
清单4 所示的MessagingBean是个简单的POJO，有两个方法，都接受订单号，但是分别返回订单细节和客户细节。
MessagingBean, illustrated in Listing 4, is a simple POJO with two methods that take an order number and return order details and customer details, respectively.
为了简化起见，清单1的示例代码中使用了一个描述订单的xml文档(po . xml)，以及一个订单模式(po . xsd)。
For simplicity, in the sample code in Listing 1, we use an XML document (po.xml) that describes a purchase order and the purchase order schema (po.xsd).
这些服务可以提供任意层次的业务功能，从订单管理，到记账，到存货清单，到执行。
These services can provide any level of business function, from order management, to billing, to inventory, to fulfillment.
这些服务可以提供任意层次的业务功能，从订单管理，到记账，到存货清单，到执行。
These services can provide any level of business function, from order management, to billing, to inventory, to fulfillment.
应用推荐