[JBoss JIRA] (JBIDE-14590) "NLS missing message" warnings in Eclips Log view after start
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14590?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-14590:
----------------------------------
Fix Version/s: 4.1.0.Beta1
> "NLS missing message" warnings in Eclips Log view after start
> -------------------------------------------------------------
>
> Key: JBIDE-14590
> URL: https://issues.jboss.org/browse/JBIDE-14590
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Beta1
> Environment: Any
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Fix For: 4.1.0.Beta1
>
>
> {code} JBossRuntimeStartup_Cannot_create_new_JBoss_Server in: org.jboss.tools.as.runtimes.download.messages
> JBossRuntimeStartup_Cannott_create_new_DTP_Connection_Profile in: org.jboss.tools.as.runtimes.download.messages
> JBossRuntimeStartup_Cannott_create_new_HSQL_DB_Driver in: org.jboss.tools.as.runtimes.download.messages
> JBossRuntimeStartup_Cannot_create_new_DB_Driver in: org.jboss.tools.as.runtimes.download.messages
> JBossRuntimeStartup_Runtime in: org.jboss.tools.as.runtimes.download.messages
> JBossRuntimeStartup_The_JBoss_AS_Hypersonic_embedded_database in: org.jboss.tools.as.runtimes.download.messages
> JBossRuntimeStartup_The_JBoss_AS_H2_embedded_database in: org.jboss.tools.as.runtimes.download.messages
> LoadRemoteRuntimes in: org.jboss.tools.as.runtimes.download.messages
> CreateDownloadRuntimes in: org.jboss.tools.as.runtimes.download.messages{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
12 years, 11 months
[JBoss JIRA] (JBIDE-14624) Seam 2 project deployed to EAP 5.1 is not running
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14624?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-14624:
----------------------------------------
I didn't find a way to modify xmlns:web attribute of WebApp object using WTP/EMF API. I hoped we can fix the broken web.xml when installing Seam facet :(
> Seam 2 project deployed to EAP 5.1 is not running
> -------------------------------------------------
>
> Key: JBIDE-14624
> URL: https://issues.jboss.org/browse/JBIDE-14624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam 2, upstream
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1-v20130519-0601-B206
> JBoss EAP 5.1
> Reporter: Vlado Pakan
> Assignee: Alexey Kazakov
> Priority: Critical
> Labels: respin-a
> Fix For: 4.1.0.Beta1
>
>
> 1. Generate seam project for EAP5.1 runtime and Seam included in this EAP
> 2. Run it on EAP5.1 server
> ERROR:
> {noformat}
> 11:43:14,215 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/opt/jboss-eap-5.1/jboss-as/server/default/deploy/seam5170.war/ state=PreParse mode=Manual requiredState=Parse
> org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/opt/jboss-eap-5.1/jboss-as/server/default/deploy/seam5170.war/
> at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
> at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
> at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
> at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)
> at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)
> at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)
> at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
> at org.jboss.Main.boot(Main.java:221)
> at org.jboss.Main$1.run(Main.java:556)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element {http://xmlns.jcp.org/xml/ns/javaee}web-app is not bound as a global element.
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
> at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
> at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189)
> at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166)
> at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137)
> at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121)
> at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:304)
> at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:286)
> at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:203)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:348)
> ... 33 more
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Element {http://xmlns.jcp.org/xml/ns/javaee}web-app is not bound as a global element.
> at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:660)
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
> at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
> at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
> at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
> at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
> ... 42 more
> {noformat}
> Looks like incorrect namespaces are used in web.xml file:
> {noformat}
> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:web="http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
> {noformat}
> When web.xml file is opened in editor via double click it's not opened in web.xml editor. It has only source displayed. There is no Tree tab.
> When replaced with definition from web.xml file generated by JBDS 6.0.0 Everything works as expected:
> {noformat}
> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
> {noformat}
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14428) Adding arquillian to a project that already have arquillian in a pom changes order of things
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14428?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14428:
---------------------------------------
{quote}
import maven project that already have arquillian in pom.xml.
{quote}
We wouldn't need to change a maven project that already has arquillian in the pom.xml file (except adding the Arquillian nature).
Arquillian Eclipse checks if there is the org.jboss.arquillian.core:arquillian-core-api artifact and, if so, it doesn't change pom.xml.
Do we need to use some other way if a project already has arquillian in the pom.xml?
Could you please attach an example of such a project (pom.xml)?
{quote}
Now the maven2Builder is moved from being last to being first.
{quote}
I will check.
{quote}
pom.xml has been rearranged and dependency is using hardcoded version instead of what is in the bom.
if version specific in pom.xml for junit-container that is now removed.
surefire-plugin is added.
{quote}
I have created the https://github.com/jbosstools/jbosstools-arquillian/blob/master/plugins/o... based on the Arquillian tutorial. The file is used to add arquillian artifacts.
The version.arquillian_core property is replaced with the arquillianVersion Eclipse preference.
Could you please specify how this file would look like?
{quote}
profiles are added.
{quote}
This is defined using the Window>Preferences>JBoss Tools>Arquillian preferences page.
Do you mean, we don't need to add profiles when adding the Arquillian nature.
There is a separate action to add profiles (Configure>Add Arquillian profiles...).
> Adding arquillian to a project that already have arquillian in a pom changes order of things
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-14428
> URL: https://issues.jboss.org/browse/JBIDE-14428
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Beta2
>
>
> import maven project that already have arquillian in pom.xml.
> Configure > Add Arquillian
> Now the maven2Builder is moved from being last to being first.
> pom.xml has been rearranged and dependency is using hardcoded version instead of what is in the bom.
> if version specific in pom.xml for junit-container that is now removed.
> surefire-plugin is added.
> profiles are added.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14590) "NLS missing message" warnings in Eclips Log view after start
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14590?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-14590:
----------------------------------
Description:
{code} JBossRuntimeStartup_Cannot_create_new_JBoss_Server in: org.jboss.tools.as.runtimes.download.messages
JBossRuntimeStartup_Cannott_create_new_DTP_Connection_Profile in: org.jboss.tools.as.runtimes.download.messages
JBossRuntimeStartup_Cannott_create_new_HSQL_DB_Driver in: org.jboss.tools.as.runtimes.download.messages
JBossRuntimeStartup_Cannot_create_new_DB_Driver in: org.jboss.tools.as.runtimes.download.messages
JBossRuntimeStartup_Runtime in: org.jboss.tools.as.runtimes.download.messages
JBossRuntimeStartup_The_JBoss_AS_Hypersonic_embedded_database in: org.jboss.tools.as.runtimes.download.messages
JBossRuntimeStartup_The_JBoss_AS_H2_embedded_database in: org.jboss.tools.as.runtimes.download.messages
LoadRemoteRuntimes in: org.jboss.tools.as.runtimes.download.messages
CreateDownloadRuntimes in: org.jboss.tools.as.runtimes.download.messages{code}
was:
{code} JBossRuntimeStartup_Cannot_create_new_JBoss_Server in: org.jboss.tools.as.runtimes.download.messages
JBossRuntimeStartup_Cannott_create_new_DTP_Connection_Profile in: org.jboss.tools.as.runtimes.download.messages
JBossRuntimeStartup_Cannott_create_new_HSQL_DB_Driver in: org.jboss.tools.as.runtimes.download.messages
JBossRuntimeStartup_Cannot_create_new_DB_Driver in: org.jboss.tools.as.runtimes.download.messages
JBossRuntimeStartup_Runtime in: org.jboss.tools.as.runtimes.download.messages
JBossRuntimeStartup_The_JBoss_AS_Hypersonic_embedded_database in: org.jboss.tools.as.runtimes.download.messages
JBossRuntimeStartup_The_JBoss_AS_H2_embedded_database in: org.jboss.tools.as.runtimes.download.messages
LoadRemoteRuntimes in: org.jboss.tools.as.runtimes.download.messages
CreateDownloadRuntimes in: org.jboss.tools.as.runtimes.download.messages
> "NLS missing message" warnings in Eclips Log view after start
> -------------------------------------------------------------
>
> Key: JBIDE-14590
> URL: https://issues.jboss.org/browse/JBIDE-14590
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Beta1
> Environment: Any
> Reporter: Denis Golovin
> Assignee: Rob Stryker
>
> {code} JBossRuntimeStartup_Cannot_create_new_JBoss_Server in: org.jboss.tools.as.runtimes.download.messages
> JBossRuntimeStartup_Cannott_create_new_DTP_Connection_Profile in: org.jboss.tools.as.runtimes.download.messages
> JBossRuntimeStartup_Cannott_create_new_HSQL_DB_Driver in: org.jboss.tools.as.runtimes.download.messages
> JBossRuntimeStartup_Cannot_create_new_DB_Driver in: org.jboss.tools.as.runtimes.download.messages
> JBossRuntimeStartup_Runtime in: org.jboss.tools.as.runtimes.download.messages
> JBossRuntimeStartup_The_JBoss_AS_Hypersonic_embedded_database in: org.jboss.tools.as.runtimes.download.messages
> JBossRuntimeStartup_The_JBoss_AS_H2_embedded_database in: org.jboss.tools.as.runtimes.download.messages
> LoadRemoteRuntimes in: org.jboss.tools.as.runtimes.download.messages
> CreateDownloadRuntimes in: org.jboss.tools.as.runtimes.download.messages{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
12 years, 11 months
[JBoss JIRA] (JBIDE-13843) Investigate use of SWTBot 2.1 (and org.junit_4.11) in target platform
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13843?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13843:
----------------------------------------
> what is the status of this ? can we just use the old swtbot for now or do we need later for kepler ?
Nope, see bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=404346 . SWTBot needs to work with Kepler
> if we do need it why aren't swtbot releasing a kepler specific one to at least have somthing working?
That's something I have been working on for the last days, but I still notice some issues before getting a Kepler-friendly release of SWTBot (see bug dependencies).
> We're using SWTBot 2.1.1 and org.junit_4.11 for now, until something better comes along. Seems not to be crashing all our tests, so I suppose this can be closed as fixed.
Just a reminder that we are using a 2.1.1-SNAPSHOT. 2.1.1 release will come as soon as bug 404346 is fixed. The issues between SWTBot and Kepler only affect some methods of SWTBot that we're not using in JBT, so the incompatibility is not yet a blocker for our usage.
> Investigate use of SWTBot 2.1 (and org.junit_4.11) in target platform
> ---------------------------------------------------------------------
>
> Key: JBIDE-13843
> URL: https://issues.jboss.org/browse/JBIDE-13843
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, testing-tools
> Affects Versions: 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 4.1.0.Beta2
>
>
> Eclipse 4.3M5a contains:
> {code}4.3milestones/S-4.3M5a-201302041400/plugins/org.junit4_4.8.1.v20120705-112236.jar{code}
> But in Eclipse 4.3M6, the only JUnit available is:
> {code}4.3milestones/S-4.3M6-201303141330/plugins/org.junit_4.11.0.v201303080030.jar{code}
> So, we need to see if a newer SWTBot can be used which depends on org.junit instead of org.junit4.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14430) Run as arquillian seem to *always* ask for there being exactly one implementation of DeploymentContainer - can't it detect it ?
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14430?page=com.atlassian.jira.plugi... ]
Snjezana Peco edited comment on JBIDE-14430 at 5/24/13 5:04 PM:
----------------------------------------------------------------
Currently, Arquillian Eclipse detects the DeploymentContainer implementation(s) by scanning a classpath. It reports an error/a warning if there isn't any or there is more than one implementation.
I propose to solve the issue in the following way:
- scan a classpath
- if there is no implementation of the DeployableContainer interface, it reports an error
- if there is exactly one implementation of this interface, nothing reported (the Arquillian environment is valid)
- if there is more than one implementation of this interface, we would check if there is the META-INF/services/org.jboss.arquillian.core.spi.LoadableExtension resource on the classpath as well as if there is a class defined in this resource.
If both exist, nothing is reported
Otherwise, Arquillian Eclipse reports an error
I am not sure if it is possible to check if the MyLoadableExtensionClass class activates the DeployableContainer interface correctly. Maybe we could analyze the b.service(DeployableContainer.class, MyDeployableContainer.class) method, check if the MyDeployableContainer.class exists and implements the DeployableContainer interface.
was (Author: snjeza):
Currently, Arquillian Eclipse detects the DeploymentContainer implementation(s) by scanning a classpath. It reports an error/a warning if there isn't any or there is more than one implementation.
I propose to solve the issue in the following way:
- scan a classpath
- if there is no implementation of the DeploymentContainer interface, it reports an error
- if there is exactly one implementation of this interface, nothing reported (the Arquillian environment is valid)
- if there is more than one implementation of this interface, we would check if there is the META-INF/services/org.jboss.arquillian.core.spi.LoadableExtension resource on the classpath as well as if there is a class defined in this resource.
If both exist, nothing is reported
Otherwise, Arquillian Eclipse reports an error
I am not sure if it is possible to check if the MyLoadableExtensionClass class activates the DeploymentContainer interface correctly. Maybe we could analyze the b.service(DeplyableContainer.class, MyDeplyableContainer.class) method, check if the MyDeplyableContainer.class exists and implements the DeplyableContainer interface.
> Run as arquillian seem to *always* ask for there being exactly one implementation of DeploymentContainer - can't it detect it ?
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14430
> URL: https://issues.jboss.org/browse/JBIDE-14430
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Beta2
>
>
> can't we detect if there is more than one DeploymentContainer for Run As > Arquillian test or is that too slow ?
> Or at least show which profile is enabled or something to give user an idea what he is currently running with.
--
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
12 years, 11 months