<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<style type="text/css">
<!--
/*
The original subSilver Theme for phpBB version 2+
Created by subBlue design
http://www.subBlue.com
NOTE: These CSS definitions are stored within the main page body so that you can use the phpBB2
theme administration centre. When you have finalised your style you could cut the final CSS code
and place it in an external file, deleting this section to save bandwidth.
*/
/* General page style. The scroll bar colours only visible in IE5.5+ */
body {
background-color: #E5E5E5;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 11;
color: #000000;
}
/* General font families for common tags */
font,th,td,p { font-family: Verdana, Arial, Helvetica, sans-serif }
p, td { font-size : 11; color : #000000; }
a:link,a:active,a:visited { color : #006699; }
a:hover { text-decoration: underline; color : #DD6900; }
hr { height: 0px; border: solid #D1D7DC 0px; border-top-width: 1px;}
h1,h2 { font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif; font-size : 22px; font-weight : bold; text-decoration : none; line-height : 120%; color : #000000;}
/* This is the border line & background colour round the entire page */
.bodyline { background-color: #FFFFFF; border: 1px #98AAB1 solid; }
/* General text */
.gen { font-size : 12px; }
.genmed { font-size : 11px; }
.gensmall { font-size : 10px; line-height: 12px}
.gen,.genmed,.gensmall { color : #000000; }
a.gen,a.genmed,a.gensmall { color: #006699; text-decoration: none; }
a.gen:hover,a.genmed:hover,a.gensmall:hover { color: #DD6900; text-decoration: underline; }
/* Forum title: Text and link to the forums used in: index.php */
.forumlink { font-weight: bold; font-size: 12px; color : #006699; }
a.forumlink { text-decoration: none; color : #006699; }
a.forumlink:hover{ text-decoration: underline; color : #DD6900; }
/* The content of the posts (body of text) */
.postbody { font-size : 12px; line-height: 18px}
a.postlink:link { text-decoration: none; color : #006699 }
a.postlink:visited { text-decoration: none; color : #5493B4; }
a.postlink:hover { text-decoration: underline; color : #DD6900}
/* Quote & Code blocks */
.code {
font-family: Courier, 'Courier New', sans-serif; font-size: 11px; color: #006600;
background-color: #FAFAFA; border: #D1D7DC; border-style: solid;
border-left-width: 1px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px
}
.quote {
font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 11px; color: #444444; line-height: 125%;
background-color: #FAFAFA; border: #D1D7DC; border-style: solid;
border-left-width: 1px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px
}
-->
</style>
</head>
<body>
<div class="postbody">The management of JBI descriptors in PETALS is processed at 3 layers, Waou! <img src="http://petals.ebmwebsourcing.com/forum/images/smiles/icon_eek.gif" alt="Shocked" border="0" /><br />
<br />
The fist layer is at the container level, the container needs information contained in the 'original' JBI schema.<br />
This original JBI schema can be found in the jar 'petals-jbi.descriptor.jar' in the 'lib' repository of your PEtALS container.<br />
This schema define ANY sections, to allow dedicated configuration for implementor of JBI.<br />
<br />
We have redefine in PEtALS project these ANY sections in two others layer: the CDK layer and the component specific layer.<br />
<br />
The CDK is the common library proposed by PEtALS to create JBI components. It contains generic stuffs common to most of the JBI components.<br />
These generic stuffs need configuration, this configuration is defined by a dedicated schema, and 'merged' in the original JBI schema by redefining it.<br />
Check the schemas contained in the jar 'petals-cdk-jbidescriptor' of one of your PEtALS component.The schema 'CDKextensions.xsd' define all the elements needed by the CDK in a CDK related namespace. the schema 'CDKjbi.xsd' redefine the namespace of JBI, 'http://java.sun.com/xml/ns/jbi', to include the CDK structured elements.<br />
With these redefined schema, we can extract the configuration toward Java binding classes, using JAXB technology<br />
<br />
Finally, the same mechanism has been attempt at the component level. Check the component's jar, eg, the petals-soap component, There is 2 schemas; 'SOAPextensions.xsd', where the elements for the SOAP component are defined and 'SOAPjbi.xsd' which redefines the JBI namespace another time to include the component structures elements.<br />
Unfortunally, we haven't be able to exploit these 3rd layer in the components code via JAXB, as we were facing a bug on Xerces about redefine in schemas.<br />
For the moment, the component's doesn't use the JAXB binding java classes to handle their configuration but a list of extensions elements, which is a map, called 'ConfigurationExtensions'.<br />
<br />
Another subject is the versionning of component's AND CDK, and compatiblity of configurations when upgrading a component in production, this is another story... There is a thread about that discussion on the forum, if you want more detail about that. <img src="http://petals.ebmwebsourcing.com/forum/images/smiles/icon_wink.gif" alt="Wink" border="0" /> <br />
<br />
/Roland</div>
<br /><div class="gensmall"><br />
<br />
<br />
-------------------- m2f --------------------<br />
<br />
Read this forum topic online here:<br />
<a href="http://petals.ebmwebsourcing.com/forum/viewtopic.php?p=455#455" target="_blank">http://petals.ebmwebsourcing.com/forum/viewtopic.php?p=455#455</a><br />
<br />
-------------------- m2f --------------------</div>
</body>
</html>