Re: [Soaplab2-dev] Re: Soaplab-two-dev digest, Vol 1 #3 - 1 msg

[Martin S. <se...@eb...>]

My 2c's are:

> What (in basic terms) is the "Soaplab build.xml file" ?
>
   It is a configuration file for Ant. It defines various tasks that the
Ant can do for us.
 
> Would EMBOSS (for example) be a "service group" ?
> 
   No, the "service group" would be identical what you can find in the ACD
files in application/groups key.

> What is the "service container" in the deplyoment component ?
> 
   I guess it is a file with everything needed for a services (including
java classes and configuration files, like its XML files, etc.)

> If an administrator deployed an archive file by copying the archive file to the Axis2
> services repository, or by using the Axis2 administration tools, would these services
> later be visible to the "service explorer" component ?
> 
   Yes, it will be visible to "service client" component (and very
probably also to "service administrator" component - but that has to be
yet defined).

> It's more obvious to me now how the dashboard and acdtools / JACD fit together. The
> Service Editor and JACD-GUI have common ground, but I face an easier proposition
> because JACD-GUI only need support what can be defined in an ACD file / by the XML-ACD
> schema, whereas the service editor needs (presumably) to handle stuff outside that
> scope / in an extended schema.
>
   No, my vision of a service editor is that it handles and edit ACD files
in a user-friendly GUI. I think that the service editor in the dashboard
will use your JACD-GUI as much as possible. I do not recommend to Mahmud
to spend *any* time of a service editor now. We should wait for your
JACD-GUI and to see how it can be used for the dashboard.
 
> Both might need to handle dependencies between options of the type, "The value of option X
> depends on the the value of option Y" - not easy, perhaps we could help each other with that
> part?
>
   That's definitely an easy thing (I know it because I have never
implemented in Soaplab). Perhaps this will need even some chnages (some
additional tags and attributes) in the Soaplab XML files. Any suggestion
from you is welcome here.

> Last thought is that it might be sensible if the XML schema used by SOAPLAB (or indeed
> any interface to EMBOSS) was managed as an extension to the (more basic) ACD-XML schema.
>
   You said it already before. I still need to be convinced that there is
a difference between them. If ACD is just for EMBOSS then yes, there will
be a difference, but I considered always to have ACD for any command-line
application - so its XML schema should be actually thye same as the
Soaplab one.

   Cheers,
   Martin

-- 
Martin Senger
   email: mar...@gm...
   skype: martinsenger