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
<[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>
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 <[EMAIL PROTECTED]
>
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 <[EMAIL PROTECTED]
>
wrote:
Sure,
That would be great.
On Tue, Jun 17, 2008 at 3:02 AM, Mohammad Nour El-Din <
[EMAIL PROTECTED]> 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
<[EMAIL PROTECTED]>
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
