Menu

Can't get Mule ebMS stubs to work

Hans Rots
2013-12-10
2013-12-10
  • Hans Rots

    Hans Rots - 2013-12-10

    I don’t get the ebMS stubs to work. I hope that, based on the following information, someone can help me to get the ebMS stubs to work!

    Using Mule ESB version 3.4.0 build c8afb471, JAVA_HOME JDK 1.7.0_25, I configured two Mule homes on the same Windows 2003 Service Pack 2 (5.2, x86) server:
    - D:\Data\Mule_3.4.0_Digipoort
    - D:\Data\Mule_3.4.0_Overheid

    file D:\Data\Mule_3.4.0_Digipoort\conf\ebf.digipoort.properties:
    service.host=localhost
    service.port=8888
    dir.base=${mule.home}/ebms-stub
    dir.upload.cpa=${mule.home}/ebms-stub/cpa/
    jmx.host=localhost
    jmx.port=1083

    file D:\Data\Mule_3.4.0_Digipoort\apps\ebms-adapter-mule3-1.5.2\mule-config.xml, between the beans tags:
    <import resource="classpath:nl/clockwork/mule/ebms/stub/ebf/main.digipoort.xml" />

    file D:\Mule_3.4.0_Overheid\conf\ebf.overheid.properties:
    service.host=localhost
    service.port=8088
    dir.base=${mule.home}/ebms-stub
    dir.upload.cpa=${mule.home}/ebms-stub/cpa/
    jmx.host=localhost
    jmx.port=1084

    file D:\Data\Mule_3.4.0_Overheid\apps\ebms-adapter-mule3-1.5.2\mule-config.xml, between the beans tags:
    <import resource="classpath:nl/clockwork/mule/ebms/stub/ebf/main.overheid.xml" />

    Both Mule environments are running as a Windows service.

    Loading the CPA’s in the digipoort EbMS stub seems to work, although I get some warnings:
    2013-12-10 06:52:23,858 [[ebms-adapter-mule3-1.5.2].connector.file.ebms.receiver.01] INFO org.mule.transport.file.FileMessageReceiver - Lock obtained on file: D:\Data\Mule_3.4.0_Digipoort\ebms-stub\cpa\cpaStubEBF.be.http.unsigned.xml
    2013-12-10 06:52:25,295 [Finalizer] WARN org.mule.transport.file.ReceiverFileInputStream - Failed to move file from D:\Data\Mule_3.4.0_Digipoort\ebms-stub\cpa\cpaStubEBF.be.http.unsigned.xml to D:\Data\Mule_3.4.0_Digipoort\ebms-stub\cpa\processed\cpaStubEBF.be.http.unsigned.xml
    2013-12-10 06:52:25,295 [Finalizer] WARN org.mule.transport.file.FileMessageReceiver - Failure trying to remove file D:\Data\Mule_3.4.0_Digipoort\ebms-stub\cpa\cpaStubEBF.be.http.unsigned.xml from list of files under processing
    2013-12-10 06:52:25,561 [[ebms-adapter-mule3-1.5.2].connector.VM.mule.default.dispatcher.01] INFO org.mule.lifecycle.AbstractLifecycleManager - Initialising: 'connector.VM.mule.default.dispatcher.8920644'. Object is: VMMessageDispatcher
    2013-12-10 06:52:25,561 [[ebms-adapter-mule3-1.5.2].connector.VM.mule.default.dispatcher.01] INFO org.mule.lifecycle.AbstractLifecycleManager - Starting: 'connector.VM.mule.default.dispatcher.8920644'. Object is: VMMessageDispatcher
    2013-12-10 06:52:25,592 [[ebms-adapter-mule3-1.5.2].connector.file.ebms.dispatcher.01] INFO org.mule.lifecycle.AbstractLifecycleManager - Initialising: 'connector.file.ebms.dispatcher.28482356'. Object is: FileMessageDispatcher
    2013-12-10 06:52:25,592 [[ebms-adapter-mule3-1.5.2].connector.file.ebms.dispatcher.01] INFO org.mule.lifecycle.AbstractLifecycleManager - Starting: 'connector.file.ebms.dispatcher.28482356'. Object is: FileMessageDispatcher
    2013-12-10 06:52:25,592 [[ebms-adapter-mule3-1.5.2].connector.file.ebms.dispatcher.01] INFO org.mule.transport.file.FileConnector - Writing file to: D:\Data\Mule_3.4.0_Digipoort\ebms-stub\cpa\reports\report_201312100652592.txt

    Sending afleverbericht message from digipoort EbMS stub to overheid EbMS stub is going wrong:
    2013-12-10 06:54:43,155 [[ebms-adapter-mule3-1.5.2].connector.file.receiver.01] INFO org.mule.transport.file.FileMessageReceiver - Lock obtained on file: D:\Data\Mule_3.4.0_Digipoort\ebms-stub\afleverService\request\Afleverbericht_Afleveren_ebMS_2.0_v1.1.xml
    2013-12-10 06:54:43,639 [[ebms-adapter-mule3-1.5.2].connector.file.receiver.01] INFO org.mule.lifecycle.AbstractLifecycleManager - Initialising: 'connector.VM.mule.default.dispatcher.8822731'. Object is: VMMessageDispatcher
    2013-12-10 06:54:43,639 [[ebms-adapter-mule3-1.5.2].connector.file.receiver.01] INFO org.mule.lifecycle.AbstractLifecycleManager - Starting: 'connector.VM.mule.default.dispatcher.8822731'. Object is: VMMessageDispatcher
    2013-12-10 06:54:45,249 [[ebms-adapter-mule3-1.5.2].connector.VM.mule.default.receiver.07] ERROR org.mule.exception.DefaultMessagingExceptionStrategy -


    Message : Component that caused exception is: DefaultJavaComponent{content.receive.component.12364751}. Message payload is of type: EbMSMessageContent
    Type : org.mule.component.ComponentException
    Code : MULE_ERROR--2
    Payload : nl.clockwork.ebms.model.EbMSMessageContent@151a934
    JavaDoc : http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/component/ComponentException.html


    Exception stack is:
    1. null (java.lang.NullPointerException)
    nl.clockwork.ebms.service.EbMSMessageServiceImpl$1:96 (null)
    2. java.lang.NullPointerException (nl.clockwork.ebms.service.EbMSMessageServiceException)
    nl.clockwork.ebms.service.EbMSMessageServiceImpl:105 (null)
    3. Component that caused exception is: DefaultJavaComponent{content.receive.component.12364751}. Message payload is of type: EbMSMessageContent (org.mule.component.ComponentException)
    org.mule.component.DefaultComponentLifecycleAdapter:352 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/component/ComponentException.html)


    Root Exception stack trace:
    java.lang.NullPointerException
    at nl.clockwork.ebms.service.EbMSMessageServiceImpl$1.doInTransaction(EbMSMessageServiceImpl.java:96)
    at nl.clockwork.ebms.dao.spring.AbstractEbMSDAO$3.doInTransactionWithoutResult(AbstractEbMSDAO.java:464)
    at org.springframework.transaction.support.TransactionCallbackWithoutResult.doInTransaction(TransactionCallbackWithoutResult.java:33)
    at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:131)
    at nl.clockwork.ebms.dao.spring.AbstractEbMSDAO.executeTransaction(AbstractEbMSDAO.java:457)
    at nl.clockwork.ebms.service.EbMSMessageServiceImpl.sendMessage(EbMSMessageServiceImpl.java:88)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.mule.model.resolvers.AbstractEntryPointResolver.invokeMethod(AbstractEntryPointResolver.java:151)
    at org.mule.model.resolvers.ReflectionEntryPointResolver.invoke(ReflectionEntryPointResolver.java:172)
    at org.mule.model.resolvers.DefaultEntryPointResolverSet.invoke(DefaultEntryPointResolverSet.java:39)
    at org.mule.component.DefaultComponentLifecycleAdapter.invoke(DefaultComponentLifecycleAdapter.java:343)
    at org.mule.component.AbstractJavaComponent.invokeComponentInstance(AbstractJavaComponent.java:86)
    at org.mule.component.AbstractJavaComponent.doInvoke(AbstractJavaComponent.java:77)
    at org.mule.component.AbstractComponent.invokeInternal(AbstractComponent.java:126)
    at org.mule.component.AbstractComponent.access$000(AbstractComponent.java:61)
    at org.mule.component.AbstractComponent$1$1.process(AbstractComponent.java:242)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:61)
    at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:47)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:61)
    at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:47)
    at org.mule.component.AbstractComponent.process(AbstractComponent.java:160)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:61)
    at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:47)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:47)
    at org.mule.interceptor.AbstractEnvelopeInterceptor.process(AbstractEnvelopeInterceptor.java:55)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:61)
    at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:47)
    at org.mule.processor.AbstractFilteringMessageProcessor.process(AbstractFilteringMessageProcessor.java:44)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:61)
    at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:47)
    at org.mule.construct.AbstractPipeline$1.process(AbstractPipeline.java:112)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:61)
    at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:47)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(Mes...


    2013-12-10 07:52:25,592 [Finalizer] WARN org.mule.transport.file.ReceiverFileInputStream - Failed to move file from D:\Data\Mule_3.4.0_Digipoort\ebms-stub\afleverService\request\Afleverbericht_Afleveren_ebMS_2.0_v1.1.xml to D:\Data\Mule_3.4.0_Digipoort\ebms-stub\afleverService\request\processed\Afleverbericht_Afleveren_ebMS_2.0_v1.1.xml

    2013-12-10 07:52:25,592 [Finalizer] WARN org.mule.transport.file.FileMessageReceiver - Failure trying to remove file D:\Data\Mule_3.4.0_Digipoort\ebms-stub\afleverService\request\Afleverbericht_Afleveren_ebMS_2.0_v1.1.xml from list of files under processing

    Loading the CPA’s in the overheid EbMS stub seems to work, although I get some warnings:
    2013-12-10 06:52:42,155 [[ebms-adapter-mule3-1.5.2].connector.file.ebms.receiver.01] INFO org.mule.transport.file.FileMessageReceiver - Lock obtained on file: D:\Data\Mule_3.4.0_Overheid\ebms-stub\cpa\cpaStubEBF.be.http.unsigned.xml
    2013-12-10 06:52:43,467 [Finalizer] WARN org.mule.transport.file.ReceiverFileInputStream - Failed to move file from D:\Data\Mule_3.4.0_Overheid\ebms-stub\cpa\cpaStubEBF.be.http.unsigned.xml to D:\Data\Mule_3.4.0_Overheid\ebms-stub\cpa\processed\cpaStubEBF.be.http.unsigned.xml

    2013-12-10 06:52:43,483 [Finalizer] WARN org.mule.transport.file.FileMessageReceiver - Failure trying to remove file D:\Data\Mule_3.4.0_Overheid\ebms-stub\cpa\cpaStubEBF.be.http.unsigned.xml from list of files under processing
    2013-12-10 06:52:43,686 [[ebms-adapter-mule3-1.5.2].connector.VM.mule.default.dispatcher.01] INFO org.mule.lifecycle.AbstractLifecycleManager - Initialising: 'connector.VM.mule.default.dispatcher.24756556'. Object is: VMMessageDispatcher
    2013-12-10 06:52:43,686 [[ebms-adapter-mule3-1.5.2].connector.VM.mule.default.dispatcher.01] INFO org.mule.lifecycle.AbstractLifecycleManager - Starting: 'connector.VM.mule.default.dispatcher.24756556'. Object is: VMMessageDispatcher
    2013-12-10 06:52:43,717 [[ebms-adapter-mule3-1.5.2].connector.file.ebms.dispatcher.01] INFO org.mule.lifecycle.AbstractLifecycleManager - Initialising: 'connector.file.ebms.dispatcher.17375533'. Object is: FileMessageDispatcher
    2013-12-10 06:52:43,717 [[ebms-adapter-mule3-1.5.2].connector.file.ebms.dispatcher.01] INFO org.mule.lifecycle.AbstractLifecycleManager - Starting: 'connector.file.ebms.dispatcher.17375533'. Object is: FileMessageDispatcher
    2013-12-10 06:52:43,733 [[ebms-adapter-mule3-1.5.2].connector.file.ebms.dispatcher.01] INFO org.mule.transport.file.FileConnector - Writing file to: D:\Data\Mule_3.4.0_Overheid\ebms-stub\cpa\reports\report_201312100652733.txt

    Sending aanleverbericht message from overheid EbMS stub to digipoort EbMS stub is going wrong:
    2013-12-10 06:53:29,342 [[ebms-adapter-mule3-1.5.2].connector.file.receiver.01] INFO org.mule.transport.file.FileMessageReceiver - Lock obtained on file: D:\Data\Mule_3.4.0_Overheid\ebms-stub\aanleverService\request\Aanleverbericht_Aanleveren_ebMS_2.0_v1.1.xml
    2013-12-10 06:53:29,358 [[ebms-adapter-mule3-1.5.2].connector.file.receiver.01] INFO org.mule.lifecycle.AbstractLifecycleManager - Initialising: 'connector.VM.mule.default.dispatcher.22608529'. Object is: VMMessageDispatcher
    2013-12-10 06:53:29,358 [[ebms-adapter-mule3-1.5.2].connector.file.receiver.01] INFO org.mule.lifecycle.AbstractLifecycleManager - Starting: 'connector.VM.mule.default.dispatcher.22608529'. Object is: VMMessageDispatcher
    2013-12-10 06:53:29,608 [Finalizer] WARN org.mule.transport.file.ReceiverFileInputStream - Failed to move file from D:\Data\Mule_3.4.0_Overheid\ebms-stub\aanleverService\request\Aanleverbericht_Aanleveren_ebMS_2.0_v1.1.xml to D:\Data\Mule_3.4.0_Overheid\ebms-stub\aanleverService\request\processed\Aanleverbericht_Aanleveren_ebMS_2.0_v1.1.xml

    2013-12-10 06:53:29,608 [Finalizer] WARN org.mule.transport.file.FileMessageReceiver - Failure trying to remove file D:\Data\Mule_3.4.0_Overheid\ebms-stub\aanleverService\request\Aanleverbericht_Aanleveren_ebMS_2.0_v1.1.xml from list of files under processing
    2013-12-10 06:53:30,686 [[ebms-adapter-mule3-1.5.2].connector.VM.mule.default.receiver.06] ERROR org.mule.exception.DefaultMessagingExceptionStrategy -


    Message : Component that caused exception is: DefaultJavaComponent{content.receive.component.4925180}. Message payload is of type: EbMSMessageContent
    Type : org.mule.component.ComponentException
    Code : MULE_ERROR--2
    Payload : nl.clockwork.ebms.model.EbMSMessageContent@189095b
    JavaDoc : http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/component/ComponentException.html


    Exception stack is:
    1. null (java.lang.NullPointerException)
    nl.clockwork.ebms.service.EbMSMessageServiceImpl$1:96 (null)
    2. java.lang.NullPointerException (nl.clockwork.ebms.service.EbMSMessageServiceException)
    nl.clockwork.ebms.service.EbMSMessageServiceImpl:105 (null)
    3. Component that caused exception is: DefaultJavaComponent{content.receive.component.4925180}. Message payload is of type: EbMSMessageContent (org.mule.component.ComponentException)
    org.mule.component.DefaultComponentLifecycleAdapter:352 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/component/ComponentException.html)


    Root Exception stack trace:
    java.lang.NullPointerException
    at nl.clockwork.ebms.service.EbMSMessageServiceImpl$1.doInTransaction(EbMSMessageServiceImpl.java:96)
    at nl.clockwork.ebms.dao.spring.AbstractEbMSDAO$3.doInTransactionWithoutResult(AbstractEbMSDAO.java:464)
    at org.springframework.transaction.support.TransactionCallbackWithoutResult.doInTransaction(TransactionCallbackWithoutResult.java:33)
    at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:131)
    at nl.clockwork.ebms.dao.spring.AbstractEbMSDAO.executeTransaction(AbstractEbMSDAO.java:457)
    at nl.clockwork.ebms.service.EbMSMessageServiceImpl.sendMessage(EbMSMessageServiceImpl.java:88)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.mule.model.resolvers.AbstractEntryPointResolver.invokeMethod(AbstractEntryPointResolver.java:151)
    at org.mule.model.resolvers.ReflectionEntryPointResolver.invoke(ReflectionEntryPointResolver.java:172)
    at org.mule.model.resolvers.DefaultEntryPointResolverSet.invoke(DefaultEntryPointResolverSet.java:39)
    at org.mule.component.DefaultComponentLifecycleAdapter.invoke(DefaultComponentLifecycleAdapter.java:343)
    at org.mule.component.AbstractJavaComponent.invokeComponentInstance(AbstractJavaComponent.java:86)
    at org.mule.component.AbstractJavaComponent.doInvoke(AbstractJavaComponent.java:77)
    at org.mule.component.AbstractComponent.invokeInternal(AbstractComponent.java:126)
    at org.mule.component.AbstractComponent.access$000(AbstractComponent.java:61)
    at org.mule.component.AbstractComponent$1$1.process(AbstractComponent.java:242)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:61)
    at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:47)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:61)
    at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:47)
    at org.mule.component.AbstractComponent.process(AbstractComponent.java:160)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:61)
    at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:47)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:47)
    at org.mule.interceptor.AbstractEnvelopeInterceptor.process(AbstractEnvelopeInterceptor.java:55)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:61)
    at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:47)
    at org.mule.processor.AbstractFilteringMessageProcessor.process(AbstractFilteringMessageProcessor.java:44)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:61)
    at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:47)
    at org.mule.construct.AbstractPipeline$1.process(AbstractPipeline.java:112)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:61)
    at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:47)
    at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
    at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(Mes...


     
  • Edwin Luinstra

    Edwin Luinstra - 2013-12-10

    hello Hans,

    good to see you found an easy way to run the stubs. So you replaced the line:
    <import resource="classpath:nl/clockwork/mule/ebms/main.xml" />
    in the file mule-config.xml with:
    <import resource="classpath:nl/clockwork/mule/ebms/stub/ebf/main.digipoort.xml" />
    and:
    <import resource="classpath:nl/clockwork/mule/ebms/stub/ebf/main.overheid.xml" />
    respectively.

    I noticed that you configured dir.base and dir.upload.cpa of the 2 stubs to the same directory. They should be configured to different directories. dir.base is used for the database directory and message directories. dir.upload.cpa is used to upload cpas. Each stub should use its own database, otherwise the stubs/adapters have unexpected behaviour. Also if you point both stubs to the same directory only one of them will load the cpa or send a message. So could you changes this and try it again?

    You could also take a look at the new EbMS Admin Console, with which you can manage an EbMS adapter. You can find this project also at SourceForge. You can start it in two ways:
    - as console only, to use with for example a standalone Mule EbMS adapter
    or
    - as console with embedded EbMS adapter

    The last way is preferable for your situation.

    The admin console starts as a java application and starts an embedded jetty server to host the application. If you use hsqldb, it can also start a database server.
    The console offers:
    - upload and view CPAs
    - send ping
    - send message
    - view send and received messages/traffic
    - configure ebms admin console and ebms adapter
    - and more

    Tomorrow I will release version 1.5.2 of the admin console

    By the way, it's better to use version 2.x of the adapter/console, if you don't use version 1.x in production already.

    If you have any questions, let me know.

    kind regards,
    Edwin

     

    Last edit: Edwin Luinstra 2013-12-10

Log in to post a comment.