You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Lin Sun (JIRA)" <de...@geronimo.apache.org> on 2005/12/22 23:06:31 UTC
[jira] Created: (GERONIMO-1399) NPE when trying to publish a simple app via eclipse plugin
NPE when trying to publish a simple app via eclipse plugin
----------------------------------------------------------
Key: GERONIMO-1399
URL: http://issues.apache.org/jira/browse/GERONIMO-1399
Project: Geronimo
Type: Bug
Components: eclipse-plugin
Versions: 1.0
Environment: Geronimo 1.0, built a few days ago
Eclipse SDK 3.1.1
WTP 1.0 RC 5 and its prerequisites
Eclipse plug-in, built a few days ago
Reporter: Lin Sun
On Dec 22, 2005, at 4:48 PM, Lin Sun wrote:
> Thanks. After you point out where the log is, I saw the following
> in the .log file:
>
> java.lang.NullPointerException
> at java.lang.Class.forName1(Native Method)
> at java.lang.Class.forName(Class.java(Compiled Code))
> at
> org.apache.geronimo.core.GeronimoConnectionFactory.discoverDeploymentF
> actory(GeronimoConnectionFactory.java:78)
> at
> org.apache.geronimo.core.GeronimoConnectionFactory.getDeploymentManage
> r(GeronimoConnectionFactory.java:45)
> at
> org.apache.geronimo.core.CommandLauncher.setDeploymentManager
> (CommandLauncher.java:87)
> at org.apache.geronimo.core.CommandLauncher.executeCommand
> (CommandLauncher.java:61)
> at
> org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy
> (GeronimoServerBehaviour.java:233)
> at
> org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeComman
> d(GeronimoServerBehaviour.java:207)
> at
> org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModul
> e(GeronimoServerBehaviour.java:194)
> at
> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul
> e(ServerBehaviourDelegate.java:658)
> at
> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul
> es(ServerBehaviourDelegate.java:738)
> at
> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish
> (ServerBehaviourDelegate.java:596)
> at org.eclipse.wst.server.core.internal.Server.doPublish
> (Server.java:799)
> at org.eclipse.wst.server.core.internal.Server.publish(Server.java:
> 788)
> at org.eclipse.wst.server.core.internal.PublishServerJob.run
> (PublishServerJob.java:145)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
>
> --- Sachin Patel <sp...@gmail.com> wrote:
>
>> Nevermind, I found the problem. In the future, eclipse plugin
>> errors/
>> exceptions can be found in the .log in the workspace metadata. So
>> you shouldn't just look for errors in the geronimo log.
>>
>> I just published and found a NPE attempting to discover the
>> deploymentFactory. Something must have changed in the runtime that
>> broke me... I'll look into it.
>>
>>
>> - sachin
>>
>>
>>
>> On Dec 22, 2005, at 4:21 PM, Sachin Patel wrote:
>>
>>> Ok, then please describe your steps, from project creation, to
>>> deployment.
>>>
>>> - sachin
Steps:
1) launch eclipse using eclipse -clean and use a brand new workspace
2) change to J2EE view. Define a geronimo server and start it.
3) right click dynamic web projects and select import to import
the hello.war file. Select default/next for everything except uncheck the "add module to
an ear application" checkbox.
4) right click the hello folder and select run as--run on server.
then I got the "unable to publish error" immediately.
I'll send you the hello.war file in a seperate note to reduce the size of the email to
the list.
Thanks, Lin
--
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
[jira] Updated: (GERONIMO-1399) DeploymentFactory-Implementation-Class property missing from deployer.jar manifest
Posted by "Sachin Patel (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1399?page=all ]
Sachin Patel updated GERONIMO-1399:
-----------------------------------
Component: deployment
(was: eclipse-plugin)
Summary: DeploymentFactory-Implementation-Class property missing from deployer.jar manifest (was: NPE when trying to publish a simple app via eclipse plugin)
Fix Version: 1.0
Moving to component deployment. The problem is that the manfiest in deployer.jar no longer contains the J2EE-DeploymentFactory-Implementation-Class property.
> DeploymentFactory-Implementation-Class property missing from deployer.jar manifest
> ----------------------------------------------------------------------------------
>
> Key: GERONIMO-1399
> URL: http://issues.apache.org/jira/browse/GERONIMO-1399
> Project: Geronimo
> Type: Bug
> Components: deployment
> Versions: 1.0
> Environment: Geronimo 1.0, built a few days ago
> Eclipse SDK 3.1.1
> WTP 1.0 RC 5 and its prerequisites
> Eclipse plug-in, built a few days ago
> Reporter: Lin Sun
> Fix For: 1.0
>
> On Dec 22, 2005, at 4:48 PM, Lin Sun wrote:
> > Thanks. After you point out where the log is, I saw the following
> > in the .log file:
> >
> > java.lang.NullPointerException
> > at java.lang.Class.forName1(Native Method)
> > at java.lang.Class.forName(Class.java(Compiled Code))
> > at
> > org.apache.geronimo.core.GeronimoConnectionFactory.discoverDeploymentF
> > actory(GeronimoConnectionFactory.java:78)
> > at
> > org.apache.geronimo.core.GeronimoConnectionFactory.getDeploymentManage
> > r(GeronimoConnectionFactory.java:45)
> > at
> > org.apache.geronimo.core.CommandLauncher.setDeploymentManager
> > (CommandLauncher.java:87)
> > at org.apache.geronimo.core.CommandLauncher.executeCommand
> > (CommandLauncher.java:61)
> > at
> > org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy
> > (GeronimoServerBehaviour.java:233)
> > at
> > org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeComman
> > d(GeronimoServerBehaviour.java:207)
> > at
> > org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModul
> > e(GeronimoServerBehaviour.java:194)
> > at
> > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul
> > e(ServerBehaviourDelegate.java:658)
> > at
> > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul
> > es(ServerBehaviourDelegate.java:738)
> > at
> > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish
> > (ServerBehaviourDelegate.java:596)
> > at org.eclipse.wst.server.core.internal.Server.doPublish
> > (Server.java:799)
> > at org.eclipse.wst.server.core.internal.Server.publish(Server.java:
> > 788)
> > at org.eclipse.wst.server.core.internal.PublishServerJob.run
> > (PublishServerJob.java:145)
> > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> >
> > --- Sachin Patel <sp...@gmail.com> wrote:
> >
> >> Nevermind, I found the problem. In the future, eclipse plugin
> >> errors/
> >> exceptions can be found in the .log in the workspace metadata. So
> >> you shouldn't just look for errors in the geronimo log.
> >>
> >> I just published and found a NPE attempting to discover the
> >> deploymentFactory. Something must have changed in the runtime that
> >> broke me... I'll look into it.
> >>
> >>
> >> - sachin
> >>
> >>
> >>
> >> On Dec 22, 2005, at 4:21 PM, Sachin Patel wrote:
> >>
> >>> Ok, then please describe your steps, from project creation, to
> >>> deployment.
> >>>
> >>> - sachin
> Steps:
> 1) launch eclipse using eclipse -clean and use a brand new workspace
> 2) change to J2EE view. Define a geronimo server and start it.
> 3) right click dynamic web projects and select import to import
> the hello.war file. Select default/next for everything except uncheck the "add module to
> an ear application" checkbox.
> 4) right click the hello folder and select run as--run on server.
> then I got the "unable to publish error" immediately.
> I'll send you the hello.war file in a seperate note to reduce the size of the email to
> the list.
> Thanks, Lin
--
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
[jira] Closed: (GERONIMO-1399) DeploymentFactory-Implementation-Class property missing from deployer.jar manifest
Posted by "Lin Sun (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1399?page=all ]
Lin Sun closed GERONIMO-1399:
-----------------------------
Verified it is fixed and I can deploy the hello program now.
> DeploymentFactory-Implementation-Class property missing from deployer.jar manifest
> ----------------------------------------------------------------------------------
>
> Key: GERONIMO-1399
> URL: http://issues.apache.org/jira/browse/GERONIMO-1399
> Project: Geronimo
> Type: Bug
> Components: deployment
> Versions: 1.0
> Environment: Geronimo 1.0, built a few days ago
> Eclipse SDK 3.1.1
> WTP 1.0 RC 5 and its prerequisites
> Eclipse plug-in, built a few days ago
> Reporter: Lin Sun
> Assignee: Sachin Patel
> Fix For: 1.0
>
> On Dec 22, 2005, at 4:48 PM, Lin Sun wrote:
> > Thanks. After you point out where the log is, I saw the following
> > in the .log file:
> >
> > java.lang.NullPointerException
> > at java.lang.Class.forName1(Native Method)
> > at java.lang.Class.forName(Class.java(Compiled Code))
> > at
> > org.apache.geronimo.core.GeronimoConnectionFactory.discoverDeploymentF
> > actory(GeronimoConnectionFactory.java:78)
> > at
> > org.apache.geronimo.core.GeronimoConnectionFactory.getDeploymentManage
> > r(GeronimoConnectionFactory.java:45)
> > at
> > org.apache.geronimo.core.CommandLauncher.setDeploymentManager
> > (CommandLauncher.java:87)
> > at org.apache.geronimo.core.CommandLauncher.executeCommand
> > (CommandLauncher.java:61)
> > at
> > org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy
> > (GeronimoServerBehaviour.java:233)
> > at
> > org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeComman
> > d(GeronimoServerBehaviour.java:207)
> > at
> > org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModul
> > e(GeronimoServerBehaviour.java:194)
> > at
> > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul
> > e(ServerBehaviourDelegate.java:658)
> > at
> > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul
> > es(ServerBehaviourDelegate.java:738)
> > at
> > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish
> > (ServerBehaviourDelegate.java:596)
> > at org.eclipse.wst.server.core.internal.Server.doPublish
> > (Server.java:799)
> > at org.eclipse.wst.server.core.internal.Server.publish(Server.java:
> > 788)
> > at org.eclipse.wst.server.core.internal.PublishServerJob.run
> > (PublishServerJob.java:145)
> > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> >
> > --- Sachin Patel <sp...@gmail.com> wrote:
> >
> >> Nevermind, I found the problem. In the future, eclipse plugin
> >> errors/
> >> exceptions can be found in the .log in the workspace metadata. So
> >> you shouldn't just look for errors in the geronimo log.
> >>
> >> I just published and found a NPE attempting to discover the
> >> deploymentFactory. Something must have changed in the runtime that
> >> broke me... I'll look into it.
> >>
> >>
> >> - sachin
> >>
> >>
> >>
> >> On Dec 22, 2005, at 4:21 PM, Sachin Patel wrote:
> >>
> >>> Ok, then please describe your steps, from project creation, to
> >>> deployment.
> >>>
> >>> - sachin
> Steps:
> 1) launch eclipse using eclipse -clean and use a brand new workspace
> 2) change to J2EE view. Define a geronimo server and start it.
> 3) right click dynamic web projects and select import to import
> the hello.war file. Select default/next for everything except uncheck the "add module to
> an ear application" checkbox.
> 4) right click the hello folder and select run as--run on server.
> then I got the "unable to publish error" immediately.
> I'll send you the hello.war file in a seperate note to reduce the size of the email to
> the list.
> Thanks, Lin
--
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
[jira] Commented: (GERONIMO-1399) DeploymentFactory-Implementation-Class property missing from deployer.jar manifest
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1399?page=comments#action_12361185 ]
David Jencks commented on GERONIMO-1399:
----------------------------------------
I'm surprised deployer.jar no longer has this, but if you are using jsr-88 the property should be located in the geronimo-deploy-jsr88-1.0-SNAPSHOT.jar (or version as appropriate) jar. I'd advise using this jar rather than deployer.jar whose contents are not needed for jsr-88 deployments.
> DeploymentFactory-Implementation-Class property missing from deployer.jar manifest
> ----------------------------------------------------------------------------------
>
> Key: GERONIMO-1399
> URL: http://issues.apache.org/jira/browse/GERONIMO-1399
> Project: Geronimo
> Type: Bug
> Components: deployment
> Versions: 1.0
> Environment: Geronimo 1.0, built a few days ago
> Eclipse SDK 3.1.1
> WTP 1.0 RC 5 and its prerequisites
> Eclipse plug-in, built a few days ago
> Reporter: Lin Sun
> Fix For: 1.0
>
> On Dec 22, 2005, at 4:48 PM, Lin Sun wrote:
> > Thanks. After you point out where the log is, I saw the following
> > in the .log file:
> >
> > java.lang.NullPointerException
> > at java.lang.Class.forName1(Native Method)
> > at java.lang.Class.forName(Class.java(Compiled Code))
> > at
> > org.apache.geronimo.core.GeronimoConnectionFactory.discoverDeploymentF
> > actory(GeronimoConnectionFactory.java:78)
> > at
> > org.apache.geronimo.core.GeronimoConnectionFactory.getDeploymentManage
> > r(GeronimoConnectionFactory.java:45)
> > at
> > org.apache.geronimo.core.CommandLauncher.setDeploymentManager
> > (CommandLauncher.java:87)
> > at org.apache.geronimo.core.CommandLauncher.executeCommand
> > (CommandLauncher.java:61)
> > at
> > org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy
> > (GeronimoServerBehaviour.java:233)
> > at
> > org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeComman
> > d(GeronimoServerBehaviour.java:207)
> > at
> > org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModul
> > e(GeronimoServerBehaviour.java:194)
> > at
> > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul
> > e(ServerBehaviourDelegate.java:658)
> > at
> > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul
> > es(ServerBehaviourDelegate.java:738)
> > at
> > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish
> > (ServerBehaviourDelegate.java:596)
> > at org.eclipse.wst.server.core.internal.Server.doPublish
> > (Server.java:799)
> > at org.eclipse.wst.server.core.internal.Server.publish(Server.java:
> > 788)
> > at org.eclipse.wst.server.core.internal.PublishServerJob.run
> > (PublishServerJob.java:145)
> > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> >
> > --- Sachin Patel <sp...@gmail.com> wrote:
> >
> >> Nevermind, I found the problem. In the future, eclipse plugin
> >> errors/
> >> exceptions can be found in the .log in the workspace metadata. So
> >> you shouldn't just look for errors in the geronimo log.
> >>
> >> I just published and found a NPE attempting to discover the
> >> deploymentFactory. Something must have changed in the runtime that
> >> broke me... I'll look into it.
> >>
> >>
> >> - sachin
> >>
> >>
> >>
> >> On Dec 22, 2005, at 4:21 PM, Sachin Patel wrote:
> >>
> >>> Ok, then please describe your steps, from project creation, to
> >>> deployment.
> >>>
> >>> - sachin
> Steps:
> 1) launch eclipse using eclipse -clean and use a brand new workspace
> 2) change to J2EE view. Define a geronimo server and start it.
> 3) right click dynamic web projects and select import to import
> the hello.war file. Select default/next for everything except uncheck the "add module to
> an ear application" checkbox.
> 4) right click the hello folder and select run as--run on server.
> then I got the "unable to publish error" immediately.
> I'll send you the hello.war file in a seperate note to reduce the size of the email to
> the list.
> Thanks, Lin
--
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
[jira] Resolved: (GERONIMO-1399) DeploymentFactory-Implementation-Class property missing from deployer.jar manifest
Posted by "Sachin Patel (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1399?page=all ]
Sachin Patel resolved GERONIMO-1399:
------------------------------------
Resolution: Fixed
Assign To: Sachin Patel
Fixed by pointing to jsr88 jar.
> DeploymentFactory-Implementation-Class property missing from deployer.jar manifest
> ----------------------------------------------------------------------------------
>
> Key: GERONIMO-1399
> URL: http://issues.apache.org/jira/browse/GERONIMO-1399
> Project: Geronimo
> Type: Bug
> Components: deployment
> Versions: 1.0
> Environment: Geronimo 1.0, built a few days ago
> Eclipse SDK 3.1.1
> WTP 1.0 RC 5 and its prerequisites
> Eclipse plug-in, built a few days ago
> Reporter: Lin Sun
> Assignee: Sachin Patel
> Fix For: 1.0
>
> On Dec 22, 2005, at 4:48 PM, Lin Sun wrote:
> > Thanks. After you point out where the log is, I saw the following
> > in the .log file:
> >
> > java.lang.NullPointerException
> > at java.lang.Class.forName1(Native Method)
> > at java.lang.Class.forName(Class.java(Compiled Code))
> > at
> > org.apache.geronimo.core.GeronimoConnectionFactory.discoverDeploymentF
> > actory(GeronimoConnectionFactory.java:78)
> > at
> > org.apache.geronimo.core.GeronimoConnectionFactory.getDeploymentManage
> > r(GeronimoConnectionFactory.java:45)
> > at
> > org.apache.geronimo.core.CommandLauncher.setDeploymentManager
> > (CommandLauncher.java:87)
> > at org.apache.geronimo.core.CommandLauncher.executeCommand
> > (CommandLauncher.java:61)
> > at
> > org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy
> > (GeronimoServerBehaviour.java:233)
> > at
> > org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeComman
> > d(GeronimoServerBehaviour.java:207)
> > at
> > org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModul
> > e(GeronimoServerBehaviour.java:194)
> > at
> > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul
> > e(ServerBehaviourDelegate.java:658)
> > at
> > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul
> > es(ServerBehaviourDelegate.java:738)
> > at
> > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish
> > (ServerBehaviourDelegate.java:596)
> > at org.eclipse.wst.server.core.internal.Server.doPublish
> > (Server.java:799)
> > at org.eclipse.wst.server.core.internal.Server.publish(Server.java:
> > 788)
> > at org.eclipse.wst.server.core.internal.PublishServerJob.run
> > (PublishServerJob.java:145)
> > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> >
> > --- Sachin Patel <sp...@gmail.com> wrote:
> >
> >> Nevermind, I found the problem. In the future, eclipse plugin
> >> errors/
> >> exceptions can be found in the .log in the workspace metadata. So
> >> you shouldn't just look for errors in the geronimo log.
> >>
> >> I just published and found a NPE attempting to discover the
> >> deploymentFactory. Something must have changed in the runtime that
> >> broke me... I'll look into it.
> >>
> >>
> >> - sachin
> >>
> >>
> >>
> >> On Dec 22, 2005, at 4:21 PM, Sachin Patel wrote:
> >>
> >>> Ok, then please describe your steps, from project creation, to
> >>> deployment.
> >>>
> >>> - sachin
> Steps:
> 1) launch eclipse using eclipse -clean and use a brand new workspace
> 2) change to J2EE view. Define a geronimo server and start it.
> 3) right click dynamic web projects and select import to import
> the hello.war file. Select default/next for everything except uncheck the "add module to
> an ear application" checkbox.
> 4) right click the hello folder and select run as--run on server.
> then I got the "unable to publish error" immediately.
> I'll send you the hello.war file in a seperate note to reduce the size of the email to
> the list.
> Thanks, Lin
--
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