Testing my web project
Hi,
I am trying to launch my web project locally. That is I have not deployed it on the server. I have created my launch configuration as suggested in the Example. On launch all I get is a console message saying:
osgi> log4j:WARN No appenders could be found for logger (com.ibm.team.repository.common.transport.AbstractElementDescriptor).
log4j:WARN Please initialize the log4j system properly.
Also this problem starting after updating to the latest milestone.
Can anyone please suggest if something special needs to be done, or I am doing something incorrectly.
Thanks and Regards,
Praveen
I am trying to launch my web project locally. That is I have not deployed it on the server. I have created my launch configuration as suggested in the Example. On launch all I get is a console message saying:
osgi> log4j:WARN No appenders could be found for logger (com.ibm.team.repository.common.transport.AbstractElementDescriptor).
log4j:WARN Please initialize the log4j system properly.
Also this problem starting after updating to the latest milestone.
Can anyone please suggest if something special needs to be done, or I am doing something incorrectly.
Thanks and Regards,
Praveen
14 answers
Hi Richard,
Thans!! the launch works now. It was
"com.ibm.team.process.common_0.5.0.I20070711-2021" which ws causing all
the problems. Btw, If I want to define my project area, do I have to
include this in the Test DB creation or is it possible to do it in the
initialisation of my launch?
Regards,
Praveen
Thans!! the launch works now. It was
"com.ibm.team.process.common_0.5.0.I20070711-2021" which ws causing all
the problems. Btw, If I want to define my project area, do I have to
include this in the Test DB creation or is it possible to do it in the
initialisation of my launch?
Regards,
Praveen
Praveen,
Right now the only way to create a project area is to connect a rich
client to your server and use the create project area wizards.
Richard
praveen.sinha@in.ibm.com wrote:
Right now the only way to create a project area is to connect a rich
client to your server and use the create project area wizards.
Richard
praveen.sinha@in.ibm.com wrote:
Hi Richard,
Thans!! the launch works now. It was
"com.ibm.team.process.common_0.5.0.I20070711-2021" which ws causing all
the problems. Btw, If I want to define my project area, do I have to
include this in the Test DB creation or is it possible to do it in the
initialisation of my launch?
Regards,
Praveen
Hi Richard,
The problem is that we are in a little bit of a catch-22 situation. Our
component models reference items from the work item models and this
forces us to pull in com.ibm.team.process.common in our manifest
dependencies.
Though not starting team.process.common enables viewing of our web
client independent from any project area being created, none of our
services start due to the unresolved dependency.
How can we solve this problem? How is workitem.web tested without a PA
since its service bundles require com.ibm.team.process.common?
We tried to start com.ibm.team.process.common and then from our client
connect and create a PA, but this led to all sorts of exceptions trying
to deploy a process to it.
Thanks.
Richard Backhouse wrote:
The problem is that we are in a little bit of a catch-22 situation. Our
component models reference items from the work item models and this
forces us to pull in com.ibm.team.process.common in our manifest
dependencies.
Though not starting team.process.common enables viewing of our web
client independent from any project area being created, none of our
services start due to the unresolved dependency.
How can we solve this problem? How is workitem.web tested without a PA
since its service bundles require com.ibm.team.process.common?
We tried to start com.ibm.team.process.common and then from our client
connect and create a PA, but this led to all sorts of exceptions trying
to deploy a process to it.
Thanks.
Richard Backhouse wrote:
Praveen,
Right now the only way to create a project area is to connect a rich
client to your server and use the create project area wizards.
Richard
praveen.sinha@in.ibm.com wrote:
Hi Richard,
Thans!! the launch works now. It was
"com.ibm.team.process.common_0.5.0.I20070711-2021" which ws causing
all the problems. Btw, If I want to define my project area, do I have
to include this in the Test DB creation or is it possible to do it in
the initialisation of my launch?
Regards,
Praveen
Sachin,
In this case it might be easier to use a reqular TeamConcert client and
server and create a db with a project area from that, then use this
created db for your development environment db.
Richard
Sachin Patel wrote:
In this case it might be easier to use a reqular TeamConcert client and
server and create a db with a project area from that, then use this
created db for your development environment db.
Richard
Sachin Patel wrote:
Hi Richard,
The problem is that we are in a little bit of a catch-22 situation. Our
component models reference items from the work item models and this
forces us to pull in com.ibm.team.process.common in our manifest
dependencies.
Though not starting team.process.common enables viewing of our web
client independent from any project area being created, none of our
services start due to the unresolved dependency.
How can we solve this problem? How is workitem.web tested without a PA
since its service bundles require com.ibm.team.process.common?
We tried to start com.ibm.team.process.common and then from our client
connect and create a PA, but this led to all sorts of exceptions trying
to deploy a process to it.
Thanks.
Richard Backhouse wrote:
Praveen,
Right now the only way to create a project area is to connect a rich
client to your server and use the create project area wizards.
Richard
praveen.sinha@in.ibm.com wrote:
Hi Richard,
Thans!! the launch works now. It was
"com.ibm.team.process.common_0.5.0.I20070711-2021" which ws causing
all the problems. Btw, If I want to define my project area, do I have
to include this in the Test DB creation or is it possible to do it in
the initialisation of my launch?
Regards,
Praveen
page 2of 1 pagesof 2 pages