Service Bus Upgrade Scenario 2: Support the latest metadata properties on entities

[gcheng]

Dev estimate: 8
Test estimate: 5

1. QueueToQueue Transfer (ForwardTo)
2. State of entity (enabled/disabled etc.)
3. Enable Pre-Filtering.
4. MessageCountDetails (Read-only)

[gcheng]

• Supporting latest properties – if you have access to our sources, then the full set of properties are in these classes. I think the most notable changes will be AuthorizationRules properties and additional metadata.
o QueueDescription
o TopicDescription
o SubscriptionDescription
o RuleDescrpition

[gcheng]

For Queue, this is the current design, those that are marked with star already exists for Java SDK.

   public static readonly TimeSpan MessageTimeToLiveDefaultValue;
   public QueueDescription(string path)
   public TimeSpan LockDuration * 
   public long MaxSizeInMegabytes *
   public bool RequiresDuplicateDetection *
   public bool RequiresSession *
   public TimeSpan DefaultMessageTimeToLive *
   public TimeSpan AutoDeleteOnIdle
   public bool EnableDeadLetteringOnMessageExpiration *
   public TimeSpan DuplicateDetectionHistoryTimeWindow *
   public string Path *
   public int MaxDeliveryCount *
   public bool EnableBatchedOperations *
   public long SizeInBytes *
   public long MessageCount *
   public MessageCountDetails MessageCountDetails
   public AuthorizationRules Authorization
   public bool IsAnonymousAccessible
   public bool SupportOrdering
   public EntityStatus Status
   public EntityAvailabilityStatus AvailabilityStatus
   public string ForwardTo
   public DateTime CreatedAt
   public DateTime UpdatedAt
   public DateTime AccessedAt
   public PartitioningPolicy PartitioningPolicy
   public string UserMetadata

[gcheng]

The DateTime created from JAXB are XMlGregorianCalender, which are hard to use with Java Date.

[gcheng]

Updates of the queue description has been sent for CR.

[gcheng]

all of them are in CR now.!

[gcheng]

all of them checked in. Adding additional integration test for QueuetoQueue Forward surface some additional requirement.

[gcheng]

get message count details seem to have some problem in integration test.

[gcheng]

Authorization Rules are also pulled out.

[xuezhai]

finished the testing for the meta data get/set, through azure service with modify code not using local object's get/set, found majority of the meta data can't be updated through azure service, error msg include "
https://javasdksbnamespace.servicebus.windows.net/testSubscriptionCanBeUpdated/subscriptions/sub returned a response status of 400 Bad Request
Response Body: 400The entity description of type 'SubscriptionDescription' has unsupported properties for api-version '' in the request. Try including the correct api-version query string in the request..TrackingId:694e4121-c610-481f-86ce-296f55736cd2_G4,TimeStamp:5/14/2013 2:04:50
or just 400 bad request or 500 internal error
several property set/get passed, like set/get maxdeliveryCount for subscript, need to follow up with feature team to find out what is support/not supported for service bus meta data