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.
Currently if I create a variable whose type comes from a schema in the global catalog, an import statement is created in the BPEL file, but the actual file is not present anywhere in the project (and its catalog). We should rethink this behavior as it is likely to often break the runtime. Especially as we broaden the set of schemes available in the catalog.
Vladimir, please take a look.
Looks like feature which should be discussed in details, requirements must be specified and this task will be passed for XML team to implement it in Catalog [Support]/ Retriever modules.
Kirill, please, provide requirements for XML team which we discussed on Friday, October 24 on Referenced meeting.
Yeah, sorry for the delay. Our discussions boiled down to two things: 1) The BPEL global catalog acts as a sort of centralized storage of schemes (and potentially other XML-based resources) which are readily available for reuse @ development time. This is a good thing, but we need to allow the developers to manage this storage, i.e. add, edit, update, and remove entries. I believe that the catalog should be visualized somehow in the Service tab and provide the required actions for the users. 2) We need to have an easy way of "localizing" the resources from the catalog. I.e. whenever a user imports a catalog-based schema to one of his files, we need to put a copy of it locally (within the project, but outside the actual sources) and to reference it properly from the project's catalog. This way the resource will be correctly packaged @ build time and will be available to the target runtime system, also doing this will help us ensure the portability of projects between different development environments whose global catalogs will (in general case) differ. 2.1) Once the resource has been cached locally from the global catalog, there should be an easy way for the user to "refresh" the local copy from the catalog. I'm not sure which part should be implemented on the XML support side, which -- on the BPEL side, so now I'm reassigning to XML for evaluation.
Sam, we'd like this one to be implemented in 7.0.
I suggest you go ahead with #2 and make a copy in your project. Use the retriever APIs to copy so that it creates catalog in entries in the project.
Okay, reassigning to meself then.
What should be implemented: "Localize" action in popup menu of a resource which retrieves the file to somewhere in <project>/nbbuild/private folder and change the record in catalog.xml. After this action the reference points to the local copy of the file. Note, that this action can not be rolled back.
As it was discussed, the action should be "Get Local Copy", which gets the local copy of the resources, and copies it into "src" folder. It doesn't modify origin reference resource and allows freedom for user to use/delete/ modify reference resource and its local copy together as he/she wishes.
After team meeting it was decided not to implement this feature.
With the decision [documented above] to not implement this feature, this ticket is closed to get it off the books. If necessary, it should be reopened with appropriate requirements.