[Users] How to provide JMS as a Service Assembly

[flaborde]

hi, 

Maybe, i have an idea... 
depending on cdk version having trouble on jbi description, i just remove the fully qualified name of each xml elements aiming to conserve target namespace and tns in jbi uri

Example : you just wrote : 


Code:
<?xml version="1.0" encoding="UTF-8"?>
<!--
   JBI descriptor for the Petals' "petals-bc-jms" component (JMS).
   Originally created for the version 3.0 of the component.
 -->
<jbi:jbi version="1.0"
   xmlns:interfaceNs="intNs"
   xmlns:jbi="http://java.sun.com/xml/ns/jbi"
   xmlns:jms="http://petals.ow2.org/components/jms/version-3.0"
   xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-4.0"
   xmlns:serviceNs="servNs"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   
   <!-- Import a Service into Petals or Expose a Petals Service => use a BC. -->
   <jbi:services binding-component="true">
   
      <!-- Import a Service into Petals => provides a Service. -->
      <jbi:provides       
         interface-name="interfaceNs:intN"
         service-name="serviceNs:serv"
         endpoint-name="autogenerate">
   
         <!-- CDK specific elements -->
         <petalsCDK:timeout>90</petalsCDK:timeout>
         <petalsCDK:wsdl xsi:nil="true" />
      
         <!-- Component specific elements -->   
         <jms:jndi-provider-url>scn://localhost:16400</jms:jndi-provider-url>
         <jms:jndi-initial-context-factory>fr.dyade.aaa.jndi2.client.NamingContextFactory</jms:jndi-initial-context-factory>
         <jms:jndi-destination-name>queue</jms:jndi-destination-name>
         <jms:jndi-connection-factory>qcf</jms:jndi-connection-factory>
         <jms:transacted>false</jms:transacted>
         <jms:max-active>10</jms:max-active>
         <jms:max-idle>5</jms:max-idle>
         <jms:max-wait>10000</jms:max-wait>
         <jms:test-while-idle>true</jms:test-while-idle>         
      </jbi:provides>
   </jbi:services>
</jbi:jbi> 



me, i would prefer without fully qualified namespace :


Code:
<jbi xmlns="http://java.sun.com/xml/ns/jbi"
    version="1.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5"
    xmlns:cdar1xslt="http://acrs.cegedim.fr/jbi/serviceunit/cdar1xslt/version-1"
    xmlns:xslt="http://petals.ow2.org/components/xslt/version-2"
    >
	<services binding-component="false">

		<provides interface-name="cdar1xslt:interface"
			service-name="cdar1xslt:service"
			endpoint-name="cdar1xsltEndpoint">

                        <petalsCDK:wsdl xsi:nil="true"/>
                        <!-- WSDL file 
                        <petalsCDK:wsdl>cdar1xsltInterface.wsdl</petalsCDK:wsdl>-->
                        <xslt:stylesheet>cdar1_enveloppeMessage.xsl</xslt:stylesheet>
		</provides>
	</services>
</jbi>



and using xmlns="http://java.sun.com/xml/ns/jbi"
by the way, i'm not using petals studio [Rolling Eyes]  : this workaround was successfull with my own generated jbi.xml models...




-------------------- m2f --------------------

Subscribe/Unsubscribe emails notifications.

Response to this email will be posted on the Petals forum.
Please delete the existing text before responding :)

Read the topic online:
http://petals.ebmwebsourcing.com/forum/viewtopic.php?p=30495#30495

-------------------- m2f --------------------


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://forum-list.petalslink.org/pipermail/users/attachments/20110316/ba1e1c33/attachment.htm>