geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sachin Patel (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMODEVTOOLS-12) NPE when publishing Web Service
Date Mon, 19 Sep 2005 12:17:36 GMT
    [ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-12?page=comments#action_12329832
] 

Sachin Patel commented on GERONIMODEVTOOLS-12:
----------------------------------------------

There is a servers.xml (I think its named that) in the plugin meta data for one of the plugins
either wst.server.core or jst.server.core.  You may be able to modify this to clean up the
configured projects and then restart your workbench.  

Sometimes though, its just best to start a whole new workspace :).  

> NPE when publishing Web Service
> -------------------------------
>
>          Key: GERONIMODEVTOOLS-12
>          URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-12
>      Project: Geronimo-Devtools
>         Type: Bug
>  Environment: latest HEAD,  wtp-I20050914 and dependencies, Linux
>     Reporter: Miguel A Paraz
>  Attachments: Screenshot-Add and Remove Projects .png, eclipse-trace.txt, eclipse-trace2.txt,
eclipse-trace3.txt
>
> 1. Create a Dynamic Web Project, using Geronimo as server
> 2. Create a bean class.
> 3. New/Web Services/Web Service
> 4. "Bottom" up, defaults
> 5. Service Deployment Configuration: run time is Axis, server is Geronimo
> 6. Web Service Java Bean Identity: defaults, all methods, Document/Literal (Wrapped)
> 7. Start server
> 8. Error dialog box:
> Could not publish to the server.
>     java.lang.NullPointerException
>     at org.apache.geronimo.core.internal.GeronimoUtils.isWebModule(GeronimoUtils.java:78)
>     at org.apache.geronimo.core.internal.GeronimoUtils.getConfigId(GeronimoUtils.java:62)
>     at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBehaviour.java:368)
>     at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBehaviour.java:281)
>     at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:632)
>     at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:685)
>     at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:586)
>     at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:705)
>     at org.eclipse.wst.server.core.internal.Server.publish(Server.java:694)
>     at org.eclipse.jst.ws.internal.consumption.command.common.StartServerCommand$1.run(StartServerCommand.java:182)
>     at org.eclipse.jst.ws.internal.consumption.command.common.StartServerCommand.publish(StartServerCommand.java:194)
>     at org.eclipse.jst.ws.internal.consumption.command.common.StartServerCommand.execute(StartServerCommand.java:104)
>     at org.eclipse.jst.ws.internal.consumption.ui.server.StartServerWidget$StartServerJob.run(StartServerWidget.java:305)
>     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message