how to clean up catalog entries?

[Kiran Bhumana-2]

Once I populate a catalog in the enterprise projects, I don't see a way to remove them or clean the entire catalog. If we do support, how do we do that?

I did try to look in the properties window and I didn't see anything. Shouldn't the list of resolved entries be here? I tried to "clear cache", but nothing happens.

[jdcondor]

Kiran Bhumana wrote:

Once I populate a catalog in the enterprise projects, I don't see a way to remove them or clean the entire catalog.

Not sure how you populate the catalog?
If you use the retriever 'External XML Schema' or 'External WSDL' wizard then the retriever let user specify location to put the retrieved files.  These files are usually shareable (source controlled) and *not* managed by the project catalog. 

If we do support, how do we do that?

I did try to look in the properties window and I didn't see anything. Shouldn't the list of resolved entries be here? I tried to "clear cache", but nothing happens.

'Clear Cache' button only clear all implicitly retrieved files in the shown cache location.  

The above view are entries in project-dir/catalog.xml, and they are produced by explicit import wizard from the editors (schema, wsdl, bpel) or by implicit retriever for import statement with absolute location URL.  You might be using some other import facility that pull the xml files into some locations which are *not* managed by this project catalog.xml. 

-Nam

[Kiran Bhumana-2]

I do like this on a SOA->BPEL project.



My WSDL imports has,
            <xsd:import namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing"
            schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing/"/>

And this will put the file at (files tab)


So far, I have not used the user interface you mention. Can you send some links so I understand the relevance of that functionality? Perhaps I may need it next time.

But still the original question needs to be answered. How do we manage these files?

thanks,
Kiran.

Nam Nguyen wrote:

Kiran Bhumana wrote:

Once I populate a catalog in the enterprise projects, I don't see a way to remove them or clean the entire catalog.

Not sure how you populate the catalog?
If you use the retriever 'External XML Schema' or 'External WSDL' wizard then the retriever let user specify location to put the retrieved files.  These files are usually shareable (source controlled) and *not* managed by the project catalog. 

If we do support, how do we do that?

I did try to look in the properties window and I didn't see anything. Shouldn't the list of resolved entries be here? I tried to "clear cache", but nothing happens.

'Clear Cache' button only clear all implicitly retrieved files in the shown cache location.  

The above view are entries in project-dir/catalog.xml, and they are produced by explicit import wizard from the editors (schema, wsdl, bpel) or by implicit retriever for import statement with absolute location URL.  You might be using some other import facility that pull the xml files into some locations which are *not* managed by this project catalog.xml. 

-Nam

[jdcondor]

This functionality is partially covered by the implicit background retriever (which is part of the project catalog system).
Yes we definitely need to consolidate to eliminate confusion...

-Nam

Kiran Bhumana wrote:

I do like this on a SOA->BPEL project.



My WSDL imports has,
            <xsd:import namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing"
            schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing/"/>

And this will put the file at (files tab)


So far, I have not used the user interface you mention. Can you send some links so I understand the relevance of that functionality? Perhaps I may need it next time.

But still the original question needs to be answered. How do we manage these files?

thanks,
Kiran.

Nam Nguyen wrote:

Kiran Bhumana wrote:

Once I populate a catalog in the enterprise projects, I don't see a way to remove them or clean the entire catalog.

Not sure how you populate the catalog?
If you use the retriever 'External XML Schema' or 'External WSDL' wizard then the retriever let user specify location to put the retrieved files.  These files are usually shareable (source controlled) and *not* managed by the project catalog. 

If we do support, how do we do that?

I did try to look in the properties window and I didn't see anything. Shouldn't the list of resolved entries be here? I tried to "clear cache", but nothing happens.

'Clear Cache' button only clear all implicitly retrieved files in the shown cache location.  

The above view are entries in project-dir/catalog.xml, and they are produced by explicit import wizard from the editors (schema, wsdl, bpel) or by implicit retriever for import statement with absolute location URL.  You might be using some other import facility that pull the xml files into some locations which are *not* managed by this project catalog.xml. 

-Nam

[Belbin, Peter]

I have a web application where I've created a web service.

I now want to relocate that web service to another project.

I see that the context menu when right-clicking the file in the project view does not allow the copy/paste nor delete options.

Ok, I figure it's doing that to protect against breaking other config files that might be related to this class exposing a web service.

So, I remove the import and references to WebMethod and WebService annotations throughout the file.

I notice that this removes the web service details from the Web Services category in the project tree.

However, the file still is shown with the globe icon, and the copy/paste / delete options on the context menu are still greyed out.

This is even after doing a build.

Closing and re-opening the project doesn't seem to make any difference either.

I still can't remove the file, or move it.

Any ideas?

Regards,
Peter.

NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named.  Any use, copying, or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.