[JBoss JIRA] (JBDS-1886) "New JBoss ESB Runtime" dialog does not automatically select runtime version based on ESB install dir for ESB 4.10
by Len DiMaggio (Created) (JIRA)
"New JBoss ESB Runtime" dialog does not automatically select runtime version based on ESB install dir for ESB 4.10
------------------------------------------------------------------------------------------------------------------
Key: JBDS-1886
URL: https://issues.jboss.org/browse/JBDS-1886
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: SOA Platform
Affects Versions: 4.1.1.M2
Environment: Version: 4.1.1.M2
Build id: v20111006-0040-H1061-M2
Build date: 20111006-0040
Reporter: Len DiMaggio
Fix For: LATER
See attached screenshots - JBDS is not automatically discovering the version # based on the install dir for ESB 4.10 - but it does work for 4.9
[ldimaggi@ldimaggi ~]$ ll /jboss/local/book_downloads/jbossesb-4.10
total 40
-rw-r--r--. 1 ldimaggi ldimaggi 625 Jul 6 22:36 Contributors.txt
drwxr-xr-x. 4 ldimaggi ldimaggi 4096 Jul 6 22:36 docs
drwxr-xr-x. 7 ldimaggi ldimaggi 4096 Jul 6 22:34 install
drwxr-xr-x. 4 ldimaggi ldimaggi 4096 Jul 6 22:34 javadocs
drwxr-xr-x. 13 ldimaggi ldimaggi 12288 Jul 6 22:37 lib
-rw-r--r--. 1 ldimaggi ldimaggi 583 Jul 6 22:36 README_FIRST.txt
drwxr-xr-x. 3 ldimaggi ldimaggi 4096 Jul 6 22:36 samples
drwxr-xr-x. 3 ldimaggi ldimaggi 4096 Jul 6 22:34 xml
[ldimaggi@ldimaggi ~]$ ll /jboss/local/book_downloads/jbossesb-4.9
total 52
-rw-r--r--. 1 ldimaggi ldimaggi 625 Aug 9 2010 Contributors.txt
drwxr-xr-x. 4 ldimaggi ldimaggi 4096 Aug 9 2010 docs
drwxr-xr-x. 6 ldimaggi ldimaggi 4096 Apr 14 21:16 install
drwxr-xr-x. 4 ldimaggi ldimaggi 4096 Aug 9 2010 javadocs
-rw-r--r--. 1 ldimaggi ldimaggi 8533 Aug 9 2010 JBossEULA.txt
drwxr-xr-x. 13 ldimaggi ldimaggi 12288 Aug 9 2010 lib
-rw-r--r--. 1 ldimaggi ldimaggi 583 Aug 9 2010 README_FIRST.txt
drwxr-xr-x. 3 ldimaggi ldimaggi 4096 Aug 9 2010 samples
drwxr-xr-x. 3 ldimaggi ldimaggi 4096 Aug 9 2010 xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-11653) Errors running builder 'JAX-RS Builder' on project 'ticket-monster'.
by Marius Bogoevici (JIRA)
Marius Bogoevici created JBIDE-11653:
----------------------------------------
Summary: Errors running builder 'JAX-RS Builder' on project 'ticket-monster'.
Key: JBIDE-11653
URL: https://issues.jboss.org/browse/JBIDE-11653
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Reporter: Marius Bogoevici
java.lang.ClassCastException: org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
at org.jboss.tools.ws.jaxrs.core.jdt.JavaMethodSignaturesVisitor.visit(JavaMethodSignaturesVisitor.java:88)
at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:489)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585)
at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585)
at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:219)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignature(JdtUtils.java:587)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.internalCreateResourceMethod(JaxrsElementFactory.java:236)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createResource(JaxrsElementFactory.java:148)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.preprocessResourceChangesOnScopeAdditionOrChange(ResourceChangedProcessor.java:531)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processResourceChangesOnScopeAdditionOrChange(ResourceChangedProcessor.java:502)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processEvent(ResourceChangedProcessor.java:177)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processEntireProject(ResourceChangedProcessor.java:108)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processAffectedResources(ResourceChangedProcessor.java:81)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuilder.build(JaxrsMetamodelBuilder.java:122)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuilder.build(JaxrsMetamodelBuilder.java:82)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:394)
at org.eclipse.core.internal.resources.Project$1.run(Project.java:618)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597)
at org.eclipse.core.internal.resources.Project.build(Project.java:114)
at com.google.gdt.eclipse.core.BuilderUtilities$2.runInWorkspace(BuilderUtilities.java:202)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-11514) AS6 run on server for war or ear-inside-war does not load browser fast
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-11514:
-----------------------------------
Summary: AS6 run on server for war or ear-inside-war does not load browser fast
Key: JBIDE-11514
URL: https://issues.jboss.org/browse/JBIDE-11514
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.Beta3
AS6 does not seem to have the mbeans as5 and below do for determining if a module is started or not. This means that attempts to poll via jmx to decide when to open the browser take the full timeout of 20 seconds.
Without a way to decide if the module is started or not, we have to hard-code a delay time. There is no easy answer here. If we go too quickly, the user will get 404. If we delay too long, the user will wait a long time to see the change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-10930) For EAR projects, Run As > Run on Server should open the 1st webapp using the context root in application.xml
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-10930:
-----------------------------------
Summary: For EAR projects, Run As > Run on Server should open the 1st webapp using the context root in application.xml
Key: JBIDE-10930
URL: https://issues.jboss.org/browse/JBIDE-10930
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Reporter: Fred Bricon
Assignee: Rob Stryker
Attachments: non.default.context.root.zip
For EAR projects, Run As > Run on Server opens the webapp url using the context root defined on the webapp project, not the value of the context root in application.xml, which obviously leads to a 404 error page.
{quote}
(09:53:24) rawbdor: fbricon, EarArtifactAdapter
(09:53:36) rawbdor: takes the first web project in the ear
(09:53:48) rawbdor: and simply returns whatever the web artifact adapter would do for that app
{quote}
When lauching, we could maybe use a IModuleArtifact decorator that provides the correct url to be opened in the browser?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months