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.Delivery


      if (!queues.isEmpty())
      {
         ClusteredQueue queue = (ClusteredQueue)queues.get(target);


         Delivery del = queue.handle(observer, ref, tx);


         if (trace) { log.trace(this + " routed to remote queue, it returned " + del); }


         incTarget();

View Full Code Here

Examples of org.jboss.messaging.core.Delivery

                  throw new IllegalStateException("Local post office has foreign bindings!");
               }


               Queue queue = binding.getQueue();


               Delivery del = queue.handle(null, ref, tx);


               if (del != null && del.isSelectorAccepted())
               {
                  routed = true;
               }
            }

View Full Code Here

Examples of org.jboss.messaging.core.Delivery

   public void acknowledge(Message r, Transaction tx) throws Throwable
   {
      log.debug(this + " acknowledging "  + r);


      Object[] touple = null;
      Delivery d = null;
      for (Iterator i = messages.iterator(); i.hasNext(); )
      {
         Object[] o = (Object[])i.next();
         Message m = (Message)o[0];
         if (m == r)
         {
            log.trace("*** found it");
            d = (Delivery)o[1];
            touple = o;
            break;
         }
      }


      if (touple == null)
      {
         throw new IllegalStateException("The message " + r + " hasn't been received yet!");
      }


      if (d == null)
      {
         throw new IllegalStateException("The message " + r + " has already been acknowledged!");
      }


      d.acknowledge(tx);


      log.trace(this + " acknowledged "  + r);


      // make sure I get rid of message if the transaction is rolled back
      if (tx != null)

View Full Code Here

Examples of org.jboss.messaging.core.Delivery

   }


   public void cancel(Message r) throws Throwable
   {
      Object[] touple = null;
      Delivery d = null;
      for (Iterator i = messages.iterator(); i.hasNext(); )
      {
         Object[] o = (Object[])i.next();
         Message m = (Message)o[0];
         if (m == r)
         {
            d = (Delivery)o[1];
            touple = o;
            i.remove();
            break;
         }
      }


      if (touple == null)
      {
         throw new IllegalStateException("The message " + r + " hasn't been received yet!");
      }


      if (d == null)
      {
         throw new IllegalStateException("The message " + r + " has already been acknowledged!");
      }


      d.cancel();


      log.trace(this + " cancelled "  + r);
   }

View Full Code Here

Examples of org.jboss.messaging.core.Delivery

            Queue queue = binding.getQueue();
   
            if (trace) log.trace("Destination for message[ID=" + ref.getMessage().getMessageID() + "] is: " + queue);
   
            //Create a new delivery - note that it must have a delivery observer otherwise acknowledge will fail
            Delivery del = new SimpleDelivery(queue, ref);


            if (trace) log.trace("Acknowledging..");


            try
            {
               del.acknowledge(tx);
            }
            catch (Throwable t)
            {
               log.error("Failed to acknowledge " + del + " during recovery", t);
            }

View Full Code Here

Examples of org.jboss.messaging.core.Delivery

         
         //Need to cancel in reverse
         
         for (int i = toCancel.size() - 1; i >= 0; i--)
         {                     
            Delivery del = (Delivery)toCancel.get(i);
            
            try
            {
               del.cancel();
            }
            catch (Throwable t)
            {
               log.error("Failed to cancel delivery", t);
               throw new TransactionException(t.getMessage(), t);

View Full Code Here

Examples of org.jboss.messaging.core.Delivery

      if (receiversCopy.isEmpty())
      {
         return null;
      }


      Delivery del = null;
      
      boolean selectorRejected = false;
      
      int initial = target;


      while (true)
      {
         Receiver r = (Receiver)receiversCopy.get(target);


         try
         {
            Delivery d = r.handle(observer, ref, tx);


            if (trace) { log.trace("receiver " + r + " handled " + ref + " and returned " + d); }


            if (d != null)
            {
               if (d.isSelectorAccepted())
               {
                  // deliver to the first receiver that accepts
                  del = d;
                  
                  incTarget();

View Full Code Here

Examples of org.jboss.messaging.core.Delivery

            
            makeCopy = false;
         }
      }    
      
      Delivery del = null;
      
      boolean selectorRejected = false;


      for(Iterator i = receiversCopy.iterator(); i.hasNext(); )
      {
         Receiver receiver = (Receiver)i.next();


         try
         {
            Delivery d = receiver.handle(observer, ref, tx);


            if (trace) { log.trace("receiver " + receiver + " handled " + ref + " and returned " + d); }


            if (d != null)
            {
               if (d.isSelectorAccepted())
               {
                  // deliver to the first receiver that accepts
                  del = d;
                  break;
               }

View Full Code Here

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

           {
             Queue queue = (Queue)iter.next();
             
             if (trace) { log.trace(this + " Routing ref to queue " + queue); }
                        
             Delivery del = queue.handle(null, ref, tx);
             
             if (trace) { log.trace("Queue returned " + del); }


               if (del != null && del.isSelectorAccepted())
               {
                  routed = true;
                  
                  if (remoteSet != null)
                  {

View Full Code Here

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

       
       //This can actually be null - e.g. if failure happened right after a successful Ack so the client doesn't
       //remove the delivery but is no longer on the server
       if (re != null)
       {                
         Delivery del = new SimpleDelivery(this, re.ref);
         
         if (trace) { log.trace("Recovered ref " + re.ref); }
         
         refs.add(del);
       }

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.