[JBoss JIRA] (JBIDE-13683) JPP not instantiated by runtime detection
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13683?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13683:
------------------------------------
Release Notes Docs Status: Documented as Resolved Issue (was: Not Yet Documented)
Writer: mmurray
Release Notes Text: Runtime detection is used to recognize and create instances of runtime servers. Although runtime detection recognized JBoss Portal Platform installations as runtime servers, it failed to create associated server instances. This issue has been resolved by updating the server bean loaders to identify JBoss Portal Platform runtime servers more specifically and by updating the runtime detection to ensure no likely server types are ignored in the future. As a result, JBoss Portal Platform runtime servers are now recognized and instantiated by runtime detection. (was: Cause: The direct cause of this issue is that runtime detection was not updated to properly handle the second phase of instantiating the runtime into a server adapter.
Consequence: A JPP installation would be recognized by runtime detection, but would not have a server adapter created for the user to make use of.
Fix: The complete fix is to update the server bean loaders to have a more specific identification of jpp servers, as well as to update the runtime detection to ensure no likely server types are ignored in the future
Result: A jpp installation will now be recognized AND instantiated into a proper server adapter. )
> JPP not instantiated by runtime detection
> -----------------------------------------
>
> Key: JBIDE-13683
> URL: https://issues.jboss.org/browse/JBIDE-13683
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.1.Final
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
>
> Use runtime detection against a folder containing JPP 6, and try to have it create the server. It does not create any server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13335) remove Juno SR1+ performance fix from Central
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13335:
------------------------------------
Release Notes Docs Status: Documented as Resolved Issue (was: Documented as Known Issue)
> remove Juno SR1+ performance fix from Central
> ----------------------------------------------
>
> Key: JBIDE-13335
> URL: https://issues.jboss.org/browse/JBIDE-13335
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: respin-a
> Fix For: 4.0.1.Final
>
> Attachments: JBIDE13335-patched-sr2.png, JBIDE13335-sr1-can-update-to-sr2.png, JBIDE13335.patch.JBDS6.0.1.txt
>
>
> For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars.
> Need to therefore, for JBT 4.0.1 and JBDS 6.0.1:
> a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places)
> b) remove the connector from discovery plugins' plugin.xml (2 files)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13346) DirectoryScanner fails on non-existing folders
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13346?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13346:
------------------------------------
Release Notes Docs Status: Documented as Resolved Issue (was: Documented as Known Issue)
> DirectoryScanner fails on non-existing folders
> ----------------------------------------------
>
> Key: JBIDE-13346
> URL: https://issues.jboss.org/browse/JBIDE-13346
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Archives, JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: Windows XP/Windows 7
> Eclipse 4.3M4
> Reporter: Jesper Skov
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
> Attachments: org.eclipse.wst.common.component
>
>
> DirectoryScanner can be made to fail on non-existing folders.
> In our setup, these folders are possibly picked up from the Deployment Assembly settings.
> The folders are created by our custom Builder with highest priority, so appears to work properly with everything else in Eclipse.
> But it seems the Archive DirectoryScanner runs before our builder.
> The stack trace looks like this:
>
> {code}
> java.lang.IllegalStateException: basedir C:\udvikler\ws\plugins\jb.it.reuters\build\gen-lib-deployable is not a directory
> at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scanPrepare(DirectoryScanner.java:552)
> at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scan(DirectoryScanner.java:588)
> at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory.createDirectoryScanner(DirectoryScannerFactory.java:66)
> at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent$WorkspaceFilter.<init>(WorkspaceFilesetVirtualComponent.java:100)
> at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent.getRootFolder(WorkspaceFilesetVirtualComponent.java:53)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.consumeComponent(FlatVirtualComponent.java:203)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.addConsumedReferences(FlatVirtualComponent.java:196)
> at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.optimize(ClasspathLibraryExpander.java:47)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:119)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.fetchResources(FlatVirtualComponent.java:101)
> at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.fetchResource(ClasspathLibraryExpander.java:74)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.getBaseEARLibRefs(J2EEComponentClasspathContainer.java:463)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.requiresUpdate(J2EEComponentClasspathContainer.java:208)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.refresh(J2EEComponentClasspathContainer.java:540)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.processModules(J2EEComponentClasspathUpdater.java:311)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.access$4(J2EEComponentClasspathUpdater.java:295)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob$1.run(J2EEComponentClasspathUpdater.java:336)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.run(J2EEComponentClasspathUpdater.java:321)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13537) Unable to create EAP6.1 server [4.0.1 maintenance]
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13537?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13537:
------------------------------------
Release Notes Docs Status: Documented as Resolved Issue (was: Documented as Known Issue)
> Unable to create EAP6.1 server [4.0.1 maintenance]
> ---------------------------------------------------
>
> Key: JBIDE-13537
> URL: https://issues.jboss.org/browse/JBIDE-13537
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers, runtime-detection
> Affects Versions: 4.1.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.0.1.Final
>
> Attachments: New Server Runtime Environment _002.png, New Server Runtime Environment _003.png
>
>
> EAP6.1 is detected via runtime detection but nothing happens when I click OK to create runtime. Also manually adding it through Runtime Enviroment -> add -> EAP6.x does not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13601) Backport to 4.0.x - [Eclipse Integration] GPE's "GWT Compile" doesn't create the errai classes
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13601?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13601:
------------------------------------
Writer: mmurray
Release Notes Text: GWT web projects must be compiled using GWT Compile before being deployed on the server. However, GWT Compile did not create the required Errai classes when compiling GWT web projects and, as a result, errors occurred during application deployment. To solve this issue, the Maven Configurator Plug-in for GWT was modified. Now GWT Compile creates the required Errai classes and applications deploy without errors. (was: Cause: Google Plugin for Eclipse action "GWT Compile" doesn't create required errai classes
Consequence: Application deployment errors
Fix: Maven GWT Configurator plugin changed to configure GPE properly
Result: No application deployment errors)
> Backport to 4.0.x - [Eclipse Integration] GPE's "GWT Compile" doesn't create the errai classes
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13601
> URL: https://issues.jboss.org/browse/JBIDE-13601
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.0.0.Final
> Environment: Windows 7, Google Plugin for Eclipse 2.5.2, JBoss Tools 3.3.0.Beta1, m2e 1.0.100, m2e-wtp 0.15.2
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Labels: new_and_noteworthy
> Fix For: 4.0.1.Final
>
> Attachments: 0001-JBIDE-13487-fix-errai-deployment-issues.patch
>
>
> We're trying to achieve the following workflow for the user inside Eclipse/ GPE / JBoss Tools:
> * create project
> * execute Google > GWT Compile
> * Run As > Run On Server
> * browse the application
> When a gwt maven project is detected, GPE sets the GWT compilation output directory to target/<artifactId>-<version>/. So ultimately we could automatically mark that folder as deployable for WTP and pretty much achieve that ideal workflow.
> Until this is done automatically, we can do it manually. Here's a slightly more complex workflow :
> * Create a new GWT Project from JBoss Central
> * Right-click on project > Google > GWT compile
> * Add the Kitchensink module
> * Click on Compile. Upon completion, a target/<artifactId>-<version> folder is created
> * Right-click on project > Properties > Deployment Assembly
> * Click Add > folder > select target/<artifactId>-<version> click ok to complete
> * Right-click on project > Run As > Run on server
> * select JBoss AS7 / EAP, OK
> * Project deploys without errors
> * KitchenSink.html is displayed in browser, with the full form.
> Problem is, when the page is displayed, the following exceptions appear in the AS console :
> {noformat}
> 23:24:33,487 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment jesuisoula.war
> 23:24:33,784 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) configuring Errai CDI
> 23:24:33,789 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) Created Errai-CDI context: cbc75356-e760-43e2-9faf-e32025719b58
> 23:24:33,964 INFO [ErraiJNDI] (MSC service thread 1-2) searching to see if ErraiService is already bound...
> 23:24:34,167 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/classes/
> 23:24:34,168 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-bus-2.0-SNAPSHOT.jar/
> 23:24:34,169 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-cdi-client-2.0-SNAPSHOT.jar/
> 23:24:34,170 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-ioc-2.0-SNAPSHOT.jar/
> 23:24:34,171 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-marshalling-2.0-SNAPSHOT.jar/
> 23:24:34,171 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-tools-2.0-SNAPSHOT.jar/
> 23:24:34,172 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-weld-integration-2.0-SNAPSHOT.jar/
> 23:24:34,206 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-tools-2.0-SNAPSHOT.jar/
> 23:24:34,368 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-cdi-client-2.0-SNAPSHOT.jar/
> 23:24:34,389 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-bus-2.0-SNAPSHOT.jar/
> 23:24:34,692 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-marshalling-2.0-SNAPSHOT.jar/
> 23:24:34,783 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-weld-integration-2.0-SNAPSHOT.jar/
> 23:24:34,821 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/classes/
> 23:24:34,833 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-ioc-2.0-SNAPSHOT.jar/
> 23:24:34,898 INFO [org.jboss.errai.reflections.Reflections] (Thread-70) Reflections took 690 ms to scan 7 urls, producing 311 keys and 1031 values
> 23:24:34,899 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-tools-2.0-SNAPSHOT.jar/
> 23:24:35,332 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-cdi-client-2.0-SNAPSHOT.jar/
> 23:24:35,344 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-bus-2.0-SNAPSHOT.jar/
> 23:24:35,505 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-marshalling-2.0-SNAPSHOT.jar/
> 23:24:35,597 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-weld-integration-2.0-SNAPSHOT.jar/
> 23:24:35,627 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/classes/
> 23:24:35,637 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-ioc-2.0-SNAPSHOT.jar/
> 23:24:35,703 INFO [org.jboss.errai.reflections.Reflections] (Thread-70) Reflections took 804 ms to scan 7 urls, producing 311 keys and 1031 values
> 23:24:35,815 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (MSC service thread 1-2) Bootstrap Errai
> 23:24:35,816 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (MSC service thread 1-2) Working directory: D:\Dev\servers\jboss-eap-6.0-ER3\bin
> 23:24:35,818 INFO [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (MSC service thread 1-2) using dispatcher implementation: org.jboss.errai.bus.server.SimpleDispatcher
> 23:24:35,825 INFO [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (MSC service thread 1-2) using session provider implementation: org.jboss.errai.bus.server.HttpSessionProvider
> 23:24:35,837 INFO [org.jboss.errai.bus.server.service.bootstrap.LoadExtensions] (MSC service thread 1-2) searching for Errai extensions ...
> 23:24:35,847 INFO [org.jboss.errai.bus.server.service.bootstrap.LoadExtensions] (MSC service thread 1-2) found extension org.jboss.errai.tools.monitoring.MonitorExtension
> 23:24:35,899 INFO [org.jboss.errai.bus.server.service.bootstrap.DiscoverServices] (MSC service thread 1-2) auto-discovery of services disabled.
> 23:24:35,900 INFO [org.jboss.errai.bus.server.service.bootstrap.BootstrapContext] (MSC service thread 1-2) Running deferred bootstrap tasks ...
> 23:24:35,900 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (MSC service thread 1-2) Initialization complete
> 23:24:35,930 INFO [ErraiJNDI] (MSC service thread 1-2) found ErraiService bound at: java:global/ErraiService
> 23:24:35,947 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) Register RPC Endpoint: public@ApplicationScoped @Service class org.jboss.tools.gwt.kitchensink.controller.MemberServiceImpl(interface org.jboss.tools.gwt.kitchensink.client.shared.MemberService)
> 23:24:36,328 INFO [org.jboss.web] (MSC service thread 1-4) JBAS018210: Registering web context: /jesuisoula
> 23:24:36,335 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015874: JBoss EAP 6.0.0.Beta1 (AS 7.1.0.Final-redhat-1) started in 20026ms - Started 195 of 268 services (72 services are passive or on-demand)
> 23:24:36,398 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "jesuisoula.war"
> 23:24:40,547 INFO [ErraiMarshalling] (http-localhost-127.0.0.1-8080-1) searching for marshaller class: org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl
> 23:24:40,548 WARN [ErraiMarshalling] (http-localhost-127.0.0.1-8080-1) could not locate marshaller class. will attempt dynamic generation.
> 23:24:40,562 INFO [org.jboss.errai.marshalling.rebind.MarshallerGeneratorFactory] (http-localhost-127.0.0.1-8080-1) generating marshalling class...
> 23:24:40,622 INFO [org.jboss.errai.marshalling.rebind.MarshallerGeneratorFactory] (http-localhost-127.0.0.1-8080-1) Checking ErraiApp.properties for configured types ...
> 23:24:40,662 INFO [org.jboss.errai.marshalling.rebind.MarshallerGeneratorFactory] (http-localhost-127.0.0.1-8080-1) comprehended 59 classes
> 23:24:41,049 INFO [org.jboss.errai.marshalling.rebind.MarshallerGeneratorFactory] (http-localhost-127.0.0.1-8080-1) generated marshalling class in 486ms.
> 23:24:42,057 INFO [stdout] (http-localhost-127.0.0.1-8080-1) *** FAILED TO COMPILE MARSHALLER CLASS ***
> 23:24:42,058 INFO [stdout] (http-localhost-127.0.0.1-8080-1) *** Classpath Used: D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-bus-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-cdi-client-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-ioc-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-marshalling-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-tools-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-weld-integration-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\jboss-modules.jar;D:\Dev\servers\jboss-eap-6.0-ER3\modules\com\sun\jsf-impl\main\jsf-impl-2.1.5-redhat-1.jar;D:\Dev\servers\jboss-eap-6.0-ER3\modules\org\jboss\as\weld\main\jboss-as-weld-7.1.0.Final-redhat-1.jar;D:\Dev\servers\jboss-eap-6.0-ER3\jboss-modules.jar
> 23:24:42,066 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'uniqueConstraints()' in type 'javax.persistence.Table': class file for javax.persistence.Table not found
> 23:24:42,071 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'columnNames()' in type 'javax.persistence.UniqueConstraint': class file for javax.persistence.UniqueConstraint not found
> 23:24:42,076 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'min()' in type 'javax.validation.constraints.Size': class file for javax.validation.constraints.Size not found
> 23:24:42,081 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'max()' in type 'javax.validation.constraints.Size'
> 23:24:42,086 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'regexp()' in type 'javax.validation.constraints.Pattern': class file for javax.validation.constraints.Pattern not found
> 23:24:42,092 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'message()' in type 'javax.validation.constraints.Pattern'
> 23:24:42,097 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'min()' in type 'javax.validation.constraints.Size'
> 23:24:42,103 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'max()' in type 'javax.validation.constraints.Size'
> 23:24:42,110 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'fraction()' in type 'javax.validation.constraints.Digits': class file for javax.validation.constraints.Digits not found
> 23:24:42,117 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'integer()' in type 'javax.validation.constraints.Digits'
> 23:24:42,124 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'name()' in type 'javax.persistence.Column': class file for javax.persistence.Column not found
> 23:24:42,128 INFO [stdout] (http-localhost-127.0.0.1-8080-1) error: Bad service configuration file, or exception thrown while constructing Processor object: javax.annotation.processing.Processor: Provider org.jboss.errai.common.rebind.ModuleAnnotationProcessor not found
> 23:24:42,129 ERROR [ErraiMarshalling] (http-localhost-127.0.0.1-8080-1) failed to load static marshallers: java.lang.NullPointerException
> at org.jboss.errai.marshalling.server.MappingContextSingleton.loadPrecompiledMarshallers(MappingContextSingleton.java:98) [errai-marshalling-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at org.jboss.errai.marshalling.server.MappingContextSingleton.<clinit>(MappingContextSingleton.java:78) [errai-marshalling-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at org.jboss.errai.bus.server.io.MessageFactory.getParts(MessageFactory.java:109) [errai-bus-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at org.jboss.errai.bus.server.io.MessageFactory.createCommandMessage(MessageFactory.java:93) [errai-bus-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at org.jboss.errai.bus.server.servlet.DefaultBlockingServlet.doPost(DefaultBlockingServlet.java:117) [errai-bus-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final-redhat-1.jar:2012-02-22 16:46]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31]
> 23:24:42,147 INFO [ErraiMarshalling] (http-localhost-127.0.0.1-8080-1) failing over to dynamic marshallers ... performance may be affected.
> {noformat}
> It turns out some files are missing from the deployment folder :
> * WEB-INF/classes/classlist.mf
> * WEB-INF/classes/org/jboss/errai/**
> These files should be created under the project /target/classes folder in the first place, during GWT Compile, as would mvn package do.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13537) Unable to create EAP6.1 server [4.0.1 maintenance]
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13537?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13537:
------------------------------------
Release Notes Docs Status: Documented as Known Issue (was: Not Yet Documented)
Writer: mmurray
Release Notes Text: JBoss Enterprise Application Platform 6.1 has a different module directory structure to previous releases of JBoss Enterprise Application Platform. Consequently, JBoss Enterprise Application Platform 6.1 was not recognized with either the new server wizard, runtime detection or Server->Runtime Environments in Preferences and servers could not be created. A new JBoss Enterprise Application Platform 6.1 (Tech Preview) server adapter has been created and integrated into the existing tooling. This recognizes JBoss Enterprise Application Platform 6.1 and allows associated server instances to be created. (was: Cause: EAP 6.1 has a different structure of its modules folder, rendering all attempts to recognize the server as failed.
Consequence: A user could not complete the new server wizard.
Fix: The fix involved adding a new EAP 6.1 (Tech Preview) server adapter, as well as all changes that go along with that.
Result: An EAP 6.1 server will now be recognized. )
> Unable to create EAP6.1 server [4.0.1 maintenance]
> ---------------------------------------------------
>
> Key: JBIDE-13537
> URL: https://issues.jboss.org/browse/JBIDE-13537
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers, runtime-detection
> Affects Versions: 4.1.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.0.1.Final
>
> Attachments: New Server Runtime Environment _002.png, New Server Runtime Environment _003.png
>
>
> EAP6.1 is detected via runtime detection but nothing happens when I click OK to create runtime. Also manually adding it through Runtime Enviroment -> add -> EAP6.x does not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13346) DirectoryScanner fails on non-existing folders
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13346?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13346:
------------------------------------
Release Notes Docs Status: Documented as Known Issue (was: Not Yet Documented)
Writer: mmurray
Release Notes Text: Deployment Assembly is used to control which files should be deployed with an application to the runtime server and it can be accessed via the Properties of a project. Previously, if Deployment Assembly contained information about nonexistent directories, error messages were generated when the project was built. These error messages were noncritical and did not have an impact on the project's build success. Server Tools has been amended so that it no longer logs the noncritical error messages for nonexistent directories and, consequently, these error messages do not appear in error logs of project builds. (was: Cause: If the Deployment assembly preference for projects referenced directories that does not exist an error was unnecessarily logged as an error with a full stack trace.
Consequence: A user having a project where not all directories are present during the build cycle could see this error and think it was a bug even when it has no impact on his project.
Fix: Server tools do no longer log the error, as it is not a critical error.
Result: There are no more logging of this special case and users should not get a long list of these errors on every build cycle.)
> DirectoryScanner fails on non-existing folders
> ----------------------------------------------
>
> Key: JBIDE-13346
> URL: https://issues.jboss.org/browse/JBIDE-13346
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Archives, JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: Windows XP/Windows 7
> Eclipse 4.3M4
> Reporter: Jesper Skov
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
> Attachments: org.eclipse.wst.common.component
>
>
> DirectoryScanner can be made to fail on non-existing folders.
> In our setup, these folders are possibly picked up from the Deployment Assembly settings.
> The folders are created by our custom Builder with highest priority, so appears to work properly with everything else in Eclipse.
> But it seems the Archive DirectoryScanner runs before our builder.
> The stack trace looks like this:
>
> {code}
> java.lang.IllegalStateException: basedir C:\udvikler\ws\plugins\jb.it.reuters\build\gen-lib-deployable is not a directory
> at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scanPrepare(DirectoryScanner.java:552)
> at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scan(DirectoryScanner.java:588)
> at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory.createDirectoryScanner(DirectoryScannerFactory.java:66)
> at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent$WorkspaceFilter.<init>(WorkspaceFilesetVirtualComponent.java:100)
> at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent.getRootFolder(WorkspaceFilesetVirtualComponent.java:53)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.consumeComponent(FlatVirtualComponent.java:203)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.addConsumedReferences(FlatVirtualComponent.java:196)
> at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.optimize(ClasspathLibraryExpander.java:47)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:119)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.fetchResources(FlatVirtualComponent.java:101)
> at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.fetchResource(ClasspathLibraryExpander.java:74)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.getBaseEARLibRefs(J2EEComponentClasspathContainer.java:463)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.requiresUpdate(J2EEComponentClasspathContainer.java:208)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.refresh(J2EEComponentClasspathContainer.java:540)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.processModules(J2EEComponentClasspathUpdater.java:311)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.access$4(J2EEComponentClasspathUpdater.java:295)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob$1.run(J2EEComponentClasspathUpdater.java:336)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.run(J2EEComponentClasspathUpdater.java:321)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13335) remove Juno SR1+ performance fix from Central
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13335:
------------------------------------
Release Notes Docs Status: Documented as Known Issue
Writer: mmurray
Release Notes Text: Following the release of JBoss Developer Studio 6.0.0, Eclipse released an optimization patch for Eclipse Juno SR1 to resolve some of its known issues. To ensure users of JBoss Developer Studio could benefit from this patch, a connector was included in JBoss Central to apply the patch. The issues resolved by the optimization patch are now incorporated in Eclipse Juno SR2 and, accordingly, JBoss Developer Studio 6.0.1 provided by the universal installer. Consequently, the connector is no longer needed and it has been removed from JBoss Central in JBoss Developer Studio 6.0.1. (was: JBT and JBDS Central in 4.0.0/6.0.0 included a connector that would install a performance fix (patch feature) which was released after Eclipse Juno SR1 was released. That fix is INCLUDED in Juno SR2, so it's available now from Help > Search for Updates in Eclipse or in JBDS.
As such the connector has been removed from Central for the 4.0.1/6.0.1 release as it's redundant to what's available from Eclipse.org directly or is bundled within JBDS.)
> remove Juno SR1+ performance fix from Central
> ----------------------------------------------
>
> Key: JBIDE-13335
> URL: https://issues.jboss.org/browse/JBIDE-13335
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: respin-a
> Fix For: 4.0.1.Final
>
> Attachments: JBIDE13335-patched-sr2.png, JBIDE13335-sr1-can-update-to-sr2.png, JBIDE13335.patch.JBDS6.0.1.txt
>
>
> For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars.
> Need to therefore, for JBT 4.0.1 and JBDS 6.0.1:
> a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places)
> b) remove the connector from discovery plugins' plugin.xml (2 files)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13263:
------------------------------------
Writer: mmurray
Release Notes Text: By default, JBoss Application Server deployment scanners monitor the workspace metadata for applications to deploy. API changes caused duplicate deployment scanners to be created for JBoss Application Server 7. In rectifying this issue, tooling modifications inadvertently caused no deployment scanners to be created for JBoss Application Server 6. As a result, applications selected for deployment on JBoss Application Server 6 failed to deploy. Modifications have been reworked to ensure a deployment scanner is created for JBoss Application Server 6 and, consequently, applications will deploy to JBoss Application Server 6. (was: Cause:Regression related to support deployment for JBoss AS 7
Consequence: Workspace metadata deployment does not work for JBoss AS 6
Fix: Restores the workspace metadata deployment for JBoss AS 6
Result:Workspace metadata deployment works for JBoss AS 6)
> Workspace metadata deployment does not work for AS 6
> ----------------------------------------------------
>
> Key: JBIDE-13263
> URL: https://issues.jboss.org/browse/JBIDE-13263
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: JBoss AS 6.1.0
> Reporter: Martin Malina
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.0.1.Final
>
>
> When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month