Re: [platform-update-dev] Update Server Redirection (site.xml)

["Brooke Kuhlmann" <Brooke_Kuhlmann@xxxxxxx>]

I noticed in an earlier thread that Elek mentioned the <archive> tag could 
be used within the site.xml for defining plugins and data that might 
reside in a different location other than the site.xml.  This seems like 
it would solve the problem.  According to the eclipse spec, you define it 
as:

<archive path="c:\updates\plugins" 
url="http://www.server-two.com/updates/plugins"/>

?maybe?

Anyone have an example of this?  When I test this, I can see the site.xml 
loads correctly and I have no parsing problems.  However, I still fail 
during mid-process on the install where it comes back saying that my 
plugins can't be found.  What's interesting is that the path it returns 
back to me is not that path I specified in the <archive> tag but the path 
to where the site.xml exists which is on www.server-one.com.  Entirely the 
wrong server.

Still stumped...

-Brooke-





"Brooke Kuhlmann" <Brooke_Kuhlmann@xxxxxxx>
Sent by: platform-update-dev-admin@xxxxxxxxxxx
11/14/2002 03:41 PM
Please respond to platform-update-dev

 
        To:     platform-update-dev@xxxxxxxxxxx
        cc: 
        Subject:        [platform-update-dev] Update Server Redirection (site.xml)

Hello,

We have update and discovery labels within our primary feature that point 
to a specific server.  Example:

http://www.server-one.com/updates

However, we want to redirect the address that the user goes to above to a 
different server.  Example:

http://www.server-two.com/updates

We are doing this by putting the site.xml on server-one and editing the 
site.xml so that each feature url points to server-two.  Example:

<feature 
url="http://www.server-two.com/updates/features/my.feature_1.0.0.jar";>

This seems to work because within the IDE, I can see the site.xml load 
with all the features and categories.  Unfortunately, when I click on the 
"install" button I get halfway through the feature install and start 
getting error reports saying that the feature is missing it's plugins.  I 
have verified that the feature directory, and plugins directory on 
server-two are at the same level and that all .jar files are there.

Any ideas why this does not work?

Thanks for any help you can provide,
Brooke

_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev