Yes, thats is the problem. Mind opening a defect for it, so I don't
forget?
- sachin
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 <[EMAIL PROTECTED]> 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
On Dec 22, 2005, at 4:16 PM, Lin Sun wrote:
I am not seeing any error in the geronimo server log. Any other
logs I can check?
Thanks, Lin
--- Sachin Patel <[EMAIL PROTECTED]> wrote:
What is the error you are getting?
- sachin
On Dec 22, 2005, at 3:15 PM, Lin Sun wrote:
I tried a simple hello war program and cannot publish it via the
eclipse plugin.
I am using:
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
Anyone able to publish some war file via the plugin?
Thanks, Lin
--- Sachin Patel <[EMAIL PROTECTED]> wrote:
The editors are being rewritten properly to move to a EMF based
editors. I recently started this, so most likely the editors
are
broken.
The XML Source view and the design view are not
synchronized. The
design view always shows the in-memory view of the model, and
the
source view shows the serialized version of the model.
Modifying the
XMLSource view does not reflect the model, unless the model is
completley reloaded by closing and reopening the editors.
Having a
synchronized source view is possible, but will be a very
challenging
task I have not yet looked into tackling. Any code donations
for
this functionality will be greatly appreciated.
As far as the deploy error, Geronimo M5 is not supported. The
plugins package the 1.0 deployment jars, and there will be no
backward compatibility support to M5. The Geronimo Eclipse
plugin
will only support every released version of the Geronimo, but
not
milestone drivers.
- sachin
On Dec 22, 2005, at 12:32 PM, Rajiv M wrote:
Hello,
I tried a web app on the following environment - a jsp which
uses a
mySQL JDBC resource
Geronimo 1.0 MD5
Eclipse SDK 3.1.1
WTP 1.0 RC 5
Eclipse plug-in latest build from Geronimo site.
I observed the following issues:
1. If i try to add a resource via Naming tab, on the first
click I
get an error, which does not describe anything but to verify
workspace ".log". A missing resource exception is logged here..
2. Any resource added in the resource dialog are not getting
reflected in the Naming screen when clicked OK.
3. Resource references present in the XML Source view disappear
when Naming view is selected
4. App does not deploy and fails at config store creation.
There
are no exception traced in server.log but an exception is
logged in
the workspace log
~Rajiv
__________________________________
Yahoo! for Good - Make a difference this year.
http://brand.yahoo.com/cybergivingweek2005/
__________________________________
Yahoo! for Good - Make a difference this year.
http://brand.yahoo.com/cybergivingweek2005/
thanks,
Lin
__________________________________________
Yahoo! DSL – Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com