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 <[EMAIL PROTECTED]> 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 > <[EMAIL PROTECTED]> 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 >> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> >>>>> 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 < >>>>>> [EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> >>>>>>> wrote: >>>>>>>> >>>>>>>> Sorry, >>>>>>>> >>>>>>>> Obviously didn't realize that . Thanks for catching that :) >>>>>>>> >>>>>>>> On Sun, Jun 22, 2008 at 5:05 PM, David Blevins >>>>>>>> <[EMAIL PROTECTED]> >>>>>>>> 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 < >>>>>>>>>> [EMAIL PROTECTED]> 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 >>>>>>>>>>> <[EMAIL PROTECTED]> 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 >>>>>>>>>>>> <[EMAIL PROTECTED]> 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 < >>>>>>> >>>>>>> [EMAIL PROTECTED]> >>>>>>>>>>>>>> >>>>>>>>>>>>>> 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
