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 92092 - NB is not reporting error
Summary: NB is not reporting error
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: Composite Application (show other bugs)
Version: 5.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jun Qian
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-09 10:56 UTC by gc140975
Modified: 2009-04-13 23:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
composite application (115.73 KB, text/plain)
2007-01-09 10:57 UTC, gc140975
Details
Projects migrated to new BPEL schema (235.91 KB, application/octet-stream)
2007-06-22 23:38 UTC, Jun Qian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gc140975 2007-01-09 10:56:00 UTC
NB is not reporting error even though runtime is reporting it when deploying the
composite application

[C:/] jbiant -Djbi.deploy.file=/tmp/testapp.zip
 deploy-service-assembly
 Buildfile: c:\glassfish\jbi\bin\jbi_admin.xml
 
 -pre-jbi-admin-setup:
 
 -jbi-admin-setup:
 
 -init-macrodef-echo-info:
 
 init-jbi-admin:
 
 -init-deploy-sa:
 
 -do-deploy-sa:
 [i18n-echo] Deploying a service assembly
 [i18n-echo]   jmx connection info: (host=localhost, port=4848,
 secure=false, username=admin, target=server )
 [i18n-echo]   file=/tmp/murali/testapp.zip
 [jbi-deploy-service-assembly] Service assembly deployment succeeded. [
 [jbi-deploy-service-assembly] testapp
 [jbi-deploy-service-assembly] ]
 
 -do-deploy-sa-from-domain:
 
 -do-deploy-sa-option-error:
 
 deploy-service-assembly:
 
 BUILD SUCCESSFUL
 Total time: 2 seconds
 [C:/] jbiant -Djbi.service.assembly.name=testapp

start-service-assembly

 Buildfile: c:\glassfish\jbi\bin\jbi_admin.xml
 
 -pre-jbi-admin-setup:
 
 -jbi-admin-setup:
 
 -init-macrodef-echo-info:
 
 init-jbi-admin:
 
 -init-sa-lifecycle-options:
 
 start-service-assembly:
 [i18n-echo] Starting a service assembly
 [i18n-echo]   jmx connection info: (host=localhost, port=4848,
 secure=false, username=admin, target=server )
 [i18n-echo]   name=testapp
 [jbi-start-service-assembly] Start service assembly succeeded. [
 [jbi-start-service-assembly]   Component: com.sun.bpelse-1.0-2
 [jbi-start-service-assembly]     ERROR:(BPELSE)Service unit failed to
 load deployment error: sch-props-correct.2: Duplicate global t
 ype: codesArray@http://siliconllama.com (Original global type found in
 file: null)
 [jbi-start-service-assembly] Detailed Message :
 [jbi-start-service-assembly]    1: SEVERE :Duplicate global type:
 codesArray@http://siliconllama.com (Original global type found in
 file: null)
 [jbi-start-service-assembly]    2: SEVERE :Duplicate global type:
 ccodeArray@http://siliconllama.com (Original global type found in
 file: null)
 [jbi-start-service-assembly]
 [jbi-start-service-assembly]   Component: com.sun.httpsoapbc-1.0-2
 [jbi-start-service-assembly]     INFO:(JBIMA0500)Lifecycle operation
 start succeeded for Service Unit testapp-com.sun.httpsoapbc-1.0
 -2.
 [jbi-start-service-assembly] ]
 
 BUILD SUCCESSFUL
 Total time: 5 seconds
Comment 1 gc140975 2007-01-09 10:57:52 UTC
Created attachment 37170 [details]
composite application
Comment 2 Jun Qian 2007-06-22 23:38:45 UTC
Created attachment 44303 [details]
Projects migrated to new BPEL schema
Comment 3 Jun Qian 2007-08-08 21:39:35 UTC
CompApp is certainly not doing all the validation that runtime components are doing and will probably not. 
Comment 4 Jun Qian 2009-03-06 00:58:19 UTC
For this particular example, the current runtime no longer throws errors when deploying the compapp.
Comment 5 fmartinez1 2009-04-13 23:05:37 UTC
After testing this scenario, I am not seeing an error message in NB or in the log. 20090410-0721