Home » Modeling » OCL » How to convert Self.description to xsd::DOMElement
|
Re: How to convert Self.description to xsd::DOMElement [message #503268 is a reply to message #502422] |
Fri, 11 December 2009 16:08 |
|
--=-HypWW9lsGrFSVZrZTimg
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Hi, Kumar,
OCL has nothing to do with XSD, except insofar as it may be working with
an Ecore model imported from an XSD. But even so, there are XSD
constructs such as feature maps that have no correspondent in EMOF/UML
and thus aren't understood by OCL.
In any case, OCL doesn't modify models, so you wouldn't use it to create
new XSD annotations anyway.
Cheers,
Christian
On Tue, 2009-12-08 at 02:41 -0500, Kumar wrote:
> Hi
>
> I want to know type casting self.descriiption (OCL type String) to xsd::DOMElement for creating userInformation for annotation element.
>
> Regards,
> Kumar
--=-HypWW9lsGrFSVZrZTimg
Content-Type: text/html; charset="utf-8"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.24.1.1">
</HEAD>
<BODY>
Hi, Kumar,<BR>
<BR>
OCL has nothing to do with XSD, except insofar as it may be working with an Ecore model imported from an XSD. But even so, there are XSD constructs such as feature maps that have no correspondent in EMOF/UML and thus aren't understood by OCL.<BR>
<BR>
In any case, OCL doesn't modify models, so you wouldn't use it to create new XSD annotations anyway.<BR>
<BR>
Cheers,<BR>
<BR>
Christian<BR>
<BR>
<BR>
On Tue, 2009-12-08 at 02:41 -0500, Kumar wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Hi
I want to know type casting self.descriiption (OCL type String) to xsd::DOMElement for creating userInformation for annotation element.
Regards,
Kumar
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>
--=-HypWW9lsGrFSVZrZTimg--
|
|
| |
Re: How to convert Self.description to xsd::DOMElement [message #503494 is a reply to message #503426] |
Mon, 14 December 2009 13:46 |
|
--=-Dkr1dLB7knT4QLOaiVFZ
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Hi, Kumar,
I'm sure there must be ... there are all kinds of libraries and APIs
that deal with XML and XSD. But your question is too open-ended to
answer usefully. Are you needed to manipulate XSD schema files? In
that case, the Eclipse WebTools Project might have something that helps.
Do you need to create XSD files to work with them in a modeling context?
Then maybe EMF's XSD Infoset Model will help. It really depends on what
you need to do with these documents.
Cheers,
Christian
On Mon, 2009-12-14 at 00:38 -0500, Kumar wrote:
> Thanks for your replay Christian,
>
> Is there any way to include annotations using Java libraries
> ?
>
>
> Regards,
> Kumar
>
--=-Dkr1dLB7knT4QLOaiVFZ
Content-Type: text/html; charset="utf-8"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.24.1.1">
</HEAD>
<BODY>
Hi, Kumar,<BR>
<BR>
I'm sure there must be ... there are all kinds of libraries and APIs that deal with XML and XSD. But your question is too open-ended to answer usefully. Are you needed to manipulate XSD schema files? In that case, the Eclipse WebTools Project might have something that helps. Do you need to create XSD files to work with them in a modeling context? Then maybe EMF's XSD Infoset Model will help. It really depends on what you need to do with these documents.<BR>
<BR>
Cheers,<BR>
<BR>
Christian<BR>
<BR>
On Mon, 2009-12-14 at 00:38 -0500, Kumar wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Thanks for your replay Christian,
Is there any way to include annotations using Java libraries
?
Regards,
Kumar
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>
--=-Dkr1dLB7knT4QLOaiVFZ--
|
|
| |
Re: How to convert Self.description to xsd::DOMElement [message #503725 is a reply to message #503639] |
Tue, 15 December 2009 14:04 |
|
--=-quJleOKs2eIebp7Kvt5e
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Hi, Kumar,
Now I understand what you are trying to accomplish! Thanks.
Yes, the QVT OML's experssion language is based on OCL. So, you will
need an Ecore model of the WSDL for starters, in order to generate an
instance of it from your UML inputs in your transformation. Probably
the Eclipse WebTools project or maybe the SOA Tools project has such a
model. I don't actually know.
Then, it should just be a matter of ensuring that the mappings for
source elements that have descriptions create annotations on the target
elements and set the details accordingly. How easy that will be to work
with in the output model depends on how XSD-ish that model is. Because
XSD is oriented more towards the shape of an XML serialization than data
modeling, with concepts that have no correspondence in EMOF (hence
neither OCL nor QVT), it might be tricky.
The M2M newsgroup will be able to help with specifics of formulating
your QVT mappings and the suppliers of the WSDL model can help you to
work with that.
Cheers,
Christian
On Mon, 2009-12-14 at 19:46 -0500, Kumar wrote:
> HI,
>
> My aim is to annotating the XSD.
>
>
> For UML to WSDL transformation using QVT (The language implementation is based on an OMG document ptc/05-11-01 (MOF 2.0 Query/View/Transformation final adopted specification). The QVT source will be use in Borland Together for transform UML model into WSDL
> definition.
>
> I have to add annotations to the schemas[Element Declaration type].
>
> Regards,
> Kumar
>
>
--=-quJleOKs2eIebp7Kvt5e
Content-Type: text/html; charset="utf-8"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.24.1.1">
</HEAD>
<BODY>
Hi, Kumar,<BR>
<BR>
Now I understand what you are trying to accomplish! Thanks.<BR>
<BR>
Yes, the QVT OML's experssion language is based on OCL. So, you will need an Ecore model of the WSDL for starters, in order to generate an instance of it from your UML inputs in your transformation. Probably the Eclipse WebTools project or maybe the SOA Tools project has such a model. I don't actually know.<BR>
<BR>
Then, it should just be a matter of ensuring that the mappings for source elements that have descriptions create annotations on the target elements and set the details accordingly. How easy that will be to work with in the output model depends on how XSD-ish that model is. Because XSD is oriented more towards the shape of an XML serialization than data modeling, with concepts that have no correspondence in EMOF (hence neither OCL nor QVT), it might be tricky.<BR>
<BR>
The M2M newsgroup will be able to help with specifics of formulating your QVT mappings and the suppliers of the WSDL model can help you to work with that.<BR>
<BR>
Cheers,<BR>
<BR>
Christian<BR>
<BR>
<BR>
On Mon, 2009-12-14 at 19:46 -0500, Kumar wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
HI,
My aim is to annotating the XSD.
For UML to WSDL transformation using QVT (The language implementation is based on an OMG document ptc/05-11-01 (MOF 2.0 Query/View/Transformation final adopted specification). The QVT source will be use in Borland Together for transform UML model into WSDL
definition.
I have to add annotations to the schemas[Element Declaration type].
Regards,
Kumar
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>
--=-quJleOKs2eIebp7Kvt5e--
|
|
|
Goto Forum:
Current Time: Mon Sep 23 08:05:37 GMT 2024
Powered by FUDForum. Page generated in 0.04189 seconds
|