incubator-wadi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Bartel <j...@mortbay.com>
Subject wadi and jetty in geronimo (trunk)
Date Thu, 05 Jan 2006 18:17:29 GMT
Jules et al,

I think wadi is working in geronimo trunk with jetty. 
At least, I can see a whole bunch of messaging going on
that looks like this:

19:04:14,698 DEBUG [ActiveMQSession] Sending message: ACTIVEMQ_OBJECT_MESSAGE: id = 0 ActiveMQMessage{
, jmsMessageID = ID:panda-36713-1136483970149-18:128, bodyAsBytes = org.activemq.io.util.ByteArray@6ee7ea,
readOnlyMessage = false, jmsClientID = 'ID:panda-36713-1136483970149-11:0' , jmsCorrelationID
= 'null' , jmsDestination = ACTIVECLUSTER.DATA.CLUSTER0, jmsReplyTo = null, jmsDeliveryMode
= 1, jmsRedelivered = false, jmsType = 'null' , jmsExpiration = 0, jmsPriority = 4, jmsTimestamp
= 1136484254688, properties = null, readOnlyProperties = false, entryBrokerName = 'null' ,
entryClusterName = 'null' , consumerNos = null, transactionId = 'null' , xaTransacted = false,
consumerIdentifer = 'null' , messageConsumed = false, transientConsumed = false, sequenceNumber
= 128, deliveryCount = 1, dispatchedFromDLQ = false, messageAcknowledge = null, jmsMessageIdentity
= null, producerKey = ID:panda-36713-1136483970149-18: } ActiveMQObjectMessage{ object = Node[destination:
Temporary
Topic-{TD{ID:panda-36713-1136483970149-11:0}TD}ID:panda-36713-1136483970149-16:0 state: {birthTime=1136484043177,
partitionKeys={0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71},
timeStamp=1136484048976, http=org.codehaus.wadi.http.HTTPProxiedLocation@2e5771, correlationIDMap={},
nodeName=azzuro, name=azzuro}] }

I've committed my changes so you can try too.

I'll now try and fix the 1.0 branch to see if it works. 
That way, we should be in good shape to do a patch.

Also, it sounds like there will be a geronimo 1.0.1 
soon after 1.0, so we may not need to have the
patch around for long.

cheers
Jan

Mime
View raw message