You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Karan Malhi <ka...@gmail.com> on 2008/06/15 03:08:56 UTC
websphere descriptors
Where would i start from to add support for Websphere descriptors?
--
Karan Singh Malhi
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
FYI, I will make sure that the referenced XMI files are not located
inside a jar as double check that we are looking inside the right
files.
On Mon, Jun 23, 2008 at 5:55 PM, Mohammad Nour El-Din
<no...@gmail.com> wrote:
> Karan as a littlw hint, replace the xmi extension of the referenced
> XMIs to the XSD extension and this will be the name of the file you
> should look for ;).
>
> On Mon, Jun 23, 2008 at 5:21 PM, Mohammad Nour El-Din
> <no...@gmail.com> wrote:
>> Well I am not sure if it is legal to send even the names of the files
>> over here, can someone help me and asnwer that question, is it legal
>> to send even the names on that list ?
>>
>> On Mon, Jun 23, 2008 at 4:48 PM, Karan Malhi <ka...@gmail.com> wrote:
>>> I have a local WAS 6.1 . I do see the <<WAS_INSTALL>>/properties/schemas,
>>> but do not see the schemas for the xmi files bundled inside an ejb-jar. I
>>> would definitely be interested in the schemas, so if you can send those to
>>> me , that would be great
>>>
>>> On Mon, Jun 23, 2008 at 9:01 AM, Daniel S. Haischt <
>>> daniel.haischt@googlemail.com> wrote:
>>>
>>>> just a suggestion - anyone that is interested in the XSD files should
>>>> reply to this thread.
>>>> Mohammad or I will then provide you with the XSDs for WAS V6.1 by
>>>> sending you a private
>>>> mail having the XSDs attached.
>>>>
>>>> That way you don't need to download and install WAS locally.
>>>>
>>>> On Mon, Jun 23, 2008 at 12:04 AM, Karan Malhi <ka...@gmail.com>
>>>> wrote:
>>>> > Sorry,
>>>> >
>>>> > Obviously didn't realize that . Thanks for catching that :)
>>>> >
>>>> > On Sun, Jun 22, 2008 at 5:05 PM, David Blevins <da...@visi.com>
>>>> > wrote:
>>>> >
>>>> >>
>>>> >> On Jun 22, 2008, at 12:46 PM, Karan Malhi wrote:
>>>> >>
>>>> >> Great,
>>>> >>>
>>>> >>> I have created a Jira issue so that we could share the zip files.
>>>> >>>
>>>> >>> https://issues.apache.org/jira/browse/OPENEJB-830
>>>> >>>
>>>> >>
>>>> >> Just an fyi, we can't publicly redistribute those on apache hardware.
>>>> >>
>>>> >> -David
>>>> >>
>>>> >>
>>>> >>
>>>> >>>
>>>> >>> On Sun, Jun 22, 2008 at 2:06 PM, Mohammad Nour El-Din <
>>>> >>> nour.mohammad@gmail.com> wrote:
>>>> >>>
>>>> >>> Hi All...
>>>> >>>>
>>>> >>>> Good news :), I found all the XSDs we need. They are shipped with
>>>> >>>> the WAS installation under <was_home>/properties/schemas directory,
>>>> >>>> all the XSDs we dreamed of, the one for XMI and for all the other WAS
>>>> >>>> specific DDs. I have to go home now, so I will collect them in 1 zip
>>>> >>>> file and I will send them on the list tomorrow 23-Jun-2008.
>>>> >>>>
>>>> >>>> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
>>>> >>>> <no...@gmail.com> wrote:
>>>> >>>>
>>>> >>>>> Thanks Daniel for clarifications. What I am doing now, is to get the
>>>> >>>>> XMI files referenced inside both the binding and extensions XMI
>>>> files,
>>>> >>>>> which will help us making the corresspodent XSDs. I talked with Dain
>>>> >>>>> on IRC about that. I just need sometime cause the XMI are located
>>>> >>>>> inside one of the large number pf JARs shipped with WAS. Expected to
>>>> >>>>> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
>>>> >>>>>
>>>> >>>>> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
>>>> >>>>> <da...@googlemail.com> wrote:
>>>> >>>>>
>>>> >>>>>> a couple of thoughts...
>>>> >>>>>>
>>>> >>>>>> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF,
>>>> MOF
>>>> >>>>>> and XMI. ECore is the Eclipse pendant to MOF. They are both
>>>> completely
>>>> >>>>>> independent efforts. Both could be used as a basis for a so-called
>>>> >>>>>> Domain Specific Language (DSL). A kinda one size fits all DSL is
>>>> UML.
>>>> >>>>>> MOF models can be access in Java using the JMI API. ECore models can
>>>> >>>>>> be accessed in Java using the EMF programmatic API. Both MOF and
>>>> ECore
>>>> >>>>>> models will be persisted using an instance of XMI.
>>>> >>>>>>
>>>> >>>>>> 2) As David already pointed out, as long as we don't ship
>>>> proprietary
>>>> >>>>>> XSDs and such, we should be fine cause AFAIK even XDoclet and other
>>>> >>>>>> tools are supporting proprietary WAS binding files. So why shouldn't
>>>> >>>>>> we be allowed to do the same?
>>>> >>>>>>
>>>> >>>>>> 3) Some more docs about the WAS binding files:
>>>> >>>>>>
>>>> >>>>>> ibm-webservicesclient-bnd.xmi:
>>>> >>>>>> ------------------------------
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>>>> >>>>
>>>> >>>>>
>>>> >>>>>> ibm-webservices-bnd.xmi:
>>>> >>>>>> ------------------------
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
>>>> >>>>
>>>> >>>>>
>>>> >>>>>>
>>>> >>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
>>>> >>>>
>>>> >>>>>
>>>> >>>>>>
>>>> >>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>>>> >>>>
>>>> >>>>>
>>>> >>>>>> Application bindings:
>>>> >>>>>> ---------------------
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>>>> >>>>
>>>> >>>>>
>>>> >>>>>>
>>>> >>>>>> Karan Malhi wrote:
>>>> >>>>>>
>>>> >>>>>>>
>>>> >>>>>>> oops!
>>>> >>>>>>>
>>>> >>>>>>> I pasted the files for ejb 1.1 . Not sure if something changed for
>>>> ejb
>>>> >>>>>>>
>>>> >>>>>> 2.1
>>>> >>>>
>>>> >>>>> .
>>>> >>>>>>> I think we can ignore the ibm-ejb-ext files for now because they
>>>> >>>>>>>
>>>> >>>>>> contain
>>>> >>>>
>>>> >>>>> ibm
>>>> >>>>>>> extensions. its the ibm-ejb-jar-bnd files which should be of
>>>> interest.
>>>> >>>>>>>
>>>> >>>>>> I
>>>> >>>>
>>>> >>>>> will try and create a more comprehensive file using RAD or AST. This
>>>> >>>>>>>
>>>> >>>>>> will
>>>> >>>>
>>>> >>>>> contain local, remote ejb references, references to activation spec
>>>> for
>>>> >>>>>>> mdb,
>>>> >>>>>>> datasource . We could probably use that to generate the schema.
>>>> >>>>>>>
>>>> >>>>>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <
>>>> karan.malhi@gmail.com>
>>>> >>>>>>> wrote:
>>>> >>>>>>>
>>>> >>>>>>> Or if you can grab the xmi files there's probably a way to convert
>>>> >>>>>>>>
>>>> >>>>>>> them
>>>> >>>>
>>>> >>>>> to
>>>> >>>>>>>>
>>>> >>>>>>>>>
>>>> >>>>>>>>> xsd.
>>>> >>>>>>>>>
>>>> >>>>>>>>> I think this would be the best approach. Since Attachments are
>>>> >>>>>>>> disallowed,
>>>> >>>>>>>> I am giving the file name, its purpose followed by its contents.
>>>> You
>>>> >>>>>>>> should
>>>> >>>>>>>> be able to create the file on the local system and paste the
>>>> contents
>>>> >>>>>>>>
>>>> >>>>>>> in
>>>> >>>>
>>>> >>>>> it.
>>>> >>>>>>>> Please keep in mind though that these files do not contain all
>>>> info
>>>> >>>>>>>>
>>>> >>>>>>> they
>>>> >>>>
>>>> >>>>> could contain, so generating a schema out of them may not get us a
>>>> >>>>>>>> comprehensive schema. (Actually, I was able to generate a schema
>>>> >>>>>>>> using
>>>> >>>>>>>>
>>>> >>>>>>> c#
>>>> >>>>
>>>> >>>>> )
>>>> >>>>>>>>
>>>> >>>>>>>> File Name:- ibm-ejb-jar-bnd.xmi
>>>> >>>>>>>> Contents:-
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> -----------------------------------------------------------------------------
>>>> >>>>
>>>> >>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> >>>>>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>>>> >>>>>>>> xmlns:xmi="http://www.omg.org/XMI"
>>>> >>>>>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>>>> >>>>>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="
>>>> >>>>>>>>
>>>> >>>>>>> http://www.w3.org/2001/XMLSchema-instance"
>>>> >>>>
>>>> >>>>> xmi:id="ejb-jar_ID_Bnd">
>>>> >>>>>>>> <defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
>>>> >>>>>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>>>> >>>>>>>> xmi:id="BasicAuthData_1">
>>>> >>>>>>>> <userId xsi:nil="true"/>
>>>> >>>>>>>> <password xsi:nil="true"/>
>>>> >>>>>>>> </defaultAuth>
>>>> >>>>>>>> </defaultDatasource>
>>>> >>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>> >>>>>>>> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
>>>> >>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>> >>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>> >>>>>>>> </ejbBindings>
>>>> >>>>>>>> </ejbbnd:EJBJarBinding>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> ----------------------------------------------------------------------------------
>>>> >>>>
>>>> >>>>>
>>>> >>>>>>>> File Name:-ibm-ejb-jar-ext.xmi
>>>> >>>>>>>> Contents:-
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> -----------------------------------------------------------------------------------
>>>> >>>>
>>>> >>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> >>>>>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>>>> >>>>>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi"
>>>> >>>>>>>> xmlns:ejb="ejb.xmi"
>>>> >>>>>>>> xmi:id="ejb-jar_ID_Ext">
>>>> >>>>>>>> <ejbExtensions xmi:type="ejbext:SessionExtension"
>>>> >>>>>>>>
>>>> >>>>>>> xmi:id="Session_1_Ext"
>>>> >>>>
>>>> >>>>> timeout="600">
>>>> >>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>> >>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>> >>>>>>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>>>> >>>>>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>>>> >>>>>>>> <internationalization xmi:id="BeanInternationalization_1"
>>>> >>>>>>>> invocationLocale="CALLER"/>
>>>> >>>>>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>>>> >>>>>>>> unresolvedAction="ROLLBACK"/>
>>>> >>>>>>>> </ejbExtensions>
>>>> >>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>> >>>>>>>> </ejbext:EJBJarExtension>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> ------------------------------------------------------------------------------------
>>>> >>>>
>>>> >>>>>
>>>> >>>>>>>> File Name:- ejb-jar.xml
>>>> >>>>>>>> Contents:-
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> -----------------------------------------------------------------------------------
>>>> >>>>
>>>> >>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> >>>>>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD
>>>> Enterprise
>>>> >>>>>>>> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd
>>>> ">
>>>> >>>>>>>>
>>>> >>>>>>>> <ejb-jar id="ejb-jar_ID">
>>>> >>>>>>>> <description>IVT Stateful Session EJB</description>
>>>> >>>>>>>> <display-name>IVT EJB Module</display-name>
>>>> >>>>>>>> <enterprise-beans>
>>>> >>>>>>>> <session id="Session_1">
>>>> >>>>>>>> <description>Verify Stateful Session EJB</description>
>>>> >>>>>>>> <display-name>Verification of Stateful Session
>>>> >>>>>>>> EJB</display-name>
>>>> >>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>> >>>>>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>>>> >>>>>>>>
>>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>>>> >>>>>>>>
>>>> >>>>>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>>>> >>>>>>>> <session-type>Stateful</session-type>
>>>> >>>>>>>> <transaction-type>Container</transaction-type>
>>>> >>>>>>>> </session>
>>>> >>>>>>>> </enterprise-beans>
>>>> >>>>>>>> <assembly-descriptor id="AssemblyDescriptor_1">
>>>> >>>>>>>> <container-transaction id="MethodTransaction_1">
>>>> >>>>>>>> <method id="MethodElement_1">
>>>> >>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>> >>>>>>>> <method-name>*</method-name>
>>>> >>>>>>>> </method>
>>>> >>>>>>>> <trans-attribute>Never</trans-attribute>
>>>> >>>>>>>> </container-transaction>
>>>> >>>>>>>> </assembly-descriptor>
>>>> >>>>>>>> </ejb-jar>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> -----------------------------------------------------------------------------------
>>>> >>>>
>>>> >>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>> --
>>>> >>>>>>>> Karan Singh Malhi
>>>> >>>>>>>>
>>>> >>>>>>>
>>>> >>>>>>>
>>>> >>>>>>>
>>>> >>>>>>>
>>>> >>>>>>>
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> --
>>>> >>>>> Thanks
>>>> >>>>> - Mohammad Nour
>>>> >>>>>
>>>> >>>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> --
>>>> >>>> Thanks
>>>> >>>> - Mohammad Nour
>>>> >>>>
>>>> >>>>
>>>> >>>
>>>> >>>
>>>> >>> --
>>>> >>> Karan Singh Malhi
>>>> >>>
>>>> >>
>>>> >>
>>>> >
>>>> >
>>>> > --
>>>> > Karan Singh Malhi
>>>> >
>>>>
>>>
>>>
>>>
>>> --
>>> Karan Singh Malhi
>>>
>>
>>
>>
>> --
>> Thanks
>> - Mohammad Nour
>>
>
>
>
> --
> Thanks
> - Mohammad Nour
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Karan as a littlw hint, replace the xmi extension of the referenced
XMIs to the XSD extension and this will be the name of the file you
should look for ;).
On Mon, Jun 23, 2008 at 5:21 PM, Mohammad Nour El-Din
<no...@gmail.com> wrote:
> Well I am not sure if it is legal to send even the names of the files
> over here, can someone help me and asnwer that question, is it legal
> to send even the names on that list ?
>
> On Mon, Jun 23, 2008 at 4:48 PM, Karan Malhi <ka...@gmail.com> wrote:
>> I have a local WAS 6.1 . I do see the <<WAS_INSTALL>>/properties/schemas,
>> but do not see the schemas for the xmi files bundled inside an ejb-jar. I
>> would definitely be interested in the schemas, so if you can send those to
>> me , that would be great
>>
>> On Mon, Jun 23, 2008 at 9:01 AM, Daniel S. Haischt <
>> daniel.haischt@googlemail.com> wrote:
>>
>>> just a suggestion - anyone that is interested in the XSD files should
>>> reply to this thread.
>>> Mohammad or I will then provide you with the XSDs for WAS V6.1 by
>>> sending you a private
>>> mail having the XSDs attached.
>>>
>>> That way you don't need to download and install WAS locally.
>>>
>>> On Mon, Jun 23, 2008 at 12:04 AM, Karan Malhi <ka...@gmail.com>
>>> wrote:
>>> > Sorry,
>>> >
>>> > Obviously didn't realize that . Thanks for catching that :)
>>> >
>>> > On Sun, Jun 22, 2008 at 5:05 PM, David Blevins <da...@visi.com>
>>> > wrote:
>>> >
>>> >>
>>> >> On Jun 22, 2008, at 12:46 PM, Karan Malhi wrote:
>>> >>
>>> >> Great,
>>> >>>
>>> >>> I have created a Jira issue so that we could share the zip files.
>>> >>>
>>> >>> https://issues.apache.org/jira/browse/OPENEJB-830
>>> >>>
>>> >>
>>> >> Just an fyi, we can't publicly redistribute those on apache hardware.
>>> >>
>>> >> -David
>>> >>
>>> >>
>>> >>
>>> >>>
>>> >>> On Sun, Jun 22, 2008 at 2:06 PM, Mohammad Nour El-Din <
>>> >>> nour.mohammad@gmail.com> wrote:
>>> >>>
>>> >>> Hi All...
>>> >>>>
>>> >>>> Good news :), I found all the XSDs we need. They are shipped with
>>> >>>> the WAS installation under <was_home>/properties/schemas directory,
>>> >>>> all the XSDs we dreamed of, the one for XMI and for all the other WAS
>>> >>>> specific DDs. I have to go home now, so I will collect them in 1 zip
>>> >>>> file and I will send them on the list tomorrow 23-Jun-2008.
>>> >>>>
>>> >>>> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
>>> >>>> <no...@gmail.com> wrote:
>>> >>>>
>>> >>>>> Thanks Daniel for clarifications. What I am doing now, is to get the
>>> >>>>> XMI files referenced inside both the binding and extensions XMI
>>> files,
>>> >>>>> which will help us making the corresspodent XSDs. I talked with Dain
>>> >>>>> on IRC about that. I just need sometime cause the XMI are located
>>> >>>>> inside one of the large number pf JARs shipped with WAS. Expected to
>>> >>>>> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
>>> >>>>>
>>> >>>>> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
>>> >>>>> <da...@googlemail.com> wrote:
>>> >>>>>
>>> >>>>>> a couple of thoughts...
>>> >>>>>>
>>> >>>>>> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF,
>>> MOF
>>> >>>>>> and XMI. ECore is the Eclipse pendant to MOF. They are both
>>> completely
>>> >>>>>> independent efforts. Both could be used as a basis for a so-called
>>> >>>>>> Domain Specific Language (DSL). A kinda one size fits all DSL is
>>> UML.
>>> >>>>>> MOF models can be access in Java using the JMI API. ECore models can
>>> >>>>>> be accessed in Java using the EMF programmatic API. Both MOF and
>>> ECore
>>> >>>>>> models will be persisted using an instance of XMI.
>>> >>>>>>
>>> >>>>>> 2) As David already pointed out, as long as we don't ship
>>> proprietary
>>> >>>>>> XSDs and such, we should be fine cause AFAIK even XDoclet and other
>>> >>>>>> tools are supporting proprietary WAS binding files. So why shouldn't
>>> >>>>>> we be allowed to do the same?
>>> >>>>>>
>>> >>>>>> 3) Some more docs about the WAS binding files:
>>> >>>>>>
>>> >>>>>> ibm-webservicesclient-bnd.xmi:
>>> >>>>>> ------------------------------
>>> >>>>>>
>>> >>>>>>
>>> >>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>>> >>>>
>>> >>>>>
>>> >>>>>> ibm-webservices-bnd.xmi:
>>> >>>>>> ------------------------
>>> >>>>>>
>>> >>>>>>
>>> >>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
>>> >>>>
>>> >>>>>
>>> >>>>>>
>>> >>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
>>> >>>>
>>> >>>>>
>>> >>>>>>
>>> >>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>>> >>>>
>>> >>>>>
>>> >>>>>> Application bindings:
>>> >>>>>> ---------------------
>>> >>>>>>
>>> >>>>>>
>>> >>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>>> >>>>
>>> >>>>>
>>> >>>>>>
>>> >>>>>> Karan Malhi wrote:
>>> >>>>>>
>>> >>>>>>>
>>> >>>>>>> oops!
>>> >>>>>>>
>>> >>>>>>> I pasted the files for ejb 1.1 . Not sure if something changed for
>>> ejb
>>> >>>>>>>
>>> >>>>>> 2.1
>>> >>>>
>>> >>>>> .
>>> >>>>>>> I think we can ignore the ibm-ejb-ext files for now because they
>>> >>>>>>>
>>> >>>>>> contain
>>> >>>>
>>> >>>>> ibm
>>> >>>>>>> extensions. its the ibm-ejb-jar-bnd files which should be of
>>> interest.
>>> >>>>>>>
>>> >>>>>> I
>>> >>>>
>>> >>>>> will try and create a more comprehensive file using RAD or AST. This
>>> >>>>>>>
>>> >>>>>> will
>>> >>>>
>>> >>>>> contain local, remote ejb references, references to activation spec
>>> for
>>> >>>>>>> mdb,
>>> >>>>>>> datasource . We could probably use that to generate the schema.
>>> >>>>>>>
>>> >>>>>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <
>>> karan.malhi@gmail.com>
>>> >>>>>>> wrote:
>>> >>>>>>>
>>> >>>>>>> Or if you can grab the xmi files there's probably a way to convert
>>> >>>>>>>>
>>> >>>>>>> them
>>> >>>>
>>> >>>>> to
>>> >>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>>>> xsd.
>>> >>>>>>>>>
>>> >>>>>>>>> I think this would be the best approach. Since Attachments are
>>> >>>>>>>> disallowed,
>>> >>>>>>>> I am giving the file name, its purpose followed by its contents.
>>> You
>>> >>>>>>>> should
>>> >>>>>>>> be able to create the file on the local system and paste the
>>> contents
>>> >>>>>>>>
>>> >>>>>>> in
>>> >>>>
>>> >>>>> it.
>>> >>>>>>>> Please keep in mind though that these files do not contain all
>>> info
>>> >>>>>>>>
>>> >>>>>>> they
>>> >>>>
>>> >>>>> could contain, so generating a schema out of them may not get us a
>>> >>>>>>>> comprehensive schema. (Actually, I was able to generate a schema
>>> >>>>>>>> using
>>> >>>>>>>>
>>> >>>>>>> c#
>>> >>>>
>>> >>>>> )
>>> >>>>>>>>
>>> >>>>>>>> File Name:- ibm-ejb-jar-bnd.xmi
>>> >>>>>>>> Contents:-
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> -----------------------------------------------------------------------------
>>> >>>>
>>> >>>>> <?xml version="1.0" encoding="UTF-8"?>
>>> >>>>>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>>> >>>>>>>> xmlns:xmi="http://www.omg.org/XMI"
>>> >>>>>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>>> >>>>>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="
>>> >>>>>>>>
>>> >>>>>>> http://www.w3.org/2001/XMLSchema-instance"
>>> >>>>
>>> >>>>> xmi:id="ejb-jar_ID_Bnd">
>>> >>>>>>>> <defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
>>> >>>>>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>>> >>>>>>>> xmi:id="BasicAuthData_1">
>>> >>>>>>>> <userId xsi:nil="true"/>
>>> >>>>>>>> <password xsi:nil="true"/>
>>> >>>>>>>> </defaultAuth>
>>> >>>>>>>> </defaultDatasource>
>>> >>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>> >>>>>>>> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
>>> >>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>> >>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>> >>>>>>>> </ejbBindings>
>>> >>>>>>>> </ejbbnd:EJBJarBinding>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> ----------------------------------------------------------------------------------
>>> >>>>
>>> >>>>>
>>> >>>>>>>> File Name:-ibm-ejb-jar-ext.xmi
>>> >>>>>>>> Contents:-
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> -----------------------------------------------------------------------------------
>>> >>>>
>>> >>>>> <?xml version="1.0" encoding="UTF-8"?>
>>> >>>>>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>>> >>>>>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi"
>>> >>>>>>>> xmlns:ejb="ejb.xmi"
>>> >>>>>>>> xmi:id="ejb-jar_ID_Ext">
>>> >>>>>>>> <ejbExtensions xmi:type="ejbext:SessionExtension"
>>> >>>>>>>>
>>> >>>>>>> xmi:id="Session_1_Ext"
>>> >>>>
>>> >>>>> timeout="600">
>>> >>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>> >>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>> >>>>>>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>>> >>>>>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>>> >>>>>>>> <internationalization xmi:id="BeanInternationalization_1"
>>> >>>>>>>> invocationLocale="CALLER"/>
>>> >>>>>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>>> >>>>>>>> unresolvedAction="ROLLBACK"/>
>>> >>>>>>>> </ejbExtensions>
>>> >>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>> >>>>>>>> </ejbext:EJBJarExtension>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> ------------------------------------------------------------------------------------
>>> >>>>
>>> >>>>>
>>> >>>>>>>> File Name:- ejb-jar.xml
>>> >>>>>>>> Contents:-
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> -----------------------------------------------------------------------------------
>>> >>>>
>>> >>>>> <?xml version="1.0" encoding="UTF-8"?>
>>> >>>>>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD
>>> Enterprise
>>> >>>>>>>> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd
>>> ">
>>> >>>>>>>>
>>> >>>>>>>> <ejb-jar id="ejb-jar_ID">
>>> >>>>>>>> <description>IVT Stateful Session EJB</description>
>>> >>>>>>>> <display-name>IVT EJB Module</display-name>
>>> >>>>>>>> <enterprise-beans>
>>> >>>>>>>> <session id="Session_1">
>>> >>>>>>>> <description>Verify Stateful Session EJB</description>
>>> >>>>>>>> <display-name>Verification of Stateful Session
>>> >>>>>>>> EJB</display-name>
>>> >>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>> >>>>>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>>> >>>>>>>>
>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>>> >>>>>>>>
>>> >>>>>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>>> >>>>>>>> <session-type>Stateful</session-type>
>>> >>>>>>>> <transaction-type>Container</transaction-type>
>>> >>>>>>>> </session>
>>> >>>>>>>> </enterprise-beans>
>>> >>>>>>>> <assembly-descriptor id="AssemblyDescriptor_1">
>>> >>>>>>>> <container-transaction id="MethodTransaction_1">
>>> >>>>>>>> <method id="MethodElement_1">
>>> >>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>> >>>>>>>> <method-name>*</method-name>
>>> >>>>>>>> </method>
>>> >>>>>>>> <trans-attribute>Never</trans-attribute>
>>> >>>>>>>> </container-transaction>
>>> >>>>>>>> </assembly-descriptor>
>>> >>>>>>>> </ejb-jar>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> -----------------------------------------------------------------------------------
>>> >>>>
>>> >>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>> --
>>> >>>>>>>> Karan Singh Malhi
>>> >>>>>>>>
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>> --
>>> >>>>> Thanks
>>> >>>>> - Mohammad Nour
>>> >>>>>
>>> >>>>>
>>> >>>>
>>> >>>>
>>> >>>> --
>>> >>>> Thanks
>>> >>>> - Mohammad Nour
>>> >>>>
>>> >>>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>> Karan Singh Malhi
>>> >>>
>>> >>
>>> >>
>>> >
>>> >
>>> > --
>>> > Karan Singh Malhi
>>> >
>>>
>>
>>
>>
>> --
>> Karan Singh Malhi
>>
>
>
>
> --
> Thanks
> - Mohammad Nour
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
I am still working on generating the JAXB classes for the DDs xsds. I
just need more time to learn JAXB more cause I didn't use it so often
before. I am facing no problems just need time to learn :)
On Mon, Jul 7, 2008 at 10:11 PM, Mohammad Nour El-Din
<no...@gmail.com> wrote:
> Thanks for giving me a new thing to learn :)
>
> On Mon, Jul 7, 2008 at 9:04 PM, Dain Sundstrom <da...@iq80.com> wrote:
>> On Jul 6, 2008, at 2:58 PM, Mohammad Nour El-Din wrote:
>>
>>> Dain, r u the one who developed the sxc-jaxb-maven plugin ???
>>
>> Yes.
>>
>> -dain
>>
>
>
>
> --
> Thanks
> - Mohammad Nour
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Thanks for giving me a new thing to learn :)
On Mon, Jul 7, 2008 at 9:04 PM, Dain Sundstrom <da...@iq80.com> wrote:
> On Jul 6, 2008, at 2:58 PM, Mohammad Nour El-Din wrote:
>
>> Dain, r u the one who developed the sxc-jaxb-maven plugin ???
>
> Yes.
>
> -dain
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by Dain Sundstrom <da...@iq80.com>.
On Jul 6, 2008, at 2:58 PM, Mohammad Nour El-Din wrote:
> Dain, r u the one who developed the sxc-jaxb-maven plugin ???
Yes.
-dain
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Dain, r u the one who developed the sxc-jaxb-maven plugin ???
On Sun, Jul 6, 2008 at 7:10 PM, Mohammad Nour El-Din
<no...@gmail.com> wrote:
> As I have a successful build of OpenEJB - at last and thanks to Karan
> - I will start on the WAS DDs JEE classes today.
>
> On Wed, Jun 25, 2008 at 3:02 PM, Mohammad Nour El-Din
> <no...@gmail.com> wrote:
>> Thanks GOD we didn't share anything in this list, but the hint I've
>> sent on the list is enough to locate the files we need and then to
>> generate parsers from them, and that's all what we need.
>>
>> But there is an idea I want to share with you all, as IBM is
>> contributing a lot to oss and specially with Apache, why not mkaing
>> some contacts to make them give us a sort of permission to use those
>> XSDs for oss purposes. I have some contacts already but I want to make
>> sure that contacting them for this idea is not a bad action towards
>> OpenEJB, I mean this way they will know that we will use their XSDs.
>> So what do you suggest, talk to them or not talk to them - this is
>> the question ;) ???
>>
>> On Mon, Jun 23, 2008 at 9:54 PM, Daniel S. Haischt
>> <da...@googlemail.com> wrote:
>>> basically I would say cause the XSDs are covered by IBM IP and thus
>>> it's prohibited to redistribute them. I discussed that with Mohammad
>>> this afternoon and I am pretty sure that this scenario is covered
>>> by the license terms anyway.
>>>
>>> what would have made things worse is that at least I and I think
>>> Mohammad as well got our WAS versions from an IBM internal site
>>> and redistributing files from such a WAS version would have been
>>> probably a disaster in regards of legal policies.
>>>
>>> so it's good we discussed this subject before doing anything bad :)
>>>
>>> David Blevins wrote:
>>>>
>>>> On Jun 23, 2008, at 7:21 AM, Mohammad Nour El-Din wrote:
>>>>
>>>>> Well I am not sure if it is legal to send even the names of the files
>>>>> over here, can someone help me and asnwer that question, is it legal
>>>>> to send even the names on that list ?
>>>>
>>>> Sending the names of xsd files is ok, sending the xsd files themselves is
>>>> not.
>>>>
>>>> -David
>>>>
>>>>> On Mon, Jun 23, 2008 at 4:48 PM, Karan Malhi <ka...@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> I have a local WAS 6.1 . I do see the
>>>>>> <<WAS_INSTALL>>/properties/schemas,
>>>>>> but do not see the schemas for the xmi files bundled inside an ejb-jar.
>>>>>> I
>>>>>> would definitely be interested in the schemas, so if you can send those
>>>>>> to
>>>>>> me , that would be great
>>>>>>
>>>>>> On Mon, Jun 23, 2008 at 9:01 AM, Daniel S. Haischt <
>>>>>> daniel.haischt@googlemail.com> wrote:
>>>>>>
>>>>>>> just a suggestion - anyone that is interested in the XSD files should
>>>>>>> reply to this thread.
>>>>>>> Mohammad or I will then provide you with the XSDs for WAS V6.1 by
>>>>>>> sending you a private
>>>>>>> mail having the XSDs attached.
>>>>>>>
>>>>>>> That way you don't need to download and install WAS locally.
>>>>>>>
>>>>>>> On Mon, Jun 23, 2008 at 12:04 AM, Karan Malhi <ka...@gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Sorry,
>>>>>>>>
>>>>>>>> Obviously didn't realize that . Thanks for catching that :)
>>>>>>>>
>>>>>>>> On Sun, Jun 22, 2008 at 5:05 PM, David Blevins
>>>>>>>> <da...@visi.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Jun 22, 2008, at 12:46 PM, Karan Malhi wrote:
>>>>>>>>>
>>>>>>>>> Great,
>>>>>>>>>>
>>>>>>>>>> I have created a Jira issue so that we could share the zip files.
>>>>>>>>>>
>>>>>>>>>> https://issues.apache.org/jira/browse/OPENEJB-830
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Just an fyi, we can't publicly redistribute those on apache hardware.
>>>>>>>>>
>>>>>>>>> -David
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sun, Jun 22, 2008 at 2:06 PM, Mohammad Nour El-Din <
>>>>>>>>>> nour.mohammad@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi All...
>>>>>>>>>>>
>>>>>>>>>>> Good news :), I found all the XSDs we need. They are shipped with
>>>>>>>>>>> the WAS installation under <was_home>/properties/schemas directory,
>>>>>>>>>>> all the XSDs we dreamed of, the one for XMI and for all the other
>>>>>>>>>>> WAS
>>>>>>>>>>> specific DDs. I have to go home now, so I will collect them in 1
>>>>>>>>>>> zip
>>>>>>>>>>> file and I will send them on the list tomorrow 23-Jun-2008.
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
>>>>>>>>>>> <no...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Thanks Daniel for clarifications. What I am doing now, is to get
>>>>>>>>>>>> the
>>>>>>>>>>>> XMI files referenced inside both the binding and extensions XMI
>>>>>>>
>>>>>>> files,
>>>>>>>>>>>>
>>>>>>>>>>>> which will help us making the corresspodent XSDs. I talked with
>>>>>>>>>>>> Dain
>>>>>>>>>>>> on IRC about that. I just need sometime cause the XMI are located
>>>>>>>>>>>> inside one of the large number pf JARs shipped with WAS. Expected
>>>>>>>>>>>> to
>>>>>>>>>>>> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
>>>>>>>>>>>>
>>>>>>>>>>>> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
>>>>>>>>>>>> <da...@googlemail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> a couple of thoughts...
>>>>>>>>>>>>>
>>>>>>>>>>>>> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF,
>>>>>>>
>>>>>>> MOF
>>>>>>>>>>>>>
>>>>>>>>>>>>> and XMI. ECore is the Eclipse pendant to MOF. They are both
>>>>>>>
>>>>>>> completely
>>>>>>>>>>>>>
>>>>>>>>>>>>> independent efforts. Both could be used as a basis for a
>>>>>>>>>>>>> so-called
>>>>>>>>>>>>> Domain Specific Language (DSL). A kinda one size fits all DSL is
>>>>>>>
>>>>>>> UML.
>>>>>>>>>>>>>
>>>>>>>>>>>>> MOF models can be access in Java using the JMI API. ECore models
>>>>>>>>>>>>> can
>>>>>>>>>>>>> be accessed in Java using the EMF programmatic API. Both MOF and
>>>>>>>
>>>>>>> ECore
>>>>>>>>>>>>>
>>>>>>>>>>>>> models will be persisted using an instance of XMI.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2) As David already pointed out, as long as we don't ship
>>>>>>>
>>>>>>> proprietary
>>>>>>>>>>>>>
>>>>>>>>>>>>> XSDs and such, we should be fine cause AFAIK even XDoclet and
>>>>>>>>>>>>> other
>>>>>>>>>>>>> tools are supporting proprietary WAS binding files. So why
>>>>>>>>>>>>> shouldn't
>>>>>>>>>>>>> we be allowed to do the same?
>>>>>>>>>>>>>
>>>>>>>>>>>>> 3) Some more docs about the WAS binding files:
>>>>>>>>>>>>>
>>>>>>>>>>>>> ibm-webservicesclient-bnd.xmi:
>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> ibm-webservices-bnd.xmi:
>>>>>>>>>>>>> ------------------------
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Application bindings:
>>>>>>>>>>>>> ---------------------
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Karan Malhi wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> oops!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I pasted the files for ejb 1.1 . Not sure if something changed
>>>>>>>>>>>>>> for
>>>>>>>
>>>>>>> ejb
>>>>>>>>>>>>>>
>>>>>>>>>>>>> 2.1
>>>>>>>>>>>
>>>>>>>>>>>> .
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I think we can ignore the ibm-ejb-ext files for now because they
>>>>>>>>>>>>>>
>>>>>>>>>>>>> contain
>>>>>>>>>>>
>>>>>>>>>>>> ibm
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> extensions. its the ibm-ejb-jar-bnd files which should be of
>>>>>>>
>>>>>>> interest.
>>>>>>>>>>>>>>
>>>>>>>>>>>>> I
>>>>>>>>>>>
>>>>>>>>>>>> will try and create a more comprehensive file using RAD or AST.
>>>>>>>>>>>> This
>>>>>>>>>>>>>>
>>>>>>>>>>>>> will
>>>>>>>>>>>
>>>>>>>>>>>> contain local, remote ejb references, references to activation
>>>>>>>>>>>> spec
>>>>>>>
>>>>>>> for
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> mdb,
>>>>>>>>>>>>>> datasource . We could probably use that to generate the schema.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <
>>>>>>>
>>>>>>> karan.malhi@gmail.com>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Or if you can grab the xmi files there's probably a way to
>>>>>>>>>>>>>> convert
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> them
>>>>>>>>>>>
>>>>>>>>>>>> to
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> xsd.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I think this would be the best approach. Since Attachments are
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> disallowed,
>>>>>>>>>>>>>>> I am giving the file name, its purpose followed by its
>>>>>>>>>>>>>>> contents.
>>>>>>>
>>>>>>> You
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> should
>>>>>>>>>>>>>>> be able to create the file on the local system and paste the
>>>>>>>
>>>>>>> contents
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> in
>>>>>>>>>>>
>>>>>>>>>>>> it.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Please keep in mind though that these files do not contain all
>>>>>>>
>>>>>>> info
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> they
>>>>>>>>>>>
>>>>>>>>>>>> could contain, so generating a schema out of them may not get us a
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> comprehensive schema. (Actually, I was able to generate a
>>>>>>>>>>>>>>> schema
>>>>>>>>>>>>>>> using
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> c#
>>>>>>>>>>>
>>>>>>>>>>>> )
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> File Name:- ibm-ejb-jar-bnd.xmi
>>>>>>>>>>>>>>> Contents:-
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>
>>>>>>> -----------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>>>>>>>>>>>>>>> xmlns:xmi="http://www.omg.org/XMI"
>>>>>>>>>>>>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>>>>>>>>>>>>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> http://www.w3.org/2001/XMLSchema-instance"
>>>>>>>>>>>
>>>>>>>>>>>> xmi:id="ejb-jar_ID_Bnd">
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <defaultDatasource xmi:id="ResourceRefBinding_1"
>>>>>>>>>>>>>>> jndiName="ivt">
>>>>>>>>>>>>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>>>>>>>>>>>>>>> xmi:id="BasicAuthData_1">
>>>>>>>>>>>>>>> <userId xsi:nil="true"/>
>>>>>>>>>>>>>>> <password xsi:nil="true"/>
>>>>>>>>>>>>>>> </defaultAuth>
>>>>>>>>>>>>>>> </defaultDatasource>
>>>>>>>>>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>>>>>>>>>> <ejbBindings xmi:id="Session_1_Bnd"
>>>>>>>>>>>>>>> jndiName="ejb/ivtEJBObject">
>>>>>>>>>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>>>>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>>>>>>>>>> </ejbBindings>
>>>>>>>>>>>>>>> </ejbbnd:EJBJarBinding>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>
>>>>>>> ----------------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>>> File Name:-ibm-ejb-jar-ext.xmi
>>>>>>>>>>>>>>> Contents:-
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>
>>>>>>> -----------------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>>>>>>>>>>>>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi"
>>>>>>>>>>>>>>> xmlns:ejb="ejb.xmi"
>>>>>>>>>>>>>>> xmi:id="ejb-jar_ID_Ext">
>>>>>>>>>>>>>>> <ejbExtensions xmi:type="ejbext:SessionExtension"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> xmi:id="Session_1_Ext"
>>>>>>>>>>>
>>>>>>>>>>>> timeout="600">
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>>>>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>>>>>>>>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>>>>>>>>>>>>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>>>>>>>>>>>>>>> <internationalization xmi:id="BeanInternationalization_1"
>>>>>>>>>>>>>>> invocationLocale="CALLER"/>
>>>>>>>>>>>>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>>>>>>>>>>>>>>> unresolvedAction="ROLLBACK"/>
>>>>>>>>>>>>>>> </ejbExtensions>
>>>>>>>>>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>>>>>>>>>> </ejbext:EJBJarExtension>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>>> File Name:- ejb-jar.xml
>>>>>>>>>>>>>>> Contents:-
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>
>>>>>>> -----------------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD
>>>>>>>
>>>>>>> Enterprise
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> JavaBeans 1.1//EN"
>>>>>>>>>>>>>>> "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd
>>>>>>>
>>>>>>> ">
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <ejb-jar id="ejb-jar_ID">
>>>>>>>>>>>>>>> <description>IVT Stateful Session EJB</description>
>>>>>>>>>>>>>>> <display-name>IVT EJB Module</display-name>
>>>>>>>>>>>>>>> <enterprise-beans>
>>>>>>>>>>>>>>> <session id="Session_1">
>>>>>>>>>>>>>>> <description>Verify Stateful Session EJB</description>
>>>>>>>>>>>>>>> <display-name>Verification of Stateful Session
>>>>>>>>>>>>>>> EJB</display-name>
>>>>>>>>>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>>>>>>>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>>>>>>>>>>>>>>>
>>>>>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>>>>>>>>>>>>>>> <session-type>Stateful</session-type>
>>>>>>>>>>>>>>> <transaction-type>Container</transaction-type>
>>>>>>>>>>>>>>> </session>
>>>>>>>>>>>>>>> </enterprise-beans>
>>>>>>>>>>>>>>> <assembly-descriptor id="AssemblyDescriptor_1">
>>>>>>>>>>>>>>> <container-transaction id="MethodTransaction_1">
>>>>>>>>>>>>>>> <method id="MethodElement_1">
>>>>>>>>>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>>>>>>>>>> <method-name>*</method-name>
>>>>>>>>>>>>>>> </method>
>>>>>>>>>>>>>>> <trans-attribute>Never</trans-attribute>
>>>>>>>>>>>>>>> </container-transaction>
>>>>>>>>>>>>>>> </assembly-descriptor>
>>>>>>>>>>>>>>> </ejb-jar>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>
>>>>>>> -----------------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Karan Singh Malhi
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Thanks
>>>>>>>>>>>> - Mohammad Nour
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Thanks
>>>>>>>>>>> - Mohammad Nour
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Karan Singh Malhi
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Karan Singh Malhi
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Karan Singh Malhi
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Thanks
>>>>> - Mohammad Nour
>>>>>
>>>>
>>>
>>>
>>
>>
>>
>> --
>> Thanks
>> - Mohammad Nour
>>
>
>
>
> --
> Thanks
> - Mohammad Nour
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
As I have a successful build of OpenEJB - at last and thanks to Karan
- I will start on the WAS DDs JEE classes today.
On Wed, Jun 25, 2008 at 3:02 PM, Mohammad Nour El-Din
<no...@gmail.com> wrote:
> Thanks GOD we didn't share anything in this list, but the hint I've
> sent on the list is enough to locate the files we need and then to
> generate parsers from them, and that's all what we need.
>
> But there is an idea I want to share with you all, as IBM is
> contributing a lot to oss and specially with Apache, why not mkaing
> some contacts to make them give us a sort of permission to use those
> XSDs for oss purposes. I have some contacts already but I want to make
> sure that contacting them for this idea is not a bad action towards
> OpenEJB, I mean this way they will know that we will use their XSDs.
> So what do you suggest, talk to them or not talk to them - this is
> the question ;) ???
>
> On Mon, Jun 23, 2008 at 9:54 PM, Daniel S. Haischt
> <da...@googlemail.com> wrote:
>> basically I would say cause the XSDs are covered by IBM IP and thus
>> it's prohibited to redistribute them. I discussed that with Mohammad
>> this afternoon and I am pretty sure that this scenario is covered
>> by the license terms anyway.
>>
>> what would have made things worse is that at least I and I think
>> Mohammad as well got our WAS versions from an IBM internal site
>> and redistributing files from such a WAS version would have been
>> probably a disaster in regards of legal policies.
>>
>> so it's good we discussed this subject before doing anything bad :)
>>
>> David Blevins wrote:
>>>
>>> On Jun 23, 2008, at 7:21 AM, Mohammad Nour El-Din wrote:
>>>
>>>> Well I am not sure if it is legal to send even the names of the files
>>>> over here, can someone help me and asnwer that question, is it legal
>>>> to send even the names on that list ?
>>>
>>> Sending the names of xsd files is ok, sending the xsd files themselves is
>>> not.
>>>
>>> -David
>>>
>>>> On Mon, Jun 23, 2008 at 4:48 PM, Karan Malhi <ka...@gmail.com>
>>>> wrote:
>>>>>
>>>>> I have a local WAS 6.1 . I do see the
>>>>> <<WAS_INSTALL>>/properties/schemas,
>>>>> but do not see the schemas for the xmi files bundled inside an ejb-jar.
>>>>> I
>>>>> would definitely be interested in the schemas, so if you can send those
>>>>> to
>>>>> me , that would be great
>>>>>
>>>>> On Mon, Jun 23, 2008 at 9:01 AM, Daniel S. Haischt <
>>>>> daniel.haischt@googlemail.com> wrote:
>>>>>
>>>>>> just a suggestion - anyone that is interested in the XSD files should
>>>>>> reply to this thread.
>>>>>> Mohammad or I will then provide you with the XSDs for WAS V6.1 by
>>>>>> sending you a private
>>>>>> mail having the XSDs attached.
>>>>>>
>>>>>> That way you don't need to download and install WAS locally.
>>>>>>
>>>>>> On Mon, Jun 23, 2008 at 12:04 AM, Karan Malhi <ka...@gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> Sorry,
>>>>>>>
>>>>>>> Obviously didn't realize that . Thanks for catching that :)
>>>>>>>
>>>>>>> On Sun, Jun 22, 2008 at 5:05 PM, David Blevins
>>>>>>> <da...@visi.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> On Jun 22, 2008, at 12:46 PM, Karan Malhi wrote:
>>>>>>>>
>>>>>>>> Great,
>>>>>>>>>
>>>>>>>>> I have created a Jira issue so that we could share the zip files.
>>>>>>>>>
>>>>>>>>> https://issues.apache.org/jira/browse/OPENEJB-830
>>>>>>>>>
>>>>>>>>
>>>>>>>> Just an fyi, we can't publicly redistribute those on apache hardware.
>>>>>>>>
>>>>>>>> -David
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sun, Jun 22, 2008 at 2:06 PM, Mohammad Nour El-Din <
>>>>>>>>> nour.mohammad@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Hi All...
>>>>>>>>>>
>>>>>>>>>> Good news :), I found all the XSDs we need. They are shipped with
>>>>>>>>>> the WAS installation under <was_home>/properties/schemas directory,
>>>>>>>>>> all the XSDs we dreamed of, the one for XMI and for all the other
>>>>>>>>>> WAS
>>>>>>>>>> specific DDs. I have to go home now, so I will collect them in 1
>>>>>>>>>> zip
>>>>>>>>>> file and I will send them on the list tomorrow 23-Jun-2008.
>>>>>>>>>>
>>>>>>>>>> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
>>>>>>>>>> <no...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Thanks Daniel for clarifications. What I am doing now, is to get
>>>>>>>>>>> the
>>>>>>>>>>> XMI files referenced inside both the binding and extensions XMI
>>>>>>
>>>>>> files,
>>>>>>>>>>>
>>>>>>>>>>> which will help us making the corresspodent XSDs. I talked with
>>>>>>>>>>> Dain
>>>>>>>>>>> on IRC about that. I just need sometime cause the XMI are located
>>>>>>>>>>> inside one of the large number pf JARs shipped with WAS. Expected
>>>>>>>>>>> to
>>>>>>>>>>> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
>>>>>>>>>>>
>>>>>>>>>>> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
>>>>>>>>>>> <da...@googlemail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> a couple of thoughts...
>>>>>>>>>>>>
>>>>>>>>>>>> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF,
>>>>>>
>>>>>> MOF
>>>>>>>>>>>>
>>>>>>>>>>>> and XMI. ECore is the Eclipse pendant to MOF. They are both
>>>>>>
>>>>>> completely
>>>>>>>>>>>>
>>>>>>>>>>>> independent efforts. Both could be used as a basis for a
>>>>>>>>>>>> so-called
>>>>>>>>>>>> Domain Specific Language (DSL). A kinda one size fits all DSL is
>>>>>>
>>>>>> UML.
>>>>>>>>>>>>
>>>>>>>>>>>> MOF models can be access in Java using the JMI API. ECore models
>>>>>>>>>>>> can
>>>>>>>>>>>> be accessed in Java using the EMF programmatic API. Both MOF and
>>>>>>
>>>>>> ECore
>>>>>>>>>>>>
>>>>>>>>>>>> models will be persisted using an instance of XMI.
>>>>>>>>>>>>
>>>>>>>>>>>> 2) As David already pointed out, as long as we don't ship
>>>>>>
>>>>>> proprietary
>>>>>>>>>>>>
>>>>>>>>>>>> XSDs and such, we should be fine cause AFAIK even XDoclet and
>>>>>>>>>>>> other
>>>>>>>>>>>> tools are supporting proprietary WAS binding files. So why
>>>>>>>>>>>> shouldn't
>>>>>>>>>>>> we be allowed to do the same?
>>>>>>>>>>>>
>>>>>>>>>>>> 3) Some more docs about the WAS binding files:
>>>>>>>>>>>>
>>>>>>>>>>>> ibm-webservicesclient-bnd.xmi:
>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> ibm-webservices-bnd.xmi:
>>>>>>>>>>>> ------------------------
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Application bindings:
>>>>>>>>>>>> ---------------------
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Karan Malhi wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> oops!
>>>>>>>>>>>>>
>>>>>>>>>>>>> I pasted the files for ejb 1.1 . Not sure if something changed
>>>>>>>>>>>>> for
>>>>>>
>>>>>> ejb
>>>>>>>>>>>>>
>>>>>>>>>>>> 2.1
>>>>>>>>>>
>>>>>>>>>>> .
>>>>>>>>>>>>>
>>>>>>>>>>>>> I think we can ignore the ibm-ejb-ext files for now because they
>>>>>>>>>>>>>
>>>>>>>>>>>> contain
>>>>>>>>>>
>>>>>>>>>>> ibm
>>>>>>>>>>>>>
>>>>>>>>>>>>> extensions. its the ibm-ejb-jar-bnd files which should be of
>>>>>>
>>>>>> interest.
>>>>>>>>>>>>>
>>>>>>>>>>>> I
>>>>>>>>>>
>>>>>>>>>>> will try and create a more comprehensive file using RAD or AST.
>>>>>>>>>>> This
>>>>>>>>>>>>>
>>>>>>>>>>>> will
>>>>>>>>>>
>>>>>>>>>>> contain local, remote ejb references, references to activation
>>>>>>>>>>> spec
>>>>>>
>>>>>> for
>>>>>>>>>>>>>
>>>>>>>>>>>>> mdb,
>>>>>>>>>>>>> datasource . We could probably use that to generate the schema.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <
>>>>>>
>>>>>> karan.malhi@gmail.com>
>>>>>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Or if you can grab the xmi files there's probably a way to
>>>>>>>>>>>>> convert
>>>>>>>>>>>>>>
>>>>>>>>>>>>> them
>>>>>>>>>>
>>>>>>>>>>> to
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> xsd.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I think this would be the best approach. Since Attachments are
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> disallowed,
>>>>>>>>>>>>>> I am giving the file name, its purpose followed by its
>>>>>>>>>>>>>> contents.
>>>>>>
>>>>>> You
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> should
>>>>>>>>>>>>>> be able to create the file on the local system and paste the
>>>>>>
>>>>>> contents
>>>>>>>>>>>>>>
>>>>>>>>>>>>> in
>>>>>>>>>>
>>>>>>>>>>> it.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Please keep in mind though that these files do not contain all
>>>>>>
>>>>>> info
>>>>>>>>>>>>>>
>>>>>>>>>>>>> they
>>>>>>>>>>
>>>>>>>>>>> could contain, so generating a schema out of them may not get us a
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> comprehensive schema. (Actually, I was able to generate a
>>>>>>>>>>>>>> schema
>>>>>>>>>>>>>> using
>>>>>>>>>>>>>>
>>>>>>>>>>>>> c#
>>>>>>>>>>
>>>>>>>>>>> )
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> File Name:- ibm-ejb-jar-bnd.xmi
>>>>>>>>>>>>>> Contents:-
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>>>>>>>>>>>>>> xmlns:xmi="http://www.omg.org/XMI"
>>>>>>>>>>>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>>>>>>>>>>>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="
>>>>>>>>>>>>>>
>>>>>>>>>>>>> http://www.w3.org/2001/XMLSchema-instance"
>>>>>>>>>>
>>>>>>>>>>> xmi:id="ejb-jar_ID_Bnd">
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <defaultDatasource xmi:id="ResourceRefBinding_1"
>>>>>>>>>>>>>> jndiName="ivt">
>>>>>>>>>>>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>>>>>>>>>>>>>> xmi:id="BasicAuthData_1">
>>>>>>>>>>>>>> <userId xsi:nil="true"/>
>>>>>>>>>>>>>> <password xsi:nil="true"/>
>>>>>>>>>>>>>> </defaultAuth>
>>>>>>>>>>>>>> </defaultDatasource>
>>>>>>>>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>>>>>>>>> <ejbBindings xmi:id="Session_1_Bnd"
>>>>>>>>>>>>>> jndiName="ejb/ivtEJBObject">
>>>>>>>>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>>>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>>>>>>>>> </ejbBindings>
>>>>>>>>>>>>>> </ejbbnd:EJBJarBinding>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>
>>>>>> ----------------------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>>> File Name:-ibm-ejb-jar-ext.xmi
>>>>>>>>>>>>>> Contents:-
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>>>>>>>>>>>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi"
>>>>>>>>>>>>>> xmlns:ejb="ejb.xmi"
>>>>>>>>>>>>>> xmi:id="ejb-jar_ID_Ext">
>>>>>>>>>>>>>> <ejbExtensions xmi:type="ejbext:SessionExtension"
>>>>>>>>>>>>>>
>>>>>>>>>>>>> xmi:id="Session_1_Ext"
>>>>>>>>>>
>>>>>>>>>>> timeout="600">
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>>>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>>>>>>>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>>>>>>>>>>>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>>>>>>>>>>>>>> <internationalization xmi:id="BeanInternationalization_1"
>>>>>>>>>>>>>> invocationLocale="CALLER"/>
>>>>>>>>>>>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>>>>>>>>>>>>>> unresolvedAction="ROLLBACK"/>
>>>>>>>>>>>>>> </ejbExtensions>
>>>>>>>>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>>>>>>>>> </ejbext:EJBJarExtension>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>>> File Name:- ejb-jar.xml
>>>>>>>>>>>>>> Contents:-
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD
>>>>>>
>>>>>> Enterprise
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> JavaBeans 1.1//EN"
>>>>>>>>>>>>>> "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd
>>>>>>
>>>>>> ">
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <ejb-jar id="ejb-jar_ID">
>>>>>>>>>>>>>> <description>IVT Stateful Session EJB</description>
>>>>>>>>>>>>>> <display-name>IVT EJB Module</display-name>
>>>>>>>>>>>>>> <enterprise-beans>
>>>>>>>>>>>>>> <session id="Session_1">
>>>>>>>>>>>>>> <description>Verify Stateful Session EJB</description>
>>>>>>>>>>>>>> <display-name>Verification of Stateful Session
>>>>>>>>>>>>>> EJB</display-name>
>>>>>>>>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>>>>>>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>>>>>>>>>>>>>>
>>>>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>>>>>>>>>>>>>> <session-type>Stateful</session-type>
>>>>>>>>>>>>>> <transaction-type>Container</transaction-type>
>>>>>>>>>>>>>> </session>
>>>>>>>>>>>>>> </enterprise-beans>
>>>>>>>>>>>>>> <assembly-descriptor id="AssemblyDescriptor_1">
>>>>>>>>>>>>>> <container-transaction id="MethodTransaction_1">
>>>>>>>>>>>>>> <method id="MethodElement_1">
>>>>>>>>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>>>>>>>>> <method-name>*</method-name>
>>>>>>>>>>>>>> </method>
>>>>>>>>>>>>>> <trans-attribute>Never</trans-attribute>
>>>>>>>>>>>>>> </container-transaction>
>>>>>>>>>>>>>> </assembly-descriptor>
>>>>>>>>>>>>>> </ejb-jar>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Karan Singh Malhi
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Thanks
>>>>>>>>>>> - Mohammad Nour
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Thanks
>>>>>>>>>> - Mohammad Nour
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Karan Singh Malhi
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Karan Singh Malhi
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Karan Singh Malhi
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Thanks
>>>> - Mohammad Nour
>>>>
>>>
>>
>>
>
>
>
> --
> Thanks
> - Mohammad Nour
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Thanks GOD we didn't share anything in this list, but the hint I've
sent on the list is enough to locate the files we need and then to
generate parsers from them, and that's all what we need.
But there is an idea I want to share with you all, as IBM is
contributing a lot to oss and specially with Apache, why not mkaing
some contacts to make them give us a sort of permission to use those
XSDs for oss purposes. I have some contacts already but I want to make
sure that contacting them for this idea is not a bad action towards
OpenEJB, I mean this way they will know that we will use their XSDs.
So what do you suggest, talk to them or not talk to them - this is
the question ;) ???
On Mon, Jun 23, 2008 at 9:54 PM, Daniel S. Haischt
<da...@googlemail.com> wrote:
> basically I would say cause the XSDs are covered by IBM IP and thus
> it's prohibited to redistribute them. I discussed that with Mohammad
> this afternoon and I am pretty sure that this scenario is covered
> by the license terms anyway.
>
> what would have made things worse is that at least I and I think
> Mohammad as well got our WAS versions from an IBM internal site
> and redistributing files from such a WAS version would have been
> probably a disaster in regards of legal policies.
>
> so it's good we discussed this subject before doing anything bad :)
>
> David Blevins wrote:
>>
>> On Jun 23, 2008, at 7:21 AM, Mohammad Nour El-Din wrote:
>>
>>> Well I am not sure if it is legal to send even the names of the files
>>> over here, can someone help me and asnwer that question, is it legal
>>> to send even the names on that list ?
>>
>> Sending the names of xsd files is ok, sending the xsd files themselves is
>> not.
>>
>> -David
>>
>>> On Mon, Jun 23, 2008 at 4:48 PM, Karan Malhi <ka...@gmail.com>
>>> wrote:
>>>>
>>>> I have a local WAS 6.1 . I do see the
>>>> <<WAS_INSTALL>>/properties/schemas,
>>>> but do not see the schemas for the xmi files bundled inside an ejb-jar.
>>>> I
>>>> would definitely be interested in the schemas, so if you can send those
>>>> to
>>>> me , that would be great
>>>>
>>>> On Mon, Jun 23, 2008 at 9:01 AM, Daniel S. Haischt <
>>>> daniel.haischt@googlemail.com> wrote:
>>>>
>>>>> just a suggestion - anyone that is interested in the XSD files should
>>>>> reply to this thread.
>>>>> Mohammad or I will then provide you with the XSDs for WAS V6.1 by
>>>>> sending you a private
>>>>> mail having the XSDs attached.
>>>>>
>>>>> That way you don't need to download and install WAS locally.
>>>>>
>>>>> On Mon, Jun 23, 2008 at 12:04 AM, Karan Malhi <ka...@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> Sorry,
>>>>>>
>>>>>> Obviously didn't realize that . Thanks for catching that :)
>>>>>>
>>>>>> On Sun, Jun 22, 2008 at 5:05 PM, David Blevins
>>>>>> <da...@visi.com>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>> On Jun 22, 2008, at 12:46 PM, Karan Malhi wrote:
>>>>>>>
>>>>>>> Great,
>>>>>>>>
>>>>>>>> I have created a Jira issue so that we could share the zip files.
>>>>>>>>
>>>>>>>> https://issues.apache.org/jira/browse/OPENEJB-830
>>>>>>>>
>>>>>>>
>>>>>>> Just an fyi, we can't publicly redistribute those on apache hardware.
>>>>>>>
>>>>>>> -David
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Jun 22, 2008 at 2:06 PM, Mohammad Nour El-Din <
>>>>>>>> nour.mohammad@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Hi All...
>>>>>>>>>
>>>>>>>>> Good news :), I found all the XSDs we need. They are shipped with
>>>>>>>>> the WAS installation under <was_home>/properties/schemas directory,
>>>>>>>>> all the XSDs we dreamed of, the one for XMI and for all the other
>>>>>>>>> WAS
>>>>>>>>> specific DDs. I have to go home now, so I will collect them in 1
>>>>>>>>> zip
>>>>>>>>> file and I will send them on the list tomorrow 23-Jun-2008.
>>>>>>>>>
>>>>>>>>> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
>>>>>>>>> <no...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Thanks Daniel for clarifications. What I am doing now, is to get
>>>>>>>>>> the
>>>>>>>>>> XMI files referenced inside both the binding and extensions XMI
>>>>>
>>>>> files,
>>>>>>>>>>
>>>>>>>>>> which will help us making the corresspodent XSDs. I talked with
>>>>>>>>>> Dain
>>>>>>>>>> on IRC about that. I just need sometime cause the XMI are located
>>>>>>>>>> inside one of the large number pf JARs shipped with WAS. Expected
>>>>>>>>>> to
>>>>>>>>>> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
>>>>>>>>>>
>>>>>>>>>> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
>>>>>>>>>> <da...@googlemail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> a couple of thoughts...
>>>>>>>>>>>
>>>>>>>>>>> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF,
>>>>>
>>>>> MOF
>>>>>>>>>>>
>>>>>>>>>>> and XMI. ECore is the Eclipse pendant to MOF. They are both
>>>>>
>>>>> completely
>>>>>>>>>>>
>>>>>>>>>>> independent efforts. Both could be used as a basis for a
>>>>>>>>>>> so-called
>>>>>>>>>>> Domain Specific Language (DSL). A kinda one size fits all DSL is
>>>>>
>>>>> UML.
>>>>>>>>>>>
>>>>>>>>>>> MOF models can be access in Java using the JMI API. ECore models
>>>>>>>>>>> can
>>>>>>>>>>> be accessed in Java using the EMF programmatic API. Both MOF and
>>>>>
>>>>> ECore
>>>>>>>>>>>
>>>>>>>>>>> models will be persisted using an instance of XMI.
>>>>>>>>>>>
>>>>>>>>>>> 2) As David already pointed out, as long as we don't ship
>>>>>
>>>>> proprietary
>>>>>>>>>>>
>>>>>>>>>>> XSDs and such, we should be fine cause AFAIK even XDoclet and
>>>>>>>>>>> other
>>>>>>>>>>> tools are supporting proprietary WAS binding files. So why
>>>>>>>>>>> shouldn't
>>>>>>>>>>> we be allowed to do the same?
>>>>>>>>>>>
>>>>>>>>>>> 3) Some more docs about the WAS binding files:
>>>>>>>>>>>
>>>>>>>>>>> ibm-webservicesclient-bnd.xmi:
>>>>>>>>>>> ------------------------------
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> ibm-webservices-bnd.xmi:
>>>>>>>>>>> ------------------------
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Application bindings:
>>>>>>>>>>> ---------------------
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Karan Malhi wrote:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> oops!
>>>>>>>>>>>>
>>>>>>>>>>>> I pasted the files for ejb 1.1 . Not sure if something changed
>>>>>>>>>>>> for
>>>>>
>>>>> ejb
>>>>>>>>>>>>
>>>>>>>>>>> 2.1
>>>>>>>>>
>>>>>>>>>> .
>>>>>>>>>>>>
>>>>>>>>>>>> I think we can ignore the ibm-ejb-ext files for now because they
>>>>>>>>>>>>
>>>>>>>>>>> contain
>>>>>>>>>
>>>>>>>>>> ibm
>>>>>>>>>>>>
>>>>>>>>>>>> extensions. its the ibm-ejb-jar-bnd files which should be of
>>>>>
>>>>> interest.
>>>>>>>>>>>>
>>>>>>>>>>> I
>>>>>>>>>
>>>>>>>>>> will try and create a more comprehensive file using RAD or AST.
>>>>>>>>>> This
>>>>>>>>>>>>
>>>>>>>>>>> will
>>>>>>>>>
>>>>>>>>>> contain local, remote ejb references, references to activation
>>>>>>>>>> spec
>>>>>
>>>>> for
>>>>>>>>>>>>
>>>>>>>>>>>> mdb,
>>>>>>>>>>>> datasource . We could probably use that to generate the schema.
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <
>>>>>
>>>>> karan.malhi@gmail.com>
>>>>>>>>>>>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Or if you can grab the xmi files there's probably a way to
>>>>>>>>>>>> convert
>>>>>>>>>>>>>
>>>>>>>>>>>> them
>>>>>>>>>
>>>>>>>>>> to
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> xsd.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I think this would be the best approach. Since Attachments are
>>>>>>>>>>>>>
>>>>>>>>>>>>> disallowed,
>>>>>>>>>>>>> I am giving the file name, its purpose followed by its
>>>>>>>>>>>>> contents.
>>>>>
>>>>> You
>>>>>>>>>>>>>
>>>>>>>>>>>>> should
>>>>>>>>>>>>> be able to create the file on the local system and paste the
>>>>>
>>>>> contents
>>>>>>>>>>>>>
>>>>>>>>>>>> in
>>>>>>>>>
>>>>>>>>>> it.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Please keep in mind though that these files do not contain all
>>>>>
>>>>> info
>>>>>>>>>>>>>
>>>>>>>>>>>> they
>>>>>>>>>
>>>>>>>>>> could contain, so generating a schema out of them may not get us a
>>>>>>>>>>>>>
>>>>>>>>>>>>> comprehensive schema. (Actually, I was able to generate a
>>>>>>>>>>>>> schema
>>>>>>>>>>>>> using
>>>>>>>>>>>>>
>>>>>>>>>>>> c#
>>>>>>>>>
>>>>>>>>>> )
>>>>>>>>>>>>>
>>>>>>>>>>>>> File Name:- ibm-ejb-jar-bnd.xmi
>>>>>>>>>>>>> Contents:-
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>> -----------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>>>>>>>>>>>>> xmlns:xmi="http://www.omg.org/XMI"
>>>>>>>>>>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>>>>>>>>>>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="
>>>>>>>>>>>>>
>>>>>>>>>>>> http://www.w3.org/2001/XMLSchema-instance"
>>>>>>>>>
>>>>>>>>>> xmi:id="ejb-jar_ID_Bnd">
>>>>>>>>>>>>>
>>>>>>>>>>>>> <defaultDatasource xmi:id="ResourceRefBinding_1"
>>>>>>>>>>>>> jndiName="ivt">
>>>>>>>>>>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>>>>>>>>>>>>> xmi:id="BasicAuthData_1">
>>>>>>>>>>>>> <userId xsi:nil="true"/>
>>>>>>>>>>>>> <password xsi:nil="true"/>
>>>>>>>>>>>>> </defaultAuth>
>>>>>>>>>>>>> </defaultDatasource>
>>>>>>>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>>>>>>>> <ejbBindings xmi:id="Session_1_Bnd"
>>>>>>>>>>>>> jndiName="ejb/ivtEJBObject">
>>>>>>>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>>>>>>>> </ejbBindings>
>>>>>>>>>>>>> </ejbbnd:EJBJarBinding>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>> ----------------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>> File Name:-ibm-ejb-jar-ext.xmi
>>>>>>>>>>>>> Contents:-
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>> -----------------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>>>>>>>>>>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi"
>>>>>>>>>>>>> xmlns:ejb="ejb.xmi"
>>>>>>>>>>>>> xmi:id="ejb-jar_ID_Ext">
>>>>>>>>>>>>> <ejbExtensions xmi:type="ejbext:SessionExtension"
>>>>>>>>>>>>>
>>>>>>>>>>>> xmi:id="Session_1_Ext"
>>>>>>>>>
>>>>>>>>>> timeout="600">
>>>>>>>>>>>>>
>>>>>>>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>>>>>>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>>>>>>>>>>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>>>>>>>>>>>>> <internationalization xmi:id="BeanInternationalization_1"
>>>>>>>>>>>>> invocationLocale="CALLER"/>
>>>>>>>>>>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>>>>>>>>>>>>> unresolvedAction="ROLLBACK"/>
>>>>>>>>>>>>> </ejbExtensions>
>>>>>>>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>>>>>>>> </ejbext:EJBJarExtension>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>> File Name:- ejb-jar.xml
>>>>>>>>>>>>> Contents:-
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>> -----------------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD
>>>>>
>>>>> Enterprise
>>>>>>>>>>>>>
>>>>>>>>>>>>> JavaBeans 1.1//EN"
>>>>>>>>>>>>> "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd
>>>>>
>>>>> ">
>>>>>>>>>>>>>
>>>>>>>>>>>>> <ejb-jar id="ejb-jar_ID">
>>>>>>>>>>>>> <description>IVT Stateful Session EJB</description>
>>>>>>>>>>>>> <display-name>IVT EJB Module</display-name>
>>>>>>>>>>>>> <enterprise-beans>
>>>>>>>>>>>>> <session id="Session_1">
>>>>>>>>>>>>> <description>Verify Stateful Session EJB</description>
>>>>>>>>>>>>> <display-name>Verification of Stateful Session
>>>>>>>>>>>>> EJB</display-name>
>>>>>>>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>>>>>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>>>>>>>>>>>>>
>>>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>>>>>>>>>>>>> <session-type>Stateful</session-type>
>>>>>>>>>>>>> <transaction-type>Container</transaction-type>
>>>>>>>>>>>>> </session>
>>>>>>>>>>>>> </enterprise-beans>
>>>>>>>>>>>>> <assembly-descriptor id="AssemblyDescriptor_1">
>>>>>>>>>>>>> <container-transaction id="MethodTransaction_1">
>>>>>>>>>>>>> <method id="MethodElement_1">
>>>>>>>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>>>>>>>> <method-name>*</method-name>
>>>>>>>>>>>>> </method>
>>>>>>>>>>>>> <trans-attribute>Never</trans-attribute>
>>>>>>>>>>>>> </container-transaction>
>>>>>>>>>>>>> </assembly-descriptor>
>>>>>>>>>>>>> </ejb-jar>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>> -----------------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Karan Singh Malhi
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Thanks
>>>>>>>>>> - Mohammad Nour
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Thanks
>>>>>>>>> - Mohammad Nour
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Karan Singh Malhi
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Karan Singh Malhi
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Karan Singh Malhi
>>>>
>>>
>>>
>>>
>>> --
>>> Thanks
>>> - Mohammad Nour
>>>
>>
>
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by "Daniel S. Haischt" <da...@googlemail.com>.
basically I would say cause the XSDs are covered by IBM IP and thus
it's prohibited to redistribute them. I discussed that with Mohammad
this afternoon and I am pretty sure that this scenario is covered
by the license terms anyway.
what would have made things worse is that at least I and I think
Mohammad as well got our WAS versions from an IBM internal site
and redistributing files from such a WAS version would have been
probably a disaster in regards of legal policies.
so it's good we discussed this subject before doing anything bad :)
David Blevins wrote:
> On Jun 23, 2008, at 7:21 AM, Mohammad Nour El-Din wrote:
>
>> Well I am not sure if it is legal to send even the names of the files
>> over here, can someone help me and asnwer that question, is it legal
>> to send even the names on that list ?
>
> Sending the names of xsd files is ok, sending the xsd files themselves
> is not.
>
> -David
>
>> On Mon, Jun 23, 2008 at 4:48 PM, Karan Malhi <ka...@gmail.com>
>> wrote:
>>> I have a local WAS 6.1 . I do see the
>>> <<WAS_INSTALL>>/properties/schemas,
>>> but do not see the schemas for the xmi files bundled inside an
>>> ejb-jar. I
>>> would definitely be interested in the schemas, so if you can send
>>> those to
>>> me , that would be great
>>>
>>> On Mon, Jun 23, 2008 at 9:01 AM, Daniel S. Haischt <
>>> daniel.haischt@googlemail.com> wrote:
>>>
>>>> just a suggestion - anyone that is interested in the XSD files should
>>>> reply to this thread.
>>>> Mohammad or I will then provide you with the XSDs for WAS V6.1 by
>>>> sending you a private
>>>> mail having the XSDs attached.
>>>>
>>>> That way you don't need to download and install WAS locally.
>>>>
>>>> On Mon, Jun 23, 2008 at 12:04 AM, Karan Malhi <ka...@gmail.com>
>>>> wrote:
>>>>> Sorry,
>>>>>
>>>>> Obviously didn't realize that . Thanks for catching that :)
>>>>>
>>>>> On Sun, Jun 22, 2008 at 5:05 PM, David Blevins
>>>>> <da...@visi.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> On Jun 22, 2008, at 12:46 PM, Karan Malhi wrote:
>>>>>>
>>>>>> Great,
>>>>>>>
>>>>>>> I have created a Jira issue so that we could share the zip files.
>>>>>>>
>>>>>>> https://issues.apache.org/jira/browse/OPENEJB-830
>>>>>>>
>>>>>>
>>>>>> Just an fyi, we can't publicly redistribute those on apache hardware.
>>>>>>
>>>>>> -David
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> On Sun, Jun 22, 2008 at 2:06 PM, Mohammad Nour El-Din <
>>>>>>> nour.mohammad@gmail.com> wrote:
>>>>>>>
>>>>>>> Hi All...
>>>>>>>>
>>>>>>>> Good news :), I found all the XSDs we need. They are shipped with
>>>>>>>> the WAS installation under <was_home>/properties/schemas directory,
>>>>>>>> all the XSDs we dreamed of, the one for XMI and for all the
>>>>>>>> other WAS
>>>>>>>> specific DDs. I have to go home now, so I will collect them in 1
>>>>>>>> zip
>>>>>>>> file and I will send them on the list tomorrow 23-Jun-2008.
>>>>>>>>
>>>>>>>> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
>>>>>>>> <no...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Thanks Daniel for clarifications. What I am doing now, is to
>>>>>>>>> get the
>>>>>>>>> XMI files referenced inside both the binding and extensions XMI
>>>> files,
>>>>>>>>> which will help us making the corresspodent XSDs. I talked with
>>>>>>>>> Dain
>>>>>>>>> on IRC about that. I just need sometime cause the XMI are located
>>>>>>>>> inside one of the large number pf JARs shipped with WAS.
>>>>>>>>> Expected to
>>>>>>>>> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
>>>>>>>>>
>>>>>>>>> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
>>>>>>>>> <da...@googlemail.com> wrote:
>>>>>>>>>
>>>>>>>>>> a couple of thoughts...
>>>>>>>>>>
>>>>>>>>>> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF,
>>>> MOF
>>>>>>>>>> and XMI. ECore is the Eclipse pendant to MOF. They are both
>>>> completely
>>>>>>>>>> independent efforts. Both could be used as a basis for a
>>>>>>>>>> so-called
>>>>>>>>>> Domain Specific Language (DSL). A kinda one size fits all DSL is
>>>> UML.
>>>>>>>>>> MOF models can be access in Java using the JMI API. ECore
>>>>>>>>>> models can
>>>>>>>>>> be accessed in Java using the EMF programmatic API. Both MOF and
>>>> ECore
>>>>>>>>>> models will be persisted using an instance of XMI.
>>>>>>>>>>
>>>>>>>>>> 2) As David already pointed out, as long as we don't ship
>>>> proprietary
>>>>>>>>>> XSDs and such, we should be fine cause AFAIK even XDoclet and
>>>>>>>>>> other
>>>>>>>>>> tools are supporting proprietary WAS binding files. So why
>>>>>>>>>> shouldn't
>>>>>>>>>> we be allowed to do the same?
>>>>>>>>>>
>>>>>>>>>> 3) Some more docs about the WAS binding files:
>>>>>>>>>>
>>>>>>>>>> ibm-webservicesclient-bnd.xmi:
>>>>>>>>>> ------------------------------
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>> ibm-webservices-bnd.xmi:
>>>>>>>>>> ------------------------
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Application bindings:
>>>>>>>>>> ---------------------
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Karan Malhi wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> oops!
>>>>>>>>>>>
>>>>>>>>>>> I pasted the files for ejb 1.1 . Not sure if something
>>>>>>>>>>> changed for
>>>> ejb
>>>>>>>>>>>
>>>>>>>>>> 2.1
>>>>>>>>
>>>>>>>>> .
>>>>>>>>>>> I think we can ignore the ibm-ejb-ext files for now because they
>>>>>>>>>>>
>>>>>>>>>> contain
>>>>>>>>
>>>>>>>>> ibm
>>>>>>>>>>> extensions. its the ibm-ejb-jar-bnd files which should be of
>>>> interest.
>>>>>>>>>>>
>>>>>>>>>> I
>>>>>>>>
>>>>>>>>> will try and create a more comprehensive file using RAD or AST.
>>>>>>>>> This
>>>>>>>>>>>
>>>>>>>>>> will
>>>>>>>>
>>>>>>>>> contain local, remote ejb references, references to activation
>>>>>>>>> spec
>>>> for
>>>>>>>>>>> mdb,
>>>>>>>>>>> datasource . We could probably use that to generate the schema.
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <
>>>> karan.malhi@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Or if you can grab the xmi files there's probably a way to
>>>>>>>>>>> convert
>>>>>>>>>>>>
>>>>>>>>>>> them
>>>>>>>>
>>>>>>>>> to
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> xsd.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I think this would be the best approach. Since Attachments are
>>>>>>>>>>>> disallowed,
>>>>>>>>>>>> I am giving the file name, its purpose followed by its
>>>>>>>>>>>> contents.
>>>> You
>>>>>>>>>>>> should
>>>>>>>>>>>> be able to create the file on the local system and paste the
>>>> contents
>>>>>>>>>>>>
>>>>>>>>>>> in
>>>>>>>>
>>>>>>>>> it.
>>>>>>>>>>>> Please keep in mind though that these files do not contain all
>>>> info
>>>>>>>>>>>>
>>>>>>>>>>> they
>>>>>>>>
>>>>>>>>> could contain, so generating a schema out of them may not get us a
>>>>>>>>>>>> comprehensive schema. (Actually, I was able to generate a
>>>>>>>>>>>> schema
>>>>>>>>>>>> using
>>>>>>>>>>>>
>>>>>>>>>>> c#
>>>>>>>>
>>>>>>>>> )
>>>>>>>>>>>>
>>>>>>>>>>>> File Name:- ibm-ejb-jar-bnd.xmi
>>>>>>>>>>>> Contents:-
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>> -----------------------------------------------------------------------------
>>>>
>>>>>>>>
>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>>>>>>>>>>>> xmlns:xmi="http://www.omg.org/XMI"
>>>>>>>>>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>>>>>>>>>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="
>>>>>>>>>>>>
>>>>>>>>>>> http://www.w3.org/2001/XMLSchema-instance"
>>>>>>>>
>>>>>>>>> xmi:id="ejb-jar_ID_Bnd">
>>>>>>>>>>>> <defaultDatasource xmi:id="ResourceRefBinding_1"
>>>>>>>>>>>> jndiName="ivt">
>>>>>>>>>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>>>>>>>>>>>> xmi:id="BasicAuthData_1">
>>>>>>>>>>>> <userId xsi:nil="true"/>
>>>>>>>>>>>> <password xsi:nil="true"/>
>>>>>>>>>>>> </defaultAuth>
>>>>>>>>>>>> </defaultDatasource>
>>>>>>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>>>>>>> <ejbBindings xmi:id="Session_1_Bnd"
>>>>>>>>>>>> jndiName="ejb/ivtEJBObject">
>>>>>>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>>>>>>> </ejbBindings>
>>>>>>>>>>>> </ejbbnd:EJBJarBinding>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>> ----------------------------------------------------------------------------------
>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>> File Name:-ibm-ejb-jar-ext.xmi
>>>>>>>>>>>> Contents:-
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>> -----------------------------------------------------------------------------------
>>>>
>>>>>>>>
>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>>>>>>>>>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi"
>>>>>>>>>>>> xmlns:ejb="ejb.xmi"
>>>>>>>>>>>> xmi:id="ejb-jar_ID_Ext">
>>>>>>>>>>>> <ejbExtensions xmi:type="ejbext:SessionExtension"
>>>>>>>>>>>>
>>>>>>>>>>> xmi:id="Session_1_Ext"
>>>>>>>>
>>>>>>>>> timeout="600">
>>>>>>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>>>>>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>>>>>>>>>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>>>>>>>>>>>> <internationalization xmi:id="BeanInternationalization_1"
>>>>>>>>>>>> invocationLocale="CALLER"/>
>>>>>>>>>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>>>>>>>>>>>> unresolvedAction="ROLLBACK"/>
>>>>>>>>>>>> </ejbExtensions>
>>>>>>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>>>>>>> </ejbext:EJBJarExtension>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>> ------------------------------------------------------------------------------------
>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>> File Name:- ejb-jar.xml
>>>>>>>>>>>> Contents:-
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>> -----------------------------------------------------------------------------------
>>>>
>>>>>>>>
>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD
>>>> Enterprise
>>>>>>>>>>>> JavaBeans 1.1//EN"
>>>>>>>>>>>> "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd
>>>> ">
>>>>>>>>>>>>
>>>>>>>>>>>> <ejb-jar id="ejb-jar_ID">
>>>>>>>>>>>> <description>IVT Stateful Session EJB</description>
>>>>>>>>>>>> <display-name>IVT EJB Module</display-name>
>>>>>>>>>>>> <enterprise-beans>
>>>>>>>>>>>> <session id="Session_1">
>>>>>>>>>>>> <description>Verify Stateful Session EJB</description>
>>>>>>>>>>>> <display-name>Verification of Stateful Session
>>>>>>>>>>>> EJB</display-name>
>>>>>>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>>>>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>>>>>>>>>>>>
>>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>>>>>>>>>>>>
>>>>>>>>>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>>>>>>>>>>>>
>>>>>>>>>>>> <session-type>Stateful</session-type>
>>>>>>>>>>>> <transaction-type>Container</transaction-type>
>>>>>>>>>>>> </session>
>>>>>>>>>>>> </enterprise-beans>
>>>>>>>>>>>> <assembly-descriptor id="AssemblyDescriptor_1">
>>>>>>>>>>>> <container-transaction id="MethodTransaction_1">
>>>>>>>>>>>> <method id="MethodElement_1">
>>>>>>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>>>>>>> <method-name>*</method-name>
>>>>>>>>>>>> </method>
>>>>>>>>>>>> <trans-attribute>Never</trans-attribute>
>>>>>>>>>>>> </container-transaction>
>>>>>>>>>>>> </assembly-descriptor>
>>>>>>>>>>>> </ejb-jar>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>> -----------------------------------------------------------------------------------
>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Karan Singh Malhi
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Thanks
>>>>>>>>> - Mohammad Nour
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks
>>>>>>>> - Mohammad Nour
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Karan Singh Malhi
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Karan Singh Malhi
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Karan Singh Malhi
>>>
>>
>>
>>
>> --
>> Thanks
>> - Mohammad Nour
>>
>
Re: websphere descriptors
Posted by David Blevins <da...@visi.com>.
On Jun 23, 2008, at 7:21 AM, Mohammad Nour El-Din wrote:
> Well I am not sure if it is legal to send even the names of the files
> over here, can someone help me and asnwer that question, is it legal
> to send even the names on that list ?
Sending the names of xsd files is ok, sending the xsd files themselves
is not.
-David
> On Mon, Jun 23, 2008 at 4:48 PM, Karan Malhi <ka...@gmail.com>
> wrote:
>> I have a local WAS 6.1 . I do see the <<WAS_INSTALL>>/properties/
>> schemas,
>> but do not see the schemas for the xmi files bundled inside an ejb-
>> jar. I
>> would definitely be interested in the schemas, so if you can send
>> those to
>> me , that would be great
>>
>> On Mon, Jun 23, 2008 at 9:01 AM, Daniel S. Haischt <
>> daniel.haischt@googlemail.com> wrote:
>>
>>> just a suggestion - anyone that is interested in the XSD files
>>> should
>>> reply to this thread.
>>> Mohammad or I will then provide you with the XSDs for WAS V6.1 by
>>> sending you a private
>>> mail having the XSDs attached.
>>>
>>> That way you don't need to download and install WAS locally.
>>>
>>> On Mon, Jun 23, 2008 at 12:04 AM, Karan Malhi
>>> <ka...@gmail.com>
>>> wrote:
>>>> Sorry,
>>>>
>>>> Obviously didn't realize that . Thanks for catching that :)
>>>>
>>>> On Sun, Jun 22, 2008 at 5:05 PM, David Blevins <david.blevins@visi.com
>>>> >
>>>> wrote:
>>>>
>>>>>
>>>>> On Jun 22, 2008, at 12:46 PM, Karan Malhi wrote:
>>>>>
>>>>> Great,
>>>>>>
>>>>>> I have created a Jira issue so that we could share the zip files.
>>>>>>
>>>>>> https://issues.apache.org/jira/browse/OPENEJB-830
>>>>>>
>>>>>
>>>>> Just an fyi, we can't publicly redistribute those on apache
>>>>> hardware.
>>>>>
>>>>> -David
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> On Sun, Jun 22, 2008 at 2:06 PM, Mohammad Nour El-Din <
>>>>>> nour.mohammad@gmail.com> wrote:
>>>>>>
>>>>>> Hi All...
>>>>>>>
>>>>>>> Good news :), I found all the XSDs we need. They are shipped
>>>>>>> with
>>>>>>> the WAS installation under <was_home>/properties/schemas
>>>>>>> directory,
>>>>>>> all the XSDs we dreamed of, the one for XMI and for all the
>>>>>>> other WAS
>>>>>>> specific DDs. I have to go home now, so I will collect them in
>>>>>>> 1 zip
>>>>>>> file and I will send them on the list tomorrow 23-Jun-2008.
>>>>>>>
>>>>>>> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
>>>>>>> <no...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Thanks Daniel for clarifications. What I am doing now, is to
>>>>>>>> get the
>>>>>>>> XMI files referenced inside both the binding and extensions XMI
>>> files,
>>>>>>>> which will help us making the corresspodent XSDs. I talked
>>>>>>>> with Dain
>>>>>>>> on IRC about that. I just need sometime cause the XMI are
>>>>>>>> located
>>>>>>>> inside one of the large number pf JARs shipped with WAS.
>>>>>>>> Expected to
>>>>>>>> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
>>>>>>>>
>>>>>>>> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
>>>>>>>> <da...@googlemail.com> wrote:
>>>>>>>>
>>>>>>>>> a couple of thoughts...
>>>>>>>>>
>>>>>>>>> 1) I think Mohammad kinda mixed up the acronyms soup such as
>>>>>>>>> EMF,
>>> MOF
>>>>>>>>> and XMI. ECore is the Eclipse pendant to MOF. They are both
>>> completely
>>>>>>>>> independent efforts. Both could be used as a basis for a so-
>>>>>>>>> called
>>>>>>>>> Domain Specific Language (DSL). A kinda one size fits all
>>>>>>>>> DSL is
>>> UML.
>>>>>>>>> MOF models can be access in Java using the JMI API. ECore
>>>>>>>>> models can
>>>>>>>>> be accessed in Java using the EMF programmatic API. Both MOF
>>>>>>>>> and
>>> ECore
>>>>>>>>> models will be persisted using an instance of XMI.
>>>>>>>>>
>>>>>>>>> 2) As David already pointed out, as long as we don't ship
>>> proprietary
>>>>>>>>> XSDs and such, we should be fine cause AFAIK even XDoclet
>>>>>>>>> and other
>>>>>>>>> tools are supporting proprietary WAS binding files. So why
>>>>>>>>> shouldn't
>>>>>>>>> we be allowed to do the same?
>>>>>>>>>
>>>>>>>>> 3) Some more docs about the WAS binding files:
>>>>>>>>>
>>>>>>>>> ibm-webservicesclient-bnd.xmi:
>>>>>>>>> ------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>>>>>>>
>>>>>>>>
>>>>>>>>> ibm-webservices-bnd.xmi:
>>>>>>>>> ------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>>>>>>>
>>>>>>>>
>>>>>>>>> Application bindings:
>>>>>>>>> ---------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Karan Malhi wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> oops!
>>>>>>>>>>
>>>>>>>>>> I pasted the files for ejb 1.1 . Not sure if something
>>>>>>>>>> changed for
>>> ejb
>>>>>>>>>>
>>>>>>>>> 2.1
>>>>>>>
>>>>>>>> .
>>>>>>>>>> I think we can ignore the ibm-ejb-ext files for now because
>>>>>>>>>> they
>>>>>>>>>>
>>>>>>>>> contain
>>>>>>>
>>>>>>>> ibm
>>>>>>>>>> extensions. its the ibm-ejb-jar-bnd files which should be of
>>> interest.
>>>>>>>>>>
>>>>>>>>> I
>>>>>>>
>>>>>>>> will try and create a more comprehensive file using RAD or
>>>>>>>> AST. This
>>>>>>>>>>
>>>>>>>>> will
>>>>>>>
>>>>>>>> contain local, remote ejb references, references to
>>>>>>>> activation spec
>>> for
>>>>>>>>>> mdb,
>>>>>>>>>> datasource . We could probably use that to generate the
>>>>>>>>>> schema.
>>>>>>>>>>
>>>>>>>>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <
>>> karan.malhi@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Or if you can grab the xmi files there's probably a way to
>>>>>>>>>> convert
>>>>>>>>>>>
>>>>>>>>>> them
>>>>>>>
>>>>>>>> to
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> xsd.
>>>>>>>>>>>>
>>>>>>>>>>>> I think this would be the best approach. Since
>>>>>>>>>>>> Attachments are
>>>>>>>>>>> disallowed,
>>>>>>>>>>> I am giving the file name, its purpose followed by its
>>>>>>>>>>> contents.
>>> You
>>>>>>>>>>> should
>>>>>>>>>>> be able to create the file on the local system and paste the
>>> contents
>>>>>>>>>>>
>>>>>>>>>> in
>>>>>>>
>>>>>>>> it.
>>>>>>>>>>> Please keep in mind though that these files do not contain
>>>>>>>>>>> all
>>> info
>>>>>>>>>>>
>>>>>>>>>> they
>>>>>>>
>>>>>>>> could contain, so generating a schema out of them may not get
>>>>>>>> us a
>>>>>>>>>>> comprehensive schema. (Actually, I was able to generate a
>>>>>>>>>>> schema
>>>>>>>>>>> using
>>>>>>>>>>>
>>>>>>>>>> c#
>>>>>>>
>>>>>>>> )
>>>>>>>>>>>
>>>>>>>>>>> File Name:- ibm-ejb-jar-bnd.xmi
>>>>>>>>>>> Contents:-
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>> -----------------------------------------------------------------------------
>>>>>>>
>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>>>>>>>>>>> xmlns:xmi="http://www.omg.org/XMI"
>>>>>>>>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>>>>>>>>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="
>>>>>>>>>>>
>>>>>>>>>> http://www.w3.org/2001/XMLSchema-instance"
>>>>>>>
>>>>>>>> xmi:id="ejb-jar_ID_Bnd">
>>>>>>>>>>> <defaultDatasource xmi:id="ResourceRefBinding_1"
>>>>>>>>>>> jndiName="ivt">
>>>>>>>>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>>>>>>>>>>> xmi:id="BasicAuthData_1">
>>>>>>>>>>> <userId xsi:nil="true"/>
>>>>>>>>>>> <password xsi:nil="true"/>
>>>>>>>>>>> </defaultAuth>
>>>>>>>>>>> </defaultDatasource>
>>>>>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>>>>>> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/
>>>>>>>>>>> ivtEJBObject">
>>>>>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>>>>>> </ejbBindings>
>>>>>>>>>>> </ejbbnd:EJBJarBinding>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>> ----------------------------------------------------------------------------------
>>>>>>>
>>>>>>>>
>>>>>>>>>>> File Name:-ibm-ejb-jar-ext.xmi
>>>>>>>>>>> Contents:-
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>> -----------------------------------------------------------------------------------
>>>>>>>
>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>>>>>>>>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi"
>>>>>>>>>>> xmlns:ejb="ejb.xmi"
>>>>>>>>>>> xmi:id="ejb-jar_ID_Ext">
>>>>>>>>>>> <ejbExtensions xmi:type="ejbext:SessionExtension"
>>>>>>>>>>>
>>>>>>>>>> xmi:id="Session_1_Ext"
>>>>>>>
>>>>>>>> timeout="600">
>>>>>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>>>>>> <structure xmi:id="BeanStructure_1"
>>>>>>>>>>> inheritenceRoot="false"/>
>>>>>>>>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>>>>>>>>>>> <internationalization xmi:id="BeanInternationalization_1"
>>>>>>>>>>> invocationLocale="CALLER"/>
>>>>>>>>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>>>>>>>>>>> unresolvedAction="ROLLBACK"/>
>>>>>>>>>>> </ejbExtensions>
>>>>>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>>>>>> </ejbext:EJBJarExtension>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>> ------------------------------------------------------------------------------------
>>>>>>>
>>>>>>>>
>>>>>>>>>>> File Name:- ejb-jar.xml
>>>>>>>>>>> Contents:-
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>> -----------------------------------------------------------------------------------
>>>>>>>
>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD
>>> Enterprise
>>>>>>>>>>> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd
>>> ">
>>>>>>>>>>>
>>>>>>>>>>> <ejb-jar id="ejb-jar_ID">
>>>>>>>>>>> <description>IVT Stateful Session EJB</description>
>>>>>>>>>>> <display-name>IVT EJB Module</display-name>
>>>>>>>>>>> <enterprise-beans>
>>>>>>>>>>> <session id="Session_1">
>>>>>>>>>>> <description>Verify Stateful Session EJB</
>>>>>>>>>>> description>
>>>>>>>>>>> <display-name>Verification of Stateful Session
>>>>>>>>>>> EJB</display-name>
>>>>>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>>>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>>>>>>>>>>>
>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>>>>>>>>>>>
>>>>>>>>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-
>>>>>>>>>>> class>
>>>>>>>>>>> <session-type>Stateful</session-type>
>>>>>>>>>>> <transaction-type>Container</transaction-type>
>>>>>>>>>>> </session>
>>>>>>>>>>> </enterprise-beans>
>>>>>>>>>>> <assembly-descriptor id="AssemblyDescriptor_1">
>>>>>>>>>>> <container-transaction id="MethodTransaction_1">
>>>>>>>>>>> <method id="MethodElement_1">
>>>>>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>>>>>> <method-name>*</method-name>
>>>>>>>>>>> </method>
>>>>>>>>>>> <trans-attribute>Never</trans-attribute>
>>>>>>>>>>> </container-transaction>
>>>>>>>>>>> </assembly-descriptor>
>>>>>>>>>>> </ejb-jar>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>> -----------------------------------------------------------------------------------
>>>>>>>
>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Karan Singh Malhi
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks
>>>>>>>> - Mohammad Nour
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Thanks
>>>>>>> - Mohammad Nour
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Karan Singh Malhi
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Karan Singh Malhi
>>>>
>>>
>>
>>
>>
>> --
>> Karan Singh Malhi
>>
>
>
>
> --
> Thanks
> - Mohammad Nour
>
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Well I am not sure if it is legal to send even the names of the files
over here, can someone help me and asnwer that question, is it legal
to send even the names on that list ?
On Mon, Jun 23, 2008 at 4:48 PM, Karan Malhi <ka...@gmail.com> wrote:
> I have a local WAS 6.1 . I do see the <<WAS_INSTALL>>/properties/schemas,
> but do not see the schemas for the xmi files bundled inside an ejb-jar. I
> would definitely be interested in the schemas, so if you can send those to
> me , that would be great
>
> On Mon, Jun 23, 2008 at 9:01 AM, Daniel S. Haischt <
> daniel.haischt@googlemail.com> wrote:
>
>> just a suggestion - anyone that is interested in the XSD files should
>> reply to this thread.
>> Mohammad or I will then provide you with the XSDs for WAS V6.1 by
>> sending you a private
>> mail having the XSDs attached.
>>
>> That way you don't need to download and install WAS locally.
>>
>> On Mon, Jun 23, 2008 at 12:04 AM, Karan Malhi <ka...@gmail.com>
>> wrote:
>> > Sorry,
>> >
>> > Obviously didn't realize that . Thanks for catching that :)
>> >
>> > On Sun, Jun 22, 2008 at 5:05 PM, David Blevins <da...@visi.com>
>> > wrote:
>> >
>> >>
>> >> On Jun 22, 2008, at 12:46 PM, Karan Malhi wrote:
>> >>
>> >> Great,
>> >>>
>> >>> I have created a Jira issue so that we could share the zip files.
>> >>>
>> >>> https://issues.apache.org/jira/browse/OPENEJB-830
>> >>>
>> >>
>> >> Just an fyi, we can't publicly redistribute those on apache hardware.
>> >>
>> >> -David
>> >>
>> >>
>> >>
>> >>>
>> >>> On Sun, Jun 22, 2008 at 2:06 PM, Mohammad Nour El-Din <
>> >>> nour.mohammad@gmail.com> wrote:
>> >>>
>> >>> Hi All...
>> >>>>
>> >>>> Good news :), I found all the XSDs we need. They are shipped with
>> >>>> the WAS installation under <was_home>/properties/schemas directory,
>> >>>> all the XSDs we dreamed of, the one for XMI and for all the other WAS
>> >>>> specific DDs. I have to go home now, so I will collect them in 1 zip
>> >>>> file and I will send them on the list tomorrow 23-Jun-2008.
>> >>>>
>> >>>> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
>> >>>> <no...@gmail.com> wrote:
>> >>>>
>> >>>>> Thanks Daniel for clarifications. What I am doing now, is to get the
>> >>>>> XMI files referenced inside both the binding and extensions XMI
>> files,
>> >>>>> which will help us making the corresspodent XSDs. I talked with Dain
>> >>>>> on IRC about that. I just need sometime cause the XMI are located
>> >>>>> inside one of the large number pf JARs shipped with WAS. Expected to
>> >>>>> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
>> >>>>>
>> >>>>> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
>> >>>>> <da...@googlemail.com> wrote:
>> >>>>>
>> >>>>>> a couple of thoughts...
>> >>>>>>
>> >>>>>> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF,
>> MOF
>> >>>>>> and XMI. ECore is the Eclipse pendant to MOF. They are both
>> completely
>> >>>>>> independent efforts. Both could be used as a basis for a so-called
>> >>>>>> Domain Specific Language (DSL). A kinda one size fits all DSL is
>> UML.
>> >>>>>> MOF models can be access in Java using the JMI API. ECore models can
>> >>>>>> be accessed in Java using the EMF programmatic API. Both MOF and
>> ECore
>> >>>>>> models will be persisted using an instance of XMI.
>> >>>>>>
>> >>>>>> 2) As David already pointed out, as long as we don't ship
>> proprietary
>> >>>>>> XSDs and such, we should be fine cause AFAIK even XDoclet and other
>> >>>>>> tools are supporting proprietary WAS binding files. So why shouldn't
>> >>>>>> we be allowed to do the same?
>> >>>>>>
>> >>>>>> 3) Some more docs about the WAS binding files:
>> >>>>>>
>> >>>>>> ibm-webservicesclient-bnd.xmi:
>> >>>>>> ------------------------------
>> >>>>>>
>> >>>>>>
>> >>>>
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>> >>>>
>> >>>>>
>> >>>>>> ibm-webservices-bnd.xmi:
>> >>>>>> ------------------------
>> >>>>>>
>> >>>>>>
>> >>>>
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
>> >>>>
>> >>>>>
>> >>>>>>
>> >>>>
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
>> >>>>
>> >>>>>
>> >>>>>>
>> >>>>
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>> >>>>
>> >>>>>
>> >>>>>> Application bindings:
>> >>>>>> ---------------------
>> >>>>>>
>> >>>>>>
>> >>>>
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>> >>>>
>> >>>>>
>> >>>>>>
>> >>>>>> Karan Malhi wrote:
>> >>>>>>
>> >>>>>>>
>> >>>>>>> oops!
>> >>>>>>>
>> >>>>>>> I pasted the files for ejb 1.1 . Not sure if something changed for
>> ejb
>> >>>>>>>
>> >>>>>> 2.1
>> >>>>
>> >>>>> .
>> >>>>>>> I think we can ignore the ibm-ejb-ext files for now because they
>> >>>>>>>
>> >>>>>> contain
>> >>>>
>> >>>>> ibm
>> >>>>>>> extensions. its the ibm-ejb-jar-bnd files which should be of
>> interest.
>> >>>>>>>
>> >>>>>> I
>> >>>>
>> >>>>> will try and create a more comprehensive file using RAD or AST. This
>> >>>>>>>
>> >>>>>> will
>> >>>>
>> >>>>> contain local, remote ejb references, references to activation spec
>> for
>> >>>>>>> mdb,
>> >>>>>>> datasource . We could probably use that to generate the schema.
>> >>>>>>>
>> >>>>>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <
>> karan.malhi@gmail.com>
>> >>>>>>> wrote:
>> >>>>>>>
>> >>>>>>> Or if you can grab the xmi files there's probably a way to convert
>> >>>>>>>>
>> >>>>>>> them
>> >>>>
>> >>>>> to
>> >>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> xsd.
>> >>>>>>>>>
>> >>>>>>>>> I think this would be the best approach. Since Attachments are
>> >>>>>>>> disallowed,
>> >>>>>>>> I am giving the file name, its purpose followed by its contents.
>> You
>> >>>>>>>> should
>> >>>>>>>> be able to create the file on the local system and paste the
>> contents
>> >>>>>>>>
>> >>>>>>> in
>> >>>>
>> >>>>> it.
>> >>>>>>>> Please keep in mind though that these files do not contain all
>> info
>> >>>>>>>>
>> >>>>>>> they
>> >>>>
>> >>>>> could contain, so generating a schema out of them may not get us a
>> >>>>>>>> comprehensive schema. (Actually, I was able to generate a schema
>> >>>>>>>> using
>> >>>>>>>>
>> >>>>>>> c#
>> >>>>
>> >>>>> )
>> >>>>>>>>
>> >>>>>>>> File Name:- ibm-ejb-jar-bnd.xmi
>> >>>>>>>> Contents:-
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> -----------------------------------------------------------------------------
>> >>>>
>> >>>>> <?xml version="1.0" encoding="UTF-8"?>
>> >>>>>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>> >>>>>>>> xmlns:xmi="http://www.omg.org/XMI"
>> >>>>>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>> >>>>>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="
>> >>>>>>>>
>> >>>>>>> http://www.w3.org/2001/XMLSchema-instance"
>> >>>>
>> >>>>> xmi:id="ejb-jar_ID_Bnd">
>> >>>>>>>> <defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
>> >>>>>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>> >>>>>>>> xmi:id="BasicAuthData_1">
>> >>>>>>>> <userId xsi:nil="true"/>
>> >>>>>>>> <password xsi:nil="true"/>
>> >>>>>>>> </defaultAuth>
>> >>>>>>>> </defaultDatasource>
>> >>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>> >>>>>>>> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
>> >>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>> >>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>> >>>>>>>> </ejbBindings>
>> >>>>>>>> </ejbbnd:EJBJarBinding>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> ----------------------------------------------------------------------------------
>> >>>>
>> >>>>>
>> >>>>>>>> File Name:-ibm-ejb-jar-ext.xmi
>> >>>>>>>> Contents:-
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> -----------------------------------------------------------------------------------
>> >>>>
>> >>>>> <?xml version="1.0" encoding="UTF-8"?>
>> >>>>>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>> >>>>>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi"
>> >>>>>>>> xmlns:ejb="ejb.xmi"
>> >>>>>>>> xmi:id="ejb-jar_ID_Ext">
>> >>>>>>>> <ejbExtensions xmi:type="ejbext:SessionExtension"
>> >>>>>>>>
>> >>>>>>> xmi:id="Session_1_Ext"
>> >>>>
>> >>>>> timeout="600">
>> >>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>> >>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>> >>>>>>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>> >>>>>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>> >>>>>>>> <internationalization xmi:id="BeanInternationalization_1"
>> >>>>>>>> invocationLocale="CALLER"/>
>> >>>>>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>> >>>>>>>> unresolvedAction="ROLLBACK"/>
>> >>>>>>>> </ejbExtensions>
>> >>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>> >>>>>>>> </ejbext:EJBJarExtension>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> ------------------------------------------------------------------------------------
>> >>>>
>> >>>>>
>> >>>>>>>> File Name:- ejb-jar.xml
>> >>>>>>>> Contents:-
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> -----------------------------------------------------------------------------------
>> >>>>
>> >>>>> <?xml version="1.0" encoding="UTF-8"?>
>> >>>>>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD
>> Enterprise
>> >>>>>>>> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd
>> ">
>> >>>>>>>>
>> >>>>>>>> <ejb-jar id="ejb-jar_ID">
>> >>>>>>>> <description>IVT Stateful Session EJB</description>
>> >>>>>>>> <display-name>IVT EJB Module</display-name>
>> >>>>>>>> <enterprise-beans>
>> >>>>>>>> <session id="Session_1">
>> >>>>>>>> <description>Verify Stateful Session EJB</description>
>> >>>>>>>> <display-name>Verification of Stateful Session
>> >>>>>>>> EJB</display-name>
>> >>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>> >>>>>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>> >>>>>>>>
>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>> >>>>>>>>
>> >>>>>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>> >>>>>>>> <session-type>Stateful</session-type>
>> >>>>>>>> <transaction-type>Container</transaction-type>
>> >>>>>>>> </session>
>> >>>>>>>> </enterprise-beans>
>> >>>>>>>> <assembly-descriptor id="AssemblyDescriptor_1">
>> >>>>>>>> <container-transaction id="MethodTransaction_1">
>> >>>>>>>> <method id="MethodElement_1">
>> >>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>> >>>>>>>> <method-name>*</method-name>
>> >>>>>>>> </method>
>> >>>>>>>> <trans-attribute>Never</trans-attribute>
>> >>>>>>>> </container-transaction>
>> >>>>>>>> </assembly-descriptor>
>> >>>>>>>> </ejb-jar>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> -----------------------------------------------------------------------------------
>> >>>>
>> >>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> --
>> >>>>>>>> Karan Singh Malhi
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> Thanks
>> >>>>> - Mohammad Nour
>> >>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Thanks
>> >>>> - Mohammad Nour
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> Karan Singh Malhi
>> >>>
>> >>
>> >>
>> >
>> >
>> > --
>> > Karan Singh Malhi
>> >
>>
>
>
>
> --
> Karan Singh Malhi
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by Karan Malhi <ka...@gmail.com>.
I have a local WAS 6.1 . I do see the <<WAS_INSTALL>>/properties/schemas,
but do not see the schemas for the xmi files bundled inside an ejb-jar. I
would definitely be interested in the schemas, so if you can send those to
me , that would be great
On Mon, Jun 23, 2008 at 9:01 AM, Daniel S. Haischt <
daniel.haischt@googlemail.com> wrote:
> just a suggestion - anyone that is interested in the XSD files should
> reply to this thread.
> Mohammad or I will then provide you with the XSDs for WAS V6.1 by
> sending you a private
> mail having the XSDs attached.
>
> That way you don't need to download and install WAS locally.
>
> On Mon, Jun 23, 2008 at 12:04 AM, Karan Malhi <ka...@gmail.com>
> wrote:
> > Sorry,
> >
> > Obviously didn't realize that . Thanks for catching that :)
> >
> > On Sun, Jun 22, 2008 at 5:05 PM, David Blevins <da...@visi.com>
> > wrote:
> >
> >>
> >> On Jun 22, 2008, at 12:46 PM, Karan Malhi wrote:
> >>
> >> Great,
> >>>
> >>> I have created a Jira issue so that we could share the zip files.
> >>>
> >>> https://issues.apache.org/jira/browse/OPENEJB-830
> >>>
> >>
> >> Just an fyi, we can't publicly redistribute those on apache hardware.
> >>
> >> -David
> >>
> >>
> >>
> >>>
> >>> On Sun, Jun 22, 2008 at 2:06 PM, Mohammad Nour El-Din <
> >>> nour.mohammad@gmail.com> wrote:
> >>>
> >>> Hi All...
> >>>>
> >>>> Good news :), I found all the XSDs we need. They are shipped with
> >>>> the WAS installation under <was_home>/properties/schemas directory,
> >>>> all the XSDs we dreamed of, the one for XMI and for all the other WAS
> >>>> specific DDs. I have to go home now, so I will collect them in 1 zip
> >>>> file and I will send them on the list tomorrow 23-Jun-2008.
> >>>>
> >>>> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
> >>>> <no...@gmail.com> wrote:
> >>>>
> >>>>> Thanks Daniel for clarifications. What I am doing now, is to get the
> >>>>> XMI files referenced inside both the binding and extensions XMI
> files,
> >>>>> which will help us making the corresspodent XSDs. I talked with Dain
> >>>>> on IRC about that. I just need sometime cause the XMI are located
> >>>>> inside one of the large number pf JARs shipped with WAS. Expected to
> >>>>> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
> >>>>>
> >>>>> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
> >>>>> <da...@googlemail.com> wrote:
> >>>>>
> >>>>>> a couple of thoughts...
> >>>>>>
> >>>>>> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF,
> MOF
> >>>>>> and XMI. ECore is the Eclipse pendant to MOF. They are both
> completely
> >>>>>> independent efforts. Both could be used as a basis for a so-called
> >>>>>> Domain Specific Language (DSL). A kinda one size fits all DSL is
> UML.
> >>>>>> MOF models can be access in Java using the JMI API. ECore models can
> >>>>>> be accessed in Java using the EMF programmatic API. Both MOF and
> ECore
> >>>>>> models will be persisted using an instance of XMI.
> >>>>>>
> >>>>>> 2) As David already pointed out, as long as we don't ship
> proprietary
> >>>>>> XSDs and such, we should be fine cause AFAIK even XDoclet and other
> >>>>>> tools are supporting proprietary WAS binding files. So why shouldn't
> >>>>>> we be allowed to do the same?
> >>>>>>
> >>>>>> 3) Some more docs about the WAS binding files:
> >>>>>>
> >>>>>> ibm-webservicesclient-bnd.xmi:
> >>>>>> ------------------------------
> >>>>>>
> >>>>>>
> >>>>
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
> >>>>
> >>>>>
> >>>>>> ibm-webservices-bnd.xmi:
> >>>>>> ------------------------
> >>>>>>
> >>>>>>
> >>>>
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
> >>>>
> >>>>>
> >>>>>>
> >>>>
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
> >>>>
> >>>>>
> >>>>>>
> >>>>
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
> >>>>
> >>>>>
> >>>>>> Application bindings:
> >>>>>> ---------------------
> >>>>>>
> >>>>>>
> >>>>
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
> >>>>
> >>>>>
> >>>>>>
> >>>>>> Karan Malhi wrote:
> >>>>>>
> >>>>>>>
> >>>>>>> oops!
> >>>>>>>
> >>>>>>> I pasted the files for ejb 1.1 . Not sure if something changed for
> ejb
> >>>>>>>
> >>>>>> 2.1
> >>>>
> >>>>> .
> >>>>>>> I think we can ignore the ibm-ejb-ext files for now because they
> >>>>>>>
> >>>>>> contain
> >>>>
> >>>>> ibm
> >>>>>>> extensions. its the ibm-ejb-jar-bnd files which should be of
> interest.
> >>>>>>>
> >>>>>> I
> >>>>
> >>>>> will try and create a more comprehensive file using RAD or AST. This
> >>>>>>>
> >>>>>> will
> >>>>
> >>>>> contain local, remote ejb references, references to activation spec
> for
> >>>>>>> mdb,
> >>>>>>> datasource . We could probably use that to generate the schema.
> >>>>>>>
> >>>>>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <
> karan.malhi@gmail.com>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>> Or if you can grab the xmi files there's probably a way to convert
> >>>>>>>>
> >>>>>>> them
> >>>>
> >>>>> to
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> xsd.
> >>>>>>>>>
> >>>>>>>>> I think this would be the best approach. Since Attachments are
> >>>>>>>> disallowed,
> >>>>>>>> I am giving the file name, its purpose followed by its contents.
> You
> >>>>>>>> should
> >>>>>>>> be able to create the file on the local system and paste the
> contents
> >>>>>>>>
> >>>>>>> in
> >>>>
> >>>>> it.
> >>>>>>>> Please keep in mind though that these files do not contain all
> info
> >>>>>>>>
> >>>>>>> they
> >>>>
> >>>>> could contain, so generating a schema out of them may not get us a
> >>>>>>>> comprehensive schema. (Actually, I was able to generate a schema
> >>>>>>>> using
> >>>>>>>>
> >>>>>>> c#
> >>>>
> >>>>> )
> >>>>>>>>
> >>>>>>>> File Name:- ibm-ejb-jar-bnd.xmi
> >>>>>>>> Contents:-
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> -----------------------------------------------------------------------------
> >>>>
> >>>>> <?xml version="1.0" encoding="UTF-8"?>
> >>>>>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
> >>>>>>>> xmlns:xmi="http://www.omg.org/XMI"
> >>>>>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
> >>>>>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="
> >>>>>>>>
> >>>>>>> http://www.w3.org/2001/XMLSchema-instance"
> >>>>
> >>>>> xmi:id="ejb-jar_ID_Bnd">
> >>>>>>>> <defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
> >>>>>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
> >>>>>>>> xmi:id="BasicAuthData_1">
> >>>>>>>> <userId xsi:nil="true"/>
> >>>>>>>> <password xsi:nil="true"/>
> >>>>>>>> </defaultAuth>
> >>>>>>>> </defaultDatasource>
> >>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
> >>>>>>>> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
> >>>>>>>> <enterpriseBean xmi:type="ejb:Session"
> >>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
> >>>>>>>> </ejbBindings>
> >>>>>>>> </ejbbnd:EJBJarBinding>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> ----------------------------------------------------------------------------------
> >>>>
> >>>>>
> >>>>>>>> File Name:-ibm-ejb-jar-ext.xmi
> >>>>>>>> Contents:-
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> -----------------------------------------------------------------------------------
> >>>>
> >>>>> <?xml version="1.0" encoding="UTF-8"?>
> >>>>>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
> >>>>>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi"
> >>>>>>>> xmlns:ejb="ejb.xmi"
> >>>>>>>> xmi:id="ejb-jar_ID_Ext">
> >>>>>>>> <ejbExtensions xmi:type="ejbext:SessionExtension"
> >>>>>>>>
> >>>>>>> xmi:id="Session_1_Ext"
> >>>>
> >>>>> timeout="600">
> >>>>>>>> <enterpriseBean xmi:type="ejb:Session"
> >>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
> >>>>>>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
> >>>>>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
> >>>>>>>> <internationalization xmi:id="BeanInternationalization_1"
> >>>>>>>> invocationLocale="CALLER"/>
> >>>>>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
> >>>>>>>> unresolvedAction="ROLLBACK"/>
> >>>>>>>> </ejbExtensions>
> >>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
> >>>>>>>> </ejbext:EJBJarExtension>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> ------------------------------------------------------------------------------------
> >>>>
> >>>>>
> >>>>>>>> File Name:- ejb-jar.xml
> >>>>>>>> Contents:-
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> -----------------------------------------------------------------------------------
> >>>>
> >>>>> <?xml version="1.0" encoding="UTF-8"?>
> >>>>>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD
> Enterprise
> >>>>>>>> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd
> ">
> >>>>>>>>
> >>>>>>>> <ejb-jar id="ejb-jar_ID">
> >>>>>>>> <description>IVT Stateful Session EJB</description>
> >>>>>>>> <display-name>IVT EJB Module</display-name>
> >>>>>>>> <enterprise-beans>
> >>>>>>>> <session id="Session_1">
> >>>>>>>> <description>Verify Stateful Session EJB</description>
> >>>>>>>> <display-name>Verification of Stateful Session
> >>>>>>>> EJB</display-name>
> >>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
> >>>>>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
> >>>>>>>>
> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
> >>>>>>>>
> >>>>>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
> >>>>>>>> <session-type>Stateful</session-type>
> >>>>>>>> <transaction-type>Container</transaction-type>
> >>>>>>>> </session>
> >>>>>>>> </enterprise-beans>
> >>>>>>>> <assembly-descriptor id="AssemblyDescriptor_1">
> >>>>>>>> <container-transaction id="MethodTransaction_1">
> >>>>>>>> <method id="MethodElement_1">
> >>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
> >>>>>>>> <method-name>*</method-name>
> >>>>>>>> </method>
> >>>>>>>> <trans-attribute>Never</trans-attribute>
> >>>>>>>> </container-transaction>
> >>>>>>>> </assembly-descriptor>
> >>>>>>>> </ejb-jar>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> -----------------------------------------------------------------------------------
> >>>>
> >>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Karan Singh Malhi
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Thanks
> >>>>> - Mohammad Nour
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Thanks
> >>>> - Mohammad Nour
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Karan Singh Malhi
> >>>
> >>
> >>
> >
> >
> > --
> > Karan Singh Malhi
> >
>
--
Karan Singh Malhi
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
David Blevins already got WAS installed and he will use the XSDs found
in the location I've sent b4.
On Mon, Jun 23, 2008 at 4:01 PM, Daniel S. Haischt
<da...@googlemail.com> wrote:
> just a suggestion - anyone that is interested in the XSD files should
> reply to this thread.
> Mohammad or I will then provide you with the XSDs for WAS V6.1 by
> sending you a private
> mail having the XSDs attached.
>
> That way you don't need to download and install WAS locally.
>
> On Mon, Jun 23, 2008 at 12:04 AM, Karan Malhi <ka...@gmail.com> wrote:
>> Sorry,
>>
>> Obviously didn't realize that . Thanks for catching that :)
>>
>> On Sun, Jun 22, 2008 at 5:05 PM, David Blevins <da...@visi.com>
>> wrote:
>>
>>>
>>> On Jun 22, 2008, at 12:46 PM, Karan Malhi wrote:
>>>
>>> Great,
>>>>
>>>> I have created a Jira issue so that we could share the zip files.
>>>>
>>>> https://issues.apache.org/jira/browse/OPENEJB-830
>>>>
>>>
>>> Just an fyi, we can't publicly redistribute those on apache hardware.
>>>
>>> -David
>>>
>>>
>>>
>>>>
>>>> On Sun, Jun 22, 2008 at 2:06 PM, Mohammad Nour El-Din <
>>>> nour.mohammad@gmail.com> wrote:
>>>>
>>>> Hi All...
>>>>>
>>>>> Good news :), I found all the XSDs we need. They are shipped with
>>>>> the WAS installation under <was_home>/properties/schemas directory,
>>>>> all the XSDs we dreamed of, the one for XMI and for all the other WAS
>>>>> specific DDs. I have to go home now, so I will collect them in 1 zip
>>>>> file and I will send them on the list tomorrow 23-Jun-2008.
>>>>>
>>>>> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
>>>>> <no...@gmail.com> wrote:
>>>>>
>>>>>> Thanks Daniel for clarifications. What I am doing now, is to get the
>>>>>> XMI files referenced inside both the binding and extensions XMI files,
>>>>>> which will help us making the corresspodent XSDs. I talked with Dain
>>>>>> on IRC about that. I just need sometime cause the XMI are located
>>>>>> inside one of the large number pf JARs shipped with WAS. Expected to
>>>>>> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
>>>>>>
>>>>>> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
>>>>>> <da...@googlemail.com> wrote:
>>>>>>
>>>>>>> a couple of thoughts...
>>>>>>>
>>>>>>> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF, MOF
>>>>>>> and XMI. ECore is the Eclipse pendant to MOF. They are both completely
>>>>>>> independent efforts. Both could be used as a basis for a so-called
>>>>>>> Domain Specific Language (DSL). A kinda one size fits all DSL is UML.
>>>>>>> MOF models can be access in Java using the JMI API. ECore models can
>>>>>>> be accessed in Java using the EMF programmatic API. Both MOF and ECore
>>>>>>> models will be persisted using an instance of XMI.
>>>>>>>
>>>>>>> 2) As David already pointed out, as long as we don't ship proprietary
>>>>>>> XSDs and such, we should be fine cause AFAIK even XDoclet and other
>>>>>>> tools are supporting proprietary WAS binding files. So why shouldn't
>>>>>>> we be allowed to do the same?
>>>>>>>
>>>>>>> 3) Some more docs about the WAS binding files:
>>>>>>>
>>>>>>> ibm-webservicesclient-bnd.xmi:
>>>>>>> ------------------------------
>>>>>>>
>>>>>>>
>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>>>>>
>>>>>>
>>>>>>> ibm-webservices-bnd.xmi:
>>>>>>> ------------------------
>>>>>>>
>>>>>>>
>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
>>>>>
>>>>>>
>>>>>>>
>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
>>>>>
>>>>>>
>>>>>>>
>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>>>>>
>>>>>>
>>>>>>> Application bindings:
>>>>>>> ---------------------
>>>>>>>
>>>>>>>
>>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>>>>>
>>>>>>
>>>>>>>
>>>>>>> Karan Malhi wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> oops!
>>>>>>>>
>>>>>>>> I pasted the files for ejb 1.1 . Not sure if something changed for ejb
>>>>>>>>
>>>>>>> 2.1
>>>>>
>>>>>> .
>>>>>>>> I think we can ignore the ibm-ejb-ext files for now because they
>>>>>>>>
>>>>>>> contain
>>>>>
>>>>>> ibm
>>>>>>>> extensions. its the ibm-ejb-jar-bnd files which should be of interest.
>>>>>>>>
>>>>>>> I
>>>>>
>>>>>> will try and create a more comprehensive file using RAD or AST. This
>>>>>>>>
>>>>>>> will
>>>>>
>>>>>> contain local, remote ejb references, references to activation spec for
>>>>>>>> mdb,
>>>>>>>> datasource . We could probably use that to generate the schema.
>>>>>>>>
>>>>>>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <ka...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Or if you can grab the xmi files there's probably a way to convert
>>>>>>>>>
>>>>>>>> them
>>>>>
>>>>>> to
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> xsd.
>>>>>>>>>>
>>>>>>>>>> I think this would be the best approach. Since Attachments are
>>>>>>>>> disallowed,
>>>>>>>>> I am giving the file name, its purpose followed by its contents. You
>>>>>>>>> should
>>>>>>>>> be able to create the file on the local system and paste the contents
>>>>>>>>>
>>>>>>>> in
>>>>>
>>>>>> it.
>>>>>>>>> Please keep in mind though that these files do not contain all info
>>>>>>>>>
>>>>>>>> they
>>>>>
>>>>>> could contain, so generating a schema out of them may not get us a
>>>>>>>>> comprehensive schema. (Actually, I was able to generate a schema
>>>>>>>>> using
>>>>>>>>>
>>>>>>>> c#
>>>>>
>>>>>> )
>>>>>>>>>
>>>>>>>>> File Name:- ibm-ejb-jar-bnd.xmi
>>>>>>>>> Contents:-
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -----------------------------------------------------------------------------
>>>>>
>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>>>>>>>>> xmlns:xmi="http://www.omg.org/XMI"
>>>>>>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>>>>>>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="
>>>>>>>>>
>>>>>>>> http://www.w3.org/2001/XMLSchema-instance"
>>>>>
>>>>>> xmi:id="ejb-jar_ID_Bnd">
>>>>>>>>> <defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
>>>>>>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>>>>>>>>> xmi:id="BasicAuthData_1">
>>>>>>>>> <userId xsi:nil="true"/>
>>>>>>>>> <password xsi:nil="true"/>
>>>>>>>>> </defaultAuth>
>>>>>>>>> </defaultDatasource>
>>>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>>>> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
>>>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>>>> </ejbBindings>
>>>>>>>>> </ejbbnd:EJBJarBinding>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ----------------------------------------------------------------------------------
>>>>>
>>>>>>
>>>>>>>>> File Name:-ibm-ejb-jar-ext.xmi
>>>>>>>>> Contents:-
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -----------------------------------------------------------------------------------
>>>>>
>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>>>>>>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi"
>>>>>>>>> xmlns:ejb="ejb.xmi"
>>>>>>>>> xmi:id="ejb-jar_ID_Ext">
>>>>>>>>> <ejbExtensions xmi:type="ejbext:SessionExtension"
>>>>>>>>>
>>>>>>>> xmi:id="Session_1_Ext"
>>>>>
>>>>>> timeout="600">
>>>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>>>>>>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>>>>>>>>> <internationalization xmi:id="BeanInternationalization_1"
>>>>>>>>> invocationLocale="CALLER"/>
>>>>>>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>>>>>>>>> unresolvedAction="ROLLBACK"/>
>>>>>>>>> </ejbExtensions>
>>>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>>>> </ejbext:EJBJarExtension>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------------
>>>>>
>>>>>>
>>>>>>>>> File Name:- ejb-jar.xml
>>>>>>>>> Contents:-
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -----------------------------------------------------------------------------------
>>>>>
>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
>>>>>>>>> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
>>>>>>>>>
>>>>>>>>> <ejb-jar id="ejb-jar_ID">
>>>>>>>>> <description>IVT Stateful Session EJB</description>
>>>>>>>>> <display-name>IVT EJB Module</display-name>
>>>>>>>>> <enterprise-beans>
>>>>>>>>> <session id="Session_1">
>>>>>>>>> <description>Verify Stateful Session EJB</description>
>>>>>>>>> <display-name>Verification of Stateful Session
>>>>>>>>> EJB</display-name>
>>>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>>>>>>>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>>>>>>>>>
>>>>>>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>>>>>>>>> <session-type>Stateful</session-type>
>>>>>>>>> <transaction-type>Container</transaction-type>
>>>>>>>>> </session>
>>>>>>>>> </enterprise-beans>
>>>>>>>>> <assembly-descriptor id="AssemblyDescriptor_1">
>>>>>>>>> <container-transaction id="MethodTransaction_1">
>>>>>>>>> <method id="MethodElement_1">
>>>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>>>> <method-name>*</method-name>
>>>>>>>>> </method>
>>>>>>>>> <trans-attribute>Never</trans-attribute>
>>>>>>>>> </container-transaction>
>>>>>>>>> </assembly-descriptor>
>>>>>>>>> </ejb-jar>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -----------------------------------------------------------------------------------
>>>>>
>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Karan Singh Malhi
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thanks
>>>>>> - Mohammad Nour
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Thanks
>>>>> - Mohammad Nour
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Karan Singh Malhi
>>>>
>>>
>>>
>>
>>
>> --
>> Karan Singh Malhi
>>
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by "Daniel S. Haischt" <da...@googlemail.com>.
AFAIK attachments will be stripped from mails by the mailing list
management software...
Mohammad Nour El-Din wrote:
> Hi All...
>
> Good news :), I found all the XSDs we need. They are shipped with
> the WAS installation under <was_home>/properties/schemas directory,
> all the XSDs we dreamed of, the one for XMI and for all the other WAS
> specific DDs. I have to go home now, so I will collect them in 1 zip
> file and I will send them on the list tomorrow 23-Jun-2008.
>
> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
> <no...@gmail.com> wrote:
>> Thanks Daniel for clarifications. What I am doing now, is to get the
>> XMI files referenced inside both the binding and extensions XMI files,
>> which will help us making the corresspodent XSDs. I talked with Dain
>> on IRC about that. I just need sometime cause the XMI are located
>> inside one of the large number pf JARs shipped with WAS. Expected to
>> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
>>
>> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
>> <da...@googlemail.com> wrote:
>>> a couple of thoughts...
>>>
>>> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF, MOF
>>> and XMI. ECore is the Eclipse pendant to MOF. They are both completely
>>> independent efforts. Both could be used as a basis for a so-called
>>> Domain Specific Language (DSL). A kinda one size fits all DSL is UML.
>>> MOF models can be access in Java using the JMI API. ECore models can
>>> be accessed in Java using the EMF programmatic API. Both MOF and ECore
>>> models will be persisted using an instance of XMI.
>>>
>>> 2) As David already pointed out, as long as we don't ship proprietary
>>> XSDs and such, we should be fine cause AFAIK even XDoclet and other
>>> tools are supporting proprietary WAS binding files. So why shouldn't
>>> we be allowed to do the same?
>>>
>>> 3) Some more docs about the WAS binding files:
>>>
>>> ibm-webservicesclient-bnd.xmi:
>>> ------------------------------
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>>>
>>> ibm-webservices-bnd.xmi:
>>> ------------------------
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>>>
>>> Application bindings:
>>> ---------------------
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>>>
>>>
>>> Karan Malhi wrote:
>>>> oops!
>>>>
>>>> I pasted the files for ejb 1.1 . Not sure if something changed for ejb 2.1
>>>> .
>>>> I think we can ignore the ibm-ejb-ext files for now because they contain
>>>> ibm
>>>> extensions. its the ibm-ejb-jar-bnd files which should be of interest. I
>>>> will try and create a more comprehensive file using RAD or AST. This will
>>>> contain local, remote ejb references, references to activation spec for
>>>> mdb,
>>>> datasource . We could probably use that to generate the schema.
>>>>
>>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <ka...@gmail.com>
>>>> wrote:
>>>>
>>>>> Or if you can grab the xmi files there's probably a way to convert them
>>>>> to
>>>>>> xsd.
>>>>>>
>>>>> I think this would be the best approach. Since Attachments are
>>>>> disallowed,
>>>>> I am giving the file name, its purpose followed by its contents. You
>>>>> should
>>>>> be able to create the file on the local system and paste the contents in
>>>>> it.
>>>>> Please keep in mind though that these files do not contain all info they
>>>>> could contain, so generating a schema out of them may not get us a
>>>>> comprehensive schema. (Actually, I was able to generate a schema using c#
>>>>> )
>>>>>
>>>>> File Name:- ibm-ejb-jar-bnd.xmi
>>>>> Contents:-
>>>>>
>>>>>
>>>>> -----------------------------------------------------------------------------
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>>>>> xmlns:xmi="http://www.omg.org/XMI"
>>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>>> xmi:id="ejb-jar_ID_Bnd">
>>>>> <defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
>>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>>>>> xmi:id="BasicAuthData_1">
>>>>> <userId xsi:nil="true"/>
>>>>> <password xsi:nil="true"/>
>>>>> </defaultAuth>
>>>>> </defaultDatasource>
>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>> </ejbBindings>
>>>>> </ejbbnd:EJBJarBinding>
>>>>>
>>>>>
>>>>> ----------------------------------------------------------------------------------
>>>>>
>>>>> File Name:-ibm-ejb-jar-ext.xmi
>>>>> Contents:-
>>>>>
>>>>>
>>>>> -----------------------------------------------------------------------------------
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi" xmlns:ejb="ejb.xmi"
>>>>> xmi:id="ejb-jar_ID_Ext">
>>>>> <ejbExtensions xmi:type="ejbext:SessionExtension" xmi:id="Session_1_Ext"
>>>>> timeout="600">
>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>>>>> <internationalization xmi:id="BeanInternationalization_1"
>>>>> invocationLocale="CALLER"/>
>>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>>>>> unresolvedAction="ROLLBACK"/>
>>>>> </ejbExtensions>
>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>> </ejbext:EJBJarExtension>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------------
>>>>>
>>>>> File Name:- ejb-jar.xml
>>>>> Contents:-
>>>>>
>>>>>
>>>>> -----------------------------------------------------------------------------------
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
>>>>> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
>>>>>
>>>>> <ejb-jar id="ejb-jar_ID">
>>>>> <description>IVT Stateful Session EJB</description>
>>>>> <display-name>IVT EJB Module</display-name>
>>>>> <enterprise-beans>
>>>>> <session id="Session_1">
>>>>> <description>Verify Stateful Session EJB</description>
>>>>> <display-name>Verification of Stateful Session
>>>>> EJB</display-name>
>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>>>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>>>>>
>>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>>>>> <session-type>Stateful</session-type>
>>>>> <transaction-type>Container</transaction-type>
>>>>> </session>
>>>>> </enterprise-beans>
>>>>> <assembly-descriptor id="AssemblyDescriptor_1">
>>>>> <container-transaction id="MethodTransaction_1">
>>>>> <method id="MethodElement_1">
>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>> <method-name>*</method-name>
>>>>> </method>
>>>>> <trans-attribute>Never</trans-attribute>
>>>>> </container-transaction>
>>>>> </assembly-descriptor>
>>>>> </ejb-jar>
>>>>>
>>>>>
>>>>>
>>>>> -----------------------------------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Karan Singh Malhi
>>>>
>>>>
>>>>
>>>
>>
>>
>> --
>> Thanks
>> - Mohammad Nour
>>
>
>
>
Re: websphere descriptors
Posted by "Daniel S. Haischt" <da...@googlemail.com>.
just a suggestion - anyone that is interested in the XSD files should
reply to this thread.
Mohammad or I will then provide you with the XSDs for WAS V6.1 by
sending you a private
mail having the XSDs attached.
That way you don't need to download and install WAS locally.
On Mon, Jun 23, 2008 at 12:04 AM, Karan Malhi <ka...@gmail.com> wrote:
> Sorry,
>
> Obviously didn't realize that . Thanks for catching that :)
>
> On Sun, Jun 22, 2008 at 5:05 PM, David Blevins <da...@visi.com>
> wrote:
>
>>
>> On Jun 22, 2008, at 12:46 PM, Karan Malhi wrote:
>>
>> Great,
>>>
>>> I have created a Jira issue so that we could share the zip files.
>>>
>>> https://issues.apache.org/jira/browse/OPENEJB-830
>>>
>>
>> Just an fyi, we can't publicly redistribute those on apache hardware.
>>
>> -David
>>
>>
>>
>>>
>>> On Sun, Jun 22, 2008 at 2:06 PM, Mohammad Nour El-Din <
>>> nour.mohammad@gmail.com> wrote:
>>>
>>> Hi All...
>>>>
>>>> Good news :), I found all the XSDs we need. They are shipped with
>>>> the WAS installation under <was_home>/properties/schemas directory,
>>>> all the XSDs we dreamed of, the one for XMI and for all the other WAS
>>>> specific DDs. I have to go home now, so I will collect them in 1 zip
>>>> file and I will send them on the list tomorrow 23-Jun-2008.
>>>>
>>>> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
>>>> <no...@gmail.com> wrote:
>>>>
>>>>> Thanks Daniel for clarifications. What I am doing now, is to get the
>>>>> XMI files referenced inside both the binding and extensions XMI files,
>>>>> which will help us making the corresspodent XSDs. I talked with Dain
>>>>> on IRC about that. I just need sometime cause the XMI are located
>>>>> inside one of the large number pf JARs shipped with WAS. Expected to
>>>>> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
>>>>>
>>>>> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
>>>>> <da...@googlemail.com> wrote:
>>>>>
>>>>>> a couple of thoughts...
>>>>>>
>>>>>> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF, MOF
>>>>>> and XMI. ECore is the Eclipse pendant to MOF. They are both completely
>>>>>> independent efforts. Both could be used as a basis for a so-called
>>>>>> Domain Specific Language (DSL). A kinda one size fits all DSL is UML.
>>>>>> MOF models can be access in Java using the JMI API. ECore models can
>>>>>> be accessed in Java using the EMF programmatic API. Both MOF and ECore
>>>>>> models will be persisted using an instance of XMI.
>>>>>>
>>>>>> 2) As David already pointed out, as long as we don't ship proprietary
>>>>>> XSDs and such, we should be fine cause AFAIK even XDoclet and other
>>>>>> tools are supporting proprietary WAS binding files. So why shouldn't
>>>>>> we be allowed to do the same?
>>>>>>
>>>>>> 3) Some more docs about the WAS binding files:
>>>>>>
>>>>>> ibm-webservicesclient-bnd.xmi:
>>>>>> ------------------------------
>>>>>>
>>>>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>>>>
>>>>>
>>>>>> ibm-webservices-bnd.xmi:
>>>>>> ------------------------
>>>>>>
>>>>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
>>>>
>>>>>
>>>>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
>>>>
>>>>>
>>>>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>>>>
>>>>>
>>>>>> Application bindings:
>>>>>> ---------------------
>>>>>>
>>>>>>
>>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>>>>
>>>>>
>>>>>>
>>>>>> Karan Malhi wrote:
>>>>>>
>>>>>>>
>>>>>>> oops!
>>>>>>>
>>>>>>> I pasted the files for ejb 1.1 . Not sure if something changed for ejb
>>>>>>>
>>>>>> 2.1
>>>>
>>>>> .
>>>>>>> I think we can ignore the ibm-ejb-ext files for now because they
>>>>>>>
>>>>>> contain
>>>>
>>>>> ibm
>>>>>>> extensions. its the ibm-ejb-jar-bnd files which should be of interest.
>>>>>>>
>>>>>> I
>>>>
>>>>> will try and create a more comprehensive file using RAD or AST. This
>>>>>>>
>>>>>> will
>>>>
>>>>> contain local, remote ejb references, references to activation spec for
>>>>>>> mdb,
>>>>>>> datasource . We could probably use that to generate the schema.
>>>>>>>
>>>>>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <ka...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Or if you can grab the xmi files there's probably a way to convert
>>>>>>>>
>>>>>>> them
>>>>
>>>>> to
>>>>>>>>
>>>>>>>>>
>>>>>>>>> xsd.
>>>>>>>>>
>>>>>>>>> I think this would be the best approach. Since Attachments are
>>>>>>>> disallowed,
>>>>>>>> I am giving the file name, its purpose followed by its contents. You
>>>>>>>> should
>>>>>>>> be able to create the file on the local system and paste the contents
>>>>>>>>
>>>>>>> in
>>>>
>>>>> it.
>>>>>>>> Please keep in mind though that these files do not contain all info
>>>>>>>>
>>>>>>> they
>>>>
>>>>> could contain, so generating a schema out of them may not get us a
>>>>>>>> comprehensive schema. (Actually, I was able to generate a schema
>>>>>>>> using
>>>>>>>>
>>>>>>> c#
>>>>
>>>>> )
>>>>>>>>
>>>>>>>> File Name:- ibm-ejb-jar-bnd.xmi
>>>>>>>> Contents:-
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -----------------------------------------------------------------------------
>>>>
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>>>>>>>> xmlns:xmi="http://www.omg.org/XMI"
>>>>>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>>>>>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="
>>>>>>>>
>>>>>>> http://www.w3.org/2001/XMLSchema-instance"
>>>>
>>>>> xmi:id="ejb-jar_ID_Bnd">
>>>>>>>> <defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
>>>>>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>>>>>>>> xmi:id="BasicAuthData_1">
>>>>>>>> <userId xsi:nil="true"/>
>>>>>>>> <password xsi:nil="true"/>
>>>>>>>> </defaultAuth>
>>>>>>>> </defaultDatasource>
>>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>>> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
>>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>>> </ejbBindings>
>>>>>>>> </ejbbnd:EJBJarBinding>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ----------------------------------------------------------------------------------
>>>>
>>>>>
>>>>>>>> File Name:-ibm-ejb-jar-ext.xmi
>>>>>>>> Contents:-
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -----------------------------------------------------------------------------------
>>>>
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>>>>>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi"
>>>>>>>> xmlns:ejb="ejb.xmi"
>>>>>>>> xmi:id="ejb-jar_ID_Ext">
>>>>>>>> <ejbExtensions xmi:type="ejbext:SessionExtension"
>>>>>>>>
>>>>>>> xmi:id="Session_1_Ext"
>>>>
>>>>> timeout="600">
>>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>>>>>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>>>>>>>> <internationalization xmi:id="BeanInternationalization_1"
>>>>>>>> invocationLocale="CALLER"/>
>>>>>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>>>>>>>> unresolvedAction="ROLLBACK"/>
>>>>>>>> </ejbExtensions>
>>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>>> </ejbext:EJBJarExtension>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------------
>>>>
>>>>>
>>>>>>>> File Name:- ejb-jar.xml
>>>>>>>> Contents:-
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -----------------------------------------------------------------------------------
>>>>
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
>>>>>>>> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
>>>>>>>>
>>>>>>>> <ejb-jar id="ejb-jar_ID">
>>>>>>>> <description>IVT Stateful Session EJB</description>
>>>>>>>> <display-name>IVT EJB Module</display-name>
>>>>>>>> <enterprise-beans>
>>>>>>>> <session id="Session_1">
>>>>>>>> <description>Verify Stateful Session EJB</description>
>>>>>>>> <display-name>Verification of Stateful Session
>>>>>>>> EJB</display-name>
>>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>>>>>>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>>>>>>>>
>>>>>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>>>>>>>> <session-type>Stateful</session-type>
>>>>>>>> <transaction-type>Container</transaction-type>
>>>>>>>> </session>
>>>>>>>> </enterprise-beans>
>>>>>>>> <assembly-descriptor id="AssemblyDescriptor_1">
>>>>>>>> <container-transaction id="MethodTransaction_1">
>>>>>>>> <method id="MethodElement_1">
>>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>>> <method-name>*</method-name>
>>>>>>>> </method>
>>>>>>>> <trans-attribute>Never</trans-attribute>
>>>>>>>> </container-transaction>
>>>>>>>> </assembly-descriptor>
>>>>>>>> </ejb-jar>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -----------------------------------------------------------------------------------
>>>>
>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Karan Singh Malhi
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Thanks
>>>>> - Mohammad Nour
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks
>>>> - Mohammad Nour
>>>>
>>>>
>>>
>>>
>>> --
>>> Karan Singh Malhi
>>>
>>
>>
>
>
> --
> Karan Singh Malhi
>
Re: websphere descriptors
Posted by Karan Malhi <ka...@gmail.com>.
Sorry,
Obviously didn't realize that . Thanks for catching that :)
On Sun, Jun 22, 2008 at 5:05 PM, David Blevins <da...@visi.com>
wrote:
>
> On Jun 22, 2008, at 12:46 PM, Karan Malhi wrote:
>
> Great,
>>
>> I have created a Jira issue so that we could share the zip files.
>>
>> https://issues.apache.org/jira/browse/OPENEJB-830
>>
>
> Just an fyi, we can't publicly redistribute those on apache hardware.
>
> -David
>
>
>
>>
>> On Sun, Jun 22, 2008 at 2:06 PM, Mohammad Nour El-Din <
>> nour.mohammad@gmail.com> wrote:
>>
>> Hi All...
>>>
>>> Good news :), I found all the XSDs we need. They are shipped with
>>> the WAS installation under <was_home>/properties/schemas directory,
>>> all the XSDs we dreamed of, the one for XMI and for all the other WAS
>>> specific DDs. I have to go home now, so I will collect them in 1 zip
>>> file and I will send them on the list tomorrow 23-Jun-2008.
>>>
>>> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
>>> <no...@gmail.com> wrote:
>>>
>>>> Thanks Daniel for clarifications. What I am doing now, is to get the
>>>> XMI files referenced inside both the binding and extensions XMI files,
>>>> which will help us making the corresspodent XSDs. I talked with Dain
>>>> on IRC about that. I just need sometime cause the XMI are located
>>>> inside one of the large number pf JARs shipped with WAS. Expected to
>>>> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
>>>>
>>>> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
>>>> <da...@googlemail.com> wrote:
>>>>
>>>>> a couple of thoughts...
>>>>>
>>>>> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF, MOF
>>>>> and XMI. ECore is the Eclipse pendant to MOF. They are both completely
>>>>> independent efforts. Both could be used as a basis for a so-called
>>>>> Domain Specific Language (DSL). A kinda one size fits all DSL is UML.
>>>>> MOF models can be access in Java using the JMI API. ECore models can
>>>>> be accessed in Java using the EMF programmatic API. Both MOF and ECore
>>>>> models will be persisted using an instance of XMI.
>>>>>
>>>>> 2) As David already pointed out, as long as we don't ship proprietary
>>>>> XSDs and such, we should be fine cause AFAIK even XDoclet and other
>>>>> tools are supporting proprietary WAS binding files. So why shouldn't
>>>>> we be allowed to do the same?
>>>>>
>>>>> 3) Some more docs about the WAS binding files:
>>>>>
>>>>> ibm-webservicesclient-bnd.xmi:
>>>>> ------------------------------
>>>>>
>>>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>>>
>>>>
>>>>> ibm-webservices-bnd.xmi:
>>>>> ------------------------
>>>>>
>>>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
>>>
>>>>
>>>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
>>>
>>>>
>>>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>>>
>>>>
>>>>> Application bindings:
>>>>> ---------------------
>>>>>
>>>>>
>>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>>>
>>>>
>>>>>
>>>>> Karan Malhi wrote:
>>>>>
>>>>>>
>>>>>> oops!
>>>>>>
>>>>>> I pasted the files for ejb 1.1 . Not sure if something changed for ejb
>>>>>>
>>>>> 2.1
>>>
>>>> .
>>>>>> I think we can ignore the ibm-ejb-ext files for now because they
>>>>>>
>>>>> contain
>>>
>>>> ibm
>>>>>> extensions. its the ibm-ejb-jar-bnd files which should be of interest.
>>>>>>
>>>>> I
>>>
>>>> will try and create a more comprehensive file using RAD or AST. This
>>>>>>
>>>>> will
>>>
>>>> contain local, remote ejb references, references to activation spec for
>>>>>> mdb,
>>>>>> datasource . We could probably use that to generate the schema.
>>>>>>
>>>>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <ka...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Or if you can grab the xmi files there's probably a way to convert
>>>>>>>
>>>>>> them
>>>
>>>> to
>>>>>>>
>>>>>>>>
>>>>>>>> xsd.
>>>>>>>>
>>>>>>>> I think this would be the best approach. Since Attachments are
>>>>>>> disallowed,
>>>>>>> I am giving the file name, its purpose followed by its contents. You
>>>>>>> should
>>>>>>> be able to create the file on the local system and paste the contents
>>>>>>>
>>>>>> in
>>>
>>>> it.
>>>>>>> Please keep in mind though that these files do not contain all info
>>>>>>>
>>>>>> they
>>>
>>>> could contain, so generating a schema out of them may not get us a
>>>>>>> comprehensive schema. (Actually, I was able to generate a schema
>>>>>>> using
>>>>>>>
>>>>>> c#
>>>
>>>> )
>>>>>>>
>>>>>>> File Name:- ibm-ejb-jar-bnd.xmi
>>>>>>> Contents:-
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -----------------------------------------------------------------------------
>>>
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>>>>>>> xmlns:xmi="http://www.omg.org/XMI"
>>>>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>>>>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="
>>>>>>>
>>>>>> http://www.w3.org/2001/XMLSchema-instance"
>>>
>>>> xmi:id="ejb-jar_ID_Bnd">
>>>>>>> <defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
>>>>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>>>>>>> xmi:id="BasicAuthData_1">
>>>>>>> <userId xsi:nil="true"/>
>>>>>>> <password xsi:nil="true"/>
>>>>>>> </defaultAuth>
>>>>>>> </defaultDatasource>
>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>> </ejbBindings>
>>>>>>> </ejbbnd:EJBJarBinding>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ----------------------------------------------------------------------------------
>>>
>>>>
>>>>>>> File Name:-ibm-ejb-jar-ext.xmi
>>>>>>> Contents:-
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -----------------------------------------------------------------------------------
>>>
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>>>>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi"
>>>>>>> xmlns:ejb="ejb.xmi"
>>>>>>> xmi:id="ejb-jar_ID_Ext">
>>>>>>> <ejbExtensions xmi:type="ejbext:SessionExtension"
>>>>>>>
>>>>>> xmi:id="Session_1_Ext"
>>>
>>>> timeout="600">
>>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>>>>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>>>>>>> <internationalization xmi:id="BeanInternationalization_1"
>>>>>>> invocationLocale="CALLER"/>
>>>>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>>>>>>> unresolvedAction="ROLLBACK"/>
>>>>>>> </ejbExtensions>
>>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>>> </ejbext:EJBJarExtension>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------------
>>>
>>>>
>>>>>>> File Name:- ejb-jar.xml
>>>>>>> Contents:-
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -----------------------------------------------------------------------------------
>>>
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
>>>>>>> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
>>>>>>>
>>>>>>> <ejb-jar id="ejb-jar_ID">
>>>>>>> <description>IVT Stateful Session EJB</description>
>>>>>>> <display-name>IVT EJB Module</display-name>
>>>>>>> <enterprise-beans>
>>>>>>> <session id="Session_1">
>>>>>>> <description>Verify Stateful Session EJB</description>
>>>>>>> <display-name>Verification of Stateful Session
>>>>>>> EJB</display-name>
>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>>>>>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>>>>>>>
>>>>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>>>>>>> <session-type>Stateful</session-type>
>>>>>>> <transaction-type>Container</transaction-type>
>>>>>>> </session>
>>>>>>> </enterprise-beans>
>>>>>>> <assembly-descriptor id="AssemblyDescriptor_1">
>>>>>>> <container-transaction id="MethodTransaction_1">
>>>>>>> <method id="MethodElement_1">
>>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>>> <method-name>*</method-name>
>>>>>>> </method>
>>>>>>> <trans-attribute>Never</trans-attribute>
>>>>>>> </container-transaction>
>>>>>>> </assembly-descriptor>
>>>>>>> </ejb-jar>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -----------------------------------------------------------------------------------
>>>
>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Karan Singh Malhi
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks
>>>> - Mohammad Nour
>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks
>>> - Mohammad Nour
>>>
>>>
>>
>>
>> --
>> Karan Singh Malhi
>>
>
>
--
Karan Singh Malhi
Re: websphere descriptors
Posted by David Blevins <da...@visi.com>.
On Jun 22, 2008, at 12:46 PM, Karan Malhi wrote:
> Great,
>
> I have created a Jira issue so that we could share the zip files.
>
> https://issues.apache.org/jira/browse/OPENEJB-830
Just an fyi, we can't publicly redistribute those on apache hardware.
-David
>
>
> On Sun, Jun 22, 2008 at 2:06 PM, Mohammad Nour El-Din <
> nour.mohammad@gmail.com> wrote:
>
>> Hi All...
>>
>> Good news :), I found all the XSDs we need. They are shipped with
>> the WAS installation under <was_home>/properties/schemas directory,
>> all the XSDs we dreamed of, the one for XMI and for all the other WAS
>> specific DDs. I have to go home now, so I will collect them in 1 zip
>> file and I will send them on the list tomorrow 23-Jun-2008.
>>
>> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
>> <no...@gmail.com> wrote:
>>> Thanks Daniel for clarifications. What I am doing now, is to get the
>>> XMI files referenced inside both the binding and extensions XMI
>>> files,
>>> which will help us making the corresspodent XSDs. I talked with Dain
>>> on IRC about that. I just need sometime cause the XMI are located
>>> inside one of the large number pf JARs shipped with WAS. Expected to
>>> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
>>>
>>> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
>>> <da...@googlemail.com> wrote:
>>>> a couple of thoughts...
>>>>
>>>> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF,
>>>> MOF
>>>> and XMI. ECore is the Eclipse pendant to MOF. They are both
>>>> completely
>>>> independent efforts. Both could be used as a basis for a so-called
>>>> Domain Specific Language (DSL). A kinda one size fits all DSL is
>>>> UML.
>>>> MOF models can be access in Java using the JMI API. ECore models
>>>> can
>>>> be accessed in Java using the EMF programmatic API. Both MOF and
>>>> ECore
>>>> models will be persisted using an instance of XMI.
>>>>
>>>> 2) As David already pointed out, as long as we don't ship
>>>> proprietary
>>>> XSDs and such, we should be fine cause AFAIK even XDoclet and other
>>>> tools are supporting proprietary WAS binding files. So why
>>>> shouldn't
>>>> we be allowed to do the same?
>>>>
>>>> 3) Some more docs about the WAS binding files:
>>>>
>>>> ibm-webservicesclient-bnd.xmi:
>>>> ------------------------------
>>>>
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>>>>
>>>> ibm-webservices-bnd.xmi:
>>>> ------------------------
>>>>
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
>>>>
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
>>>>
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>>>>
>>>> Application bindings:
>>>> ---------------------
>>>>
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>>>>
>>>>
>>>> Karan Malhi wrote:
>>>>>
>>>>> oops!
>>>>>
>>>>> I pasted the files for ejb 1.1 . Not sure if something changed
>>>>> for ejb
>> 2.1
>>>>> .
>>>>> I think we can ignore the ibm-ejb-ext files for now because they
>> contain
>>>>> ibm
>>>>> extensions. its the ibm-ejb-jar-bnd files which should be of
>>>>> interest.
>> I
>>>>> will try and create a more comprehensive file using RAD or AST.
>>>>> This
>> will
>>>>> contain local, remote ejb references, references to activation
>>>>> spec for
>>>>> mdb,
>>>>> datasource . We could probably use that to generate the schema.
>>>>>
>>>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <karan.malhi@gmail.com
>>>>> >
>>>>> wrote:
>>>>>
>>>>>> Or if you can grab the xmi files there's probably a way to
>>>>>> convert
>> them
>>>>>> to
>>>>>>>
>>>>>>> xsd.
>>>>>>>
>>>>>> I think this would be the best approach. Since Attachments are
>>>>>> disallowed,
>>>>>> I am giving the file name, its purpose followed by its
>>>>>> contents. You
>>>>>> should
>>>>>> be able to create the file on the local system and paste the
>>>>>> contents
>> in
>>>>>> it.
>>>>>> Please keep in mind though that these files do not contain all
>>>>>> info
>> they
>>>>>> could contain, so generating a schema out of them may not get
>>>>>> us a
>>>>>> comprehensive schema. (Actually, I was able to generate a
>>>>>> schema using
>> c#
>>>>>> )
>>>>>>
>>>>>> File Name:- ibm-ejb-jar-bnd.xmi
>>>>>> Contents:-
>>>>>>
>>>>>>
>>>>>>
>> -----------------------------------------------------------------------------
>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>>>>>> xmlns:xmi="http://www.omg.org/XMI"
>>>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>>>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance"
>>>>>> xmi:id="ejb-jar_ID_Bnd">
>>>>>> <defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
>>>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>>>>>> xmi:id="BasicAuthData_1">
>>>>>> <userId xsi:nil="true"/>
>>>>>> <password xsi:nil="true"/>
>>>>>> </defaultAuth>
>>>>>> </defaultDatasource>
>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>> </ejbBindings>
>>>>>> </ejbbnd:EJBJarBinding>
>>>>>>
>>>>>>
>>>>>>
>> ----------------------------------------------------------------------------------
>>>>>>
>>>>>> File Name:-ibm-ejb-jar-ext.xmi
>>>>>> Contents:-
>>>>>>
>>>>>>
>>>>>>
>> -----------------------------------------------------------------------------------
>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>>>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi"
>>>>>> xmlns:ejb="ejb.xmi"
>>>>>> xmi:id="ejb-jar_ID_Ext">
>>>>>> <ejbExtensions xmi:type="ejbext:SessionExtension"
>> xmi:id="Session_1_Ext"
>>>>>> timeout="600">
>>>>>> <enterpriseBean xmi:type="ejb:Session"
>>>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>>>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>>>>>> <internationalization xmi:id="BeanInternationalization_1"
>>>>>> invocationLocale="CALLER"/>
>>>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>>>>>> unresolvedAction="ROLLBACK"/>
>>>>>> </ejbExtensions>
>>>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>>>> </ejbext:EJBJarExtension>
>>>>>>
>>>>>>
>>>>>>
>> ------------------------------------------------------------------------------------
>>>>>>
>>>>>> File Name:- ejb-jar.xml
>>>>>> Contents:-
>>>>>>
>>>>>>
>>>>>>
>> -----------------------------------------------------------------------------------
>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD
>>>>>> Enterprise
>>>>>> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-
>>>>>> jar_1_1.dtd">
>>>>>>
>>>>>> <ejb-jar id="ejb-jar_ID">
>>>>>> <description>IVT Stateful Session EJB</description>
>>>>>> <display-name>IVT EJB Module</display-name>
>>>>>> <enterprise-beans>
>>>>>> <session id="Session_1">
>>>>>> <description>Verify Stateful Session EJB</description>
>>>>>> <display-name>Verification of Stateful Session
>>>>>> EJB</display-name>
>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>>>>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</
>>>>>> remote>
>>>>>>
>>>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>>>>>> <session-type>Stateful</session-type>
>>>>>> <transaction-type>Container</transaction-type>
>>>>>> </session>
>>>>>> </enterprise-beans>
>>>>>> <assembly-descriptor id="AssemblyDescriptor_1">
>>>>>> <container-transaction id="MethodTransaction_1">
>>>>>> <method id="MethodElement_1">
>>>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>>>> <method-name>*</method-name>
>>>>>> </method>
>>>>>> <trans-attribute>Never</trans-attribute>
>>>>>> </container-transaction>
>>>>>> </assembly-descriptor>
>>>>>> </ejb-jar>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>> -----------------------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Karan Singh Malhi
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Thanks
>>> - Mohammad Nour
>>>
>>
>>
>>
>> --
>> Thanks
>> - Mohammad Nour
>>
>
>
>
> --
> Karan Singh Malhi
Re: websphere descriptors
Posted by Karan Malhi <ka...@gmail.com>.
Great,
I have created a Jira issue so that we could share the zip files.
https://issues.apache.org/jira/browse/OPENEJB-830
On Sun, Jun 22, 2008 at 2:06 PM, Mohammad Nour El-Din <
nour.mohammad@gmail.com> wrote:
> Hi All...
>
> Good news :), I found all the XSDs we need. They are shipped with
> the WAS installation under <was_home>/properties/schemas directory,
> all the XSDs we dreamed of, the one for XMI and for all the other WAS
> specific DDs. I have to go home now, so I will collect them in 1 zip
> file and I will send them on the list tomorrow 23-Jun-2008.
>
> On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
> <no...@gmail.com> wrote:
> > Thanks Daniel for clarifications. What I am doing now, is to get the
> > XMI files referenced inside both the binding and extensions XMI files,
> > which will help us making the corresspodent XSDs. I talked with Dain
> > on IRC about that. I just need sometime cause the XMI are located
> > inside one of the large number pf JARs shipped with WAS. Expected to
> > send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
> >
> > On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
> > <da...@googlemail.com> wrote:
> >> a couple of thoughts...
> >>
> >> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF, MOF
> >> and XMI. ECore is the Eclipse pendant to MOF. They are both completely
> >> independent efforts. Both could be used as a basis for a so-called
> >> Domain Specific Language (DSL). A kinda one size fits all DSL is UML.
> >> MOF models can be access in Java using the JMI API. ECore models can
> >> be accessed in Java using the EMF programmatic API. Both MOF and ECore
> >> models will be persisted using an instance of XMI.
> >>
> >> 2) As David already pointed out, as long as we don't ship proprietary
> >> XSDs and such, we should be fine cause AFAIK even XDoclet and other
> >> tools are supporting proprietary WAS binding files. So why shouldn't
> >> we be allowed to do the same?
> >>
> >> 3) Some more docs about the WAS binding files:
> >>
> >> ibm-webservicesclient-bnd.xmi:
> >> ------------------------------
> >>
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
> >>
> >> ibm-webservices-bnd.xmi:
> >> ------------------------
> >>
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
> >>
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
> >>
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
> >>
> >> Application bindings:
> >> ---------------------
> >>
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
> >>
> >>
> >> Karan Malhi wrote:
> >>>
> >>> oops!
> >>>
> >>> I pasted the files for ejb 1.1 . Not sure if something changed for ejb
> 2.1
> >>> .
> >>> I think we can ignore the ibm-ejb-ext files for now because they
> contain
> >>> ibm
> >>> extensions. its the ibm-ejb-jar-bnd files which should be of interest.
> I
> >>> will try and create a more comprehensive file using RAD or AST. This
> will
> >>> contain local, remote ejb references, references to activation spec for
> >>> mdb,
> >>> datasource . We could probably use that to generate the schema.
> >>>
> >>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <ka...@gmail.com>
> >>> wrote:
> >>>
> >>>> Or if you can grab the xmi files there's probably a way to convert
> them
> >>>> to
> >>>>>
> >>>>> xsd.
> >>>>>
> >>>> I think this would be the best approach. Since Attachments are
> >>>> disallowed,
> >>>> I am giving the file name, its purpose followed by its contents. You
> >>>> should
> >>>> be able to create the file on the local system and paste the contents
> in
> >>>> it.
> >>>> Please keep in mind though that these files do not contain all info
> they
> >>>> could contain, so generating a schema out of them may not get us a
> >>>> comprehensive schema. (Actually, I was able to generate a schema using
> c#
> >>>> )
> >>>>
> >>>> File Name:- ibm-ejb-jar-bnd.xmi
> >>>> Contents:-
> >>>>
> >>>>
> >>>>
> -----------------------------------------------------------------------------
> >>>> <?xml version="1.0" encoding="UTF-8"?>
> >>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
> >>>> xmlns:xmi="http://www.omg.org/XMI"
> >>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
> >>>> xmlns:ejb="ejb.xmi" xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance"
> >>>> xmi:id="ejb-jar_ID_Bnd">
> >>>> <defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
> >>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
> >>>> xmi:id="BasicAuthData_1">
> >>>> <userId xsi:nil="true"/>
> >>>> <password xsi:nil="true"/>
> >>>> </defaultAuth>
> >>>> </defaultDatasource>
> >>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
> >>>> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
> >>>> <enterpriseBean xmi:type="ejb:Session"
> >>>> href="META-INF/ejb-jar.xml#Session_1"/>
> >>>> </ejbBindings>
> >>>> </ejbbnd:EJBJarBinding>
> >>>>
> >>>>
> >>>>
> ----------------------------------------------------------------------------------
> >>>>
> >>>> File Name:-ibm-ejb-jar-ext.xmi
> >>>> Contents:-
> >>>>
> >>>>
> >>>>
> -----------------------------------------------------------------------------------
> >>>> <?xml version="1.0" encoding="UTF-8"?>
> >>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
> >>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi" xmlns:ejb="ejb.xmi"
> >>>> xmi:id="ejb-jar_ID_Ext">
> >>>> <ejbExtensions xmi:type="ejbext:SessionExtension"
> xmi:id="Session_1_Ext"
> >>>> timeout="600">
> >>>> <enterpriseBean xmi:type="ejb:Session"
> >>>> href="META-INF/ejb-jar.xml#Session_1"/>
> >>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
> >>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
> >>>> <internationalization xmi:id="BeanInternationalization_1"
> >>>> invocationLocale="CALLER"/>
> >>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
> >>>> unresolvedAction="ROLLBACK"/>
> >>>> </ejbExtensions>
> >>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
> >>>> </ejbext:EJBJarExtension>
> >>>>
> >>>>
> >>>>
> ------------------------------------------------------------------------------------
> >>>>
> >>>> File Name:- ejb-jar.xml
> >>>> Contents:-
> >>>>
> >>>>
> >>>>
> -----------------------------------------------------------------------------------
> >>>> <?xml version="1.0" encoding="UTF-8"?>
> >>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
> >>>> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
> >>>>
> >>>> <ejb-jar id="ejb-jar_ID">
> >>>> <description>IVT Stateful Session EJB</description>
> >>>> <display-name>IVT EJB Module</display-name>
> >>>> <enterprise-beans>
> >>>> <session id="Session_1">
> >>>> <description>Verify Stateful Session EJB</description>
> >>>> <display-name>Verification of Stateful Session
> >>>> EJB</display-name>
> >>>> <ejb-name>ivtEJBObject</ejb-name>
> >>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
> >>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
> >>>>
> >>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
> >>>> <session-type>Stateful</session-type>
> >>>> <transaction-type>Container</transaction-type>
> >>>> </session>
> >>>> </enterprise-beans>
> >>>> <assembly-descriptor id="AssemblyDescriptor_1">
> >>>> <container-transaction id="MethodTransaction_1">
> >>>> <method id="MethodElement_1">
> >>>> <ejb-name>ivtEJBObject</ejb-name>
> >>>> <method-name>*</method-name>
> >>>> </method>
> >>>> <trans-attribute>Never</trans-attribute>
> >>>> </container-transaction>
> >>>> </assembly-descriptor>
> >>>> </ejb-jar>
> >>>>
> >>>>
> >>>>
> >>>>
> -----------------------------------------------------------------------------------
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Karan Singh Malhi
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
> >
> > --
> > Thanks
> > - Mohammad Nour
> >
>
>
>
> --
> Thanks
> - Mohammad Nour
>
--
Karan Singh Malhi
Re: websphere descriptors
Posted by David Blevins <da...@visi.com>.
On Jun 22, 2008, at 11:06 AM, Mohammad Nour El-Din wrote:
> Hi All...
>
> Good news :), I found all the XSDs we need. They are shipped with
> the WAS installation under <was_home>/properties/schemas directory,
Thanks for the location. I'll grab a copy of WAS and give it a shot.
-David
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi All...
Good news :), I found all the XSDs we need. They are shipped with
the WAS installation under <was_home>/properties/schemas directory,
all the XSDs we dreamed of, the one for XMI and for all the other WAS
specific DDs. I have to go home now, so I will collect them in 1 zip
file and I will send them on the list tomorrow 23-Jun-2008.
On Sun, Jun 22, 2008 at 2:26 PM, Mohammad Nour El-Din
<no...@gmail.com> wrote:
> Thanks Daniel for clarifications. What I am doing now, is to get the
> XMI files referenced inside both the binding and extensions XMI files,
> which will help us making the corresspodent XSDs. I talked with Dain
> on IRC about that. I just need sometime cause the XMI are located
> inside one of the large number pf JARs shipped with WAS. Expected to
> send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
>
> On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
> <da...@googlemail.com> wrote:
>> a couple of thoughts...
>>
>> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF, MOF
>> and XMI. ECore is the Eclipse pendant to MOF. They are both completely
>> independent efforts. Both could be used as a basis for a so-called
>> Domain Specific Language (DSL). A kinda one size fits all DSL is UML.
>> MOF models can be access in Java using the JMI API. ECore models can
>> be accessed in Java using the EMF programmatic API. Both MOF and ECore
>> models will be persisted using an instance of XMI.
>>
>> 2) As David already pointed out, as long as we don't ship proprietary
>> XSDs and such, we should be fine cause AFAIK even XDoclet and other
>> tools are supporting proprietary WAS binding files. So why shouldn't
>> we be allowed to do the same?
>>
>> 3) Some more docs about the WAS binding files:
>>
>> ibm-webservicesclient-bnd.xmi:
>> ------------------------------
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>>
>> ibm-webservices-bnd.xmi:
>> ------------------------
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>>
>> Application bindings:
>> ---------------------
>> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>>
>>
>> Karan Malhi wrote:
>>>
>>> oops!
>>>
>>> I pasted the files for ejb 1.1 . Not sure if something changed for ejb 2.1
>>> .
>>> I think we can ignore the ibm-ejb-ext files for now because they contain
>>> ibm
>>> extensions. its the ibm-ejb-jar-bnd files which should be of interest. I
>>> will try and create a more comprehensive file using RAD or AST. This will
>>> contain local, remote ejb references, references to activation spec for
>>> mdb,
>>> datasource . We could probably use that to generate the schema.
>>>
>>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <ka...@gmail.com>
>>> wrote:
>>>
>>>> Or if you can grab the xmi files there's probably a way to convert them
>>>> to
>>>>>
>>>>> xsd.
>>>>>
>>>> I think this would be the best approach. Since Attachments are
>>>> disallowed,
>>>> I am giving the file name, its purpose followed by its contents. You
>>>> should
>>>> be able to create the file on the local system and paste the contents in
>>>> it.
>>>> Please keep in mind though that these files do not contain all info they
>>>> could contain, so generating a schema out of them may not get us a
>>>> comprehensive schema. (Actually, I was able to generate a schema using c#
>>>> )
>>>>
>>>> File Name:- ibm-ejb-jar-bnd.xmi
>>>> Contents:-
>>>>
>>>>
>>>> -----------------------------------------------------------------------------
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>>>> xmlns:xmi="http://www.omg.org/XMI"
>>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>>>> xmlns:ejb="ejb.xmi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>> xmi:id="ejb-jar_ID_Bnd">
>>>> <defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
>>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>>>> xmi:id="BasicAuthData_1">
>>>> <userId xsi:nil="true"/>
>>>> <password xsi:nil="true"/>
>>>> </defaultAuth>
>>>> </defaultDatasource>
>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
>>>> <enterpriseBean xmi:type="ejb:Session"
>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>> </ejbBindings>
>>>> </ejbbnd:EJBJarBinding>
>>>>
>>>>
>>>> ----------------------------------------------------------------------------------
>>>>
>>>> File Name:-ibm-ejb-jar-ext.xmi
>>>> Contents:-
>>>>
>>>>
>>>> -----------------------------------------------------------------------------------
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi" xmlns:ejb="ejb.xmi"
>>>> xmi:id="ejb-jar_ID_Ext">
>>>> <ejbExtensions xmi:type="ejbext:SessionExtension" xmi:id="Session_1_Ext"
>>>> timeout="600">
>>>> <enterpriseBean xmi:type="ejb:Session"
>>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>>>> <internationalization xmi:id="BeanInternationalization_1"
>>>> invocationLocale="CALLER"/>
>>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>>>> unresolvedAction="ROLLBACK"/>
>>>> </ejbExtensions>
>>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>>> </ejbext:EJBJarExtension>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------------
>>>>
>>>> File Name:- ejb-jar.xml
>>>> Contents:-
>>>>
>>>>
>>>> -----------------------------------------------------------------------------------
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
>>>> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
>>>>
>>>> <ejb-jar id="ejb-jar_ID">
>>>> <description>IVT Stateful Session EJB</description>
>>>> <display-name>IVT EJB Module</display-name>
>>>> <enterprise-beans>
>>>> <session id="Session_1">
>>>> <description>Verify Stateful Session EJB</description>
>>>> <display-name>Verification of Stateful Session
>>>> EJB</display-name>
>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>>>>
>>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>>>> <session-type>Stateful</session-type>
>>>> <transaction-type>Container</transaction-type>
>>>> </session>
>>>> </enterprise-beans>
>>>> <assembly-descriptor id="AssemblyDescriptor_1">
>>>> <container-transaction id="MethodTransaction_1">
>>>> <method id="MethodElement_1">
>>>> <ejb-name>ivtEJBObject</ejb-name>
>>>> <method-name>*</method-name>
>>>> </method>
>>>> <trans-attribute>Never</trans-attribute>
>>>> </container-transaction>
>>>> </assembly-descriptor>
>>>> </ejb-jar>
>>>>
>>>>
>>>>
>>>> -----------------------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>> --
>>>> Karan Singh Malhi
>>>
>>>
>>>
>>>
>>
>>
>
>
>
> --
> Thanks
> - Mohammad Nour
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Thanks Daniel for clarifications. What I am doing now, is to get the
XMI files referenced inside both the binding and extensions XMI files,
which will help us making the corresspodent XSDs. I talked with Dain
on IRC about that. I just need sometime cause the XMI are located
inside one of the large number pf JARs shipped with WAS. Expected to
send my input today 22-Jun-2008 or tomorrow max. 23-Jun-2008.
On Sat, Jun 21, 2008 at 9:03 PM, Daniel S. Haischt
<da...@googlemail.com> wrote:
> a couple of thoughts...
>
> 1) I think Mohammad kinda mixed up the acronyms soup such as EMF, MOF
> and XMI. ECore is the Eclipse pendant to MOF. They are both completely
> independent efforts. Both could be used as a basis for a so-called
> Domain Specific Language (DSL). A kinda one size fits all DSL is UML.
> MOF models can be access in Java using the JMI API. ECore models can
> be accessed in Java using the EMF programmatic API. Both MOF and ECore
> models will be persisted using an instance of XMI.
>
> 2) As David already pointed out, as long as we don't ship proprietary
> XSDs and such, we should be fine cause AFAIK even XDoclet and other
> tools are supporting proprietary WAS binding files. So why shouldn't
> we be allowed to do the same?
>
> 3) Some more docs about the WAS binding files:
>
> ibm-webservicesclient-bnd.xmi:
> ------------------------------
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
>
> ibm-webservices-bnd.xmi:
> ------------------------
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
>
> Application bindings:
> ---------------------
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
>
>
> Karan Malhi wrote:
>>
>> oops!
>>
>> I pasted the files for ejb 1.1 . Not sure if something changed for ejb 2.1
>> .
>> I think we can ignore the ibm-ejb-ext files for now because they contain
>> ibm
>> extensions. its the ibm-ejb-jar-bnd files which should be of interest. I
>> will try and create a more comprehensive file using RAD or AST. This will
>> contain local, remote ejb references, references to activation spec for
>> mdb,
>> datasource . We could probably use that to generate the schema.
>>
>> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <ka...@gmail.com>
>> wrote:
>>
>>> Or if you can grab the xmi files there's probably a way to convert them
>>> to
>>>>
>>>> xsd.
>>>>
>>> I think this would be the best approach. Since Attachments are
>>> disallowed,
>>> I am giving the file name, its purpose followed by its contents. You
>>> should
>>> be able to create the file on the local system and paste the contents in
>>> it.
>>> Please keep in mind though that these files do not contain all info they
>>> could contain, so generating a schema out of them may not get us a
>>> comprehensive schema. (Actually, I was able to generate a schema using c#
>>> )
>>>
>>> File Name:- ibm-ejb-jar-bnd.xmi
>>> Contents:-
>>>
>>>
>>> -----------------------------------------------------------------------------
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <ejbbnd:EJBJarBinding xmi:version="2.0"
>>> xmlns:xmi="http://www.omg.org/XMI"
>>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>>> xmlns:ejb="ejb.xmi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmi:id="ejb-jar_ID_Bnd">
>>> <defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
>>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>>> xmi:id="BasicAuthData_1">
>>> <userId xsi:nil="true"/>
>>> <password xsi:nil="true"/>
>>> </defaultAuth>
>>> </defaultDatasource>
>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
>>> <enterpriseBean xmi:type="ejb:Session"
>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>> </ejbBindings>
>>> </ejbbnd:EJBJarBinding>
>>>
>>>
>>> ----------------------------------------------------------------------------------
>>>
>>> File Name:-ibm-ejb-jar-ext.xmi
>>> Contents:-
>>>
>>>
>>> -----------------------------------------------------------------------------------
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi" xmlns:ejb="ejb.xmi"
>>> xmi:id="ejb-jar_ID_Ext">
>>> <ejbExtensions xmi:type="ejbext:SessionExtension" xmi:id="Session_1_Ext"
>>> timeout="600">
>>> <enterpriseBean xmi:type="ejb:Session"
>>> href="META-INF/ejb-jar.xml#Session_1"/>
>>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>>> <internationalization xmi:id="BeanInternationalization_1"
>>> invocationLocale="CALLER"/>
>>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>>> unresolvedAction="ROLLBACK"/>
>>> </ejbExtensions>
>>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>>> </ejbext:EJBJarExtension>
>>>
>>>
>>> ------------------------------------------------------------------------------------
>>>
>>> File Name:- ejb-jar.xml
>>> Contents:-
>>>
>>>
>>> -----------------------------------------------------------------------------------
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
>>> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
>>>
>>> <ejb-jar id="ejb-jar_ID">
>>> <description>IVT Stateful Session EJB</description>
>>> <display-name>IVT EJB Module</display-name>
>>> <enterprise-beans>
>>> <session id="Session_1">
>>> <description>Verify Stateful Session EJB</description>
>>> <display-name>Verification of Stateful Session
>>> EJB</display-name>
>>> <ejb-name>ivtEJBObject</ejb-name>
>>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>>>
>>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>>> <session-type>Stateful</session-type>
>>> <transaction-type>Container</transaction-type>
>>> </session>
>>> </enterprise-beans>
>>> <assembly-descriptor id="AssemblyDescriptor_1">
>>> <container-transaction id="MethodTransaction_1">
>>> <method id="MethodElement_1">
>>> <ejb-name>ivtEJBObject</ejb-name>
>>> <method-name>*</method-name>
>>> </method>
>>> <trans-attribute>Never</trans-attribute>
>>> </container-transaction>
>>> </assembly-descriptor>
>>> </ejb-jar>
>>>
>>>
>>>
>>> -----------------------------------------------------------------------------------
>>>
>>>
>>>
>>> --
>>> Karan Singh Malhi
>>
>>
>>
>>
>
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by "Daniel S. Haischt" <da...@googlemail.com>.
a couple of thoughts...
1) I think Mohammad kinda mixed up the acronyms soup such as EMF, MOF
and XMI. ECore is the Eclipse pendant to MOF. They are both completely
independent efforts. Both could be used as a basis for a so-called
Domain Specific Language (DSL). A kinda one size fits all DSL is UML.
MOF models can be access in Java using the JMI API. ECore models can
be accessed in Java using the EMF programmatic API. Both MOF and ECore
models will be persisted using an instance of XMI.
2) As David already pointed out, as long as we don't ship proprietary
XSDs and such, we should be fine cause AFAIK even XDoclet and other
tools are supporting proprietary WAS binding files. So why shouldn't
we be allowed to do the same?
3) Some more docs about the WAS binding files:
ibm-webservicesclient-bnd.xmi:
------------------------------
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembpropclient.html
ibm-webservices-bnd.xmi:
------------------------
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/twbs_atkdd2.html
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rwbs_assembprop.html
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/cwbs_wssinwas.html
Application bindings:
---------------------
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/crun_app_bindings.html
Karan Malhi wrote:
> oops!
>
> I pasted the files for ejb 1.1 . Not sure if something changed for ejb 2.1 .
> I think we can ignore the ibm-ejb-ext files for now because they contain ibm
> extensions. its the ibm-ejb-jar-bnd files which should be of interest. I
> will try and create a more comprehensive file using RAD or AST. This will
> contain local, remote ejb references, references to activation spec for mdb,
> datasource . We could probably use that to generate the schema.
>
> On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <ka...@gmail.com> wrote:
>
>> Or if you can grab the xmi files there's probably a way to convert them to
>>> xsd.
>>>
>> I think this would be the best approach. Since Attachments are disallowed,
>> I am giving the file name, its purpose followed by its contents. You should
>> be able to create the file on the local system and paste the contents in it.
>> Please keep in mind though that these files do not contain all info they
>> could contain, so generating a schema out of them may not get us a
>> comprehensive schema. (Actually, I was able to generate a schema using c# )
>>
>> File Name:- ibm-ejb-jar-bnd.xmi
>> Contents:-
>>
>> -----------------------------------------------------------------------------
>> <?xml version="1.0" encoding="UTF-8"?>
>> <ejbbnd:EJBJarBinding xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI"
>> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
>> xmlns:ejb="ejb.xmi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xmi:id="ejb-jar_ID_Bnd">
>> <defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
>> <defaultAuth xmi:type="commonbnd:BasicAuthData"
>> xmi:id="BasicAuthData_1">
>> <userId xsi:nil="true"/>
>> <password xsi:nil="true"/>
>> </defaultAuth>
>> </defaultDatasource>
>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
>> <enterpriseBean xmi:type="ejb:Session"
>> href="META-INF/ejb-jar.xml#Session_1"/>
>> </ejbBindings>
>> </ejbbnd:EJBJarBinding>
>>
>> ----------------------------------------------------------------------------------
>>
>> File Name:-ibm-ejb-jar-ext.xmi
>> Contents:-
>>
>> -----------------------------------------------------------------------------------
>> <?xml version="1.0" encoding="UTF-8"?>
>> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
>> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi" xmlns:ejb="ejb.xmi"
>> xmi:id="ejb-jar_ID_Ext">
>> <ejbExtensions xmi:type="ejbext:SessionExtension" xmi:id="Session_1_Ext"
>> timeout="600">
>> <enterpriseBean xmi:type="ejb:Session"
>> href="META-INF/ejb-jar.xml#Session_1"/>
>> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
>> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
>> <internationalization xmi:id="BeanInternationalization_1"
>> invocationLocale="CALLER"/>
>> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
>> unresolvedAction="ROLLBACK"/>
>> </ejbExtensions>
>> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
>> </ejbext:EJBJarExtension>
>>
>> ------------------------------------------------------------------------------------
>>
>> File Name:- ejb-jar.xml
>> Contents:-
>>
>> -----------------------------------------------------------------------------------
>> <?xml version="1.0" encoding="UTF-8"?>
>> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
>> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
>>
>> <ejb-jar id="ejb-jar_ID">
>> <description>IVT Stateful Session EJB</description>
>> <display-name>IVT EJB Module</display-name>
>> <enterprise-beans>
>> <session id="Session_1">
>> <description>Verify Stateful Session EJB</description>
>> <display-name>Verification of Stateful Session
>> EJB</display-name>
>> <ejb-name>ivtEJBObject</ejb-name>
>> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
>> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>>
>> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
>> <session-type>Stateful</session-type>
>> <transaction-type>Container</transaction-type>
>> </session>
>> </enterprise-beans>
>> <assembly-descriptor id="AssemblyDescriptor_1">
>> <container-transaction id="MethodTransaction_1">
>> <method id="MethodElement_1">
>> <ejb-name>ivtEJBObject</ejb-name>
>> <method-name>*</method-name>
>> </method>
>> <trans-attribute>Never</trans-attribute>
>> </container-transaction>
>> </assembly-descriptor>
>> </ejb-jar>
>>
>>
>> -----------------------------------------------------------------------------------
>>
>>
>>
>> --
>> Karan Singh Malhi
>
>
>
>
Re: websphere descriptors
Posted by Karan Malhi <ka...@gmail.com>.
oops!
I pasted the files for ejb 1.1 . Not sure if something changed for ejb 2.1 .
I think we can ignore the ibm-ejb-ext files for now because they contain ibm
extensions. its the ibm-ejb-jar-bnd files which should be of interest. I
will try and create a more comprehensive file using RAD or AST. This will
contain local, remote ejb references, references to activation spec for mdb,
datasource . We could probably use that to generate the schema.
On Thu, Jun 19, 2008 at 8:33 PM, Karan Malhi <ka...@gmail.com> wrote:
>
> Or if you can grab the xmi files there's probably a way to convert them to
>> xsd.
>>
>
> I think this would be the best approach. Since Attachments are disallowed,
> I am giving the file name, its purpose followed by its contents. You should
> be able to create the file on the local system and paste the contents in it.
> Please keep in mind though that these files do not contain all info they
> could contain, so generating a schema out of them may not get us a
> comprehensive schema. (Actually, I was able to generate a schema using c# )
>
> File Name:- ibm-ejb-jar-bnd.xmi
> Contents:-
>
> -----------------------------------------------------------------------------
> <?xml version="1.0" encoding="UTF-8"?>
> <ejbbnd:EJBJarBinding xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI"
> xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
> xmlns:ejb="ejb.xmi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmi:id="ejb-jar_ID_Bnd">
> <defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
> <defaultAuth xmi:type="commonbnd:BasicAuthData"
> xmi:id="BasicAuthData_1">
> <userId xsi:nil="true"/>
> <password xsi:nil="true"/>
> </defaultAuth>
> </defaultDatasource>
> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
> <ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
> <enterpriseBean xmi:type="ejb:Session"
> href="META-INF/ejb-jar.xml#Session_1"/>
> </ejbBindings>
> </ejbbnd:EJBJarBinding>
>
> ----------------------------------------------------------------------------------
>
> File Name:-ibm-ejb-jar-ext.xmi
> Contents:-
>
> -----------------------------------------------------------------------------------
> <?xml version="1.0" encoding="UTF-8"?>
> <ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="
> http://www.omg.org/XMI" xmlns:ejbext="ejbext.xmi" xmlns:ejb="ejb.xmi"
> xmi:id="ejb-jar_ID_Ext">
> <ejbExtensions xmi:type="ejbext:SessionExtension" xmi:id="Session_1_Ext"
> timeout="600">
> <enterpriseBean xmi:type="ejb:Session"
> href="META-INF/ejb-jar.xml#Session_1"/>
> <structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
> <beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
> <internationalization xmi:id="BeanInternationalization_1"
> invocationLocale="CALLER"/>
> <localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
> unresolvedAction="ROLLBACK"/>
> </ejbExtensions>
> <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
> </ejbext:EJBJarExtension>
>
> ------------------------------------------------------------------------------------
>
> File Name:- ejb-jar.xml
> Contents:-
>
> -----------------------------------------------------------------------------------
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
> JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
>
> <ejb-jar id="ejb-jar_ID">
> <description>IVT Stateful Session EJB</description>
> <display-name>IVT EJB Module</display-name>
> <enterprise-beans>
> <session id="Session_1">
> <description>Verify Stateful Session EJB</description>
> <display-name>Verification of Stateful Session
> EJB</display-name>
> <ejb-name>ivtEJBObject</ejb-name>
> <home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
> <remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
>
> <ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
> <session-type>Stateful</session-type>
> <transaction-type>Container</transaction-type>
> </session>
> </enterprise-beans>
> <assembly-descriptor id="AssemblyDescriptor_1">
> <container-transaction id="MethodTransaction_1">
> <method id="MethodElement_1">
> <ejb-name>ivtEJBObject</ejb-name>
> <method-name>*</method-name>
> </method>
> <trans-attribute>Never</trans-attribute>
> </container-transaction>
> </assembly-descriptor>
> </ejb-jar>
>
>
> -----------------------------------------------------------------------------------
>
>
>
> --
> Karan Singh Malhi
--
Karan Singh Malhi
Re: websphere descriptors
Posted by Karan Malhi <ka...@gmail.com>.
> Or if you can grab the xmi files there's probably a way to convert them to
> xsd.
>
I think this would be the best approach. Since Attachments are disallowed, I
am giving the file name, its purpose followed by its contents. You should be
able to create the file on the local system and paste the contents in it.
Please keep in mind though that these files do not contain all info they
could contain, so generating a schema out of them may not get us a
comprehensive schema. (Actually, I was able to generate a schema using c# )
File Name:- ibm-ejb-jar-bnd.xmi
Contents:-
-----------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<ejbbnd:EJBJarBinding xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI"
xmlns:ejbbnd="ejbbnd.xmi" xmlns:commonbnd="commonbnd.xmi"
xmlns:ejb="ejb.xmi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmi:id="ejb-jar_ID_Bnd">
<defaultDatasource xmi:id="ResourceRefBinding_1" jndiName="ivt">
<defaultAuth xmi:type="commonbnd:BasicAuthData"
xmi:id="BasicAuthData_1">
<userId xsi:nil="true"/>
<password xsi:nil="true"/>
</defaultAuth>
</defaultDatasource>
<ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
<ejbBindings xmi:id="Session_1_Bnd" jndiName="ejb/ivtEJBObject">
<enterpriseBean xmi:type="ejb:Session"
href="META-INF/ejb-jar.xml#Session_1"/>
</ejbBindings>
</ejbbnd:EJBJarBinding>
----------------------------------------------------------------------------------
File Name:-ibm-ejb-jar-ext.xmi
Contents:-
-----------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<ejbext:EJBJarExtension xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI"
xmlns:ejbext="ejbext.xmi" xmlns:ejb="ejb.xmi" xmi:id="ejb-jar_ID_Ext">
<ejbExtensions xmi:type="ejbext:SessionExtension" xmi:id="Session_1_Ext"
timeout="600">
<enterpriseBean xmi:type="ejb:Session"
href="META-INF/ejb-jar.xml#Session_1"/>
<structure xmi:id="BeanStructure_1" inheritenceRoot="false"/>
<beanCache xmi:id="BeanCache_1" activateAt="ONCE"/>
<internationalization xmi:id="BeanInternationalization_1"
invocationLocale="CALLER"/>
<localTran xmi:id="LocalTran_1" boundary="BEAN_METHOD"
unresolvedAction="ROLLBACK"/>
</ejbExtensions>
<ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
</ejbext:EJBJarExtension>
------------------------------------------------------------------------------------
File Name:- ejb-jar.xml
Contents:-
-----------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
<ejb-jar id="ejb-jar_ID">
<description>IVT Stateful Session EJB</description>
<display-name>IVT EJB Module</display-name>
<enterprise-beans>
<session id="Session_1">
<description>Verify Stateful Session EJB</description>
<display-name>Verification of Stateful Session
EJB</display-name>
<ejb-name>ivtEJBObject</ejb-name>
<home>com.ibm.websphere.ivt.ivtEJB.ivtEJBHome</home>
<remote>com.ibm.websphere.ivt.ivtEJB.ivtEJBObject</remote>
<ejb-class>com.ibm.websphere.ivt.ivtEJB.ivtEJBSession</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor id="AssemblyDescriptor_1">
<container-transaction id="MethodTransaction_1">
<method id="MethodElement_1">
<ejb-name>ivtEJBObject</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Never</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
-----------------------------------------------------------------------------------
--
Karan Singh Malhi
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
I've found the XSD of XMI on the omg site here it is -
http://www.omg.org/spec/XMI/20071213/XMI.xsd - hope this can help for
now, at least to generate parsers for it and see if we can pare an IBM
spec DD with it. And I attached a sample IBM spec DD for u to test.
On Fri, Jun 20, 2008 at 1:20 AM, Mohammad Nour El-Din
<no...@gmail.com> wrote:
> Sorry for my mistake, XMI is not invented by Eclipse people, it is the
> invention of OMG - Object Management Group http://www.omg.org - Here
> is the link for XMI
> http://www.omg.org/technology/documents/modeling_spec_catalog.htm#XMI
> . But still this does not resolve the issues related to IBM specific
> DDs, cause they their own models and hence they can be considered as
> applications of XMIs .
>
> On Fri, Jun 20, 2008 at 1:05 AM, Mohammad Nour El-Din
> <no...@gmail.com> wrote:
>> XMIs are not XSDs Dain, they are XML representation for EMF models - u
>> can say UML described using EMF. I think there is a way to convert an
>> XMI to XSD, and I think this can be found on Eclipse site. But the XMI
>> schema itself which the WAS specific DDs follow, are not public and
>> they are located using the deployment tool of was inside the was
>> deployment itself - I will look for them. But this leads us to a
>> license issue, can we use those XMIs deployed with was and not
>> published publicly ???
>>
>> On Fri, Jun 20, 2008 at 12:25 AM, Dain Sundstrom <da...@iq80.com> wrote:
>>> Oh, I see. XMI is an alternative to XSD. I thought is was a new way to
>>> encode XML data (like SOAP encoded). So converting them to XSD and then
>>> running JAXB on the converted file makes the most sense.
>>>
>>> -dain
>>>
>>> On Jun 19, 2008, at 2:00 PM, David Blevins wrote:
>>>
>>>> Or if you can grab the xmi files there's probably a way to convert them to
>>>> xsd.
>>>>
>>>> If you can point me at them I can take a look.
>>>>
>>>> -David
>>>>
>>>> On Jun 19, 2008, at 1:37 PM, Dain Sundstrom wrote:
>>>>
>>>>> Can you post some example WS descriptors? I may be able to create a JAXB
>>>>> parser using SXC that can read an XMI input file. I'll only know how
>>>>> difficult a task it is after seeing some samples.
>>>>>
>>>>> -dain
>>>>>
>>>>> On Jun 19, 2008, at 10:11 AM, Mohammad Nour El-Din wrote:
>>>>>
>>>>>> :D, here is the trick, they are not normal XML files, they are XMI
>>>>>> files - which are still XML files - they are the XML representation of
>>>>>> an EMF model - EMF stand for Eclipse Meta Facility - it is the
>>>>>> customized implementation of the OMG's OMF - Object Meta Facility. EMF
>>>>>> is the frame work developed by Eclipse to impl the OMF in its own
>>>>>> Eclipse mindset way :), and u can think about it like a framework to
>>>>>> tie three main points together, that is Java, XML and UML. I kept
>>>>>> thinking about that even starting from the point David impled the
>>>>>> WebLogic import feature. I mean we have two approaches here:
>>>>>>
>>>>>> 1- To use the EMF to be able to read those XMI easily. But I still
>>>>>> don't know how exactly to do it - needs some investigation, and I have
>>>>>> some contacts to ask for that point. But we have to think about using
>>>>>> EMF in our project, it is not that easy cause we will have to package
>>>>>> it with OEJB, or the customer will have a headace doing it himself :S.
>>>>>>
>>>>>> 2- To use our intelligence and make a JAXB parsers - or anyother
>>>>>> kind of parsers - so we can read it as a kind of normal XML files to
>>>>>> get the info from it.
>>>>>>
>>>>>>
>>>>>> Think about it and I will make my contacts to have a more precise
>>>>>> decision.
>>>>>>
>>>>>> On Wed, Jun 18, 2008 at 6:11 PM, Karan Malhi <ka...@gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> I could not find the schemas for the descriptors. Any clue on where I
>>>>>>> could
>>>>>>> find them?
>>>>>>>
>>>>>>> On Tue, Jun 17, 2008 at 1:04 PM, Karan Malhi <ka...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Sure,
>>>>>>>>
>>>>>>>> That would be great.
>>>>>>>>
>>>>>>>> On Tue, Jun 17, 2008 at 3:02 AM, Mohammad Nour El-Din <
>>>>>>>> nour.mohammad@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Karan I would like to share this task with you as I have some
>>>>>>>>> experience with WAS specific DDs.
>>>>>>>>>
>>>>>>>>> On Tue, Jun 17, 2008 at 4:16 AM, David Blevins
>>>>>>>>> <da...@visi.com>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> On Jun 14, 2008, at 6:08 PM, Karan Malhi wrote:
>>>>>>>>>>
>>>>>>>>>>> Where would i start from to add support for Websphere descriptors?
>>>>>>>>>>
>>>>>>>>>> First thing would be to grab the xsds and generate a jaxb tree. You
>>>>>>>>>> can
>>>>>>>>>> throw then in a new package at org.apache.openejb.jee.was in the
>>>>>>>>>
>>>>>>>>> openejb-jee
>>>>>>>>>>
>>>>>>>>>> module.
>>>>>>>>>>
>>>>>>>>>> For the trees that I did, I just grabbed the latest 2.0.x version of
>>>>>>>>>> the
>>>>>>>>>> jaxb ri and generated via the command line.
>>>>>>>>>>
>>>>>>>>>> -David
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Thanks
>>>>>>>>> - Mohammad Nour
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Karan Singh Malhi
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Karan Singh Malhi
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thanks
>>>>>> - Mohammad Nour
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>>
>> --
>> Thanks
>> - Mohammad Nour
>>
>
>
>
> --
> Thanks
> - Mohammad Nour
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by David Blevins <da...@visi.com>.
We should be fine.
-David
On Jun 19, 2008, at 4:18 PM, Mohammad Nour El-Din wrote:
> So using those XSDs or XMIs to generate parsers is ok ?
>
> On Fri, Jun 20, 2008 at 1:38 AM, David Blevins
> <da...@visi.com> wrote:
>>
>> On Jun 19, 2008, at 3:05 PM, Mohammad Nour El-Din wrote:
>>
>>> XMIs are not XSDs Dain, they are XML representation for EMF models
>>> - u
>>> can say UML described using EMF. I think there is a way to convert
>>> an
>>> XMI to XSD, and I think this can be found on Eclipse site. But the
>>> XMI
>>> schema itself which the WAS specific DDs follow, are not public and
>>> they are located using the deployment tool of was inside the was
>>> deployment itself - I will look for them. But this leads us to a
>>> license issue, can we use those XMIs deployed with was and not
>>> published publicly ???
>>
>> We don't copy or distribute any xml (xsd or xmi) of other vendors
>> so we
>> should be fine.
>>
>> -David
>>
>>> On Fri, Jun 20, 2008 at 12:25 AM, Dain Sundstrom <da...@iq80.com>
>>> wrote:
>>>>
>>>> Oh, I see. XMI is an alternative to XSD. I thought is was a new
>>>> way to
>>>> encode XML data (like SOAP encoded). So converting them to XSD
>>>> and then
>>>> running JAXB on the converted file makes the most sense.
>>>>
>>>> -dain
>>>>
>>>> On Jun 19, 2008, at 2:00 PM, David Blevins wrote:
>>>>
>>>>> Or if you can grab the xmi files there's probably a way to
>>>>> convert them
>>>>> to
>>>>> xsd.
>>>>>
>>>>> If you can point me at them I can take a look.
>>>>>
>>>>> -David
>>>>>
>>>>> On Jun 19, 2008, at 1:37 PM, Dain Sundstrom wrote:
>>>>>
>>>>>> Can you post some example WS descriptors? I may be able to
>>>>>> create a
>>>>>> JAXB
>>>>>> parser using SXC that can read an XMI input file. I'll only
>>>>>> know how
>>>>>> difficult a task it is after seeing some samples.
>>>>>>
>>>>>> -dain
>>>>>>
>>>>>> On Jun 19, 2008, at 10:11 AM, Mohammad Nour El-Din wrote:
>>>>>>
>>>>>>> :D, here is the trick, they are not normal XML files, they are
>>>>>>> XMI
>>>>>>> files - which are still XML files - they are the XML
>>>>>>> representation of
>>>>>>> an EMF model - EMF stand for Eclipse Meta Facility - it is the
>>>>>>> customized implementation of the OMG's OMF - Object Meta
>>>>>>> Facility. EMF
>>>>>>> is the frame work developed by Eclipse to impl the OMF in its
>>>>>>> own
>>>>>>> Eclipse mindset way :), and u can think about it like a
>>>>>>> framework to
>>>>>>> tie three main points together, that is Java, XML and UML. I
>>>>>>> kept
>>>>>>> thinking about that even starting from the point David impled
>>>>>>> the
>>>>>>> WebLogic import feature. I mean we have two approaches here:
>>>>>>>
>>>>>>> 1- To use the EMF to be able to read those XMI easily. But I
>>>>>>> still
>>>>>>> don't know how exactly to do it - needs some investigation,
>>>>>>> and I have
>>>>>>> some contacts to ask for that point. But we have to think
>>>>>>> about using
>>>>>>> EMF in our project, it is not that easy cause we will have to
>>>>>>> package
>>>>>>> it with OEJB, or the customer will have a headace doing it
>>>>>>> himself :S.
>>>>>>>
>>>>>>> 2- To use our intelligence and make a JAXB parsers - or anyother
>>>>>>> kind of parsers - so we can read it as a kind of normal XML
>>>>>>> files to
>>>>>>> get the info from it.
>>>>>>>
>>>>>>>
>>>>>>> Think about it and I will make my contacts to have a more
>>>>>>> precise
>>>>>>> decision.
>>>>>>>
>>>>>>> On Wed, Jun 18, 2008 at 6:11 PM, Karan Malhi <karan.malhi@gmail.com
>>>>>>> >
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> I could not find the schemas for the descriptors. Any clue on
>>>>>>>> where I
>>>>>>>> could
>>>>>>>> find them?
>>>>>>>>
>>>>>>>> On Tue, Jun 17, 2008 at 1:04 PM, Karan Malhi <karan.malhi@gmail.com
>>>>>>>> >
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Sure,
>>>>>>>>>
>>>>>>>>> That would be great.
>>>>>>>>>
>>>>>>>>> On Tue, Jun 17, 2008 at 3:02 AM, Mohammad Nour El-Din <
>>>>>>>>> nour.mohammad@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Karan I would like to share this task with you as I have
>>>>>>>>>> some
>>>>>>>>>> experience with WAS specific DDs.
>>>>>>>>>>
>>>>>>>>>> On Tue, Jun 17, 2008 at 4:16 AM, David Blevins
>>>>>>>>>> <da...@visi.com>
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> On Jun 14, 2008, at 6:08 PM, Karan Malhi wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Where would i start from to add support for Websphere
>>>>>>>>>>>> descriptors?
>>>>>>>>>>>
>>>>>>>>>>> First thing would be to grab the xsds and generate a jaxb
>>>>>>>>>>> tree.
>>>>>>>>>>> You
>>>>>>>>>>> can
>>>>>>>>>>> throw then in a new package at org.apache.openejb.jee.was
>>>>>>>>>>> in the
>>>>>>>>>>
>>>>>>>>>> openejb-jee
>>>>>>>>>>>
>>>>>>>>>>> module.
>>>>>>>>>>>
>>>>>>>>>>> For the trees that I did, I just grabbed the latest 2.0.x
>>>>>>>>>>> version
>>>>>>>>>>> of
>>>>>>>>>>> the
>>>>>>>>>>> jaxb ri and generated via the command line.
>>>>>>>>>>>
>>>>>>>>>>> -David
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Thanks
>>>>>>>>>> - Mohammad Nour
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Karan Singh Malhi
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Karan Singh Malhi
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Thanks
>>>>>>> - Mohammad Nour
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Thanks
>>> - Mohammad Nour
>>>
>>
>>
>
>
>
> --
> Thanks
> - Mohammad Nour
>
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
So using those XSDs or XMIs to generate parsers is ok ?
On Fri, Jun 20, 2008 at 1:38 AM, David Blevins <da...@visi.com> wrote:
>
> On Jun 19, 2008, at 3:05 PM, Mohammad Nour El-Din wrote:
>
>> XMIs are not XSDs Dain, they are XML representation for EMF models - u
>> can say UML described using EMF. I think there is a way to convert an
>> XMI to XSD, and I think this can be found on Eclipse site. But the XMI
>> schema itself which the WAS specific DDs follow, are not public and
>> they are located using the deployment tool of was inside the was
>> deployment itself - I will look for them. But this leads us to a
>> license issue, can we use those XMIs deployed with was and not
>> published publicly ???
>
> We don't copy or distribute any xml (xsd or xmi) of other vendors so we
> should be fine.
>
> -David
>
>> On Fri, Jun 20, 2008 at 12:25 AM, Dain Sundstrom <da...@iq80.com> wrote:
>>>
>>> Oh, I see. XMI is an alternative to XSD. I thought is was a new way to
>>> encode XML data (like SOAP encoded). So converting them to XSD and then
>>> running JAXB on the converted file makes the most sense.
>>>
>>> -dain
>>>
>>> On Jun 19, 2008, at 2:00 PM, David Blevins wrote:
>>>
>>>> Or if you can grab the xmi files there's probably a way to convert them
>>>> to
>>>> xsd.
>>>>
>>>> If you can point me at them I can take a look.
>>>>
>>>> -David
>>>>
>>>> On Jun 19, 2008, at 1:37 PM, Dain Sundstrom wrote:
>>>>
>>>>> Can you post some example WS descriptors? I may be able to create a
>>>>> JAXB
>>>>> parser using SXC that can read an XMI input file. I'll only know how
>>>>> difficult a task it is after seeing some samples.
>>>>>
>>>>> -dain
>>>>>
>>>>> On Jun 19, 2008, at 10:11 AM, Mohammad Nour El-Din wrote:
>>>>>
>>>>>> :D, here is the trick, they are not normal XML files, they are XMI
>>>>>> files - which are still XML files - they are the XML representation of
>>>>>> an EMF model - EMF stand for Eclipse Meta Facility - it is the
>>>>>> customized implementation of the OMG's OMF - Object Meta Facility. EMF
>>>>>> is the frame work developed by Eclipse to impl the OMF in its own
>>>>>> Eclipse mindset way :), and u can think about it like a framework to
>>>>>> tie three main points together, that is Java, XML and UML. I kept
>>>>>> thinking about that even starting from the point David impled the
>>>>>> WebLogic import feature. I mean we have two approaches here:
>>>>>>
>>>>>> 1- To use the EMF to be able to read those XMI easily. But I still
>>>>>> don't know how exactly to do it - needs some investigation, and I have
>>>>>> some contacts to ask for that point. But we have to think about using
>>>>>> EMF in our project, it is not that easy cause we will have to package
>>>>>> it with OEJB, or the customer will have a headace doing it himself :S.
>>>>>>
>>>>>> 2- To use our intelligence and make a JAXB parsers - or anyother
>>>>>> kind of parsers - so we can read it as a kind of normal XML files to
>>>>>> get the info from it.
>>>>>>
>>>>>>
>>>>>> Think about it and I will make my contacts to have a more precise
>>>>>> decision.
>>>>>>
>>>>>> On Wed, Jun 18, 2008 at 6:11 PM, Karan Malhi <ka...@gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> I could not find the schemas for the descriptors. Any clue on where I
>>>>>>> could
>>>>>>> find them?
>>>>>>>
>>>>>>> On Tue, Jun 17, 2008 at 1:04 PM, Karan Malhi <ka...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Sure,
>>>>>>>>
>>>>>>>> That would be great.
>>>>>>>>
>>>>>>>> On Tue, Jun 17, 2008 at 3:02 AM, Mohammad Nour El-Din <
>>>>>>>> nour.mohammad@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Karan I would like to share this task with you as I have some
>>>>>>>>> experience with WAS specific DDs.
>>>>>>>>>
>>>>>>>>> On Tue, Jun 17, 2008 at 4:16 AM, David Blevins
>>>>>>>>> <da...@visi.com>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> On Jun 14, 2008, at 6:08 PM, Karan Malhi wrote:
>>>>>>>>>>
>>>>>>>>>>> Where would i start from to add support for Websphere
>>>>>>>>>>> descriptors?
>>>>>>>>>>
>>>>>>>>>> First thing would be to grab the xsds and generate a jaxb tree.
>>>>>>>>>> You
>>>>>>>>>> can
>>>>>>>>>> throw then in a new package at org.apache.openejb.jee.was in the
>>>>>>>>>
>>>>>>>>> openejb-jee
>>>>>>>>>>
>>>>>>>>>> module.
>>>>>>>>>>
>>>>>>>>>> For the trees that I did, I just grabbed the latest 2.0.x version
>>>>>>>>>> of
>>>>>>>>>> the
>>>>>>>>>> jaxb ri and generated via the command line.
>>>>>>>>>>
>>>>>>>>>> -David
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Thanks
>>>>>>>>> - Mohammad Nour
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Karan Singh Malhi
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Karan Singh Malhi
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thanks
>>>>>> - Mohammad Nour
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>>
>> --
>> Thanks
>> - Mohammad Nour
>>
>
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by David Blevins <da...@visi.com>.
On Jun 19, 2008, at 3:05 PM, Mohammad Nour El-Din wrote:
> XMIs are not XSDs Dain, they are XML representation for EMF models - u
> can say UML described using EMF. I think there is a way to convert an
> XMI to XSD, and I think this can be found on Eclipse site. But the XMI
> schema itself which the WAS specific DDs follow, are not public and
> they are located using the deployment tool of was inside the was
> deployment itself - I will look for them. But this leads us to a
> license issue, can we use those XMIs deployed with was and not
> published publicly ???
We don't copy or distribute any xml (xsd or xmi) of other vendors so
we should be fine.
-David
> On Fri, Jun 20, 2008 at 12:25 AM, Dain Sundstrom <da...@iq80.com>
> wrote:
>> Oh, I see. XMI is an alternative to XSD. I thought is was a new
>> way to
>> encode XML data (like SOAP encoded). So converting them to XSD and
>> then
>> running JAXB on the converted file makes the most sense.
>>
>> -dain
>>
>> On Jun 19, 2008, at 2:00 PM, David Blevins wrote:
>>
>>> Or if you can grab the xmi files there's probably a way to convert
>>> them to
>>> xsd.
>>>
>>> If you can point me at them I can take a look.
>>>
>>> -David
>>>
>>> On Jun 19, 2008, at 1:37 PM, Dain Sundstrom wrote:
>>>
>>>> Can you post some example WS descriptors? I may be able to
>>>> create a JAXB
>>>> parser using SXC that can read an XMI input file. I'll only know
>>>> how
>>>> difficult a task it is after seeing some samples.
>>>>
>>>> -dain
>>>>
>>>> On Jun 19, 2008, at 10:11 AM, Mohammad Nour El-Din wrote:
>>>>
>>>>> :D, here is the trick, they are not normal XML files, they are XMI
>>>>> files - which are still XML files - they are the XML
>>>>> representation of
>>>>> an EMF model - EMF stand for Eclipse Meta Facility - it is the
>>>>> customized implementation of the OMG's OMF - Object Meta
>>>>> Facility. EMF
>>>>> is the frame work developed by Eclipse to impl the OMF in its own
>>>>> Eclipse mindset way :), and u can think about it like a
>>>>> framework to
>>>>> tie three main points together, that is Java, XML and UML. I kept
>>>>> thinking about that even starting from the point David impled the
>>>>> WebLogic import feature. I mean we have two approaches here:
>>>>>
>>>>> 1- To use the EMF to be able to read those XMI easily. But I still
>>>>> don't know how exactly to do it - needs some investigation, and
>>>>> I have
>>>>> some contacts to ask for that point. But we have to think about
>>>>> using
>>>>> EMF in our project, it is not that easy cause we will have to
>>>>> package
>>>>> it with OEJB, or the customer will have a headace doing it
>>>>> himself :S.
>>>>>
>>>>> 2- To use our intelligence and make a JAXB parsers - or anyother
>>>>> kind of parsers - so we can read it as a kind of normal XML
>>>>> files to
>>>>> get the info from it.
>>>>>
>>>>>
>>>>> Think about it and I will make my contacts to have a more precise
>>>>> decision.
>>>>>
>>>>> On Wed, Jun 18, 2008 at 6:11 PM, Karan Malhi <karan.malhi@gmail.com
>>>>> >
>>>>> wrote:
>>>>>>
>>>>>> I could not find the schemas for the descriptors. Any clue on
>>>>>> where I
>>>>>> could
>>>>>> find them?
>>>>>>
>>>>>> On Tue, Jun 17, 2008 at 1:04 PM, Karan Malhi <karan.malhi@gmail.com
>>>>>> >
>>>>>> wrote:
>>>>>>
>>>>>>> Sure,
>>>>>>>
>>>>>>> That would be great.
>>>>>>>
>>>>>>> On Tue, Jun 17, 2008 at 3:02 AM, Mohammad Nour El-Din <
>>>>>>> nour.mohammad@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi Karan I would like to share this task with you as I have
>>>>>>>> some
>>>>>>>> experience with WAS specific DDs.
>>>>>>>>
>>>>>>>> On Tue, Jun 17, 2008 at 4:16 AM, David Blevins
>>>>>>>> <da...@visi.com>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> On Jun 14, 2008, at 6:08 PM, Karan Malhi wrote:
>>>>>>>>>
>>>>>>>>>> Where would i start from to add support for Websphere
>>>>>>>>>> descriptors?
>>>>>>>>>
>>>>>>>>> First thing would be to grab the xsds and generate a jaxb
>>>>>>>>> tree. You
>>>>>>>>> can
>>>>>>>>> throw then in a new package at org.apache.openejb.jee.was in
>>>>>>>>> the
>>>>>>>>
>>>>>>>> openejb-jee
>>>>>>>>>
>>>>>>>>> module.
>>>>>>>>>
>>>>>>>>> For the trees that I did, I just grabbed the latest 2.0.x
>>>>>>>>> version of
>>>>>>>>> the
>>>>>>>>> jaxb ri and generated via the command line.
>>>>>>>>>
>>>>>>>>> -David
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks
>>>>>>>> - Mohammad Nour
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Karan Singh Malhi
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Karan Singh Malhi
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Thanks
>>>>> - Mohammad Nour
>>>>
>>>>
>>>
>>
>>
>
>
>
> --
> Thanks
> - Mohammad Nour
>
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Sorry for my mistake, XMI is not invented by Eclipse people, it is the
invention of OMG - Object Management Group http://www.omg.org - Here
is the link for XMI
http://www.omg.org/technology/documents/modeling_spec_catalog.htm#XMI
. But still this does not resolve the issues related to IBM specific
DDs, cause they their own models and hence they can be considered as
applications of XMIs .
On Fri, Jun 20, 2008 at 1:05 AM, Mohammad Nour El-Din
<no...@gmail.com> wrote:
> XMIs are not XSDs Dain, they are XML representation for EMF models - u
> can say UML described using EMF. I think there is a way to convert an
> XMI to XSD, and I think this can be found on Eclipse site. But the XMI
> schema itself which the WAS specific DDs follow, are not public and
> they are located using the deployment tool of was inside the was
> deployment itself - I will look for them. But this leads us to a
> license issue, can we use those XMIs deployed with was and not
> published publicly ???
>
> On Fri, Jun 20, 2008 at 12:25 AM, Dain Sundstrom <da...@iq80.com> wrote:
>> Oh, I see. XMI is an alternative to XSD. I thought is was a new way to
>> encode XML data (like SOAP encoded). So converting them to XSD and then
>> running JAXB on the converted file makes the most sense.
>>
>> -dain
>>
>> On Jun 19, 2008, at 2:00 PM, David Blevins wrote:
>>
>>> Or if you can grab the xmi files there's probably a way to convert them to
>>> xsd.
>>>
>>> If you can point me at them I can take a look.
>>>
>>> -David
>>>
>>> On Jun 19, 2008, at 1:37 PM, Dain Sundstrom wrote:
>>>
>>>> Can you post some example WS descriptors? I may be able to create a JAXB
>>>> parser using SXC that can read an XMI input file. I'll only know how
>>>> difficult a task it is after seeing some samples.
>>>>
>>>> -dain
>>>>
>>>> On Jun 19, 2008, at 10:11 AM, Mohammad Nour El-Din wrote:
>>>>
>>>>> :D, here is the trick, they are not normal XML files, they are XMI
>>>>> files - which are still XML files - they are the XML representation of
>>>>> an EMF model - EMF stand for Eclipse Meta Facility - it is the
>>>>> customized implementation of the OMG's OMF - Object Meta Facility. EMF
>>>>> is the frame work developed by Eclipse to impl the OMF in its own
>>>>> Eclipse mindset way :), and u can think about it like a framework to
>>>>> tie three main points together, that is Java, XML and UML. I kept
>>>>> thinking about that even starting from the point David impled the
>>>>> WebLogic import feature. I mean we have two approaches here:
>>>>>
>>>>> 1- To use the EMF to be able to read those XMI easily. But I still
>>>>> don't know how exactly to do it - needs some investigation, and I have
>>>>> some contacts to ask for that point. But we have to think about using
>>>>> EMF in our project, it is not that easy cause we will have to package
>>>>> it with OEJB, or the customer will have a headace doing it himself :S.
>>>>>
>>>>> 2- To use our intelligence and make a JAXB parsers - or anyother
>>>>> kind of parsers - so we can read it as a kind of normal XML files to
>>>>> get the info from it.
>>>>>
>>>>>
>>>>> Think about it and I will make my contacts to have a more precise
>>>>> decision.
>>>>>
>>>>> On Wed, Jun 18, 2008 at 6:11 PM, Karan Malhi <ka...@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> I could not find the schemas for the descriptors. Any clue on where I
>>>>>> could
>>>>>> find them?
>>>>>>
>>>>>> On Tue, Jun 17, 2008 at 1:04 PM, Karan Malhi <ka...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Sure,
>>>>>>>
>>>>>>> That would be great.
>>>>>>>
>>>>>>> On Tue, Jun 17, 2008 at 3:02 AM, Mohammad Nour El-Din <
>>>>>>> nour.mohammad@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi Karan I would like to share this task with you as I have some
>>>>>>>> experience with WAS specific DDs.
>>>>>>>>
>>>>>>>> On Tue, Jun 17, 2008 at 4:16 AM, David Blevins
>>>>>>>> <da...@visi.com>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> On Jun 14, 2008, at 6:08 PM, Karan Malhi wrote:
>>>>>>>>>
>>>>>>>>>> Where would i start from to add support for Websphere descriptors?
>>>>>>>>>
>>>>>>>>> First thing would be to grab the xsds and generate a jaxb tree. You
>>>>>>>>> can
>>>>>>>>> throw then in a new package at org.apache.openejb.jee.was in the
>>>>>>>>
>>>>>>>> openejb-jee
>>>>>>>>>
>>>>>>>>> module.
>>>>>>>>>
>>>>>>>>> For the trees that I did, I just grabbed the latest 2.0.x version of
>>>>>>>>> the
>>>>>>>>> jaxb ri and generated via the command line.
>>>>>>>>>
>>>>>>>>> -David
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks
>>>>>>>> - Mohammad Nour
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Karan Singh Malhi
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Karan Singh Malhi
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Thanks
>>>>> - Mohammad Nour
>>>>
>>>>
>>>
>>
>>
>
>
>
> --
> Thanks
> - Mohammad Nour
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
XMIs are not XSDs Dain, they are XML representation for EMF models - u
can say UML described using EMF. I think there is a way to convert an
XMI to XSD, and I think this can be found on Eclipse site. But the XMI
schema itself which the WAS specific DDs follow, are not public and
they are located using the deployment tool of was inside the was
deployment itself - I will look for them. But this leads us to a
license issue, can we use those XMIs deployed with was and not
published publicly ???
On Fri, Jun 20, 2008 at 12:25 AM, Dain Sundstrom <da...@iq80.com> wrote:
> Oh, I see. XMI is an alternative to XSD. I thought is was a new way to
> encode XML data (like SOAP encoded). So converting them to XSD and then
> running JAXB on the converted file makes the most sense.
>
> -dain
>
> On Jun 19, 2008, at 2:00 PM, David Blevins wrote:
>
>> Or if you can grab the xmi files there's probably a way to convert them to
>> xsd.
>>
>> If you can point me at them I can take a look.
>>
>> -David
>>
>> On Jun 19, 2008, at 1:37 PM, Dain Sundstrom wrote:
>>
>>> Can you post some example WS descriptors? I may be able to create a JAXB
>>> parser using SXC that can read an XMI input file. I'll only know how
>>> difficult a task it is after seeing some samples.
>>>
>>> -dain
>>>
>>> On Jun 19, 2008, at 10:11 AM, Mohammad Nour El-Din wrote:
>>>
>>>> :D, here is the trick, they are not normal XML files, they are XMI
>>>> files - which are still XML files - they are the XML representation of
>>>> an EMF model - EMF stand for Eclipse Meta Facility - it is the
>>>> customized implementation of the OMG's OMF - Object Meta Facility. EMF
>>>> is the frame work developed by Eclipse to impl the OMF in its own
>>>> Eclipse mindset way :), and u can think about it like a framework to
>>>> tie three main points together, that is Java, XML and UML. I kept
>>>> thinking about that even starting from the point David impled the
>>>> WebLogic import feature. I mean we have two approaches here:
>>>>
>>>> 1- To use the EMF to be able to read those XMI easily. But I still
>>>> don't know how exactly to do it - needs some investigation, and I have
>>>> some contacts to ask for that point. But we have to think about using
>>>> EMF in our project, it is not that easy cause we will have to package
>>>> it with OEJB, or the customer will have a headace doing it himself :S.
>>>>
>>>> 2- To use our intelligence and make a JAXB parsers - or anyother
>>>> kind of parsers - so we can read it as a kind of normal XML files to
>>>> get the info from it.
>>>>
>>>>
>>>> Think about it and I will make my contacts to have a more precise
>>>> decision.
>>>>
>>>> On Wed, Jun 18, 2008 at 6:11 PM, Karan Malhi <ka...@gmail.com>
>>>> wrote:
>>>>>
>>>>> I could not find the schemas for the descriptors. Any clue on where I
>>>>> could
>>>>> find them?
>>>>>
>>>>> On Tue, Jun 17, 2008 at 1:04 PM, Karan Malhi <ka...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Sure,
>>>>>>
>>>>>> That would be great.
>>>>>>
>>>>>> On Tue, Jun 17, 2008 at 3:02 AM, Mohammad Nour El-Din <
>>>>>> nour.mohammad@gmail.com> wrote:
>>>>>>
>>>>>>> Hi Karan I would like to share this task with you as I have some
>>>>>>> experience with WAS specific DDs.
>>>>>>>
>>>>>>> On Tue, Jun 17, 2008 at 4:16 AM, David Blevins
>>>>>>> <da...@visi.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> On Jun 14, 2008, at 6:08 PM, Karan Malhi wrote:
>>>>>>>>
>>>>>>>>> Where would i start from to add support for Websphere descriptors?
>>>>>>>>
>>>>>>>> First thing would be to grab the xsds and generate a jaxb tree. You
>>>>>>>> can
>>>>>>>> throw then in a new package at org.apache.openejb.jee.was in the
>>>>>>>
>>>>>>> openejb-jee
>>>>>>>>
>>>>>>>> module.
>>>>>>>>
>>>>>>>> For the trees that I did, I just grabbed the latest 2.0.x version of
>>>>>>>> the
>>>>>>>> jaxb ri and generated via the command line.
>>>>>>>>
>>>>>>>> -David
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Thanks
>>>>>>> - Mohammad Nour
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Karan Singh Malhi
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Karan Singh Malhi
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Thanks
>>>> - Mohammad Nour
>>>
>>>
>>
>
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by Dain Sundstrom <da...@iq80.com>.
Oh, I see. XMI is an alternative to XSD. I thought is was a new way
to encode XML data (like SOAP encoded). So converting them to XSD and
then running JAXB on the converted file makes the most sense.
-dain
On Jun 19, 2008, at 2:00 PM, David Blevins wrote:
> Or if you can grab the xmi files there's probably a way to convert
> them to xsd.
>
> If you can point me at them I can take a look.
>
> -David
>
> On Jun 19, 2008, at 1:37 PM, Dain Sundstrom wrote:
>
>> Can you post some example WS descriptors? I may be able to create
>> a JAXB parser using SXC that can read an XMI input file. I'll only
>> know how difficult a task it is after seeing some samples.
>>
>> -dain
>>
>> On Jun 19, 2008, at 10:11 AM, Mohammad Nour El-Din wrote:
>>
>>> :D, here is the trick, they are not normal XML files, they are XMI
>>> files - which are still XML files - they are the XML
>>> representation of
>>> an EMF model - EMF stand for Eclipse Meta Facility - it is the
>>> customized implementation of the OMG's OMF - Object Meta Facility.
>>> EMF
>>> is the frame work developed by Eclipse to impl the OMF in its own
>>> Eclipse mindset way :), and u can think about it like a framework to
>>> tie three main points together, that is Java, XML and UML. I kept
>>> thinking about that even starting from the point David impled the
>>> WebLogic import feature. I mean we have two approaches here:
>>>
>>> 1- To use the EMF to be able to read those XMI easily. But I still
>>> don't know how exactly to do it - needs some investigation, and I
>>> have
>>> some contacts to ask for that point. But we have to think about
>>> using
>>> EMF in our project, it is not that easy cause we will have to
>>> package
>>> it with OEJB, or the customer will have a headace doing it
>>> himself :S.
>>>
>>> 2- To use our intelligence and make a JAXB parsers - or anyother
>>> kind of parsers - so we can read it as a kind of normal XML files to
>>> get the info from it.
>>>
>>>
>>> Think about it and I will make my contacts to have a more precise
>>> decision.
>>>
>>> On Wed, Jun 18, 2008 at 6:11 PM, Karan Malhi
>>> <ka...@gmail.com> wrote:
>>>> I could not find the schemas for the descriptors. Any clue on
>>>> where I could
>>>> find them?
>>>>
>>>> On Tue, Jun 17, 2008 at 1:04 PM, Karan Malhi
>>>> <ka...@gmail.com> wrote:
>>>>
>>>>> Sure,
>>>>>
>>>>> That would be great.
>>>>>
>>>>> On Tue, Jun 17, 2008 at 3:02 AM, Mohammad Nour El-Din <
>>>>> nour.mohammad@gmail.com> wrote:
>>>>>
>>>>>> Hi Karan I would like to share this task with you as I have some
>>>>>> experience with WAS specific DDs.
>>>>>>
>>>>>> On Tue, Jun 17, 2008 at 4:16 AM, David Blevins <david.blevins@visi.com
>>>>>> >
>>>>>> wrote:
>>>>>>> On Jun 14, 2008, at 6:08 PM, Karan Malhi wrote:
>>>>>>>
>>>>>>>> Where would i start from to add support for Websphere
>>>>>>>> descriptors?
>>>>>>>
>>>>>>> First thing would be to grab the xsds and generate a jaxb
>>>>>>> tree. You can
>>>>>>> throw then in a new package at org.apache.openejb.jee.was in the
>>>>>> openejb-jee
>>>>>>> module.
>>>>>>>
>>>>>>> For the trees that I did, I just grabbed the latest 2.0.x
>>>>>>> version of the
>>>>>>> jaxb ri and generated via the command line.
>>>>>>>
>>>>>>> -David
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thanks
>>>>>> - Mohammad Nour
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Karan Singh Malhi
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Karan Singh Malhi
>>>>
>>>
>>>
>>>
>>> --
>>> Thanks
>>> - Mohammad Nour
>>
>>
>
Re: websphere descriptors
Posted by David Blevins <da...@visi.com>.
Or if you can grab the xmi files there's probably a way to convert
them to xsd.
If you can point me at them I can take a look.
-David
On Jun 19, 2008, at 1:37 PM, Dain Sundstrom wrote:
> Can you post some example WS descriptors? I may be able to create a
> JAXB parser using SXC that can read an XMI input file. I'll only
> know how difficult a task it is after seeing some samples.
>
> -dain
>
> On Jun 19, 2008, at 10:11 AM, Mohammad Nour El-Din wrote:
>
>> :D, here is the trick, they are not normal XML files, they are XMI
>> files - which are still XML files - they are the XML representation
>> of
>> an EMF model - EMF stand for Eclipse Meta Facility - it is the
>> customized implementation of the OMG's OMF - Object Meta Facility.
>> EMF
>> is the frame work developed by Eclipse to impl the OMF in its own
>> Eclipse mindset way :), and u can think about it like a framework to
>> tie three main points together, that is Java, XML and UML. I kept
>> thinking about that even starting from the point David impled the
>> WebLogic import feature. I mean we have two approaches here:
>>
>> 1- To use the EMF to be able to read those XMI easily. But I still
>> don't know how exactly to do it - needs some investigation, and I
>> have
>> some contacts to ask for that point. But we have to think about using
>> EMF in our project, it is not that easy cause we will have to package
>> it with OEJB, or the customer will have a headace doing it
>> himself :S.
>>
>> 2- To use our intelligence and make a JAXB parsers - or anyother
>> kind of parsers - so we can read it as a kind of normal XML files to
>> get the info from it.
>>
>>
>> Think about it and I will make my contacts to have a more precise
>> decision.
>>
>> On Wed, Jun 18, 2008 at 6:11 PM, Karan Malhi
>> <ka...@gmail.com> wrote:
>>> I could not find the schemas for the descriptors. Any clue on
>>> where I could
>>> find them?
>>>
>>> On Tue, Jun 17, 2008 at 1:04 PM, Karan Malhi
>>> <ka...@gmail.com> wrote:
>>>
>>>> Sure,
>>>>
>>>> That would be great.
>>>>
>>>> On Tue, Jun 17, 2008 at 3:02 AM, Mohammad Nour El-Din <
>>>> nour.mohammad@gmail.com> wrote:
>>>>
>>>>> Hi Karan I would like to share this task with you as I have some
>>>>> experience with WAS specific DDs.
>>>>>
>>>>> On Tue, Jun 17, 2008 at 4:16 AM, David Blevins <david.blevins@visi.com
>>>>> >
>>>>> wrote:
>>>>>> On Jun 14, 2008, at 6:08 PM, Karan Malhi wrote:
>>>>>>
>>>>>>> Where would i start from to add support for Websphere
>>>>>>> descriptors?
>>>>>>
>>>>>> First thing would be to grab the xsds and generate a jaxb
>>>>>> tree. You can
>>>>>> throw then in a new package at org.apache.openejb.jee.was in the
>>>>> openejb-jee
>>>>>> module.
>>>>>>
>>>>>> For the trees that I did, I just grabbed the latest 2.0.x
>>>>>> version of the
>>>>>> jaxb ri and generated via the command line.
>>>>>>
>>>>>> -David
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Thanks
>>>>> - Mohammad Nour
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Karan Singh Malhi
>>>
>>>
>>>
>>>
>>> --
>>> Karan Singh Malhi
>>>
>>
>>
>>
>> --
>> Thanks
>> - Mohammad Nour
>
>
Re: websphere descriptors
Posted by Dain Sundstrom <da...@iq80.com>.
Can you post some example WS descriptors? I may be able to create a
JAXB parser using SXC that can read an XMI input file. I'll only know
how difficult a task it is after seeing some samples.
-dain
On Jun 19, 2008, at 10:11 AM, Mohammad Nour El-Din wrote:
> :D, here is the trick, they are not normal XML files, they are XMI
> files - which are still XML files - they are the XML representation of
> an EMF model - EMF stand for Eclipse Meta Facility - it is the
> customized implementation of the OMG's OMF - Object Meta Facility. EMF
> is the frame work developed by Eclipse to impl the OMF in its own
> Eclipse mindset way :), and u can think about it like a framework to
> tie three main points together, that is Java, XML and UML. I kept
> thinking about that even starting from the point David impled the
> WebLogic import feature. I mean we have two approaches here:
>
> 1- To use the EMF to be able to read those XMI easily. But I still
> don't know how exactly to do it - needs some investigation, and I have
> some contacts to ask for that point. But we have to think about using
> EMF in our project, it is not that easy cause we will have to package
> it with OEJB, or the customer will have a headace doing it himself :S.
>
> 2- To use our intelligence and make a JAXB parsers - or anyother
> kind of parsers - so we can read it as a kind of normal XML files to
> get the info from it.
>
>
> Think about it and I will make my contacts to have a more precise
> decision.
>
> On Wed, Jun 18, 2008 at 6:11 PM, Karan Malhi <ka...@gmail.com>
> wrote:
>> I could not find the schemas for the descriptors. Any clue on where
>> I could
>> find them?
>>
>> On Tue, Jun 17, 2008 at 1:04 PM, Karan Malhi
>> <ka...@gmail.com> wrote:
>>
>>> Sure,
>>>
>>> That would be great.
>>>
>>> On Tue, Jun 17, 2008 at 3:02 AM, Mohammad Nour El-Din <
>>> nour.mohammad@gmail.com> wrote:
>>>
>>>> Hi Karan I would like to share this task with you as I have some
>>>> experience with WAS specific DDs.
>>>>
>>>> On Tue, Jun 17, 2008 at 4:16 AM, David Blevins <david.blevins@visi.com
>>>> >
>>>> wrote:
>>>>> On Jun 14, 2008, at 6:08 PM, Karan Malhi wrote:
>>>>>
>>>>>> Where would i start from to add support for Websphere
>>>>>> descriptors?
>>>>>
>>>>> First thing would be to grab the xsds and generate a jaxb tree.
>>>>> You can
>>>>> throw then in a new package at org.apache.openejb.jee.was in the
>>>> openejb-jee
>>>>> module.
>>>>>
>>>>> For the trees that I did, I just grabbed the latest 2.0.x
>>>>> version of the
>>>>> jaxb ri and generated via the command line.
>>>>>
>>>>> -David
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Thanks
>>>> - Mohammad Nour
>>>>
>>>
>>>
>>>
>>> --
>>> Karan Singh Malhi
>>
>>
>>
>>
>> --
>> Karan Singh Malhi
>>
>
>
>
> --
> Thanks
> - Mohammad Nour
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
:D, here is the trick, they are not normal XML files, they are XMI
files - which are still XML files - they are the XML representation of
an EMF model - EMF stand for Eclipse Meta Facility - it is the
customized implementation of the OMG's OMF - Object Meta Facility. EMF
is the frame work developed by Eclipse to impl the OMF in its own
Eclipse mindset way :), and u can think about it like a framework to
tie three main points together, that is Java, XML and UML. I kept
thinking about that even starting from the point David impled the
WebLogic import feature. I mean we have two approaches here:
1- To use the EMF to be able to read those XMI easily. But I still
don't know how exactly to do it - needs some investigation, and I have
some contacts to ask for that point. But we have to think about using
EMF in our project, it is not that easy cause we will have to package
it with OEJB, or the customer will have a headace doing it himself :S.
2- To use our intelligence and make a JAXB parsers - or anyother
kind of parsers - so we can read it as a kind of normal XML files to
get the info from it.
Think about it and I will make my contacts to have a more precise decision.
On Wed, Jun 18, 2008 at 6:11 PM, Karan Malhi <ka...@gmail.com> wrote:
> I could not find the schemas for the descriptors. Any clue on where I could
> find them?
>
> On Tue, Jun 17, 2008 at 1:04 PM, Karan Malhi <ka...@gmail.com> wrote:
>
>> Sure,
>>
>> That would be great.
>>
>> On Tue, Jun 17, 2008 at 3:02 AM, Mohammad Nour El-Din <
>> nour.mohammad@gmail.com> wrote:
>>
>>> Hi Karan I would like to share this task with you as I have some
>>> experience with WAS specific DDs.
>>>
>>> On Tue, Jun 17, 2008 at 4:16 AM, David Blevins <da...@visi.com>
>>> wrote:
>>> > On Jun 14, 2008, at 6:08 PM, Karan Malhi wrote:
>>> >
>>> >> Where would i start from to add support for Websphere descriptors?
>>> >
>>> > First thing would be to grab the xsds and generate a jaxb tree. You can
>>> > throw then in a new package at org.apache.openejb.jee.was in the
>>> openejb-jee
>>> > module.
>>> >
>>> > For the trees that I did, I just grabbed the latest 2.0.x version of the
>>> > jaxb ri and generated via the command line.
>>> >
>>> > -David
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Thanks
>>> - Mohammad Nour
>>>
>>
>>
>>
>> --
>> Karan Singh Malhi
>
>
>
>
> --
> Karan Singh Malhi
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by Karan Malhi <ka...@gmail.com>.
I could not find the schemas for the descriptors. Any clue on where I could
find them?
On Tue, Jun 17, 2008 at 1:04 PM, Karan Malhi <ka...@gmail.com> wrote:
> Sure,
>
> That would be great.
>
> On Tue, Jun 17, 2008 at 3:02 AM, Mohammad Nour El-Din <
> nour.mohammad@gmail.com> wrote:
>
>> Hi Karan I would like to share this task with you as I have some
>> experience with WAS specific DDs.
>>
>> On Tue, Jun 17, 2008 at 4:16 AM, David Blevins <da...@visi.com>
>> wrote:
>> > On Jun 14, 2008, at 6:08 PM, Karan Malhi wrote:
>> >
>> >> Where would i start from to add support for Websphere descriptors?
>> >
>> > First thing would be to grab the xsds and generate a jaxb tree. You can
>> > throw then in a new package at org.apache.openejb.jee.was in the
>> openejb-jee
>> > module.
>> >
>> > For the trees that I did, I just grabbed the latest 2.0.x version of the
>> > jaxb ri and generated via the command line.
>> >
>> > -David
>> >
>> >
>>
>>
>>
>> --
>> Thanks
>> - Mohammad Nour
>>
>
>
>
> --
> Karan Singh Malhi
--
Karan Singh Malhi
Re: websphere descriptors
Posted by Karan Malhi <ka...@gmail.com>.
Sure,
That would be great.
On Tue, Jun 17, 2008 at 3:02 AM, Mohammad Nour El-Din <
nour.mohammad@gmail.com> wrote:
> Hi Karan I would like to share this task with you as I have some
> experience with WAS specific DDs.
>
> On Tue, Jun 17, 2008 at 4:16 AM, David Blevins <da...@visi.com>
> wrote:
> > On Jun 14, 2008, at 6:08 PM, Karan Malhi wrote:
> >
> >> Where would i start from to add support for Websphere descriptors?
> >
> > First thing would be to grab the xsds and generate a jaxb tree. You can
> > throw then in a new package at org.apache.openejb.jee.was in the
> openejb-jee
> > module.
> >
> > For the trees that I did, I just grabbed the latest 2.0.x version of the
> > jaxb ri and generated via the command line.
> >
> > -David
> >
> >
>
>
>
> --
> Thanks
> - Mohammad Nour
>
--
Karan Singh Malhi
Re: websphere descriptors
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi Karan I would like to share this task with you as I have some
experience with WAS specific DDs.
On Tue, Jun 17, 2008 at 4:16 AM, David Blevins <da...@visi.com> wrote:
> On Jun 14, 2008, at 6:08 PM, Karan Malhi wrote:
>
>> Where would i start from to add support for Websphere descriptors?
>
> First thing would be to grab the xsds and generate a jaxb tree. You can
> throw then in a new package at org.apache.openejb.jee.was in the openejb-jee
> module.
>
> For the trees that I did, I just grabbed the latest 2.0.x version of the
> jaxb ri and generated via the command line.
>
> -David
>
>
--
Thanks
- Mohammad Nour
Re: websphere descriptors
Posted by David Blevins <da...@visi.com>.
On Jun 14, 2008, at 6:08 PM, Karan Malhi wrote:
> Where would i start from to add support for Websphere descriptors?
First thing would be to grab the xsds and generate a jaxb tree. You
can throw then in a new package at org.apache.openejb.jee.was in the
openejb-jee module.
For the trees that I did, I just grabbed the latest 2.0.x version of
the jaxb ri and generated via the command line.
-David