Look for a file called log4j.properties or log4j.xml in your Tomcat install. Or else, there will be one under $ODE/WEB-INF/classes/log4j.properties.

alex

Alina Dima wrote:
Where in Tomcat do I do that, I mean which configuration file holds the
debug category?

On 11/8/06, Alex Boisvert <[EMAIL PROTECTED]> wrote:


In that case, you could try setting the debug category "org.apache.ode"
to DEBUG and see if you can get more compile information out of the log.

alex


Alina Dima wrote:
> It does not say anything else...this is the whole exception.
>
> Alina
>
> On 11/8/06, Alex Boisvert <[EMAIL PROTECTED]> wrote:
>>
>>
>> Can you send the full stacktrace?   You should see the underlying
reason
>> further down the call stack, e.g. "Caused by:  java.some.Exception"
>>
>>
>> Alina Dima wrote:
>> > Hi,
>> >
>> > Thanks for your reply.I solved that..I was missing one wsdl file
which
>> > declared the respective service:( and I just realized in the
>> meantime).
>> > However, my problem now is that I get the following compillation
>> error:
>> >
>> > 15:01:13,466 WARN  [BpelC]
>> > file:///C:/IntalioServer/intalio-bpms-4.3.0.015/repos
>> > itory/ode/ode-war/2.0.13/ode-war-2.0.13.war
>> > /WEB-INF/processes/BprId220/BpId322.b
>> > pel:85: warning: [] The "out" correlation pattern is the only one
that
>> > makes
>> > sen
>> > se for <reply>.
>> > 15:01:13,622 ERROR [DeploymentPoller] Deployment of BprId220 failed,
>> > aborting fo
>> > r now.
>> > org.apache.ode.bpel.iapi.BpelEngineException: Compilation failure!
>> >        at
>> > org.apache.ode.bpel.deploy.DeploymentUnitImpl.loadProcessDefinitions(
>> > DeploymentUnitImpl.java:148)
>> >        at org.apache.ode.bpel.deploy.DeploymentUnitImpl.refresh
>> > (DeploymentUnitI
>> > mpl.java:288)
>> >        at org.apache.ode.bpel.deploy.DeploymentUnitImpl
>> > .<init>(DeploymentUnitIm
>> > pl.java:110)
>> >        at
>> > org.apache.ode.bpel.deploy.DeploymentManagerImpl.createDeploymentUnit
>> > (DeploymentManagerImpl.java:71)
>> >        at org.apache.ode.bpel.engine.BpelServerImpl.deploy(
>> > BpelServerImpl.java:
>> > 630)
>> >        at org.apache.ode.axis2.deploy.DeploymentPoller.check(
>> > DeploymentPoller.j
>> > ava:133)
>> >        at org.apache.ode.axis2.deploy.DeploymentPoller.access$300
>> > (DeploymentPol
>> > ler.java:55)
>> >        at
>> org.apache.ode.axis2.deploy.DeploymentPoller$PollingThread.run
>> > (Deploy
>> > mentPoller.java:188)
>> >
>> > There is no real explanation as I see from the Exception as to why
>> this
>> > failure occurs. Any ideas?
>> > Unofrtunately, my boss just told me I am not allowed to send the
code,
>> > since
>> > it is supposedly confidential...
>> >
>> > Thanks,
>> > Alina
>> >
>> >
>> > On 11/8/06, Alex Boisvert <[EMAIL PROTECTED]> wrote:
>> >>
>> >>
>> >> You do mean the partnerLink is assigned a value at runtime using
>> >> assignments?   If so, you don't have to provide a value in
deploy.xml
>> >> but you must use the initializePartnerRole="no" attribute on the
>> >> partnerLink.
>> >>
>> >> alex
>> >>
>> >> Alina Dima wrote:
>> >> > Hi,
>> >> >
>> >> > What happens if there is a PartnerLink specified in the bpel file,
>> but
>> >> no
>> >> > service associated to it in any of the wsdl files, no endpoint
>> >> > reference? In
>> >> > this case, will the partner link still appear in any form in the
>> >> > deploy.xml?
>> >> >
>> >> > Thanks,
>> >> > Alina
>> >> >
>> >>
>> >>
>> >
>>
>>
>




Reply via email to