November 2012 - jbosstools-issues

[JBoss JIRA] (JBDS-2372) Xhtml files appear garbled when it's reopened in the JBDS editor.

by Suzumura Keishi (JIRA)

Suzumura Keishi created JBDS-2372: ------------------------------------- Summary: Xhtml files appear garbled when it's reopened in the JBDS editor. Key: JBDS-2372 URL: https://issues.jboss.org/browse/JBDS-2372 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.GA Reporter: Suzumura Keishi Xhtml files appear garbled when it's reopened in the JBDS editor. In Japanese environment, a xhtml file encoded utf8 is written in Japanese characters. The xhtml file appears garbled when it's reopened. This xhtml default text file encoding is Shift_JIS in Properties > Resource. It seems the JBDS does not determine the UTF-8 encoding file. -- 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, 7 months

4
5
0 / 0

[JBoss JIRA] (JBIDE-12627) EL resolver for expresions which use <ui:param> doesn't work after eclipse restarting

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-12627: -------------------------------------- Summary: EL resolver for expresions which use <ui:param> doesn't work after eclipse restarting Key: JBIDE-12627 URL: https://issues.jboss.org/browse/JBIDE-12627 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 4.0.0.Alpha2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.0.x 1. Create JSF 2 KickStart project 2. Open inputname.xhtml 3. Add <ui:param name="client" value="#{user}" /> inside <ui:composition> (line #9) 4. Save the file. 5. Open common.xhtml 6. Add <h:outputText value="#{client.}" /> 7. Try Ctrl+Space for #{client.|} 8. ASSERT: There is "name" in the list of proposals. 9. Close all the editors. 10. Re-start the eclipse 11. Open common.xhtml 12. FAILURE: Try Ctrl+Space for #{client.|}. It's not working anymore. 13. Clean/build the project. 14. Try Ctrl+Space for #{client.|} 15. ASSERT: There is "name" in the list of proposals. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] (JBDS-2379) consider new UI in Central for displaying Certified/Selected status to users

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2379: -------------------------------- Summary: consider new UI in Central for displaying Certified/Selected status to users Key: JBDS-2379 URL: https://issues.jboss.org/browse/JBDS-2379 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: central Affects Versions: 6.0.0.Beta2 Reporter: Nick Boldt Assignee: Max Rydahl Andersen For future consideration. Should we display "Certified" and "Selected" status of connectors in Central so we no longer need a separate Extras site? -- 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, 7 months

4
19
0 / 0

[JBoss JIRA] (JBIDE-12586) editing remote server home does not take affect unless using the browse button

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-12586: ------------------------------------------- Summary: editing remote server home does not take affect unless using the browse button Key: JBIDE-12586 URL: https://issues.jboss.org/browse/JBIDE-12586 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Max Rydahl Andersen 1) EXEC: create a server with remote deployment and point to a directory that does not have standalone/deployments. 2) EXEC: perform publish 3) ASSERT: weird error message and fail to publish because of JBIDE-12585. The path listed is though correct. 4) EXEC: edit the path manually by hand to be correct 5) EXEC: save and perform publish 6) ASSERT: publishining should work now. Currently #6 fails with same error as #3 and even listing the old path and not the new. 7) EXEC: restart 8) ASSERT: the field contains the hand edited value. #8 fails too - its as if the handedited changes does not take affect - only the browse button works. -- 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, 7 months

3
14
0 / 0

[JBoss JIRA] (JBIDE-12585) remote publishing gives weird error when not pointing to exact expected directory layout

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-12585: ------------------------------------------- Summary: remote publishing gives weird error when not pointing to exact expected directory layout Key: JBIDE-12585 URL: https://issues.jboss.org/browse/JBIDE-12585 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Max Rydahl Andersen setup an ASx server to deploy remotely (i.e. on openshift) and point to a directory that *does not* have standalone/deployments already in it - then at publish time you get errors like: "failed to copy to /home/max/work/standalone/deployments/test.war/META-INF/MANIFEST.MF on host neo6.gva.redhat.com Missing element for : ''" Not very informative. If you fix the server to point to a directory that have standalone/deployments already things starts working again. The error should be more informative - optimally ask the user if the missing directories should be made ? Didnt we at some point have a "verify" button for the remote setup to check if directories were present? -- 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, 7 months

3
8
0 / 0

[JBoss JIRA] (JBIDE-12900) MBean explorer should be able to refresh (on demand?)

by Martin Malina (JIRA)

Martin Malina created JBIDE-12900: ------------------------------------- Summary: MBean explorer should be able to refresh (on demand?) Key: JBIDE-12900 URL: https://issues.jboss.org/browse/JBIDE-12900 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jmx Affects Versions: 4.0.0.Beta1 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.0.0.CR1 When you execute an operation on an MBean that will remove said MBean (or any other MBean) this change is not reflected. And there is no way to refresh the mbeans. For example say you want to remove a deployment scanner. You run the remove operation on it. It works. But you can still see the mbean. And if you click on Attributes on that mbean and select an attribute you get an error: {code} Unavailable javax.management.InstanceNotFoundException: JBAS011340: No MBean found with name jboss.as:subsystem=deployment-scanner,scanner=jbosstoolsscanner1 at org.jboss.as.jmx.model.ModelControllerMBeanHelper.createInstanceNotFoundException(ModelControllerMBeanHelper.java:382) at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getAttribute(ModelControllerMBeanHelper.java:179) at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getAttribute(ModelControllerMBeanServerPlugin.java:69) at org.jboss.as.jmx.PluggableMBeanServerImpl.getAttribute(PluggableMBeanServerImpl.java:154) at org.jboss.remotingjmx.protocol.v1.ServerProxy$GetAttributeHandler.handle(ServerProxy.java:773) at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) {code} We need to find a way to address this. At the very least there should be a "refresh button" somewhere that would refresh the mbeans for a given jmx connection (or all). Even better would be if we could detect the removal of the mbean somehow. -- 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, 7 months

4
9
0 / 0

[JBoss JIRA] (JBIDE-10592) deployments tab war module deployment location is ignored

by erik van altena (Created) (JIRA)

deployments tab war module deployment location is ignored --------------------------------------------------------- Key: JBIDE-10592 URL: https://issues.jboss.org/browse/JBIDE-10592 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Environment: Eclipse Indigo SR1 Reporter: erik van altena Assignee: Rob Stryker Priority: Minor This bug report is created as per requested in this closed issue: https://issues.jboss.org/browse/JBIDE-10590 I have a Mavenized project (m2eclipse, JBoss Tools Maven Integration) which I publish to a JBoss 7 runtime (standalone) by dragging it to the runtime instance. To work around the publish directory names not matching the maven pom configuration, I use the runtime deployment tab to override the directory names that the project modules are deployed under in the deployments folder of the server. (next part copy/pasted from original issue comments) But then I run into the next oddity: the settings for the war module seem to be ignored out of the box. The deployment tab mentions the war module as being deployed as 'app-web.war' while in fact it ends up in the deployments directory as 'app-web-1.0.0-SNAPSHOT.war', just like Maven would name it if you don't provide a finalName. However, as soon as I tab over the deployment locations and save the changes to the runtime configuration, upon full publish the web module gets the directory name as it is listed in the deployments tab. To be a little more specific: I get this behavior when I haven't made changes yet to the war entry in the deployment tab; the tab indicates the correct name but the result after publishing is wrong. When I then press tab to navigate to the deployment-location of the war, I don't change anything but I hit CTRL+S to save changes, upon full publish the name is then correct. -- 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, 7 months

8
25
0 / 0

[JBoss JIRA] (JBIDE-13065) html5 quickstart displayed incorrectly in internal browser

by Martin Malina (JIRA)

Martin Malina created JBIDE-13065: ------------------------------------- Summary: html5 quickstart displayed incorrectly in internal browser Key: JBIDE-13065 URL: https://issues.jboss.org/browse/JBIDE-13065 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, maven Affects Versions: 4.0.0.Beta2 Environment: JBDS 6.0.0.Beta2 B62 OS X 10.8 Mountain Lion Reporter: Martin Malina Assignee: Snjezana Peco Fix For: 4.0.0.CR1 Attachments: html5-internal-browser.png When you create the html5 project from Central and then run it on AS7 (Project -> Run As -> Run on server) it is opened in the internal browser by default. For some reason the application thinks the eclipse internal browser is a mobile device and displays it as such. I'm pretty sure it worked correctly in the past. I assume usually this is controlled by the user agent http header. I checked the access_log on a server I own and this is what I get: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 (KHTML, like Gecko) Safari/522.0" When I just used Safari to display the html5 project, I saw this in the access_log: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17" -- 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, 7 months

3
8
0 / 0

[JBoss JIRA] (JBIDE-13080) JBDS5 - Does not recognize ESB 4.11 - deployments to SPA-P servers fail

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-13080: ------------------------------------ Summary: JBDS5 - Does not recognize ESB 4.11 - deployments to SPA-P servers fail Key: JBIDE-13080 URL: https://issues.jboss.org/browse/JBIDE-13080 Project: Tools (JBoss Tools) Issue Type: Bug Components: SOA Tooling Affects Versions: 3.3.0.Final-SOA Reporter: Len DiMaggio Assignee: Douglas Palmer Priority: Blocker Fix For: 3.3.1.Final-SOA See: https://issues.jboss.org/browse/JBDS-2365 -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13014) Replace activeByDefault

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-13014: -------------------------------------- Summary: Replace activeByDefault Key: JBIDE-13014 URL: https://issues.jboss.org/browse/JBIDE-13014 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Mickael Istria Assignee: Mickael Istria Fix For: 4.0.0.CR1 Since activeByDefault does automatically get disabled when another profile is enabled (such as osx profile), it's not doing what we want. Let's try moving to a property-based approach to select profiles that are exclusive, and the default value of the property will enable the current activeByDefault profile. -- 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, 7 months

3
13
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2012