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.

Bug 174797 - Project fails to build when BPEL refers to External WSDL Document
Summary: Project fails to build when BPEL refers to External WSDL Document
Status: RESOLVED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Vladimir Yaroslavskiy
URL:
Keywords:
: 174640 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-10-17 02:51 UTC by Murali Pottlapelli
Modified: 2009-11-12 03:04 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
project to reproduce the issue (24.33 KB, application/octet-stream)
2009-10-17 02:51 UTC, Murali Pottlapelli
Details
Updated test project (11.16 KB, application/zip)
2009-11-10 02:34 UTC, Vladimir Yaroslavskiy
Details
screen shot to demonstrate the issue (20.50 KB, image/png)
2009-11-11 13:51 UTC, Murali Pottlapelli
Details
project to reproduce issue (86.89 KB, application/octet-stream)
2009-11-11 15:22 UTC, Murali Pottlapelli
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Murali Pottlapelli 2009-10-17 02:51:19 UTC
Remote resource with ? is added by File->NewFile ->XML->External WSDL Document, and used in BPEL project it fails on build.

Created dir: C:\Users\mpottlapelli\Documents\NetBeansProjects\testExternalRef\testExternalRef\build
C:/Users/mpottlapelli/Documents/NetBeansProjects/testExternalRef/testExternalRef/src/Synchronous.bpel:68: 8
WARNING: The variable "GetCustomNewsOut" is initialized and not used.

Copying 5 files to C:\Users\mpottlapelli\Documents\NetBeansProjects\testExternalRef\testExternalRef\build
C:\Users\mpottlapelli\Documents\NetBeansProjects\testExternalRef\testExternalRefApplication\nbproject\build-impl.xml:112: The
following error occurred while executing this line:
C:\Users\mpottlapelli\Documents\NetBeansProjects\testExternalRef\testExternalRef\nbproject\build-impl.xml:109: Failed to
create an XML catalog.
BUILD FAILED (total time: 0 seconds)
Comment 1 Murali Pottlapelli 2009-10-17 02:51:54 UTC
Created attachment 89648 [details]
project to reproduce the issue
Comment 2 Sergey Lunegov 2009-10-19 10:25:08 UTC
Vladimir, please take a look.
Comment 3 Vladimir Yaroslavskiy 2009-10-23 15:09:40 UTC
*** Issue 174640 has been marked as a duplicate of this issue. ***
Comment 4 Vladimir Yaroslavskiy 2009-10-23 15:10:12 UTC
Remote resource with ? cant be added, for example, http://www.xmlme.com/WSCustNews.asmx?WSDL

java.io.IOException: The filename, directory name, or volume label syntax is incorrect
        at java.io.WinNTFileSystem.createFileExclusively(Native Method)
        at java.io.File.createNewFile(File.java:883)
        at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FolderObj.createData(FolderObj.java:287)
        at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FolderObj.createDataImpl(FolderObj.java:244)
        at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FolderObj$1.call(FolderObj.java:214)
        at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FolderObj$1.call(FolderObj.java:212)
        at org.netbeans.modules.masterfs.filebasedfs.FileBasedFileSystem.runAsInconsistent(FileBasedFileSystem.java:112)
        at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FolderObj.createData(FolderObj.java:217)
        at org.openide.filesystems.FileObject.createData(FileObject.java:820)
        at org.netbeans.modules.xml.util.resources.ResourceHelper.createData(ResourceHelper.java:498)
        at org.netbeans.modules.xml.util.resources.ResourceHelper.getRemote(ResourceHelper.java:462)
        at org.netbeans.modules.xml.util.resources.ResourceChild$ReloadAction.reload(ResourceChild.java:314)
        at org.netbeans.modules.xml.util.resources.ResourceChild.getFromRemote(ResourceChild.java:204)
        at org.netbeans.modules.xml.util.resources.ResourceHelper.addURL(ResourceHelper.java:198)
        at org.netbeans.modules.xml.util.resources.ResourceHelper.addURLAction(ResourceHelper.java:143)
        at
org.netbeans.modules.xml.util.resources.ResourceNode$AddAction$AddRemoteAction.actionPerformed(ResourceNode.java:2
55)
        at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
        at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
        at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
        at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
        at javax.swing.AbstractButton.doClick(AbstractButton.java:357)
        at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1225)
        at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1266)
        at java.awt.Component.processMouseEvent(Component.java:6263)
        at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
        at java.awt.Component.processEvent(Component.java:6028)
        at java.awt.Container.processEvent(Container.java:2041)
        at java.awt.Component.dispatchEventImpl(Component.java:4630)
        at java.awt.Container.dispatchEventImpl(Container.java:2099)
        at java.awt.Component.dispatchEvent(Component.java:4460)
        at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)
        at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
        at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
        at java.awt.Container.dispatchEventImpl(Container.java:2085)
        at java.awt.Window.dispatchEventImpl(Window.java:2475)
        at java.awt.Component.dispatchEvent(Component.java:4460)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
        at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
        at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Comment 5 Vladimir Yaroslavskiy 2009-11-10 02:32:51 UTC
fixed in gfesbv22: 84fc78aa43e2
Comment 6 Vladimir Yaroslavskiy 2009-11-10 02:34:16 UTC
Created attachment 90673 [details]
Updated test project
Comment 7 Murali Pottlapelli 2009-11-11 13:49:52 UTC
Refer to attached screen shot, reference shows twice after populating catalog.

It also does not migrate old projects, actions available on reference for existing project created with older version is different from current version.
Comment 8 Murali Pottlapelli 2009-11-11 13:51:10 UTC
Created attachment 90845 [details]
screen shot to demonstrate the issue
Comment 9 Vladimir Yaroslavskiy 2009-11-11 14:00:35 UTC
Did you use old or updated project?
Old project has invalid catalog.xml
therefore I updated it.

what do you mean "It also does not migrate old projects, actions available on reference for existing project created with older version is different from current version."? Which functionality should migrate?

Note that actions on Referenced Resources don't depend on project, its depend on build version.

Please, specify steps to reproduce and test project: I have no idea how to reproduce based on screen shot, no enough information.
Comment 10 Murali Pottlapelli 2009-11-11 15:22:22 UTC
Created attachment 90850 [details]
project to reproduce issue

Add http://www.xmlme.com/WSCustNews.asmx?WSDL by File->New->External  WSDL  Document, import it to bpel.

populate catalog
WSCustNews.asmx.wsdl is there in the source folder and retrieved

build project
it is there in the root folder as well as meta
 
You observe duplicate entries given WSDL.
Comment 11 Murali Pottlapelli 2009-11-11 15:36:05 UTC
<Vladimir>
Did you use old or updated project?
Old project has invalid catalog.xml
therefore I updated it.
</Vladimir>

<Murali>
I have created brand new project. added external ref, added import to bp, build. No issue.
populate catalog, build, it shows two entries for a given ref, refer to screen shot.
</Murali>

<Vladimir>
what do you mean "It also does not migrate old projects, actions available on
reference for existing project created with older version is different from
current version."? Which functionality should migrate?
</Vladimir>

<Murali>
It needs to be migrated, user should have same behavior with already created projects.

We can not ask user to recreate project.
</Murali>

<Vladimir>
Note that actions on Referenced Resources don't depend on project, its depend
on build version.
</Vladimir>
<Murali>
I am observing different actions based on the build used for creating project and how external Ref is added, (ReferenceResouces-Add Remote) vs (File->New->External  WSDL Document)

We need it to be uniform.
</Murali>
Comment 12 Sergey Lunegov 2009-11-12 01:22:38 UTC
Vladimir, reassigned to you again.
Comment 13 Vladimir Yaroslavskiy 2009-11-12 03:04:42 UTC
I open last attached project and see only one entry of the wsdl file.

I'm not sure what should be migrated? Functionality defined by NetBeans IDE, not project. The structure of catalog.xml is standard and never changed. Files build-impl.xml is regenerated by NetBeans automatically.

"Populate catalog" and "New->External WSDL Document" actions: before Referenced Resources feature is implemented, these actions make sense. Now its functionality is covered by Referenced Resources feature. Moreover, "New->External WSDL Document" saves a document inside "src" folder which is not good.

I'd prefer to eliminate "Populate catalog" and "New->External WSDL Document" actions. Anyway, it is out of scope of this issue, therefore I'm closing as fixed. For "Populate catalog" and "New->External WSDL Document" actions, please, file separate issues (if any) or e-mail.