Sorry, no exceptions are written to the IDE log, my bad

this seems specific to the validation run by Build ... which i don't understand
since I thought the build was using the same validation infrastructure as the
point artifacts. 

But in this case, the point artifacts (wsdl and bpel) can be validated
individually just fine. It is only when you run the project level Build that
this validation problem loadAndValidateExistingBusinessProcess
SEVERE: org/apache/xml/resolver/CatalogManager ... appears.

also, fyi, i saw this on Mikhail's machine which was running an installer
version. On my local machine, where i was using NB binaries plus "ant soa" I did
not see this problem and my project build was ok.

getting latest and doing build.. will test and see if this is happening in
latest build.

Not happening in latest build.

Tested with latest available build: 06.09.21_1, started at 23.30 PDT

Still can reproduce the issue. I tried setting proxy in Netbeans, tried invoking
Populate Catalog in context menu - I still can't compile the samples. Reopening
the issue. 

We could reproduce this on 5 out of 7 machines.

Mikhail, 
  Can you please attach the project that's failing also can you enumerate 
the steps to reproduce this problem. 

I tried in the latest build and still couldn't reproduce this. I need to
reproduce this inorder to identify the problem.

Identified the issue.. Working on fix.

Fixed. Please test it in next build.

Appears this bug is still effecting *bpel blueprint samples* in Coke trunk build
060925_1 (running on windows). 

Mikhail Kondratyev confirmed that he does not see this bug on Solaris and is
retesting windows.

Steps to reproduce:
 -create any BPEL BluePrint project (using default name)
 - try to Clean and Build
Compilation will fail with...

Validation has errors on C:\Documents and
Settings\Kennedy\BPEL\Test-9-26-06\BluePrint1\BluePrint1\src\InventoryService.bpel
Sep 26, 2006 10:38:47 AM
org.netbeans.modules.bpel.project.anttasks.ValidateBPELProject
loadAndValidateExistingBusinessProcess
SEVERE: Validation has errors on C:\Documents and
Settings\Kennedy\BPEL\Test-9-26-06\BluePrint1\BluePrint1\src\InventoryService.bpel
Error Message - org/apache/xml/resolver/CatalogManager
Sep 26, 2006 10:38:47 AM
org.netbeans.modules.bpel.project.anttasks.ValidateBPELProject
loadAndValidateExistingBusinessProcess
SEVERE: org/apache/xml/resolver/CatalogManager
C:\Documents and
Settings\Kennedy\BPEL\Test-9-26-06\BluePrint1\BluePrint1Application\nbproject\build-impl.xml:94:
The following error occurred while executing this line:
C:\Documents and
Settings\Kennedy\BPEL\Test-9-26-06\BluePrint1\BluePrint1\nbproject\build-impl.xml:152:
Found compilation errors.
BUILD FAILED (total time: 0 seconds)

1) Is Synchronous sample working?.  This issue is about compiling 
   Synchronous sample/ new bpel projects.. 
2) The build-impl files in blueprint project could be outdated. Can you please
attach the project to the issue. 

3) Yesterday I made checkin
to Alaska test drivers (including blueprint projects
\jbicomps\test\bpelse\blueprints ).. Are these projects same. If so then you
should try with latest blueprint project.

Created attachment 34558 [details]
BPEL BluePrint1 sample project

1) Is Synchronous sample working?.  This issue is about compiling 
   Synchronous sample/ new bpel projects.

RK - Synchronous and Asynchronous samples appear to be working properly. The
issue is only effecting BPEL BluePrints samples 1, 2, 3, 4, 5.

2) The build-impl files in blueprint project could be outdated. Can you please
attach the project to the issue. 

RK - See attachement above.

3) Yesterday I made checkin
to Alaska test drivers (including blueprint projects
\jbicomps\test\bpelse\blueprints ).. Are these projects same. If so then you
should try with latest blueprint project.

If it helps:  I tried with the latest continuous build Build060926_21, and all
blueprints build successfully on my machine (Windows). 

The build-impl files looks old. You need to use the latest blueprint projects.
Please update and try again.

why is this bug still open?

After updating the build-impl.xml files for blueprints 1-5 on Fri, the projects
appeared to be working properly in local testing. After retesting the samples in
Build061001 on Mon morning, I'm still seeing the same behavior on my local
windows machine (compilation fails).

Oddly though, the samples appear to work properly in the release55_dev branch.
e.g. we may need to simply copy the working projects over from release55_dev to
release55.

Compilation is still fails in build 06.10.02

On my development build of release55 all projects build successfully. I did find
a warning related to "retrieved" directory. But this was warning and did not
affect build success. I filed a different bug for the warning. see bug 86453.

i will see this on some install machine.

Created attachment 34857 [details]
IDE version screen

We have found that the build_impl discrepancy described in bug 86453 is the
cause of the build failure on mkhramov environmnent.

We are not yet sure why it is a failure on his environment but only a warning on
my and Andrey environment. This is only remaining msytery - what is trigger for
difference b/t warning and error? This is only QE  reprocibility/validation
question, because I have confirmed that on mkhramov machine, that if I correct
the build_impl.xml as described in bug 86453, then his build will succees. Undo
that change, and his build will fail. So it is reproducible on his environment,
perfectly. He will attach image showing his combiantion of NB and EntPack. He
installed NB first and added EntPack.

I see that Ryan, made changes to release55_dev branch already. His build_impl is
correct in release55_dev but incorrect in release55. 

Ryan, please, please, commit to release55 also. 

I have reviewed changes. 

Please commit same changes to release55 .
Please change the  TargetMilestone of this bug to 5.5.
Please close this bug as fixed.

*** Issue 86453 has been marked as a duplicate of this issue. ***

Sigh ... wait a minute.

After further review there is still confusion. This is getting quite
frustrating. I think the Alaska project engineers should really monitor this
because it is quite strange and we need to resolve it quickly. I thought it was
easy fix. I thought - just make all the samples have the same build_impl.xml.
However when I do diff on the build_impl.xml on various samples in release55_dev
branch, I expected them to be identical. However they are not ... and why not is
the big question. Either the blueprints versions are unnecessarily complex and
should just copy what has been done for SynchronousSample, or the Synch sample
is lagging behind what blueprints has done. One or the other, but ultimately
they should have same exact code in build_impl.xml


 In the release55_dev branch  I did diff on build_iml.xml for Blueprint1 and
build_impl.xml for SynchronousSample. They are effectively the same but due to
fomat changes, the diff utility shows them to be quite different. Why is that? 
How did you go about making changes to build_impl.xml in Blueprint? Did you
manaully edit it or did you have IDE generate it again for you? I am curious,
because if you manually edited it, you could have simply copied the
build_impl.xml from SychronousSample. You can do a diff on the build_impl.xml
for SynchronousSample, AsyncSample and TRS. You will see that all of their
build_impl.xml are idecntical according to diff utility.  I assumed you would
just copy the contents onf Sync's build_impl.xml onto the Blueprint version, so
that the were truly identical. I did that on machine where bug was manifest and
it corrected the bug. All things being equal I would prefer that you do the same
because it will be easier to track deviations across the samples if they remain
consistent as much as possible.

However, if you had the IDE generate the build_impl.xml and the discrepancy in
format is due to that, then I suppose you should leave it as is and just
propagate to release55.

Do you follow this topic completely? 

adding sreeni and tli to make sure we close the loop on this discrepancy in
build_impl.xml across ALL samples.

Basically, the sample versions of build_impl.xml should be identical to the
versions generated by the New Project > SOA > BPEL Module wizard. That version
will represent the project team's most current version of this very fluid file.

chaning subject line, since is particular problem of samples geting out of sync
with project system. 

Ok, I just did complete audit of the build_impl.xml in release55 vs release55_dev.

It seems that blueprints are the only ones out of sync.

Both New Project > BPEL Module and Nwe Project > Samples > SOA > Sync/Async/TRS
- ALL of these generate the exact same build_impl.xml.

So I don't know why Blueprints in release55_dev should have slightly different
content. In my opinion it should be identical content unless Ryan has
explanation for difference. Yes, Ryan's version seems to compile ok, and does
not geneate warning, so it seems functionally equivalent. However, I am a bit
nervous about the diffs. So unless there is good explanation, I suggest Ryan
make the build_impl in blueprints consistent with the build_impl's in other BPEL
samples.

Note: Kiran Bhumana is the eng who repackaged BluePrint samples 1-5.

Kiran - How were the changes made to build_impl.xml in the Blueprint samples?
Was build_impl.xml edited manaully or did you have IDE generate it again for you? 

As suggested by Mike, for consistency across all samples, we should make the
build_impl in blueprints consistent with the build_impl's in other BPEL
samples. 

So, I will begin modifying the blueprint build-impl files in my local
development build of the release55_dev branch so they are the exact same as
those found in Sync/Async/TRS. After testing is complete, I will commit the new
files to release55_dev, notify the netbeans reviewers alias so they can review
the changes, and add comment to this issue indicating updated status.

All of them are IDE generated.

Kiran, it is very surprising to read that the Blueprint versions in
release55_dev were IDE generated unless there was a a window when the IDE was
generating different versions that are ONLY reflected in yesterdays
release55_dev Blueprints and nowhere else? Not in today's release55_dev New
Project > BPEL Module. Not in release55 New Project > BPEL Module (which if
anything is typically slightly behind release55_dev due to check in lag). It
really does not make sense because the Sync/Async/TRS build_impl.xmls are from
last week. They have not changed, yet they are identical to  TODAY's
release55_dev New Project > BPEL Module (i.e. identical to IDE generated for
totally new projects). Yet somehow the Blueprint versions were different? It
would suggest the IDE was generating one format last week (when TRS/Sync/Async
were last updated , then changed to something differnt in release55_dev while
you regenerated Blueprint build_impl.xml's YESTERDAY, creating the divergent set
... then the IDE changed back today to again generate what is identical to what
it was generating last week? 

It does not really make sense.  But, it can remain a mystery as long as these
finally work.

New build-impl.xml files were regenerated for BPEL BluePrints 1-5 using 10-04-06
build of NB Ent Pack. Integrated into release55 branch at 8:30pm pacific.

Please test BPEL BluePrints 1-5 to confirm the samples are working properly in
next nightly build.

In latest build 061009 the Blueprints compilation fails again with message:
..\BluePrint5\nbproject\build-impl.xml:95: taskdef class
org.netbeans.modules.bpel.project.anttasks.GenerateJBIDescriptorTask cannot be found

Modifying build-impl.xml by copying the file or modifying the file by hand seems
to corrupt the checklist maintained by netbeans. 

 

Netbeans seems to maintain the checksum of the project in 

 

            \nbproject\genfiles.properties

 

Contents of this file 

build.xml.data.CRC32=29ea292a

build.xml.script.CRC32=b97989c7

build.xml.stylesheet.CRC32=9d2b221a

# This file is used by a NetBeans-based IDE to track changes in generated files
such as build-impl.xml.

# Do not edit this file. You may delete it but then the IDE will never
regenerate such files for you.

nbproject/build-impl.xml.data.CRC32=29ea292a

nbproject/build-impl.xml.script.CRC32=2896cdf6

nbproject/build-impl.xml.stylesheet.CRC32=a7727fd7

 

 

If the build files are modified by hand, it seems to disrupt the checksum and
next time build scripts were modified in bpel project module, 

the build files doesn’t seem to get refreshed.

 

Best way is to let the IDE get the latest build files. If you delete the
build.xml, nbproject\build-impl.xml and nbproject\genfile.properties, the next time 

You open the project IDE will generate the latest build files. 

 

Try this..

 

1)   In blue print project,  deleting the following build files ( don’t have the
blue print project open in IDE) 

 

      <project>\build.xml

      <project>\nbproject\build-impl.xml

      <project>\nbproject\genfile.properties

 

2)       Open the blue print projects in IDE, IDE will generate the build files. 

3)       Check the build files in CVS

 

The next time Bpel Project build files got changed, all you have to do is open
the project in IDE it will generate the build files.

venkat, can you put Kiran, Jun, and Sreeni together to fix this now?

Please update the bug as soon as you checkin the repackaged samples

The problem doesnt seem to go away with build file changes. 

Ryan Kennedy has checked in input.xml and output.xml yesterday.. If I use the
previous version of Input.xml,and run the test I  get the output. If I save the
output obtained as output.xml and re run the test the test is passing 

 

Input used : 

<soapenv:Envelope 

  xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/"

  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

  xmlns:xsd="http://www.w3.org/2001/XMLSchema"

  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" 

  xmlns:pur="http://enterprise.netbeans.org/bpel/wsdl/purchase/bp2" 

  xmlns="http://enterprise.netbeans.org/bpel/xsd/purchase">

  <soapenv:Body>

    <pur:sendPurchaseOrder>

      <purchaseOrder>

        <orderId>0012341</orderId>

    <customerId>9876</customerId>

    <orderDescription>OrderVal_Any_Description</orderDescription>

    <price></price>

      </purchaseOrder>

    </pur:sendPurchaseOrder>

  </soapenv:Body>

</soapenv:Envelope>

 

Ouput: 

<?xml version="1.0" encoding="UTF-8"?>

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/"
xmlns="http://enterprise.netbeans.org/bpel/xsd/purchase">

<SOAP-ENV:Header/>

<SOAP-ENV:Body>

  <purchaseOrder xmlns="http://enterprise.netbeans.org/bpel/xsd/purchase">

      <orderId>0012341</orderId>

  <customerId>9876</customerId>

  <orderDescription>OrderVal_Any_Description</orderDescription>

  <price>49.98</price>

    </purchaseOrder>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

I checked with Kiran, he feels the input and output xmls are valid.. 

There seems to be a problem at the project's WSDL or XSDs.. In server 
the following error is seen 

[#|2006-10-10T16:20:05.029-0700|SEVERE|sun-appserver-pe9.0|com.sun.jbi.component.com.sun.bpelse-1.0-2com.sun.jbi.engine.bpel.core.bpms.bpelImpl.runtime.BPELInterpreter|_ThreadID=36;_ThreadName=BPELSEInOutThread0;_RequestID=57f7100d-0df7-4552-908b-9edcc4a3e3b7;|Exception
occured while executing a business process instance.            
com.sun.xml.transform.sware.MissingSchemaInfoException: Cannot find the element
declaration in the schema type system:
{http://manufacturing.org/xsd/purchase}purchaseOrder
	at
com.sun.xml.transform.sware.impl.ReorderTransformerImpl.transform(ReorderTransformerImpl.java:170)
	at
com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.transformDocument(AssignUnitImpl.java:273)
	at
com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.validateOrAndTransformVariable(AssignUnitImpl.java:213)
	at
com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.doAction(AssignUnitImpl.java:165)
	at
com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.CodeReUseHelper.executeChildActivities(CodeReUseHelper.java:60)
	at
com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.executeChildActivities(StructuredActivityUnitImpl.java:148)
	at
com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.doAction(StructuredActivityUnitImpl.java:83)
	at
com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.SequenceUnitImpl.doAction(SequenceUnitImpl.java:77)
	at
com.sun.jbi.engine.bpel.core.bpms.bpelImpl.runtime.BPELInterpreter.interpret1(BPELInterpreter.java:292)
	at
com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:650)
	at
com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:236)
	at
com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:577)
	at
com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.processRequest(EngineImpl.java:156)
	at
com.sun.jbi.engine.bpel.BPELSEInOutThread.processRequest(BPELSEInOutThread.java:376)
	at
com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:197)
	at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:138)
|#]


Since this has to be corrected in the test case level, assigning this to 
Kiran.

In bpel project, the namespaces for wsdl/xsd files was 
 
http://enterprise.netbeans.org/bpel/xsd/purchase
http://enterprise.netbeans.org/bpel/wsdl/purchase/bp2
 
but in input.xml the namespace for corresponding XSD and WSDL was 
 
http://manufacturing.org/xsd/purchase 
http://manufacturing.org/wsdl/purchase/bp2
 
By comparing the input files with Alaska test driver projects, the original
namespace is - http://manufacturing.org/..
This was changed by yaroslavsky to http://enterprise.netbeans.org.. 
 
The same change was not done in input.xml file of the test case.
(BluePrint2Application\test\testAsynchronousReplyingFault)
 
I modified the input.xml and changed the namespaces from 
http://manufacturing.org/xsd/purchase  to
http://enterprise.netbeans.org/bpel/xsd/purchase
http://manufacturing.org/wsdl/purchase/bp2 to
http://enterprise.netbeans.org/bpel/wsdl/purchase/bp2
 
to synchronize the bpel project file namespaces. 
 
With this change, blueprint2 test case worked.
I have checked in the input file. Please test with next build.

fixed please test using next build

 This has dependency on http://enterprise.netbeans.org/issues/show_bug.cgi?id=86861+

fyi sreeni, you can just type in bug 86861 and issuezilla will create hyperlink
automatically

Verified in build m22