I just sync'ed up and am seeing the following build error? I did a clean
before trying the build.

[INFO] [compiler:compile]
Compiling 66 source files to
C:\repositories\ode-update\bpel-compiler\target\cla
sses
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Compilation failure

C:\repositories\ode-update\bpel-compiler\src\main\java\org\apache\ode\bpel\compi
ler\wsdl\WSDLFactoryBPEL20.java:[40,23] cannot find symbol
symbol  : variable NS_WSBPEL_2004_03
location: class org.apache.ode.bpel.compiler.bom.Constants

C:\repositories\ode-update\bpel-compiler\src\main\java\org\apache\ode\bpel\compi
ler\wsdl\WSDLFactoryBPEL20.java:[40,52] cannot find symbol
symbol  : variable NS_WSBPEL_PARTNERLINK_2004_03
location: class org.apache.ode.bpel.compiler.bom.Constants

C:\repositories\ode-update\bpel-compiler\src\main\java\org\apache\ode\bpel\compi
ler\wsdl\WSDLFactoryBPEL20.java:[55,78] cannot find symbol
symbol  : variable NS_WSBPEL_PARTNERLINK_2004_03
location: class org.apache.ode.bpel.compiler.bom.Constants

C:\repositories\ode-update\bpel-compiler\src\main\java\org\apache\ode\bpel\compi
ler\BpelCompiler.java:[549,42] cannot find symbol
symbol  : variable NS_WSBPEL_2004_03
location: class org.apache.ode.bpel.compiler.bom.Constants

C:\repositories\ode-update\bpel-compiler\src\main\java\org\apache\ode\bpel\compi
ler\BpelCompiler20.java:[59,24] cannot find symbol
symbol  : variable NS_WSBPEL_2004_03
location: class org.apache.ode.bpel.compiler.bom.Constants

On 10/24/06, Maciej Szefler <[EMAIL PROTECTED]> wrote:

The trunk has been updated with a refactored BPEL Compiler. This new
compiler no longer uses the bpel-parser, bpel-bom modules. These modules
have been removed. The FSA-based parser has been replaced with a standard
SAX-based DOM-builder. The BOM has been demoted. It is now a package of
the
bpel-compiler module. This new BOM is now a collection of BPEL-specific
classes that wrap DOM-elements with handy getters, much like XMLBeans but
more flexible. Also, some dependencies have changed. The compiler API
"capi"
has been moved into the bpel-compiler module from the bpel-api module.
This
means that the expression language modules bpel-el-xpath* now depend on
the
bpel-compiler, and not the other way around. The compiler depends on these
modules at runtime only via dynamic class-loading. Sounds complicated, but
really makes things a lot simpler. It also makes it much much easier to
write extension activities. Hooray.
-mbs


Reply via email to