RE: [ebxml-cppa] Why is there no port attribute in the protocolType.type orendpointType.type elements?

["Dale Moberg" <dmoberg@cyclonecommerce.com>]

Hi Sacha,

Steve Capell is correct; CPPA currently handles endpoint information by
using a URL. But we are working on the extensibility points
for the 2.1 maintenance version so if there are needs for 
generalizations it is a good time to mention them. There
are other mechanisms under discussion in the WS arena for
referencing services and endpoints. Mostly these are for runtime
exchange
of information. Perhaps we need to document which types of runtime
mechanism
are used to exchange endpoint information? 

Dale Moberg


-----Original Message-----
From: Steve Capell [mailto:steve.capell@redwahoo.com] 
Sent: Wednesday, September 08, 2004 3:03 AM
To: 'Sacha Schlegel'; 'ebxml-cppa'
Subject: RE: [ebxml-cppa] Why is there no port attribute in the
protocolType.type orendpointType.type elements?


Wouldn't you just specify that in the URL?  Eg to specify port 8888 for
http:  http://b2b.acme.com:8888/invoiceService

Regards,

Steve Capell
Red Wahoo Pty Ltd
+61 410 437854

-----Original Message-----
From: Sacha Schlegel [mailto:sacha_oasis@schlegel.li] 
Sent: Wednesday, 8 September 2004 7:55 PM
To: ebxml-cppa
Subject: [ebxml-cppa] Why is there no port attribute in the
protocolType.type orendpointType.type elements?

Hi CPPA team

Just doing some tests I am wondering where people can set ports (eg http
goes to port 80) in a CPP or CPA. What if they want to set specific
ports, eg HTTP goes to port 143534

The points where I was expecting this information were

protocolType.type or
endpointType.type

Am I missing something?

Kind regards

Sacha



To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/ebxml-cppa/members/leave_wo
rkgroup.php.