This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Retriever API should expose an action to refresh already retrieved files in a project. This should be done by reverse looking up the entries in the catalog file, getting the original source URL and retrieving them back using retriever API.
I need the client of this action to tell me where and how exactly this action will be used.... The options as I see are: 1. This action will be shown to the user on the project node, upon execution, will refresh all the absolute URL entries that is present in the project wide Catalog file. 2. This action will be shown only for the files (schema/wsdl) which have reference to external entities and whose original URL and cached location is present in the projectwide catalog. The action would then download and refresh only that URL (with its closure) and cache. Please record your option in this bug.
It was agreed that this is more like an enhancement. So, marking this as an enhancement and will revisit later.
What we implemented in Basic WS Support is : Refresh Client and Refresh Service actions on WS Client Node/WS Node. This basically calls the Retriever.retrieveResource() again and local xml artifacts are replaced by the originals. Then, java artifacts are re-generated again. Personally, I don't see the sense to have the refresh action in API.
Lets reopen if there is a need for it.