Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-16854

NPE when publishing ticket-monster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.2.0.Beta1
    • 4.2.0.Beta1
    • server
    • Hide

      1. Checkout ticket monster from here:
      https://github.com/mmalina/ticket-monster/tree/JBIDE-14659
      e.g. git clone git@github.com:mmalina/ticket-monster.git
      cd ticket-monster
      git checkout origin/JBIDE-14659
      2. Import to eclipse as existing maven project:
      File -> Import -> Maven -> Existing Maven project
      and point it to the demo folder.
      3. Wait for Eclipse to resolve maven dependencies
      4. Finally the project has an error decorator and I see this in Problems view:
      console configuration "ticket-monster-TRUNK" does not exist - line 0 - JPA Problem

      • this is somewhat strange since it cannot be tracked to a file, but never mind now
        5. Set up and start JBoss AS 7.1.1
        6. In server view, select server -> Add and Remove... and add ticket-monster
        7. When you click Finish to add the project, you will be shown this:
        Publishing to jboss-as-7.1.1.Final... has encountered a problem
        Could not publish to the server.
        java.lang.NullPointerException
        What's more, the project is shown in the list of server modules (without any decorator), so it seems it's deployed, but in fact it is not.
      Show
      1. Checkout ticket monster from here: https://github.com/mmalina/ticket-monster/tree/JBIDE-14659 e.g. git clone git@github.com:mmalina/ticket-monster.git cd ticket-monster git checkout origin/ JBIDE-14659 2. Import to eclipse as existing maven project: File -> Import -> Maven -> Existing Maven project and point it to the demo folder. 3. Wait for Eclipse to resolve maven dependencies 4. Finally the project has an error decorator and I see this in Problems view: console configuration "ticket-monster-TRUNK" does not exist - line 0 - JPA Problem this is somewhat strange since it cannot be tracked to a file, but never mind now 5. Set up and start JBoss AS 7.1.1 6. In server view, select server -> Add and Remove... and add ticket-monster 7. When you click Finish to add the project, you will be shown this: Publishing to jboss-as-7.1.1.Final... has encountered a problem Could not publish to the server. java.lang.NullPointerException What's more, the project is shown in the list of server modules (without any decorator), so it seems it's deployed, but in fact it is not.

      While verifying JBIDE-14659 I got a NPE when I tried to do "Server -> Add or Remove from server" to deploy the ticket-monster project.

      !ENTRY org.eclipse.wst.server.core 4 0 2014-03-24 12:54:02.397
!MESSAGE Could not publish to the server.
!STACK 0
java.lang.NullPointerException
	at org.jboss.ide.eclipse.as.core.publishers.patterns.ModuleDirectoryScannerPathFilter.explode(ModuleDirectoryScannerPathFilter.java:51)
	at org.jboss.ide.eclipse.as.core.publishers.patterns.ModuleDirectoryScannerPathFilter.<init>(ModuleDirectoryScannerPathFilter.java:46)
	at org.jboss.ide.eclipse.as.core.modules.ResourceModuleResourceUtil.findDefaultModuleFilter(ResourceModuleResourceUtil.java:76)
	at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.publishModule(StandardFileSystemPublishController.java:273)
	at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:134)
	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
	at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3154)
	at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

              adietish@redhat.com André Dietisheim
              exd-mmalina Martin Malina
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: