Examples of Delivery

com.asakusafw.compiler.flow.jobflow.JobflowModel.Delivery
com.oltpbenchmark.benchmarks.tpcc.procedures.Delivery
com.rabbitmq.client.QueueingConsumer.Delivery
com.sun.sgs.app.Delivery
jsprit.core.problem.job.Delivery
Delivery extends Service and is intended to model a Service where smth is UNLOADED (i.e. delivered) from a transport unit. @author schroeder
org.apache.camel.example.cafe.Delivery
org.apache.qpid.proton.engine.Delivery
Delivery
org.apache.savan.eventing.Delivery
org.jboss.messaging.core.Delivery
A message delivery. It can be "done" or active. @author Ovidiu Feodorov @author Tim Fox @version $Revision: 2284 $ $Id: Delivery.java 2284 2007-02-13 06:47:23Z ovidiu.feodorov@jboss.com $
org.jboss.messaging.core.contract.Delivery
A message delivery. It can be "done" or active. @author Ovidiu Feodorov @author Tim Fox @version $Revision: 5505 $ $Id: Delivery.java 5505 2008-12-10 14:32:06Z gaohoward $
org.multibit.mbm.client.domain.model.model.Delivery
DTO to provide the following to the application
- Provision of persistent state
A Delivery provides the mechanism for temporary storage of {@link Item}s. A {@link Supplier} maintains a single Delivery(created on demand)
org.qi4j.sample.dcicargo.sample_a.data.shipping.delivery.Delivery
The Delivery describes the actual transportation of the cargo, as opposed to the customer requirement {@link RouteSpecification} and the plan {@link Itinerary}. Complex data of the shipping domain is captured here in a value object that is re-created each time some delivery status changes. Booking The life cycle of a cargo begins with the booking procedure. During a (short) period of time, between booking and initial routing, the cargo has no itinerary and is therefore not_routed. Routing The booking clerk requests a list of possible routes, matching the route specification, and assigns the cargo to one route. The route to which a cargo is assigned is described by an itinerary. The cargo is now routed. Handling Receipt of the cargo in the origin location marks the beginning of a series of handling events that will eventually deliver the cargo at the destination. Handling events are supposed to be registered by local authorities and sent asynchronously to the cargo system which then re-calculate and replaces the delivery value object of the cargo. (In this implementation the trigger is synchronous in {@link ApplicationEvents}and the registration-ui is close to the booking and tracking interfaces for simplicity). Change of destination It may also happen that a cargo is accidentally misrouted when a new destination is selected in the middle of the voyage of the cargo. The cargo then becomes misrouted, which should notify the proper personnel and also trigger a re-routing procedure. In this implementation a synchronous message is sent to system output. Re-routing A cargo can be re-routed during transport, on demand of the customer, in which case a new route is specified for the cargo and a new route is requested. The old itinerary, being a value object, is discarded and a new one is attached to the cargo. Customs The cargo can be checked by the custom authorities anytime during the delivery. In that case it's unknown what happens next so the cargo is then considered misdirected. Claim The life cycle of a cargo ends when the cargo is claimed by the customer.
org.qi4j.sample.dcicargo.sample_b.data.structure.delivery.Delivery
Delivery The Delivery describes the actual transportation of the cargo, as opposed to the Cargo Owner requirement {@link RouteSpecification} and the plan {@link Itinerary}. Complex data of the shipping domain is captured here in a value object that is re-created each time some delivery status changes. Booking The life cycle of a cargo begins with the booking procedure. During a (short) period of time, between booking and initial routing, the cargo has no itinerary and is therefore not routed. Routing The Cargo Owner or booking clerk requests a list of possible routes, matching the route specification, and assigns the cargo to a preferred route. The route to which a cargo is assigned is described by an itinerary. The cargo is now routed. Cargo handling Receipt of the cargo in the origin location marks the beginning of a series of handling events that will eventually deliver the cargo at the destination. Handling events are supposed to be reported by local handling authorities through incident logging applications that then notify us of those events. Processing of handling events When we receive handling event data from an incident logging application we validate and register the event to determine what action to take. A new Delivery snapshot value object is saved with the Cargo. Change of destination It may happen that the Cargo Owner changes the destination of a cargo in the middle of a voyage. The cargo route specification then no longer matches the itinerary and we say that the cargo is misrouted. This will cause the system to notify the proper personel and request the Cargo Owner to re-route the cargo. Re-routing A cargo can be re-routed during transport, on demand of the Cargo Owner, in which case a new itinerary is requested. The old itinerary, being a value object, is discarded and a new one is attached to the cargo. Customs The cargo can be checked by custom authorities anytime during the delivery. This doesn't affect the delivery status of the cargo. Claim The life cycle of a cargo ends when the cargo is claimed by the Cargo Owner. ItineraryProgressIndex We have added an index that tells us how far we have come on our route. An Itinerary describes a route by a list of "legs" that each describes a load time/location, a voyage and an unload time/location. The itineraryProgressIndex indicates what leg is the current leg. In the DDD sample the location was used to determine the current leg, but if the cargo was suddenly in an unexpected location (not in the itinerary) then we wouldn't be able to find out what to expect next. With the itineraryProgressIndex we can and that allow us to derive a more precise delivery snapshot taking the chronological perspective into account too. LastKnowLocation and currentVoyage didn't add much value since we can extract those from the lastHandlingEvent, so we removed those.
org.springbyexample.integration.book.Delivery
Delivery order information. @author David Winterfeldt
org.springframework.integration.samples.cafe.Delivery
@author Marius Bogoevici

Examples of org.jboss.messaging.core.contract.Delivery

                  if (trace)
                  {
                     log.trace(this + " pushing " + ref);
                  }


                  Delivery del = distributor.handle(this, ref, null);


                  setReceiversReady(del != null);


                  if (del == null)
                  {


                     // No receiver, broken receiver or full receiver so we stop delivering
                     if (trace)
                     {
                        log.trace(this + " got no delivery for " +
                                  ref +
                                  " so no receiver got the message. Stopping delivery.");
                     }


                     break;
                  }
                  else if (!del.isSelectorAccepted())
                  {
                     // No receiver accepted the message because no selectors matched, so we create
                     // an iterator (if we haven't already created it) to iterate through the refs
                     // in the channel. No delivery was really performed

View Full Code Here

Examples of org.jboss.messaging.core.contract.Delivery

         {
            // Attempt to push the ref to a receiver


            if (trace) { log.trace(this + " pushing " + ref); }


            Delivery del = distributor.handle(this, ref, null);


            setReceiversReady(del != null);


            if (del == null)
            {
               // No receiver, broken receiver or full receiver so we stop delivering
               if (trace) { log.trace(this + ": no delivery returned for message" + ref + " so no receiver got the message. Delivery is now complete"); }


               return false;
            }
            else if (del.isSelectorAccepted())
            {
               if (trace) { log.trace(this + ": " + del + " returned for message:" + ref); }


               // Receiver accepted the reference

View Full Code Here

Examples of org.multibit.mbm.client.domain.model.model.Delivery


  @Override
  public Optional<Delivery> getInitialisedDeliveryBySupplier(Supplier supplier) {
    Preconditions.checkNotNull(supplier, "supplier cannot be null");


    Delivery delivery;
    if (supplier.getDeliveries().isEmpty()) {
      // Create a suitable delivery
      delivery = DeliveryBuilder
        .newInstance()
        .withSupplier(supplier)

View Full Code Here

Examples of org.qi4j.sample.dcicargo.sample_a.data.shipping.delivery.Delivery

    @Test
    public void step_3_to_5_ValidRegistration__Load_in_Hong_Kong() throws Exception
    {
        new RegisterHandlingEvent( time, time, trackId, "LOAD", "CNHKG", "V100S" ).register();


        Delivery delivery = cargo.delivery().get();
        assertThat( delivery.routingStatus().get(), is( equalTo( RoutingStatus.ROUTED ) ) );
        assertThat( delivery.transportStatus().get(), is( equalTo( TransportStatus.ONBOARD_CARRIER ) ) );
        assertThat( delivery.nextExpectedHandlingEvent().get().handlingEventType().get(), is( equalTo( UNLOAD ) ) );
        assertThat( delivery.nextExpectedHandlingEvent().get().location().get(), is( equalTo( NEWYORK ) ) );
        assertThat( delivery.nextExpectedHandlingEvent().get().voyage().get(), is( equalTo( V100S ) ) );
        assertThat( delivery.lastKnownLocation().get(), is( equalTo( HONGKONG ) ) );
        assertThat( delivery.currentVoyage().get(), is( equalTo( V100S ) ) );
        assertThat( delivery.eta().get(), is( equalTo( arrival ) ) );
        assertThat( delivery.isMisdirected().get(), is( equalTo( false ) ) );
        assertThat( delivery.isUnloadedAtDestination().get(), is( equalTo( false ) ) );
    }

View Full Code Here

Examples of org.qi4j.sample.dcicargo.sample_b.data.structure.delivery.Delivery

                RouteSpecification routeSpec = cargo.routeSpecification().get();
                String destination = routeSpec.destination().get().getCode();
                Date deadline = routeSpec.arrivalDeadline().get();


                // Routing status
                Delivery delivery = cargo.delivery().get();
                RoutingStatus routingStatus = cargo.delivery().get().routingStatus().get();
                boolean isMisrouted = routingStatus == RoutingStatus.MISROUTED;


                // Transport status
                TransportStatus transportStatus = delivery.transportStatus().get();
                boolean isHiJacked = transportStatus.equals( UNKNOWN );


                // Delivery status
                boolean isMisdirected = delivery.isMisdirected().get();
                HandlingEvent event = delivery.lastHandlingEvent().get();
                boolean inCustoms = event != null && event.handlingEventType().get() == CUSTOMS;


                // Output


                item.add( new LinkPanel( "trackingId", CargoDetailsPage.class, trackingId ) );

View Full Code Here

Examples of org.springbyexample.integration.book.Delivery

                    lPickups.add(order);
                    break;              
          }
      }
      
    return new ShoppingCart[] { new Delivery(lDeliveries), new Pickup(lPickups) };
  }

View Full Code Here

Examples of org.springframework.integration.samples.cafe.Delivery

                orderItem.getDrinkType(),
                orderItem.isIced(),
                orderItem.getShots()))
        .aggregate(aggregator -> aggregator
            .outputProcessor(g ->
                new Delivery(g.getMessages()
                    .stream()
                    .map(message -> (Drink) message.getPayload())
                    .collect(Collectors.toList())))
            .correlationStrategy(m -> ((Drink) m.getPayload()).getOrderNumber()), null)
        .handle(CharacterStreamWritingMessageHandler.stdout());

View Full Code Here

Examples of org.springframework.integration.samples.cafe.Delivery

@MessageEndpoint
public class Waiter {


  @Aggregator(inputChannel = "preparedDrinks", outputChannel = "deliveries")
  public Delivery prepareDelivery(List<Drink> drinks) {
    return new Delivery(drinks);
  }

View Full Code Here

Examples of org.springframework.integration.samples.cafe.Delivery

 * @author Marius Bogoevici
 */
public class Waiter {


  public Delivery prepareDelivery(List<Drink> drinks) {
    return new Delivery(drinks);
  }

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.