Hi Andrew
thanks. We are embedding CXF jars into our web application. Is one
approach better than the other?
Regards
Suneet
Andrew Dinn wrote:
On 07/24/2009 06:12 AM, Suneet Shah wrote:
Hi Dan
I added the portName, but I am still getting some errors but the one
related to the port is now gone.
Any thought how I can get past them?
On my OrganizationDataWebServiceImpl I have the following annotation:
@WebService(endpointInterface="org.openiam.idm.srvc.org.service.OrganizationDataService",
targetNamespace="urn:idm.openiam.org/srvc/org/service",
portName = "OrganizationDataWebServicePort",
serviceName="OrganizationDataWebService")
INFO: Creating Service
{urn:idm.openiam.org/srvc/org/service}OrganizationDataWebService from
class org.openiam.idm.srvc.org.service.OrganizationDataService
01:09:23,486 ERROR [STDERR] Jul 24, 2009 1:09:23 AM
org.apache.cxf.endpoint.ServerImpl initDestination
INFO: Setting the server's publish address to be
/idmsrvc/OrganizationDataService
01:09:23,560 ERROR [STDERR] Jul 24, 2009 1:09:23 AM
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
buildServiceFromClass
Those are info/trace messages, not error messages. You are seeing them
tagged as errors because the JBoss logger tags anything written to
stderr with the prefix ERROR [STDERR].
Are you using the CXF stack underneath JBossWS or by embedding the CXF
jars in your web application? It looks to me like the latter. If so
then you need to change your app so that its output is explicitly
directed to the JBoss logger rather than via stderr. Alternatively,
you can just ignore the ERROR [STDERR] at the front and check the
message for an ERROR, WARN or INFO tag (clearly, looking at message 2,
CXF does not always append an INFO tag so you may need to apply some
discretion).
regards,
Andrew Dinn
-----------
