Could you explain what would these two technologies (Jini, UDDI) be responsible for? I guess it would be possible to publish the UUID of a Jini service into the UDDI registry and then lookup the service from available Jini Lookup Services, but that still doesn't make it a web service if the actual Jini service is being invoked with an RMI call, a raw socket connection, or something else which isn't SOAP.
I think you are going to always need an interface component that handles the "web service" to JINI translation. For example, I have a servlet that takes an HTML form request and creates a Java object that is sent via JINI to a JavaSpace. Another process looks for requests showing up in the space - does the required processing and writes the result to the space. The servlet then picks up the result via the JINI connection to the JavaSpace and creates the HTML response. This could just as easily work with a SOAP request and a published WSDL. Bill