[Messaging, JMS & JBossMQ] - Re: MDB login for topic subscriber
by pacwest
I also have similar issues. The application was working without any issues with HSQL. But when I ported the JMS tables to Sybase, I started getting the following error:-
2007-02-22 10:41:48,683 WARN {Timer-3} [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
javax.resource.spi.CommException: javax.jms.JMSSecurityException: The login id has an assigned client id 'guest', that is already connected to the server!
at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:756)
at org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:172)
at org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:95)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:519)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:208)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:529)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:410)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:342)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:462)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:894)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactoryImpl.java:378)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:133)
at com.pacwest.commons.jms.Sender.sendObject(Sender.java:62)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.notifyOrderScheduling(ActivationSchedulerTimerListener.java:69)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.handleNotification2(ActivationSchedulerTimerListener.java:50)
at org.jboss.system.ListenerServiceMBeanSupport.handleNotification(ListenerServiceMBeanSupport.java:391)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138)
at $Proxy57.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.jms.JMSSecurityException: The login id has an assigned client id 'guest', that is already connected to the server!
at org.jboss.mq.sm.AbstractStateManager.checkUser(AbstractStateManager.java:168)
at org.jboss.mq.server.JMSDestinationManager.checkUser(JMSDestinationManager.java:741)
at org.jboss.mq.server.JMSServerInterceptorSupport.checkUser(JMSServerInterceptorSupport.java:274)
at org.jboss.mq.server.TracingInterceptor.checkUser(TracingInterceptor.java:694)
at org.jboss.mq.server.JMSServerInvoker.checkUser(JMSServerInvoker.java:274)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:188)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:369)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:595)
2007-02-22 10:41:48,687 ERROR {Timer-3} [org.jboss.resource.adapter.jms.JmsSessionFactoryImpl] could not create session
javax.resource.spi.CommException: javax.jms.JMSSecurityException: The login id has an assigned client id 'guest', that is already connected to the server!
at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:756)
at org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:172)
at org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:95)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:519)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:208)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:529)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:410)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:342)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:462)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:894)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactoryImpl.java:378)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:133)
at com.pacwest.commons.jms.Sender.sendObject(Sender.java:62)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.notifyOrderScheduling(ActivationSchedulerTimerListener.java:69)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.handleNotification2(ActivationSchedulerTimerListener.java:50)
at org.jboss.system.ListenerServiceMBeanSupport.handleNotification(ListenerServiceMBeanSupport.java:391)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138)
at $Proxy57.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.jms.JMSSecurityException: The login id has an assigned client id 'guest', that is already connected to the server!
at org.jboss.mq.sm.AbstractStateManager.checkUser(AbstractStateManager.java:168)
at org.jboss.mq.server.JMSDestinationManager.checkUser(JMSDestinationManager.java:741)
at org.jboss.mq.server.JMSServerInterceptorSupport.checkUser(JMSServerInterceptorSupport.java:274)
at org.jboss.mq.server.TracingInterceptor.checkUser(TracingInterceptor.java:694)
at org.jboss.mq.server.JMSServerInvoker.checkUser(JMSServerInvoker.java:274)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:188)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:369)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:595)
2007-02-22 10:41:48,688 ERROR {Timer-3} [com.pacwest.commons.jms.Sender] [sendObject] Failure closing producer:
java.lang.NullPointerException
at com.pacwest.commons.jms.Sender.sendObject(Sender.java:77)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.notifyOrderScheduling(ActivationSchedulerTimerListener.java:69)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.handleNotification2(ActivationSchedulerTimerListener.java:50)
at org.jboss.system.ListenerServiceMBeanSupport.handleNotification(ListenerServiceMBeanSupport.java:391)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138)
at $Proxy57.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
2007-02-22 10:41:48,690 ERROR {Timer-3} [com.pacwest.commons.jms.Sender] [sendObject] Failure closing session:
java.lang.NullPointerException
at com.pacwest.commons.jms.Sender.sendObject(Sender.java:87)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.notifyOrderScheduling(ActivationSchedulerTimerListener.java:69)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.handleNotification2(ActivationSchedulerTimerListener.java:50)
at org.jboss.system.ListenerServiceMBeanSupport.handleNotification(ListenerServiceMBeanSupport.java:391)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138)
at $Proxy57.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
2007-02-22 10:41:48,691 ERROR {Timer-3} [com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener] An Exception was received.
javax.jms.JMSException: Could not create a session: javax.resource.spi.CommException: javax.jms.JMSSecurityException: The login id has an assigned client id 'guest', that is already connected to the server!
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactoryImpl.java:392)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:133)
at com.pacwest.commons.jms.Sender.sendObject(Sender.java:62)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.notifyOrderScheduling(ActivationSchedulerTimerListener.java:69)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.handleNotification2(ActivationSchedulerTimerListener.java:50)
at org.jboss.system.ListenerServiceMBeanSupport.handleNotification(ListenerServiceMBeanSupport.java:391)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138)
at $Proxy57.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
2007-02-22 10:41:48,692 ERROR {Timer-3} [com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener] An error occurred during the call to notify that Order Scheduling should proceed
2007-02-22 10:41:52,612 INFO {Timer-4} [com.pacwest.schedulable.service_activation.BlocksActivationTimerListener] Got notification (#5): javax.management.timer.TimerNotification[source=pacwest.com:name=BlocksActivationTimer,type=Timer][type=jboss.monitor.heartbeat][message=50], handback: null
2007-02-22 10:41:52,613 INFO {Timer-4} [com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener] The Timer has sent a notification !!! Must wake up the Blocks Order Scheduler!!
2007-02-22 10:41:52,614 DEBUG {Timer-4} [com.pacwest.commons.jms.Sender] [sendObject] preparing jms {queue/BlocksActivationSchedulingQueue}...
2007-02-22 10:41:52,614 DEBUG {Timer-4} [com.pacwest.commons.service_locator.ServiceLocator] Inside ServiceLocator identifying cluster
2007-02-22 10:41:52,614 DEBUG {Timer-4} [com.pacwest.commons.service_locator.ServiceLocator] Setting ServiceLocator in Cluster Mode
2007-02-22 10:41:52,657 WARN {Timer-4} [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
javax.resource.spi.CommException: javax.jms.JMSSecurityException: The login id has an assigned client id 'guest', that is already connected to the server!
at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:756)
at org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:172)
at org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:95)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:519)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:208)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:529)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:410)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:342)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:462)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:894)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactoryImpl.java:378)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:133)
at com.pacwest.commons.jms.Sender.sendObject(Sender.java:62)
at com.pacwest.schedulable.service_activation.BlocksActivationTimerListener.notifyOrderScheduling(BlocksActivationTimerListener.java:70)
at com.pacwest.schedulable.service_activation.BlocksActivationTimerListener.handleNotification2(BlocksActivationTimerListener.java:51)
at org.jboss.system.ListenerServiceMBeanSupport.handleNotification(ListenerServiceMBeanSupport.java:391)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138)
at $Proxy57.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.jms.JMSSecurityException: The login id has an assigned client id 'guest', that is already connected to the server!
at org.jboss.mq.sm.AbstractStateManager.checkUser(AbstractStateManager.java:168)
at org.jboss.mq.server.JMSDestinationManager.checkUser(JMSDestinationManager.java:741)
at org.jboss.mq.server.JMSServerInterceptorSupport.checkUser(JMSServerInterceptorSupport.java:274)
at org.jboss.mq.server.TracingInterceptor.checkUser(TracingInterceptor.java:694)
at org.jboss.mq.server.JMSServerInvoker.checkUser(JMSServerInvoker.java:274)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:188)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:369)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:595)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020749#4020749
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020749
19Â years, 2Â months
[JBoss jBPM] - Cannot deploy my simple BPEL. Please help!
by meghanai_99
I am pasting my BPEL and WSDL files here.
---------------------------- Hello.bpel -------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<!--
BPEL Process Definition
Edited using ActiveWebflow(tm) Professional Designer Version 1.6.0 (http://www.active-endpoints.com)
-->
<process name="Hello" targetNamespace="http://Hello/0" suppressJoinFailure="yes" xmlns:tns="http://Hello/0" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:wsdlevt="http://www.eclipse.org/alf/schema/EventBase/1" xmlns:schemaevt="http://www.eclipse.org/alf/schema/EventBase/1">
<!-- ================================================================= -->
<!-- PARTNERLINKS -->
<!-- List of services participating in this BPEL process -->
<!-- ================================================================= -->
<!-- The 'client' role represents the requester of this service. -->
<!-- ================================================================= -->
<!-- VARIABLES -->
<!-- List of messages and XML documents used within this BPEL process -->
<!-- ================================================================= -->
<!-- Reference to the message passed as input during initiation -->
<!-- Variables generated by Studio -->
<!-- InitVars generated by Studio -->
<!-- Activities generated by Studio -->
<!-- Final Reply activity generated by Studio -->
----------------------------- Hello.wsdl------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="AlfServiceFlow" targetNamespace="http://Hello/0"
xmlns:tns="http://Hello/0"
xmlns:evt="http://www.eclipse.org/alf/schema/EventBase/1"
xmlns:plt2="http://schemas.xmlsoap.org/ws/2004/03/partner-link/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:bpel2="http://schemas.xmlsoap.org/ws/2004/03/business-process/"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://Hello/0" xmlns="http://Hello/0">
<xs:element name="DataElement" type="xs:string"/>
</xs:schema>
<plt2:partnerLinkType name="AlfServiceFlow">
<plt2:role name="AlfServiceFlowProvider" portType="evt:ALFServiceFlow"/>
</plt2:partnerLinkType>
<bpel2:property name="ServiceFlowId" type="xs:string"/>
<bpel2:propertyAlias propertyName="tns:ServiceFlowId" messageType="evt:EventNotice" part="EventNotice">
<bpel2:query>/EventNotice/evt:Base/evt:EventControl/evt:ServiceFlowId</bpel2:query>
</bpel2:propertyAlias>
------------------------ Imported ALFEventManagerSOAP.wsdl -----------------
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:tns="http://www.eclipse.org/alf/schema/EventBase/1" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:evt="http://www.eclipse.org/alf/schema/EventBase/1" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="ALFEventManager" targetNamespace="http://www.eclipse.org/alf/schema/EventBase/1" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:documentation>
WARNING: PRELIMINARY VERSION SUBJECT TO CHANGE
Copyright Notice
The material in this document is Copyright (c) Serena Software, Inc. and others, 2005, 2006
Terms and Conditions:
The Eclipse Foundation makes available all content in this document ("Content").
Unless otherwise indicated below, the Content is provided to you under the terms
and conditions of the Eclipse Public License Version 1.0 ("EPL").
A copy of the EPL is available at http://www.eclipse.org/legal/epl-v10.html.
For purposes of the EPL, "Program" will mean the Content.
If you did not receive this Content directly from the Eclipse Foundation, the
Content is being redistributed by another party ("Redistributor") and different
terms and conditions may apply to your use of any object code in the Content.
Check the Redistributor's license that was provided with the Content.
If you did not receive any such license, contact the Redistributor.
Unless otherwise indicated below, the terms and conditions of the EPL still apply to the Content.
</wsdl:documentation>
<wsdl:types>
<xs:schema xmlns="http://www.eclipse.org/alf/schema/EventBase/1" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.eclipse.org/alf/schema/EventBase/1" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
<xs:annotation>
<xs:documentation>
WARNING: PRELIMINARY VERSION SUBJECT TO CHANGE
</xs:documentation>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Copyright Notice The material in this document is Copyright
(c) Serena Software, Inc. and others, 2005, 2006 Terms and
Conditions: The Eclipse Foundation makes available all
content in this document ("Content"). Unless otherwise
indicated below, the Content is provided to you under the
terms and conditions of the Eclipse Public License Version
1.0 ("EPL"). A copy of the EPL is available at
http://www.eclipse.org/legal/epl-v10.html. For purposes of
the EPL, "Program" will mean the Content. If you did not
receive this Content directly from the Eclipse Foundation,
the Content is being redistributed by another party
("Redistributor") and different terms and conditions may
apply to your use of any object code in the Content. Check
the Redistributor's license that was provided with the
Content. If you did not receive any such license, contact
the Redistributor. Unless otherwise indicated below, the
terms and conditions of the EPL still apply to the Content.
</xs:documentation>
</xs:annotation>
<xs:complexType name="EventBaseType">
<xs:annotation>
<xs:documentation>
EventBaseType is a container for that portion of an ALF
Event that is generally set by the Tool that raises the
event.
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="EventId" type="EventIdType"/>
<xs:element name="Timestamp" type="TimestampType"/>
<xs:element name="EventType" type="EventTypeType"/>
<xs:element name="ObjectType" type="ObjectTypeType"/>
<xs:element name="ObjectId" type="ObjectIdType"/>
<xs:element name="Source" type="SourceType"/>
<xs:element name="User" type="CredentialsType"/>
<xs:element name="EventControl" type="EmBaseType"/>
<xs:element name="BaseExtension" type="BaseExtensionType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:complexType>
<xs:complexType name="EmBaseType">
<xs:annotation>
<xs:documentation>
EventControlType is a container for that portion of an
ALF Event that is generally set by the ALF EventManager.
In some cases, ALF compliant tools may set some fields,
in particular when the event is a result of an ALF
service call to that tool from a ServiceFlow.
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="EmEventId" type="xs:string"/>
<xs:element name="EmTimestamp" type="TimestampType"/>
<xs:element name="PredecedingEmEventId" type="EventIdType"/>
<xs:element name="ApplicationName" type="ApplicationNameType"/>
<xs:element name="EventMatchName" type="EventMatchNameType"/>
<xs:element name="ServiceFlowName" type="ServiceFlowNameType"/>
<xs:element name="ServiceFlowId" type="ServiceFlowIdType"/>
<xs:element name="Callback" type="xs:boolean"/>
<xs:element name="Environment" type="EnvironmentType"/>
<xs:element name="EmUser" type="CredentialsType"/>
<xs:element name="EmExtension" type="EmExtensionType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:complexType>
<xs:simpleType name="EventIdType">
<xs:annotation>
<xs:documentation>
A UUID that uniquely identifies the Event instance.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:maxLength value="36"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="ServiceFlowIdType">
<xs:annotation>
<xs:documentation>
A UUID that uniquely identifies the ServiceFlow
instance.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:maxLength value="36"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="TimestampType">
<xs:annotation>
<xs:documentation>
The date and timestamp when the EventManager received
the Event. This element may be left empty by the event
emitter, in which case, the Event Manager will supply a
value.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:dateTime"/>
</xs:simpleType>
<xs:simpleType name="EventTypeType">
<xs:annotation>
<xs:documentation>
A string indicating the type of event. EventType
designates the verb. That is what action happened to the
Objects that triggered the event.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:simpleType name="ObjectIdType">
<xs:annotation>
<xs:documentation>
An ObjectId identifies the entity or relationship that
changed within a tool. The identifier must be unique for
a particular instance of the source tool. The format of
this element will not be standardized by ALF. The
primary purpose is to allow subsequent ServiceFlows to
uniquely identify (and perhaps access) the object that
triggered the event.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:simpleType name="ObjectTypeType">
<xs:annotation>
<xs:documentation>
The type of entity involved. Note that the word entity
is taken in its broadest sense, referring to whatever
artifact a tool was operating on. For example, for a
data modeling tool, an E-R relationship is a type of
entity (i.e., and ObjectType) to ALF.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:complexType name="SourceType">
<xs:annotation>
<xs:documentation>
A Source element is a container type that describes the
source of the event. ProductCallbackURI is optional for
tools that don't provide a listener to accept the
callback from a tool or serviceflow at a later time.
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="Product" type="ProductType"/>
<xs:element name="ProductVersion" type="ProductVersionType"/>
<xs:element name="ProductInstance" type="ProductInstanceType"/>
<xs:element name="ProductCallbackURI" type="ProductCallbackURIType" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:simpleType name="ProductType">
<xs:annotation>
<xs:documentation>
A descriptive name for the tool (i.e., program) that
emitted the Event. Note that this is a datatype for a
Product element.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:simpleType name="ProductCallbackURIType">
<xs:annotation>
<xs:documentation>
The web service endpoint for tools that support
callbacks from ServiceFlows for additional information.
The element content is optional for transient tools that
may not be running at a later time, and so cannot accept
a callback. Constantly running (server) tools that
support callbacks should supply a URI.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:anyURI"/>
</xs:simpleType>
<xs:simpleType name="ProductInstanceType">
<xs:annotation>
<xs:documentation>
A unique string identifying the instance of the tool.
This is useful when there may be multiple instances of a
product working within an instance of ALF.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:simpleType name="ProductVersionType">
<xs:annotation>
<xs:documentation>
The release version of the product, such as 5.06
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:complexType name="CredentialsType">
<xs:annotation>
<xs:documentation>
A structure to hold security authentication-relevant data.
If present the data within may be encrypted.
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:complexType>
<xs:simpleType name="ApplicationNameType">
<xs:annotation>
<xs:documentation>
The name of the ALF application to which this event
belongs. Depending on the emitting tool, events may or
may not be associated with an ALF application. If the
emitting tool has the information available then it can
provide the ALF ApplicationName as an additional
information to distinguish the event.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:simpleType name="EventMatchNameType">
<xs:annotation>
<xs:documentation>
The name of the event match within the ALF Application
that matches this event. This fields is set by the Event Manager
when it dispatches the event.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:simpleType name="ServiceFlowNameType">
<xs:annotation>
<xs:documentation>
The name of the service flow withing the event match that
matches this event. This field is set by the Event Manager
when it dispatches the event.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:simpleType name="EnvironmentType">
<xs:annotation>
<xs:documentation>
The name of the environment in which this event is being
raised. This element will be set by the ALF Event
manager from its installation configuration.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:simpleType name="ALFSchemaVersionType">
<xs:restriction base="xs:string">
<xs:enumeration value="1.0"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="BaseExtensionType">
<xs:annotation>
<xs:documentation>
Place holder type for future extensions of
BaseExtensionType
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:any namespace="targetnamespace" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:complexType>
<xs:complexType name="EmExtensionType">
<xs:annotation>
<xs:documentation>
Place holder type for future extensions of EmBaseType
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:any namespace="targetnamespace" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:complexType>
<xs:complexType name="DetailExtensionType">
<xs:annotation>
<xs:documentation>
Place holder type for vocabulary based Event payload "details"
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:any namespace="##other" processContents="lax" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:complexType>
<xs:complexType name="CustomExtensionType">
<xs:annotation>
<xs:documentation>
Place holder type for custom Event payload "extensions"
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:any namespace="##other" processContents="lax" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:complexType>
<xs:complexType name="ALFEventType">
<xs:sequence>
<xs:element name="Base" type="EventBaseType"/>
<xs:element name="Detail" type="DetailExtensionType" minOccurs="0"/>
<xs:element name="Extension" type="CustomExtensionType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="version" type="ALFSchemaVersionType" default="1.0"/>
</xs:complexType>
<xs:complexType name="ALFEventResponseType">
<xs:sequence>
<xs:any minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="ALFEventWithReplyResponseType">
<xs:sequence>
<xs:any minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:element name="EventNotice" type="ALFEventType"/>
</xs:schema>
</wsdl:types>
<wsdl:message name="EventNotice">
<wsdl:part name="EventNotice" type="evt:ALFEventType" />
</wsdl:message>
<wsdl:message name="EventNoticeResponse">
<wsdl:part name="EventNoticeResponse" type="evt:ALFEventResponseType" />
</wsdl:message>
<wsdl:message name="EventNoticeWithReply">
<wsdl:part name="EventNoticeWithReply" type="evt:ALFEventType" />
</wsdl:message>
<wsdl:message name="EventNoticeWithReplyResponse">
<wsdl:part name="EventNoticeWithReplyResponse" type="evt:ALFEventWithReplyResponseType" />
</wsdl:message>
<wsdl:portType name="ALFEventManager">
<wsdl:operation name="EventNotice">
<wsdl:input message="evt:EventNotice" />
<wsdl:output message="evt:EventNoticeResponse" />
</wsdl:operation>
<wsdl:operation name="EventNoticeWithReply">
<wsdl:input message="evt:EventNoticeWithReply" />
<wsdl:output message="evt:EventNoticeWithReplyResponse" />
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="ALFServiceFlow">
<wsdl:operation name="TEMPEventNotice">
<wsdl:input message="evt:EventNotice" />
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="ALFServiceFlowWithReply">
<wsdl:operation name="EventNotice">
<wsdl:input message="evt:EventNotice" />
<wsdl:output message="evt:EventNoticeWithReplyResponse" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="ALFEventManagerSOAP" type="evt:ALFEventManager">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc" />
<wsdl:operation name="EventNotice">
<soap:operation soapAction="" />
<wsdl:input>
<soap:body use="literal" namespace="http://www.eclipse.org/alf/schema/EventBase/1" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="http://www.eclipse.org/alf/schema/EventBase/1" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="EventNoticeWithReply">
<soap:operation soapAction="" />
<wsdl:input>
<soap:body use="literal" namespace="http://www.eclipse.org/alf/schema/EventBase/1" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="http://www.eclipse.org/alf/schema/EventBase/1" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="ALFServiceFlowSOAP" type="evt:ALFServiceFlow">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc" />
<wsdl:operation name="TEMPEventNotice">
<soap:operation soapAction="" />
<wsdl:input>
<soap:body use="literal" namespace="http://www.eclipse.org/alf/schema/EventBase/1" />
</wsdl:input>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="ALFServiceFlowWithReplySOAP" type="evt:ALFServiceFlowWithReply">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc" />
<wsdl:operation name="EventNotice">
<soap:operation soapAction="" />
<wsdl:input>
<soap:body use="literal" namespace="http://www.eclipse.org/alf/schema/EventBase/1" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="http://www.eclipse.org/alf/schema/EventBase/1" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="ALFEventManager">
<wsdl:port name="ALFEventManagerSOAP" binding="evt:ALFEventManagerSOAP">
<soap:address location="http://localhost:8080/ALFEventManager/services/ALFEventManagerSOAP" />
</wsdl:port>
</wsdl:service>
<wsdl:service name="ALFServiceFlow">
<wsdl:port name="ALFServiceFlowSOAP" binding="evt:ALFServiceFlowSOAP">
<soap:address location="http://localhost:8080/ALFServiceFlow/services/ALFServiceFlowSOAP" />
</wsdl:port>
</wsdl:service>
<wsdl:service name="ALFServiceFlowWithReply">
<wsdl:port name="ALFServiceFlowWithReplySOAP" binding="evt:ALFServiceFlowWithReplySOAP">
<soap:address location="http://localhost:8080/ALFServiceFlow/services/ALFServiceFlowWithReplySOAP" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
---------------------------------------------------------------------------------
I end up in NullPointerException in WSDL11Reader.processOperationInput method call when I call ant deploy.
Please help me to figure out what is wrong with these files? I could deploy the atm sample successfully. Only difference I see is the complex datastructure of 'EventNotice'. I can deploy this BPEL to Oracle BPEL Process Manager and ActiveBPEL engine both. I am responsible for investigating if JBPM works for us. At this point I am not able to get this simple BPEL going on JBPM so I need help from this community. We are very much inclined to rather use open source product.
Thank you,
Meghana
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020748#4020748
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020748
19Â years, 2Â months