-
15. Re: Definition of type of transformation service
Sorry, was offline for a few days.
So, as far as Transformation Service definitions are concerned, I'd guess it's pretty much as you say...
* ServiceName: XYZTransformationService
* ServiceVersion: 2.1
* ServiceType: Transformation
* TransformationSupport:
** 1: A(v1.1) -> C(v4.8)
** 2: C(v4.8) -> A(v1.1)
** 3: H(v1.1) -> P(v4.8)
** etc
Where A, C, H etc is ??? the schema name ???
What does the interface to the registry look like? How are the queries constructed? -
16. Re: Definition of type of transformation service
Do these Transformation Service definitions need to be more explicit in terms of what they say they can transform (from a request response perspective), or are we saying that A(v1.1) -> C(v4.8) always means.. "Can transform A(v1.1) requests into C(v4.8) requests, and C(v4.8) responses into A(v1.1) responses" i.e. supports all transformations required to allow a client that "speaka" A(v1.1) to speak to, and get responses from, a Service that speaks C(v4.8).
Does that make sense? -
17. Re: Definition of type of transformation service
Yes, this is all part of the Contract Definition Language (and query). We're at a point now where we need to cover that before we can really make progress: it's needed for all services, not just transformation. There's already a topic on the forum for it (no activity yet). Let's move the discussion over there.
-
18. Re: Definition of type of transformation service
Sorry Mark, not 100% sure I follow that last post. What are you saying "yes" to, the registry question I think, yeah? Where is this other thread (I see a number of registry related therads if that's what we're talking about)?
I think the other topics can be addressed here though, right? e.g. what exactly does a TransformationSupport definition of the form "A(v1.1) -> C(v4.8)" really mean ala the post I made before your last post? -
19. Re: Definition of type of transformation service
"tfennelly" wrote:
Sorry Mark, not 100% sure I follow that last post. What are you saying "yes" to, the registry question I think, yeah? Where is this other thread (I see a number of registry related therads if that's what we're talking about)?
I think the other topics can be addressed here though, right? e.g. what exactly does a TransformationSupport definition of the form "A(v1.1) -> C(v4.8)" really mean ala the post I made before your last post?
I meant that discussions about the format of the general contract definition language should go http://www.jboss.org/index.html?module=bb&op=viewtopic&t=80688
We can talk about what specific information we need for the transformation service here, but I'd like to get discussions about how we represent information elsewhere: makes it easier to track.
Does that make sense?
Apologies in advance if I'm less responsive on the forums than usual, but I'm at JavaOne this week. Back next week. -
20. Re: Definition of type of transformation service
OK, back from JavaOne. Lots of interest in what we're doing with JBossESB.
Tom, can you take a go at writing down precisely what information we need to provide in order to uniquely identify a type of transformation? We can approach this from an English language perspective initially and then translate that into a contract (probably some dialect using XML) later. It may be better to do this on a wiki page, linked from the JBossESB wiki page. -
22. Re: Definition of type of transformation service
Thanks Tom, it looks good. I've got some specific comments, which I'll stick down asap.
-
23. Re: Definition of type of transformation service
Done:
http://wiki.jboss.org/wiki/Wiki.jsp?page=TransformationServices
This page is also linked off the JBossESB wiki home.
Did the tutorial make sense??? If not, I'd like to know how to improve it! -
24. Re: Definition of type of transformation service
Sorry, last post is on the wrong thread. Please ignore. Duh!