Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EPF » Possible EPF 1.2 side effect on published web site ? different naming convention + change in ID
Possible EPF 1.2 side effect on published web site ? different naming convention + change in ID [message #581074] Mon, 06 August 2007 09:36
Karim Benameur is currently offline Karim Benameur
Messages: 20
Registered: July 2009
Junior Member
Hi all,

I noticed a possible side effect due to the migration to the new EPF 1.2.

Some of the web pages have now have a different naming & ID.

For example for each discipline we provided a direct link to a custom
categorie:

* before 1.2 :
arch_task_container\customcategories\arch,_jBFJoCTGEdyJ0P6WN Il8_Q.html
* after 1.2 :
arch_task_container\customcategories\arch_D5639D6C.html

All direct links to these web pages are now broken. They have to be updated.

Seems that it is a very bad idea to use direct links to these web pages
as there is no garantee that the name will not change in the future.
Or may be I missed something ;)

Any ideas concerning a way to have a more stable web page access ?
I was thinking about renaming or have a redirection of some sort ...

May be a publishing option for these pages that will be used externally
can be a possible EPF evolution ?

What are the possible scenario that can lead to a change ?

- Import / export ? Upgrade to a new version ?...


What are the web pages that are impacted ?
- All ?

Sorry for asking all these questions !!!

Best Regards
Previous Topic:Any ideas to automate the publication ?
Next Topic:Eclipse shell sharing with EPF Composer 1.2: an example
Goto Forum:
  


Current Time: Wed Apr 23 19:44:17 EDT 2014

Powered by FUDForum. Page generated in 0.01782 seconds