Apache jUDDICommunity Documentation  Chapter 8. UDDI Annotations
8.1. Introduction 8.2. UDDIService Annotation 8.3.
UDDIServiceBinding Annotation 8.4. WebService Example 8.5.
CategoryBag Attribute  Conventionally Services (BusinessService)
and their EndPoints (BindingTemplates) are registered to a UDDI
Registry using a GUI, where an admin user manually adds the
necessary info. This process tends to make the data in the
Registry rather static and the data can grow stale over time. To
make the data in the UDDI more dynamic it makes sense to
register and EndPoint (BindingTemplate) when it comes online,
which is when it gets deployed. The UDDI annotations are
designed to just that: register a Service when it get deployed
to an Application Server. There are two annotations:
UDDIService, and UDDIServiceBinding. You need to use both
annotations to register an EndPoint. Upon undeployment of the
Service, the EndPoint will be de-registered from the UDDI. The
Service information stays in the UDDI. It makes sense to lea