Extract binary-content in OSB

Problem: 
From time-to-time, OSB will pass content via reference. For example the following.

<con:binary-content      ref="cid:-394e488:14e149a6684:-7f0d" xmlns:con="http://www.bea.com/wli/sb/context"/>

Resolution:
Use the java callout method org.apache.commons.codec.binary.StringUtils.newStringUsAscii() from commons-codec-1.7.jar to convert reference into string.

Got-cha:
Be sure to place the star in to fetch the byte[] content in $attachments/ctx:attachment/ctx:body/*

Enjoy.

BEA-045049

Description:
A destination of name conflicting has a jms-create-destination-identifier of name id. However, another destination of name original has the same jms-create-destination-identifier. Two destinations with the same jms-create-destination-identifier cannot be co-located on the JMSServer named beName.

Cause:
Two destinations cannot both have the same jms-create-destination-identifier on the same JMSServer, even if the two destinations are from different modules.

This is generally caused by user deploying OSB proxy polling JMS queue/topic but not yet defined in JMSModule.

Weblogic will automatically creates the JNDI under jmsResources JMSModule.

Resolution:
First, check the JNDI tree. If it doesn't appears in the JNDI tree then you'll need to restart the Managed Server.

After restarting Managed Server and problem still persists? Goto jmsResources JMSModule, locate your JMS queue/topic and delete it. Activate your session.

Now recreate your JMS queue/topic.