1 2 Previous Next 28 Replies Latest reply on Dec 22, 2008 8:11 AM by maxandersen Go to original post
      • 15. Re: XSD validation in Eclipse
        maxandersen

        that is just about the double registration of find references both done by springide and jboss tools...this should not effect the editors syntax highlight and completion

        • 16. Re: XSD validation in Eclipse
          speleomaniac

          Any futher suggestions for me, I don't know how can I further investigate the problem...

          To send my Eclipse instance would not help alot I think (it is around 300 mb)....

          How can I activate this not activated seam plugin, there must be something that I can do, I hope....

          • 17. Re: XSD validation in Eclipse
            akazakov

            Try to install fresh JBossTools 3.0.0 nightly build
            http://download.jboss.org/jbosstools/builds/nightly/3.0.0.GA/
            with fresh Eclipse 3.4.1 + other Build Drivers (see full list of drivers on nightly build page.
            Does code assist work there?

            • 18. Re: XSD validation in Eclipse
              nickboldt

              Some other things to check:

              a) you're using Open JDK 6.0, or Sun JDK, IBM JDK, or BEA JRockit version 5.0 or 6.0
              b) you're using matching JVM and Eclipse version (32-bit or 64-bit)
              c) you're using a compatible stack of projects under JBoss Tools 3.0 (Web Tools 3, EMF 2.4, XSD 2.4, Eclipse 3.4, BIRT 2.3 (only required for JBoss BIRT feature))

              See also:

              http://wiki.eclipse.org/IRC_FAQ#How_do_I_start_Eclipse.3F
              http://wiki.eclipse.org/IRC_FAQ#How_do_I_debug_Eclipse.3F_How_can_I_see_what_plugins_are_being_started.3F_How_do_I_start_the_OSGi_console.3F
              http://wiki.eclipse.org/IRC_FAQ#I.27m_having_memory.2C_heap.2C_or_permgen_problems.2C_what_can_I_do.3F

              • 19. Re: XSD validation in Eclipse
                speleomaniac

                Well when I have to answer in order

                a) Nope I have Sun JDK 1.5
                b) I have 32 bit JVM and Eclipse
                c) I can't say exactly but my eclipse confiugration is at the begining of the thread

                I will check the link

                • 20. Re: XSD validation in Eclipse
                  nickboldt

                  You're using Sun 6.0, actually.

                  java.specification.vendor=Sun Microsystems Inc.
                  java.specification.version=1.6
                  java.version=1.6.0_10

                  If you want to force Eclipse to use 5.0, use the -vm /path/to/java.exe (or to javaw.exe).

                  I think you might have to reinstall WTP. I don't see any Web Tools 3.0 plugins in the list. You can get them from the Ganymede update site.

                  • 21. Re: XSD validation in Eclipse
                    speleomaniac

                    I just downloaded a new Eclipse from http://www.eclipse.org/downloads/packages/ (Eclipse IDE for JEE Developer) and set the -vm option to 1.5 JDK...

                    And a nightly build of JBoss Tools into the dropins, same result...

                    No content assist in components.xml....

                    • 22. Re: XSD validation in Eclipse
                      maxandersen

                      does it open in JBoss Tools XML Editor ?

                      Or just plain text editor ?

                      • 23. Re: XSD validation in Eclipse
                        maxandersen

                        btw. it works out of the box for me....

                        Please run eclipse with -debug and tell us what is in the error log.

                        • 24. Re: XSD validation in Eclipse
                          speleomaniaque

                          Ok I guess I figured out what is going on....

                          I downloaded latest Ganymede JEE and make the installation from update site 'http://download.jboss.org/jbosstools/updates/nightly/trunk/' also including the BIRT update site 'http://download.eclipse.org/birt/update-site/2.3/' (actually I followed the instruction from the Web Site 'http://www.jboss.org/community/docs/DOC-10044').

                          Now everything works fines, I can see the Seam Tools in installed software part of the software updates...

                          My problems caused by the fact that I was using the dropins functionality of the Ganymede...

                          When I used the update site, it is automatically configuring the dependencies and everything, how can i make it work with dropins functionality... (I actually won't to use dropins functionality it fits better for nightly build)

                          Should I have to place the whole BIRT in dropins also or can Eclipse configure that itself?

                          • 25. Re: XSD validation in Eclipse
                            speleomaniaque

                            Ok if I deploy nightly with dropins I see this in log file

                            !SESSION 2008-12-21 16:35:01.285 -----------------------------------------------
                            eclipse.buildId=M20080911-1700
                            java.version=1.6.0_10
                            java.vendor=Sun Microsystems Inc.
                            BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
                            Command-line arguments: -os win32 -ws win32 -arch x86

                            !ENTRY org.eclipse.equinox.p2.metadata.repository 2 0 2008-12-21 16:42:22.052
                            !MESSAGE Error parsing metadata repository
                            !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-12-21 16:42:22.053
                            !MESSAGE Error at line 10, column 91: Missing required attribute in "repository": url
                            !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-12-21 16:42:22.053
                            !MESSAGE Error at line 10, column 91: Illegal value for attribute "url" of element "repository": null
                            !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-12-21 16:42:22.053
                            !MESSAGE Error at line 11, column 91: Missing required attribute in "repository": url
                            !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-12-21 16:42:22.053
                            !MESSAGE Error at line 11, column 91: Illegal value for attribute "url" of element "repository": null
                            !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-12-21 16:42:22.053
                            !MESSAGE Error at line 12, column 90: Missing required attribute in "repository": url
                            !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-12-21 16:42:22.053
                            !MESSAGE Error at line 12, column 90: Illegal value for attribute "url" of element "repository": null
                            !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-12-21 16:42:22.053
                            !MESSAGE Error at line 13, column 90: Missing required attribute in "repository": url
                            !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-12-21 16:42:22.053
                            !MESSAGE Error at line 13, column 90: Illegal value for attribute "url" of element "repository": null
                            !SESSION 2008-12-21 16:44:51.511 -----------------------------------------------
                            eclipse.buildId=M20080911-1700
                            java.version=1.6.0_10
                            java.vendor=Sun Microsystems Inc.
                            BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
                            Command-line arguments: -os win32 -ws win32 -arch x86 -clean -debug -console

                            !ENTRY org.eclipse.equinox.p2.director 2 0 2008-12-21 16:45:13.152
                            !MESSAGE Problems resolving provisioning plan.
                            !SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-12-21 16:45:13.152
                            !MESSAGE Unable to satisfy dependency from org.jboss.tools.birt.core 1.0.0.GA-N200812201616 to requiredCapability: osgi.bundle/org.eclipse.birt.integration.wtp.ui/0.0.0.
                            !SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-12-21 16:45:13.152
                            !MESSAGE Unable to satisfy dependency from org.jboss.tools.eclipse.as.tptp 1.0.0 to requiredCapability: osgi.bundle/org.eclipse.hyades.trace.ui/0.0.0.
                            !SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-12-21 16:45:13.152
                            !MESSAGE Unable to satisfy dependency from org.jboss.tools.eclipse.as.tptp 1.0.0 to requiredCapability: osgi.bundle/org.eclipse.tptp.platform.jvmti.client/0.0.0.
                            !SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-12-21 16:45:13.152
                            !MESSAGE Unable to satisfy dependency from org.jboss.tools.eclipse.as.tptp 1.0.0 to requiredCapability: osgi.bundle/org.eclipse.tptp.platform.execution/0.0.0.
                            !SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-12-21 16:45:13.152
                            !MESSAGE Unable to satisfy dependency from org.jboss.tools.eclipse.as.tptp 1.0.0 to requiredCapability: osgi.bundle/org.eclipse.tptp.platform.profile.server.core/0.0.0.
                            !SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-12-21 16:45:13.152
                            !MESSAGE Unable to satisfy dependency from org.jboss.tools.eclipse.as.tptp 1.0.0 to requiredCapability: osgi.bundle/org.eclipse.tptp.platform.instrumentation.ui/4.3.100.
                            !SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-12-21 16:45:13.152
                            !MESSAGE Unable to satisfy dependency from org.jboss.tools.birt.feature.feature.group 1.0.0.GA-N200812201616 to requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.birt.feature.group/[2.3.1,3.0.0).
                            !SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-12-21 16:45:13.152
                            !MESSAGE Unable to satisfy dependency from org.jboss.tools.birt.feature.feature.group 1.0.0.GA-N200812201616 to requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.birt.integration.wtp.feature.group/[2.3.1,3.0.0).
                            !SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-12-21 16:45:13.156
                            !MESSAGE Unable to satisfy dependency from org.jboss.tools.birt.feature.feature.group 1.0.0.GA-N200812201616 to requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.birt.integration.wtp.ui/[2.3.1.v20080827,2.3.1.v20080827].

                            !ENTRY org.eclipse.equinox.p2.reconciler.dropins 4 0 2008-12-21 16:45:50.205
                            !MESSAGE
                            !STACK 0
                            org.osgi.framework.BundleException: State change in progress for bundle "reference:file:plugins\org.eclipse.equinox.p2.reconciler.dropins_1.0.2.R34x_v20080909.jar" by thread "Start Level Event Dispatcher".
                            at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1144)
                            at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:529)
                            at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1104)
                            at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.suspendBundle(PackageAdminImpl.java:281)
                            at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.processDelta(PackageAdminImpl.java:416)
                            at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.doResolveBundles(PackageAdminImpl.java:224)
                            at org.eclipse.osgi.framework.internal.core.PackageAdminImpl$1.run(PackageAdminImpl.java:162)
                            at java.lang.Thread.run(Unknown Source)
                            Caused by: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
                            ... 8 more
                            Root exception:
                            org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
                            at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1144)
                            at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:529)
                            at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1104)
                            at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.suspendBundle(PackageAdminImpl.java:281)
                            at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.processDelta(PackageAdminImpl.java:416)
                            at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.doResolveBundles(PackageAdminImpl.java:224)
                            at org.eclipse.osgi.framework.internal.core.PackageAdminImpl$1.run(PackageAdminImpl.java:162)
                            at java.lang.Thread.run(Unknown Source)

                            !ENTRY org.eclipse.equinox.p2.metadata.repository 4 0 2008-12-21 16:45:53.672
                            !MESSAGE ProvisioningEventBus could not be obtained. Metadata caches may not be cleaned up properly.

                            !ENTRY org.eclipse.equinox.p2.garbagecollector 4 0 2008-12-21 16:45:53.695
                            !MESSAGE ProvisioningEventBus service could not be obtained, CoreGarbageCollector will not function properly.

                            • 26. Re: XSD validation in Eclipse
                              maxandersen

                              The last log seem to indicate some bug in p2 updatesite - it shouldn't throw an exception like this.

                              About dropin then it should work and surprised it doesn't - report it in jira please.

                              And finally missing the birt dependency should *not* result in code completion not working - sounds like something big was missing from your eclipse install, i.e. WTP xml editors ?

                              • 27. Re: XSD validation in Eclipse
                                speleomaniaque

                                Before I place JBoss Nightly in dropins directory, I installed manually from tptp and BIRT from their update site and now everything working fine...

                                Should open a bug as 'dropins functionality doesn' work because of missing dependencies' or you mean something else....

                                • 28. Re: XSD validation in Eclipse
                                  maxandersen

                                  yes, please report it in jira with steps to reproduce.

                                  missing Birt should not result in code completion to fail!

                                  1 2 Previous Next