I haven't seen use of UUIDs (GUIDs) per
http://www.opengroup.org/dce/info/draft-leach-uuids-guids-01.txt
for js unique id's.
I use them whenever I need truly unique (even cross system) identifiers.
Windows clsid is a UUID.
UDDI etc ... they're used in many applications and look like:
ex: E00A4490-C7E0-11D7-8CAB-C94877403D5C
(always 36 char when string representation)

I'd like to recommend adopting UUID use where applicable, if I may?
Or perhaps they are in use in js... I just haven't seen them.
I prefer uuid to rmi.uid.

If it helps:
UUID code from axis csv:
http://cvs.apache.org/viewcvs.cgi/xml-axis/java/src/org/apache/axis/componen
ts/uuid/
Package summary
http://dwdemos.dfw.ibm.com/wstk/common/wstkdoc/axis/docs/apiDocs/org/apache/
axis/components/uuid/package-summary.html

I was working with the WebPagePortlet2 and I was looking for a class such as
org.apache.axis.components.uuid.SimpleUUIDGen in the js
org.apache.jetspeed.util directory but didn't see one.
Perhaps this could be added if it will be used else where?



-----Original Message-----
From: Luta, Raphael (VUN) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 05, 2003 10:13 AM
To: 'Jetspeed Developers List'
Subject: RE : RE : RE : [J2] New Page API committed to CVS



Right now, I'm simply using JetspeedIDGenerator, which
We may possibly extend to provide "scoped" unique ID, like:

 getPortalUniqueID(String seed)

to get a guaranteed unique portal-wide ID using the provided seed. We could
also have:

 getUserUniqueID(User user, String seed)

And so on...

What do you think ?

--
Rapha�l Luta - [EMAIL PROTECTED]
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/

> -----Message d'origine-----
> De : Weaver, Scott [mailto:[EMAIL PROTECTED] > Envoy� : mardi 5 ao�t 2003
16:11
> � : 'Jetspeed Developers List'
> Objet : RE: RE : RE : [J2] New Page API committed to CVS
> > > <component instance ID>
> > I'm guessing this ties to component defined within the PSML.  > How are
you generating this?  Or could we be using the UID > class to generate this?
> > *===================================*
> * Scott T Weaver������������������� *
> * Jakarta Jetspeed Portal Project�� *
> * [EMAIL PROTECTED] *
> *===================================*
> � > > > > -----Original Message-----
> > From: Luta, Raphael (VUN) [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, August 05, 2003 9:49 AM
> > To: 'Jetspeed Developers List'
> > Subject: RE : RE : [J2] New Page API committed to CVS
> > > > > > De : Weaver, Scott [mailto:[EMAIL PROTECTED]
> > > > > Envoy� : mardi 5 ao�t 2003 15:24
> > > � : 'Jetspeed Developers List'
> > > Objet : RE: RE : [J2] New Page API committed to CVS
> > >
> > > > >
> > > > > > That's cool because I don't plan to have any portlet
> > > > > preference stored
> > > > > > in PSML this time around :) However I do need a way to uniquely
> > > > > > reference a PortletEntity
> > > >
> > > > > > from the page markup. Is a simple portletEntity ID enough as a >
> > > key,
> > >
> > > > > The PortletEntity's id is a composite key, "portlet
> > > > > name":"portlet id":"instance name"
> > >
> > > > > "instance name" being the name defined in the PSML.
> > > > > "portlet id" is guaranteed unique as it serves also as the PK
> > > > > in the PORTLET_DEFINITION table.
> > >
> > > > > > Right now, I've assumed that I would be able to use the
following
> > > > tuple to uniquely retrieve any graphic component instance:
> > > > <component registry name>:<component name>:<component instance ID>
> > > > with the assumption that the instance ID would be > portal-wide
unique.
> > > > For portlets, that would be for example: <Portlet:RSSPortlet:194536>
> > > > I'd really love not have to expose the portlet ID, since it's an > >
Impelmentation-specific value, and keep the portlet name as the > >
Functional key in the page description. Also note, that I > don't plan > >
to have any instance name assigned, since I can't see any > use for it > >
actually and an instance ID seems more
> > > > generally useful.
> > > > > We may need to extend the PorletEntity's id to include an
> > > > > information that makes it unique portal-wide.  I was also
> > > > > thinking about using the java.rmi.server.UID to create
> > > > > additional "salt" for the PortletEntity's id.
> > >
> > > > >
> > > > > > +1
> > > > --
> > Rapha�l Luta - [EMAIL PROTECTED]
> > Jakarta Jetspeed - Enterprise Portal in Java > >
http://jakarta.apache.org/jetspeed/
> > > > **********************************************
> > Vivendi Universal - HTTP://www.vivendiUniversal.com:
> > > > The information transmitted is intended only for the person > or
entity > > to which it is addressed and may contain confidential and/or > >
privileged material of Vivendi Universal which is for the exclusive > > use
of the individual designated above as the recipient. > Any review, > >
retransmission, dissemination or other use of, or taking of > any action > >
in reliance upon,
> > > > this information by persons or entities other than the intended > >
recipient
> > > > is prohibited. If you received this in error, please contact > >
immediately
> > > > the sender by returning e-mail and delete the material from any > >
computer.
> > > > If you are not the specified recipient, you are hereby > notified
that > > all
> > > > disclosure, reproduction, distribution or action taken on > the
basis of > > this
> > > > message is prohibited.
> > > >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: > [EMAIL PROTECTED]
>
**********************************************
Vivendi Universal - HTTP://www.vivendiUniversal.com: The information
transmitted is intended only for the person or entity
to which it is addressed and may contain confidential and/or privileged
material of Vivendi Universal which is for the exclusive use of the
individual designated above as the recipient. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact immediately the
sender by returning e-mail and delete the material from any computer. If you
are not the specified recipient, you are hereby notified that all
disclosure, reproduction, distribution or action taken on the basis of this
message is prohibited.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to