[svn] 2449: Add some JMS messaging tests to app server specific excludes lists.

Revision: 2449
Author: [email protected]
Date: 2008-07-11 07:22:10 -0700 (Fri, 11 Jul 2008)
Log Message:
Add some JMS messaging tests to app server specific excludes lists. Some of the JMS tests fail on certain app servers because of features that are not supported on those app servers.
Modified Paths:
blazeds/branches/3.0.x/qa/features/excludes.properties

Hi,
Did you create your destinations in your application server? It seems that the destinations such as topics and queues are not created. First you should create them and then start using them.
For example, in here, it says that jndi/Topic is not valid. To check if the destinations are valid or not; you can do it either through the graphical user interface or the command line console.

Similar Messages

[svn:bz-trunk] 7643: Add app server specific excludes for jboss5 and websphere7.

Revision: 7643
Author:   [email protected]
Date:     2009-06-08 13:32:14 -0700 (Mon, 08 Jun 2009)
Log Message:
Add app server specific excludes for jboss5 and websphere7.
Modified Paths:
    blazeds/trunk/qa/features/excludes.properties

[svn] 3687: Add some messaging tests for scenarios that involve subscribing to a destination , disconnecting from the channel currently being used and resubscribing to the destination .

Revision: 3687
Author: [email protected]
Date: 2008-10-16 11:23:39 -0700 (Thu, 16 Oct 2008)
Log Message:
Add some messaging tests for scenarios that involve subscribing to a destination, disconnecting from the channel currently being used and resubscribing to the destination. There is an issue that is causing the streaming/multipleDisconnectsResubscribesTest.mxml test to fail that I will log a bug for.
Added Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeJMSTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/multipleDisconnectsResubscribesTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeJMSTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/multipleDisconnectsResubscribesTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeJMSTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/multipleDisconnectsResubscribesTest.mxml

Revision: 3687
Author: [email protected]
Date: 2008-10-16 11:23:39 -0700 (Thu, 16 Oct 2008)
Log Message:
Add some messaging tests for scenarios that involve subscribing to a destination, disconnecting from the channel currently being used and resubscribing to the destination. There is an issue that is causing the streaming/multipleDisconnectsResubscribesTest.mxml test to fail that I will log a bug for.
Added Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeJMSTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/multipleDisconnectsResubscribesTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeJMSTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/multipleDisconnectsResubscribesTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeJMSTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/multipleDisconnectsResubscribesTest.mxml

[svn] 4068: fix some negative config tests - updates to the error message text

Revision: 4068
Author: [email protected]
Date: 2008-11-11 08:37:37 -0800 (Tue, 11 Nov 2008)
Log Message:
fix some negative config tests - updates to the error message text
additional negative test to validate we throw when advanced messaging property access is attempted
Modified Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/InvalidBufferPolicyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/InvalidConflatePolicyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/frequencies/McfGreaterthanMfTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/InvalidBufferPolicyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/InvalidConflatePolicyTest/error.txt
Added Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/messaging-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/messaging-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/messaging-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/readme.txt

Revision: 4068
Author: [email protected]
Date: 2008-11-11 08:37:37 -0800 (Tue, 11 Nov 2008)
Log Message:
fix some negative config tests - updates to the error message text
additional negative test to validate we throw when advanced messaging property access is attempted
Modified Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/InvalidBufferPolicyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/InvalidConflatePolicyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/frequencies/McfGreaterthanMfTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/InvalidBufferPolicyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/InvalidConflatePolicyTest/error.txt
Added Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/messaging-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/messaging-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/messaging-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/readme.txt

[svn] 2219: Add a negative constructor test case for RemoteObject destination.

Revision: 2219
Author: [email protected]
Date: 2008-06-24 14:20:55 -0700 (Tue, 24 Jun 2008)
Log Message:
Add a negative constructor test case for RemoteObject destination.
Modified Paths:
blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/remoting-config.mods.xml
Added Paths:
blazeds/trunk/qa/apps/qa-regress/WEB-INF/src/remoting/ConstructorNegativeTest.java
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/ConstructorNegat iveTest.mxml

Revision: 2219
Author: [email protected]
Date: 2008-06-24 14:20:55 -0700 (Tue, 24 Jun 2008)
Log Message:
Add a negative constructor test case for RemoteObject destination.
Modified Paths:
blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/remoting-config.mods.xml
Added Paths:
blazeds/trunk/qa/apps/qa-regress/WEB-INF/src/remoting/ConstructorNegativeTest.java
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/ConstructorNegat iveTest.mxml

[svn] 4203: * Fixed some failing invalidation tests.

Revision: 4203
Author: [email protected]
Date: 2008-12-01 10:25:12 -0800 (Mon, 01 Dec 2008)
Log Message:
* Fixed some failing invalidation tests.
tests Passed: checkintests
Needs QA: YES
Needs DOC: NO
Bug fixes: SDK-18180
API Change: NO
Reviewer: Pete F.
Code-level description of changes:
Modified validateCompilationUnits() to restrict
DependencyNeedsRecompilation to dependents not in
updatedWithStableSignature and to restrict DependencyNotCached to
compilation units with type information.
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18180
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java

[svn] 4598: Fixed some approval FlexUnit tests.

Revision: 4598
Author: [email protected]
Date: 2009-01-20 10:45:04 -0800 (Tue, 20 Jan 2009)
Log Message:
Fixed some approval FlexUnit tests.
tests Passed: checkintests
Needs QA: YES
Needs DOC: NO
API Change: NO
Reviewer: Carol
Code-level description of changes:
Modified watchXML() and unwatchXML() to work with XMLList's of
length greater than 1.
Modified Paths:
flex/sdk/trunk/frameworks/projects/framework/src/mx/utils/XMLNotifier.as

How to add some html text between check boxes choices in SharePoint list?

I'm customizing "New Form" of a share point list using SharePoint Designer.
One of column is check boxes, and I need to add some break lines and text between choices, so the choice doesn't become cluttered.
e.g.
Choice 1 ^n
Date
Location
Choice 2 ^n
Date
Location
and so on...
Is that possible?
Thanks

I think your best option would be using InfoPath if you can.
Andy Wessendorf SharePoint Developer II | Rackspace [email protected]

Standalone JMS client in SJS App Server 8.0

Hi
I am trying to retrieve a message from a JMS queue from astandalone client.
The code the client uses to lookup JMS resources is:
try
          /* Create the object of InitialContext interface */
Properties env = new Properties( );
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
env.put(Context.PROVIDER_URL,"iiop://localhost:3700");
     jndiContext = new InitialContext(env);
          /* Find the connection factory object */
     QConnectionFactory = (QueueConnectionFactory)jndiContext.lookup("jms/QConnectionFactory");
     /* Find the queue */
          queue = (Queue) jndiContext.lookup("jms/Queue");
catch (NamingException e)
     System.out.println("Error: " + e.toString());
The code throws the following exception:
Error: javax.naming.NameNotFoundException [Root exception is org.omg.CosNaming.N
amingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
Exception in thread "main" java.lang.NullPointerException
at QReceiver.main(QReceiver.java:51)
What might be the problem? Pls help. The code works fine when executed as an Application client of SJS Appserver without using the JNDI Context part.
Thanks in advance
JLRocky

Also have a problem similar to this. I have found that
1. JMS between beans on the same server work fine
2. JMS between standalone client and server work fine if you start the bundled imq as a standalone message server
3. If you are using the Appserver then standalones cannont connect, but it you are using the imq beans cannot connect.
so i haven't had time to try this yet but my possible solution is:
configure the app server to use an external JMS server (its in the admin console some place) make the external server to be an imq running as a standalone, hopefully it can be started on localhost with out any port changes.
I think rather than bundling the two so both could be used they embeded the imq in the appserver and shielded it from outside comminication

How to add the JMS adapter property in BPEL1.1 version

Hi,
I am working on the Jms adapter by using BPEL version1.1 and i am want to add some Jms property to send with Jms message.We have option to add the Jms property in BPEL2.0 version. But i am not able to add Jms property in BPEL version1.1.
Please help me
SOA 11g : 11.1.1.5

Thanks for everyone's replies. I am now able to set the parameters for the sequence file, just that I added a property node for the sequence file path and the sequence before loading the parameters. That did the trick and the rest was easy. Also for Goto, with some digging, I was able to add a custom property step if it fails or passes the step. It works like a charm. I'm attaching a modified version of my code in LV 7.0 format.
Attachments:
Dynamic Sequence File-1.vi ‏175 KB

PeerGoneException sending large JMS messages using T3.

Hello,
          I'm using WL 7.0 SP4 on the backend. I have clients that send JMS messages to this WL server using T3. Some of the messages are ~1MB in size, and sometimes the clients use dial-up connections with a maximum speed of 54 Kbps. (Yes, I know we are living in the dark ages...)
          Anyway, sometimes the WL server throws a PeerGoneException. I realize this is because the CompleteT3MessageTimeout has expired. I have already set it to the maximum of 480 seconds, but sometimes that's not enough. Is there a way to disable this timeout or set it to be infinite?
          Does anyone have any suggestions?
          thanks in advance,
          matt

sorry for answering myself...
          if you set 480 seconds on client and on server side, you will get a time
          range of 480 seconds.
          you will never be able to get more then 480 seconds. (And yes, there
          only existe the T3MessageTimout, which should be fine to my point of view.
          Another point might be the jta transaction timeout server-side.
          Regards
          Klaas
          Klaas Hagemann schrieb:
          > Hi Matt,
          >
          >
          > the settings have to be the same, client- and serverside. The whole t3
          > connection times out.
          > I only tested it with 8.1, so i cannot give you any advice concerning 7.0.
          > Maybe you should contact BEA Support, they should easily be able to
          > check whether there exists a patch for 7.0
          >
          >
          > Sorry...
          >
          >
          > Klaas
          >
          >
          > Matt Hill schrieb:
          >
          >>Thanks for the reply, Klaus.
          >>
          >>We are using WL 7.0 (not 8.1), so we do not have the CompleteMessageTimeout attribute. WL 7.0 only has the CompleteT3MessageTimeout attribute, which I set to the maximum of 480 secs, but unfortunately it sometimes takes longer to transfer our messages.
          >>
          >>I tried your suggestion of setting the client-side java property, but it did not help. I believe my problem is that the server times out - not the client.
          >>
          >>Any other ideas would be greatly appreciated.
          >>
          >>thanks,
          >>matt

Specifying additional JMS message attributes in Sender Adapter

Hi,
Iam using sender JMS adapter and I have to use the option " Specify Additional JMS Message Properties" for adding addtionalJMS properties in XI message header.
Once I cselect the option in the below table Iam not able to add new lines to add addtional JMS Message Properties..But In receiver adapter I was able to add the new lines.
Is this option graded in SAP PI 7.3 or relatd to any authorization issue..?
Is anyone faced this issue before.. Please help me out
Thank you

Hi everybody
I'm starting a project where I have to take adptadores JMS and I'm in the same situation kirian, I am need to configure a JMS adapter with version of SAP PI 7.3 and I wonder if anyone can help me or give me manuals leagues where information comes related.
Someone can help me with this information
Regards

BusinessService which sends JMS messages to a JBoss 4.2.x server

Hi,
how do I configure my OSB so that I can send JMS messages to a JBoss server? I have added a Foreign JMS server with the appropriate initial context data and have put the jboss relevant jars into my <domain>/lib directory (javassist.jar, jbossall-client.jar, jboss-aop-jdk50.jar, jboss-messaging-client.jar, trove.jar) but I still get an error in the proxy service when it forwards the message to the business service referencing the imported JMS queues and connectionFactory. The message is:
<18.02.2010 18:00 Uhr MEZ> <Warning> <ALSB Logging> <BEA-000000> < [RouteToJboss, _onErrorHandler-1181696354513531347--39bf6a8e.126dc62f38e.-7e57, Log error, ERROR] Error occurred in flow: BEA-380002[JMSPool:169803]JNDI lookup of the JMS connection factory jboss.connectionFactory failed: javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]RouteToJbossrequest-pipeline>
Am I missing something?
Best regards,
Dimo
PS. I also had to put a newer log4j version in the preclasspath because jboss client seems to require verisons >= 1.2.12 and the one shipped with OSB does not cut it

There is a difference between supported and certified.
ADF was certified (meaning tested) with JBoss 4.0.4.
We didn't test with JBoss 4.2 so we don't know if it works or not.
However it is supported - meaning that if you try to deploy to 4.2 and run into issues you can open bugs with Oracle support.

[svn:bz-trunk] 22381: Add some unit tests for the flex.messaging.client. FlexClientManager, including one for the new getFlexClient(String id, boolean createNewIfNotExist) method signature.

Revision: 22381
Revision: 22381
Author:   [email protected]
Date:     2011-09-02 05:10:41 -0700 (Fri, 02 Sep 2011)
Log Message:
Add some unit tests for the flex.messaging.client.FlexClientManager, including one for the new getFlexClient(String id, boolean createNewIfNotExist) method signature.
Added Paths:
    blazeds/trunk/modules/core/test/src/flex/messaging/client/
    blazeds/trunk/modules/core/test/src/flex/messaging/client/FlexClientManagerTest.java

JMS Listner: Test Configuration Successful but not listening the messages

Hi,
I have configured the JMS Listner adapter in IDM 7.0 with Sun MQ 3.5.
My test configuration is susscessful. I have some messages on Sun MQ. I have one wotkflow associated with this adapter. I have mapped it via process rule of Edit Sync Policy. Now I want to read the messages from MQ and want to retrive in my workflow. But when I starts the scynchronization nothing comes to my workflow. The log is showing as
2007-08-16T19:05:38.354+0530: SARunner: initialized adapter
2007-08-16T19:05:38.404+0530: Initializing JMS Listener adapter.
2007-08-16T19:05:38.414+0530: Setting up JMS: local_transaction:true ackMode:1
2007-08-16T19:05:38.414+0530: Setting up JMS: user:admin password:<secret length=5/>
2007-08-16T19:05:38.414+0530: Setting up JMS: destinationType=QUEUE connFactoryName=MyQueueConnectionFactory destinationName=MyQueue messageSelector=null
2007-08-16T19:05:38.424+0530: Connection factory JNDI lookup returned an object of type com.sun.messaging.QueueConnectionFactory
2007-08-16T19:05:38.504+0530: JMS connection and consumer successfully created.
2007-08-16T19:05:38.514+0530: Connection JMS Info
PROVIDER NAME = Sun Java(tm) System Message Queue
PROVIDER VERSION = 3.5
PROVIDER MAJOR = 3
PROVIDER MINOR = 6
JMS VERSION = 1.1
JMS MAJOR = 1
JMS MINOR = 1
CLIENT_ID = null
2007-08-16T19:05:38.524+0530: Done initializing JMS Listener adapter.
2007-08-16T19:05:38.534+0530: SARunner: loop 0
2007-08-16T19:05:38.955+0530: Started, paused until Thu Aug 16 19:05:38 GMT+05:30 2007
2007-08-16T19:05:44.123+0530: Pause completed
2007-08-16T19:05:44.333+0530: Polling
2007-08-16T19:05:45.334+0530: Poll processed 0 messages.
2007-08-16T19:05:45.334+0530: Poll complete.
I am new with this adapter. Please anybody tell me what should I have to configure so that I would be able to read the messages from my JMS Listner Active Sync adapter?
Thanks in Advance

So, in order to get the message you have to map it. That is done be specifying the "Message Mapping", one of the Resource Parameters for JMS Listener. This can be done by specifying a rule that returns a <map> with the attribute. This would be, in my opinion, the preferred approach for text messages. For Map massages, the rule approach can't be used unless you use the jms java libraries, getString etc.
You can also implement the com.waveset.adapter.jms.JmsMessageMapper if java is your cup of tea, and put that in the message mapping text box. Password synch uses a java class to do the mapping.
To map the attribute called accId on the right side, you would use something like this:
<Rule name='JMS Message Mapper Rule'>
    <block>
        <map>
            <s>accId</s>
            <ref>message</ref>
        </map>
    </block>The Message Mapping text box would in this case look like this:
"rule:JMS Message Mapper Rule"
The <ref>message</ref> part contains the JMS text message. In this case the message consist of only one word. In a real-life situation, you would send a bunch of information, perhaps using split to separate the data.

[svn] 2449: Add some JMS messaging tests to app server specific excludes lists.

Similar Messages

Maybe you are looking for