Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: skiwi on October 20, 2010, 06:38:22 am

Title: Enterprise Architect protocol handler
Post by: skiwi on October 20, 2010, 06:38:22 am: Geert brought to my attention (http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1287455954/4#4) the Enterprise Architect protocol handler (http://community.sparxsystems.com/news/091109/enterprise-architect-protocol-handler-beta-release).

I'm curious to know about anyone's experiences using it.
From what I can see from the manual to be of use it will have to be installed on all EA users machines.

I'm also curious to know if anyone has integrated it on the server side of a website to provide 'live' access to an EA model?

tia

Simon
Title: Re: Enterprise Architect protocol handler
Post by: Geert Bellekens on October 20, 2010, 04:20:14 pm: Simon,

I've installed in on my pc to do some testing.
I'm planning to use it in a new document generator I'm about to write, so users can visit the part they are reading about in EA.

Geert
Title: Re: Enterprise Architect protocol handler
Post by: lubos on October 20, 2010, 05:08:32 pm: I have also installed this extension to try its functionality yesterday. My experience is following:

Internet Explorer: hyperlinks work
Chrome: hyperlinks do not work
MSWord: hyperlinks fail

Functionality in Word is very important for me, but it is still beta so may be it will be usable later.
Meantime we have already created simple VB script in Word that highlights referenced element in enterprise architect based on the guid stored in hyperlink texts in Word document.
Title: Re: Enterprise Architect protocol handler
Post by: Geert Bellekens on October 20, 2010, 05:17:30 pm: I've just done a little test in Word (2007) and it worked like a charm.

Geert
Title: Re: Enterprise Architect protocol handler
Post by: lubos on October 20, 2010, 07:10:35 pm: I have tested it again and I think the problem is that a reference text is bigger than dialog for setting hyperlink adress enables to type into -- so the hyperlink is shortened

example:

ea://Model?c=YwodwmcbyEhbyqGQ6OFyrwwsiihGQ0MSl4y41%2fMG%2fk8oBAizw2THtSd1KaDrc4uIp%2fKLCqXl28yAAPDCuXikDFwQQP0i3avnHx9SUCHmYkdsAddgf9Yd5No3I0GgHSnXC%2fxkJVo%2fPvcyGDOkdINSbghD8Tf5aVJgJQoSJZcWv1J92UR%2fzZPsu9cCCAHgktXusnNj8n5hbJgGlcwykfr7KdeuuzMUkO6AKQEdNjZmJTsw%3d&p=229CDCF9A5D9441f9EB0886DCF01528D
Title: Re: Enterprise Architect protocol handler
Post by: Geert Bellekens on October 20, 2010, 07:24:58 pm: Yes, that is probably the issue.
The reason my test worked was because the link is shorter:

ea://eap?c=iuzDLw%2bibrBdR53Ng35UBJ5N%2ffoSY1vWk8owO6j3tRjDZAScEpNBlRCo9lRG5Bu%2btgCKBDlfTDrI%2fVNI4rdf2qUxbX4M49mACc9zzlj2cb8dSVGx5D1%2bIPxeIH1e662STDV3HENDlsKH%2fk4Rg0gVPQ%3d%3d&p=5B484BA68DCA414b8DBB9D13255A49F1

This probably depends on the settings for the protocolhandler, I chose "From current Repository"

Geert

Geert
Title: Re: Enterprise Architect protocol handler
Post by: lubos on October 20, 2010, 07:58:55 pm: my setting is the same, but the connection string is just longer ...
I will try to play with another settings but I was not successful with them yet, since it always try to open new EA instance instead of using the already opened one.