Petals BC SOAP

Log that JMS is activated whereas the SU configuration specifies not.

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 4.0.3
  • Fix Version/s: 4.0.3
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    In deploy a SU configured like that:

    <jbi:consumes interface-name="generatedNs:AddAndMultiplyProcessPortType"
    service-name="generatedNs:AddAndMultiplyProcessService"
    endpoint-name="AddAndMultiplyProcessEndpoint">

    <!-- CDK specific elements -->
    <petalsCDK:timeout>30000</petalsCDK:timeout>
    <petalsCDK:operation xmlns:op="http://petals.ow2.org/bpel/AddAndMultiplyProcess/">op:process</petalsCDK:operation>
    <petalsCDK:mep>InOut</petalsCDK:mep>

    <!-- Component specific elements -->
    <soap:address>bpelProcess</soap:address>
    <soap:remove-root>false</soap:remove-root>
    <soap:mode>SOAP</soap:mode>
    <soap:rest-add-namespace-prefix>soapbc</soap:rest-add-namespace-prefix>
    <soap:enable-http-transport>true</soap:enable-http-transport>
    <soap:enable-jms-transport>false</soap:enable-jms-transport>
    </jbi:consumes>

    and the log says:

    [Petals.Container.Components.petals-bc-soap]-INFO 2010-08-19 10:00:02,164 The Axis2 service 'bpelProcess' has been registered and is available through JMS.

    The log is wrong, or the parameter 'enable-jms-transport' do not work.

    Show
    In deploy a SU configured like that: <jbi:consumes interface-name="generatedNs:AddAndMultiplyProcessPortType" service-name="generatedNs:AddAndMultiplyProcessService" endpoint-name="AddAndMultiplyProcessEndpoint"> <!-- CDK specific elements --> <petalsCDK:timeout>30000</petalsCDK:timeout> <petalsCDK:operation xmlns:op="http://petals.ow2.org/bpel/AddAndMultiplyProcess/">op:process</petalsCDK:operation> <petalsCDK:mep>InOut</petalsCDK:mep> <!-- Component specific elements --> <soap:address>bpelProcess</soap:address> <soap:remove-root>false</soap:remove-root> <soap:mode>SOAP</soap:mode> <soap:rest-add-namespace-prefix>soapbc</soap:rest-add-namespace-prefix> <soap:enable-http-transport>true</soap:enable-http-transport> <soap:enable-jms-transport>false</soap:enable-jms-transport> </jbi:consumes> and the log says: [Petals.Container.Components.petals-bc-soap]-INFO 2010-08-19 10:00:02,164 The Axis2 service 'bpelProcess' has been registered and is available through JMS. The log is wrong, or the parameter 'enable-jms-transport' do not work.
  • Environment:
    OS:all

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
noddoux added a comment - Thu, 19 Aug 2010 - 12:16:43 +0200

The parameter does not work. It is fixed only on the trunk.

Show
noddoux added a comment - Thu, 19 Aug 2010 - 12:16:43 +0200 The parameter does not work. It is fixed only on the trunk.

People

Dates

  • Created:
    Thu, 19 Aug 2010 - 10:28:38 +0200
    Updated:
    Wed, 15 Sep 2010 - 10:03:50 +0200
    Resolved:
    Thu, 19 Aug 2010 - 12:16:43 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.