You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Harvey Jiang (JIRA)" <ju...@ws.apache.org> on 2005/01/06 07:25:13 UTC

[jira] Created: (JUDDI-48) Ant tasks for managing juddi repository

Ant tasks for managing juddi repository 
----------------------------------------

         Key: JUDDI-48
         URL: http://issues.apache.org/jira/browse/JUDDI-48
     Project: jUDDI
        Type: New Feature
    Reporter: Harvey Jiang
 Assigned to: Steve Viens 


Organisations provide more Web Services to their customers this year or after and will uses UDDI to store information of these services.  To achieve automatic system testing of Web Services with integration of juddi, ant tasks are required to manage a juddi repository.  These tasks may be:
 
-save_business
-save_service
-save_tmodel
 
-delete_business
-delete_service
-delete_tmodel
 
-find_business
-find_service
-find_tmodel
 
Every of save_xxx tasks at least provide two attributes;
   -source:  a xml file used to populate a juddi repository
   -destination: a xml file to store a value returned by the juddi repository
 
Every of delete_xxx tasks at least provide one attribute:
   -source: a xml file to store information used to delete a business entity or a service or a tModel 
 
Every of find_xxx tasks at least provide two attributes;
   -source:  a xml file used to query a juddi repository
   -destination: a xml file to store a value returned by the juddi repository
 
Note: xml schema used above should be identical to one used by data structures in the uddi specification.

In addition, as Steve suggested, ant tasks should cover a jUDDI-specific functions and the others such as publisher assertion functions which I didn't listed above.
 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Closed: (JUDDI-48) Ant tasks for managing juddi repository

Posted by "Kurt Stam (JIRA)" <ju...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/JUDDI-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt Stam closed JUDDI-48.
--------------------------

    Assignee: Kurt Stam  (was: Steve Viens)

> Ant tasks for managing juddi repository
> ---------------------------------------
>
>                 Key: JUDDI-48
>                 URL: https://issues.apache.org/jira/browse/JUDDI-48
>             Project: jUDDI
>          Issue Type: New Feature
>            Reporter: Harvey Jiang
>            Assignee: Kurt Stam
>            Priority: Minor
>             Fix For: 2.0rc6
>
>
> Organisations provide more Web Services to their customers this year or after and will uses UDDI to store information of these services.  To achieve automatic system testing of Web Services with integration of juddi, ant tasks are required to manage a juddi repository.  These tasks may be:
>  
> -save_business
> -save_service
> -save_tmodel
>  
> -delete_business
> -delete_service
> -delete_tmodel
>  
> -find_business
> -find_service
> -find_tmodel
>  
> Every of save_xxx tasks at least provide two attributes;
>    -source:  a xml file used to populate a juddi repository
>    -destination: a xml file to store a value returned by the juddi repository
>  
> Every of delete_xxx tasks at least provide one attribute:
>    -source: a xml file to store information used to delete a business entity or a service or a tModel 
>  
> Every of find_xxx tasks at least provide two attributes;
>    -source:  a xml file used to query a juddi repository
>    -destination: a xml file to store a value returned by the juddi repository
>  
> Note: xml schema used above should be identical to one used by data structures in the uddi specification.
> In addition, as Steve suggested, ant tasks should cover a jUDDI-specific functions and the others such as publisher assertion functions which I didn't listed above.
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: juddi-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: juddi-dev-help@ws.apache.org


[jira] Updated: (JUDDI-48) Ant tasks for managing juddi repository

Posted by "Steve Viens (JIRA)" <ju...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/JUDDI-48?page=history ]

Steve Viens updated JUDDI-48:
-----------------------------

    Priority: Minor  (was: Major)

Lowering priority.

> Ant tasks for managing juddi repository
> ---------------------------------------
>
>          Key: JUDDI-48
>          URL: http://issues.apache.org/jira/browse/JUDDI-48
>      Project: jUDDI
>         Type: New Feature
>     Reporter: Harvey Jiang
>     Assignee: Steve Viens
>     Priority: Minor

>
> Organisations provide more Web Services to their customers this year or after and will uses UDDI to store information of these services.  To achieve automatic system testing of Web Services with integration of juddi, ant tasks are required to manage a juddi repository.  These tasks may be:
>  
> -save_business
> -save_service
> -save_tmodel
>  
> -delete_business
> -delete_service
> -delete_tmodel
>  
> -find_business
> -find_service
> -find_tmodel
>  
> Every of save_xxx tasks at least provide two attributes;
>    -source:  a xml file used to populate a juddi repository
>    -destination: a xml file to store a value returned by the juddi repository
>  
> Every of delete_xxx tasks at least provide one attribute:
>    -source: a xml file to store information used to delete a business entity or a service or a tModel 
>  
> Every of find_xxx tasks at least provide two attributes;
>    -source:  a xml file used to query a juddi repository
>    -destination: a xml file to store a value returned by the juddi repository
>  
> Note: xml schema used above should be identical to one used by data structures in the uddi specification.
> In addition, as Steve suggested, ant tasks should cover a jUDDI-specific functions and the others such as publisher assertion functions which I didn't listed above.
>  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Resolved: (JUDDI-48) Ant tasks for managing juddi repository

Posted by "Kurt Stam (JIRA)" <ju...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/JUDDI-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt Stam resolved JUDDI-48.
----------------------------

       Resolution: Invalid
    Fix Version/s: 2.0rc6

Closing this issue since we don't even support ant anymore. What we really need is a good UI.

> Ant tasks for managing juddi repository
> ---------------------------------------
>
>                 Key: JUDDI-48
>                 URL: https://issues.apache.org/jira/browse/JUDDI-48
>             Project: jUDDI
>          Issue Type: New Feature
>            Reporter: Harvey Jiang
>            Assignee: Steve Viens
>            Priority: Minor
>             Fix For: 2.0rc6
>
>
> Organisations provide more Web Services to their customers this year or after and will uses UDDI to store information of these services.  To achieve automatic system testing of Web Services with integration of juddi, ant tasks are required to manage a juddi repository.  These tasks may be:
>  
> -save_business
> -save_service
> -save_tmodel
>  
> -delete_business
> -delete_service
> -delete_tmodel
>  
> -find_business
> -find_service
> -find_tmodel
>  
> Every of save_xxx tasks at least provide two attributes;
>    -source:  a xml file used to populate a juddi repository
>    -destination: a xml file to store a value returned by the juddi repository
>  
> Every of delete_xxx tasks at least provide one attribute:
>    -source: a xml file to store information used to delete a business entity or a service or a tModel 
>  
> Every of find_xxx tasks at least provide two attributes;
>    -source:  a xml file used to query a juddi repository
>    -destination: a xml file to store a value returned by the juddi repository
>  
> Note: xml schema used above should be identical to one used by data structures in the uddi specification.
> In addition, as Steve suggested, ant tasks should cover a jUDDI-specific functions and the others such as publisher assertion functions which I didn't listed above.
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: juddi-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: juddi-dev-help@ws.apache.org