Error while trying to build the Simple example project

Mohamed A. Shahat

November 08, 2010 07:54

None

Hello ,

I faced the following error while trying to deploy-dev , the Simple example project :

C:\tibco-temp\TIBant-bin-1.3.2\examples\SimpleProject>ant deploy-dev

Buildfile: C:\tibco-temp\TIBant-bin-1.3.2\examples\SimpleProject\build.xml
[example] LOADING: C:\Users\Mohamed/example.properties
[example] LOADING: C:\Users\Mohamed/build.properties
[example] LOADING: config/Mohamed.properties
[example] LOADING: config/default.properties
[TIBant] IMPORTED: tibant.xml
[TIBant] TIBant Home: C:\tibco-temp\TIBant-bin-1.3.2

ear:

BUILD FAILED
C:\tibco-temp\TIBant-bin-1.3.2\examples\SimpleProject\build.xml:235: The following error occurred while executing this lin
C:\tibco-temp\TIBant-bin-1.3.2\tibant.xml:397: The following error occurred while executing this line:
C:\tibco-temp\TIBant-bin-1.3.2\tibant.xml:256: The following error occurred while executing this line:
C:\tibco-temp\TIBant-bin-1.3.2\tibant.xml:2580: The following error occurred while executing this line:
C:\tibco-temp\TIBant-bin-1.3.2\tibant.xml:921: Problem: failed to create task or type if
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.

Is it a mis-configuration of anything,

Thanks in advance,

Mohamed

Date Votes

5 comments

0

Tom Howard November 08, 2010 21:16

Hi Mohamed,

That's a defect in the Simple example. As of version 1.3.0 TIBant stopped automatically loading ant-contrib and required ant-contrib to be loaded manually before calling any of the TIBant macros. This was to avoid the warnings generated by Ant where ant-contrib was loaded multiple times (once in the user's Ant script and once in TIBant).

A convenience macro has been provided called 'load-ant-contrib', which can be used to load the ant-contrib tasks.

The Simple example is missing the dependency between the 'deploy-dev' target and the '-init' target, which calls the 'load-ant-contrib' macro. I've created a defect ticket for this at assembla.

Comment actions Permalink
0

Kennedy Nakana February 11, 2011 12:10

Hi,

I have send this on our conversation.

I have configured the Simple project with Hudson, ActiveMQ installed and running but I get the following error below:

     [exec] 2011 Feb 11 13:57:32:611 GMT +2 BW.Simple Info [BW_Plugin] BW-HTTP-1

00500 Using the following HTTP minProcessors/maxProcessors [host=localhost port

=6767]: 10/75

     [exec] 2011 Feb 11 13:57:33:071 GMT +2 BW.Simple Warn [org.apache.activemq.

broker.jmx.ManagementContext] BW-EXT-LOG-200000 Failed to start jmx connector: C

annot bind to URL [rmi://localhost:1099/jmxrmi]: javax.naming.ServiceUnavailable

Exception [Root exception is java.rmi.ConnectException: Connection refused to ho

st: localhost; nested exception is:

     [exec]     java.net.ConnectException: Connection refused: connect]

     [exec] 2011 Feb 11 13:57:34:643 GMT +2 BW.Simple Info [BW_Plugin] BW-HTTP-1

00500 Using the following HTTP minProcessors/maxProcessors [host=localhost port

=5656]: 10/75

     [exec] Error 0: [Service = Service.serviceagent; Endpoint = pocEndpoint1, O

peration = concatNamePassword, Message = {http://xmlns.example.com/1295963436545

}input]: Configuration Error. Only one message part can be defined using type at

tribute for document style services in literal encoding

     [exec] 2011 Feb 11 13:57:34:674 GMT +2 BW.Simple Error [BW-Core] BWENGINE-1

00011 Error processing plugin agent [TIBCommunity/Service.serviceagent]

     [exec] The Service [TIBCommunity/Service.serviceagent] is not started due t

o configuration errors

     [exec]     at com.tibco.bw.service.serviceAgent.ServiceServiceAgent.validat

eServiceConfiguration(ServiceServiceAgent.java:188)

     [exec]     at com.tibco.bw.service.serviceAgent.ServiceServiceAgent.init(Se

rviceServiceAgent.java:111)

     [exec]     at com.tibco.pe.core.AgentJobCreator.init(AgentJobCreator.java:8

7)

     [exec]     at com.tibco.pe.core.JobPoolConfigurator.if(JobPoolConfigurator.

java:436)

     [exec]     at com.tibco.pe.core.JobPoolConfigurator.a(JobPoolConfigurator.j

ava:190)

     [exec]     at com.tibco.pe.core.JobPoolConfigurator.do(JobPoolConfigurator.

java:100)

     [exec]     at com.tibco.pe.core.JobPool.<init>(JobPool.java:313)

     [exec]     at com.tibco.pe.core.JobPoolCreator.init(JobPoolCreator.java:81)

     [exec]     at com.tibco.pe.core.JobPoolCreator.<init>(JobPoolCreator.java:7

3)

     [exec]     at com.tibco.pe.PEMain.do(PEMain.java:386)

     [exec]     at com.tibco.pe.PEMain.a(PEMain.java:197)

     [exec]     at com.tibco.pe.PEMain.<init>(PEMain.java:184)

     [exec]     at com.tibco.pe.PEMain.main(PEMain.java:122)

     [exec]

Regards,

Kennedy Nakana

Comment actions Permalink
0

Tom Howard February 13, 2011 20:00

Hi Kennedy,

The first warning, which is related to Apache MQ and JMX, may be caused by firewall settings within Windows. The Apache MQ JMX connection is not needed (for a longer running daemon, you could use it to configure the MQ daemon) and the warning can be safely ignored.

The configuration error is releated to a service agent located at TIBCommunity/Service.serviceagent. There is no such service agent in the TIBCommunity folder in BWUnit 1.3.0. Did you add it yourself or are you using a different version of BWUnit?

Cheers,

Tom

Comment actions Permalink
0

Kennedy Nakana February 14, 2011 07:54

Hi,

Using version BWUnit 1.3.0. Switched off the firewall and now i get the following issue.

[xslt] Processing C:\BWUnit-1.3.0\Examples\Simple\build\test-reports\results.soap to C:\BWUnit-1.3.0\Examples\Simple\build\test-reports\results.html
     [xslt] Loading stylesheet C:\BWUnit-1.3.0\util\xslt\render-html.xslt
     [xslt] : Error! Syntax error in '//(bwu:test-suite-result|bwu:test-case-result)'.
     [xslt] : Error! file:/C:/BWUnit-1.3.0/util/xslt/render-html.xslt: line 432: Error parsing XPath expression '//(bwu:test-suite-result|bwu:test-case-result)'.
     [xslt] : Fatal Error! Could not compile stylesheet

It looks loke it fails to process the stylesheet in the bwunit.xml file.

Regards,

Kennedy

Comment actions Permalink
0

Tom Howard February 14, 2011 21:13

Hi Kennedy,

This error occurs when Apache Ant fail to correctly load the Saxon XSLT processor. There is a solution for a similar problem with TIBant, the only difference is that the path to Saxon is <bwunit-home>/util/lib/saxon9he.jar. e.g., if BWUnit is installed in C:\Program Files\BWUnit the the path to Saxon is C:\Program Files\BWUnit\util\lib\saxon9he.jar

Comment actions Permalink

Please sign in to leave a comment.