[JBoss JIRA] Created: (JBDS-656) Work of adding additional servers in installer is incorrect.
by Anton Klimkovich (JIRA)
Work of adding additional servers in installer is incorrect.
-------------------------------------------------------------
Key: JBDS-656
URL: https://jira.jboss.org/jira/browse/JBDS-656
Project: Developer Studio
Issue Type: Bug
Components: installer, servers
Affects Versions: 2.0.0.GA
Reporter: Anton Klimkovich
EXECUTE: Run installer
EXECUTE: Press Add button On step 5
EXECUTE: Press Browse button and select path to JBoss EAP server (\jbdevstudio20GA\jboss-eap\jboss-as)
EXECUTE: Set checkbox to EAP and press ok
ASSERT: EAP is added
EXECUTE: Finish installation and run JBDS
EXECUTE: Open JBoss Server view
FAILURE: There is no JBoss EAP server in JBoss Server view. Runtime is absent too.
Once I also got an exception but can't get it again.
!ENTRY org.eclipse.wst.server.core 4 0 2009-03-10 14:32:28.674
!MESSAGE Could not save servers
!STACK 0
java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449)
at java.util.AbstractList$Itr.next(AbstractList.java:420)
at org.eclipse.wst.server.core.internal.ResourceManager.saveServersList(ResourceManager.java:536)
at org.eclipse.wst.server.core.internal.ResourceManager.addServer(ResourceManager.java:632)
at org.eclipse.wst.server.core.internal.Server.saveToMetadata(Server.java:408)
at org.eclipse.wst.server.core.internal.Base.doSave(Base.java:264)
at org.eclipse.wst.server.core.internal.Server.doSave(Server.java:397)
at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:421)
at org.jboss.ide.eclipse.as.core.server.internal.ServerAttributeHelper.save(ServerAttributeHelper.java:116)
at org.jboss.ide.eclipse.as.core.server.internal.ServerAttributeHelper.save(ServerAttributeHelper.java:121)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.save(XPathModel.java:202)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel$1.run(XPathModel.java:100)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-5310) Determine Smooks XSD and runtime versions
by Brian Fitzpatrick (JIRA)
Determine Smooks XSD and runtime versions
-----------------------------------------
Key: JBIDE-5310
URL: https://jira.jboss.org/jira/browse/JBIDE-5310
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Brian Fitzpatrick
Assignee: Tom Fennelly
Fix For: 3.1.0.GA
There are a few issues here...
1) You specify a Smooks runtime version in the New Smooks Configuration wizard (1.0, 1.1, and 1.2 appear in the drop-down). If we are truly only supporting version 1.2, we can get rid of this page in the wizard.
2) Previously we were determining the Smooks runtime version based on an element set in the <graph> portion of the configuration. Now that this element and XSD are gone, we need to provide a different way of noting this setting in the configuration that is based on #3.
3) To determine the runtime version, we must look at the component XSDs used by the configuration. This includes CSV, Freemarker, and other XSDs set in the namespace.
To determine this, you must look at the combination of XSDs as documented in the table in this document: https://docspace.corp.redhat.com/clearspace/docs/DOC-23650#Schemas_and_Ve...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBDS-1015) RC1 will not start
by Joshua Wulf (JIRA)
RC1 will not start
------------------
Key: JBDS-1015
URL: https://jira.jboss.org/jira/browse/JBDS-1015
Project: JBoss Developer Studio
Issue Type: Bug
Affects Versions: 3.0.0.CR1
Environment: Mac OS X 10.4.11 32-bit PPC, Apple Java 1.5
Reporter: Joshua Wulf
Attachments: 1261439578596.log
after installing using the installer jar JBDS will not start.
Double-clicking on JBoss Developer Studio in the $root/eclipse folder results in an error dialog: "The Eclipse executable launcher was unable to locate its companion shared library"
Double-clicking on $root/eclipse/Eclipse results in "An error has occurred. See the log file /Applications/jbdevstudio_3.0_RC1/eclipse/configuration/1261439578596.log"
Log file is attached.
3.0.0.M4 runs fine (ok, a little bit slow - but it starts and does stuff) on this machine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBDS-1026) Full Publish of ESB projects does not redeploy and also can't deploy at all from eclipse workspace directory (deploy option)
by Aaron Pestel (JIRA)
Full Publish of ESB projects does not redeploy and also can't deploy at all from eclipse workspace directory (deploy option)
----------------------------------------------------------------------------------------------------------------------------
Key: JBDS-1026
URL: https://jira.jboss.org/jira/browse/JBDS-1026
Project: JBoss Developer Studio
Issue Type: Bug
Affects Versions: 3.0.0.M4
Environment: Fedora 9, SOA-P 5.0 Beta1, JBDS 3 M4
Reporter: Aaron Pestel
Create a new ESB project, add it to a SOA-P server, in the JBossAS view, right-click on the project and choose "Full Publish" - it doesn't republish the project like it used to. Can also modify the project (jboss-esb.xml) and select full publish and it still won't republish, have to remove project from server and re-add project to server.
JBDS project now seems to be setup by default to deploy to JBoss deploy directory as opposed to the Ecplise workspace. I changed it to deploy to the workspace (like I think previoius versions defaulted to), and couldn't even get the project to deploy that way.
If this isn't reproducible enough, please let me know and I'll attach a project with more clear steps.
Thanks!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months