| The AXIS engine could not find a target service to invoke! targetService is null [message #255425] |
Fri, 14 September 2007 07:56  |
Eclipse User |
|
|
|
Originally posted by: teemu.turkia.propentus.fi
Hi!
I deployed BIRT 2.2.0 to WebSphere 6.0. index.jsp shows fine, but when I try
to run the test report, I get this error message:
The AXIS engine could not find a target service to invoke! targetService is
null.
When I click "Show Exception Stack Trace", it shows only empty Stack Trace.
EAR classloader mode is set to parent last and WAR class loader policy is
set to Application. Also the web modules class loader mode is set to parent
last.
I have tried the default library structure and I also tried to remove emf
jars from platform/plugins directory (+ moved org.eclipse.emf_2.2.0...jar to
WEB-INF/lib folder) as described in
http://wiki.eclipse.org/Birt_WebSphere_Deployment. Nothing seems to help.
Any ideas what I am doing wrong?
Thanks,
Teemu Turkia
|
|
|
| Re: The AXIS engine could not find a target service to invoke! targetService is null [message #255429 is a reply to message #255425] |
Fri, 14 September 2007 08:03  |
| Eclipse User |
|
|
|
Originally posted by: mil.methodpark.de
Hi,
I have the same problem with tomcat 6...
Greetings,
Matthias
"Teemu Turkia" <teemu.turkia@propentus.fi> schrieb im Newsbeitrag
news:fcdev3$dnd$1@build.eclipse.org...
> Hi!
>
> I deployed BIRT 2.2.0 to WebSphere 6.0. index.jsp shows fine, but when I
> try to run the test report, I get this error message:
> The AXIS engine could not find a target service to invoke! targetService
> is null.
> When I click "Show Exception Stack Trace", it shows only empty Stack
> Trace.
> EAR classloader mode is set to parent last and WAR class loader policy is
> set to Application. Also the web modules class loader mode is set to
> parent last.
> I have tried the default library structure and I also tried to remove emf
> jars from platform/plugins directory (+ moved org.eclipse.emf_2.2.0...jar
> to WEB-INF/lib folder) as described in
> http://wiki.eclipse.org/Birt_WebSphere_Deployment. Nothing seems to help.
>
> Any ideas what I am doing wrong?
>
> Thanks,
>
> Teemu Turkia
>
|
|
|
| Re: The AXIS engine could not find a target service to invoke! targetService is null [message #255433 is a reply to message #255429] |
Fri, 14 September 2007 08:24 |
| Eclipse User |
|
|
|
Originally posted by: mil.methodpark.de
Argh, I made a stupid mistake: I forgot to copy some config files
(server-config.wsdd, ...) to the appropriate folder of my webapp.
It works fine now!
Greetings,
Matthias
"Meandron" <mil@methodpark.de> schrieb im Newsbeitrag
news:fcdf8t$er4$1@build.eclipse.org...
> Hi,
>
> I have the same problem with tomcat 6...
>
> Greetings,
> Matthias
>
> "Teemu Turkia" <teemu.turkia@propentus.fi> schrieb im Newsbeitrag
> news:fcdev3$dnd$1@build.eclipse.org...
>> Hi!
>>
>> I deployed BIRT 2.2.0 to WebSphere 6.0. index.jsp shows fine, but when I
>> try to run the test report, I get this error message:
>> The AXIS engine could not find a target service to invoke! targetService
>> is null.
>> When I click "Show Exception Stack Trace", it shows only empty Stack
>> Trace.
>> EAR classloader mode is set to parent last and WAR class loader policy is
>> set to Application. Also the web modules class loader mode is set to
>> parent last.
>> I have tried the default library structure and I also tried to remove emf
>> jars from platform/plugins directory (+ moved org.eclipse.emf_2.2.0...jar
>> to WEB-INF/lib folder) as described in
>> http://wiki.eclipse.org/Birt_WebSphere_Deployment. Nothing seems to help.
>>
>> Any ideas what I am doing wrong?
>>
>> Thanks,
>>
>> Teemu Turkia
>>
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03276 seconds
] 
Search
Help
Register
Login
Home
