January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13398) Document AS adapter main architecture

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13398?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13398: -------------------------------- Attachment: New Server Workflow.png > Document AS adapter main architecture > ------------------------------------- > > Key: JBIDE-13398 > URL: https://issues.jboss.org/browse/JBIDE-13398 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: JBossAS/Servers > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Attachments: astools api.gliffy, astools api.png, launch a server.gliffy, New Server Workflow.gliffy, New Server Workflow.png, runtime workflow.gliffy, runtime workflow.png > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2180) Document the fact that Oracle OSX Java 7 is not supported by JBDS 5

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2180?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-2180: ------------------------------------- Michelle, I just verified this in JBDS 5.0.2 and I think it behaves still the same way as I originally described - on Mac, regardless of which JDK you run the installer with (Apple JDK 1.6 or Oracle JDK 1.7) and regardless of what JVM you select during installation, the installed JBDS will run with Apple JDK 1.6. So users cannot really run into the situation when JBDS won't start at all - JBDS will automatically start with Java 1.6. The one odd thing is that when you run the installer with java 1.7 and leave the jvm as default in the installation but select 32bit, this 32bit setting will not be used and JBDS will start in 64bit mode. There are many combinations the user can select, so let me summarize: 1. Installer run with java 1.6 - java 1.6 will be used to run JBDS (regardless of what JVM you choose) and 32/64bit setting is honored 2. Installer run with java 1.7 and during installation a) default Java VM or path to Java 1.7 is entered and 32bit is selected - java 1.6 64bit will be used to run JBDS b) default Java VM or path to Java 1.7 is entered and 64bit is selected - java 1.6 64bit will be used to run JBDS c) path to Java 1.6 is entered and 32bit or 64bit is selected - everything works as expected and 32/64 selection is honored So there are these problems included in this JIRA: 1. JBDS 5 will not run with Oracle JDK 1.7 on Mac (but I think it does run with Java 1.7 on other OSs) 2. When the installer is run with java 1.7 it may have unexpected behavior 3. Even if you choose java 1.7 during installation, java 1.6 will be always used Note that all of the above applies to Mac only. > Document the fact that Oracle OSX Java 7 is not supported by JBDS 5 > ------------------------------------------------------------------- > > Key: JBDS-2180 > URL: https://issues.jboss.org/browse/JBDS-2180 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: documentation, installer > Affects Versions: 5.0.0.CR1 > Environment: jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar > Reporter: Martin Malina > Assignee: Michelle Murray > Fix For: 5.0.2.GA > > > I accidentally had my java set to java 1.7 on my mac computer: > vokuro:5.0.0.CR1 rasp$ java -version > java version "1.7.0_04" > Java(TM) SE Runtime Environment (build 1.7.0_04-b21) > Java HotSpot(TM) 64-Bit Server VM (build 23.0-b21, mixed mode) > When you then launch the installer using > java -jar jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar > everything seems ok, you are allowed to select either 32 or 64-bit installation, but regardless of what you choose, the 64-bit version will be installed. > Not sure how this can be handled. At the very least we should disable the radio buttons and preselect 64-bit if that's what must be installed. But the fact is that JBDS will run with java 1.6 anyway. Even if you installed it using 1.7. So wouldn't it be possible to install the 32-bit version even if the installer is run using java 1.7 64-bit? > FYI, on Mac OS X Lion, there are currently these jdk versions: > Apple JDK 1.6 32-bit > Apple JDK 1.6 64-bit > Oracle JDK 1.7 64-bit > I don't expect there will ever be Oracle JDK 1.7 32-bit available. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13398) Document AS adapter main architecture

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13398?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13398: -------------------------------- Attachment: runtime workflow.png > Document AS adapter main architecture > ------------------------------------- > > Key: JBIDE-13398 > URL: https://issues.jboss.org/browse/JBIDE-13398 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: JBossAS/Servers > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Attachments: astools api.gliffy, astools api.png, launch a server.gliffy, New Server Workflow.gliffy, runtime workflow.gliffy, runtime workflow.png > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12619) CLONE - Building JAX-RS metamodel is very slow at times

by Jaroslav Jankovič (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12619?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič closed JBIDE-12619. ------------------------------------- Closing after release notes addition > CLONE - Building JAX-RS metamodel is very slow at times > ------------------------------------------------------- > > Key: JBIDE-12619 > URL: https://issues.jboss.org/browse/JBIDE-12619 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 3.3.2 > > Attachments: JBIDE-12224.m4v, JBIDE-12224.patch > > > I haven't worked out when :-( > I'll try to reproduce it now -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13398) Document AS adapter main architecture

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13398?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13398: -------------------------------- Attachment: New Server Workflow.gliffy runtime workflow.gliffy > Document AS adapter main architecture > ------------------------------------- > > Key: JBIDE-13398 > URL: https://issues.jboss.org/browse/JBIDE-13398 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: JBossAS/Servers > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Attachments: astools api.gliffy, astools api.png, launch a server.gliffy, New Server Workflow.gliffy, runtime workflow.gliffy > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13398) Document AS adapter main architecture

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13398?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13398: -------------------------------- Attachment: launch a server.gliffy > Document AS adapter main architecture > ------------------------------------- > > Key: JBIDE-13398 > URL: https://issues.jboss.org/browse/JBIDE-13398 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: JBossAS/Servers > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Attachments: astools api.gliffy, astools api.png, launch a server.gliffy, New Server Workflow.gliffy, runtime workflow.gliffy > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11348) Not generate clientsample codes in user-created folder on JBoss web services, only in src folder.

by Joseph Hwang (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11348?page=com.atlassian.jira.plugi... ] Joseph Hwang commented on JBIDE-11348: -------------------------------------- Can you reproduce the issues? If not, kindly attach the screenshot so I can understand the step. > Not generate clientsample codes in user-created folder on JBoss web services, only in src folder. > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-11348 > URL: https://issues.jboss.org/browse/JBIDE-11348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.3.0.M5 > Environment: Eclipse Indigo 3.7.2, JBossTools 3.3 > Reporter: Joseph Hwang > Assignee: Brian Fitzpatrick > Priority: Minor > Fix For: 4.0.x > > Attachments: 1_buildpath.jpg, 2_no_folder_choice.jpg, 3_generate_user_defined_folder.jpg, 4_choose_user_defined_folder.jpg, 5_generate_ws_client_code.jpg, 6_no_client_sample.jpg, 7_choose_src_folder.jpg, client_2.jpg, client_3.jpg, client_4.jpg, generating_client.doc, HelloWorld.zip, readme_pls.docx > > > Web Services deployment is ok! But generating clientsample codes is failed in user-created folder. > clientsample codes is generated only in default 'src' folder. > Pls, check this thread https://community.jboss.org/thread/196669?start=0&tstart=0 . -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13404) Support for Deltaspike 0.4

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-13404: ----------------------------------------- Summary: Support for Deltaspike 0.4 Key: JBIDE-13404 URL: https://issues.jboss.org/browse/JBIDE-13404 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: CDI extensions Affects Versions: 4.0.0.Final Reporter: Jaroslav Jankovič Assignee: Alexey Kazakov Fix For: 4.1.0.Alpha1 At this moment, deltaspike tooling supports deltaspike 0.3. However, the current version of deltaspike is 0.4. This should be supported as well. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1786) Installing m2eclipse 1.0 from community site fails

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-1786?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-1786: ---------------------------------- Release Notes Text: Downloading m2e from Eclipse Marketplace or other sites and installing in JBoss Developer Studio can fail due to incompatibility and missing requirements. m2e certified for use with JBoss Developer Studio 5 is available via the JBoss Developer Studio Extras website. m2e can be installed from within JBoss Developer Studio by clicking <application>Help > Install New Software</application> to open the <application>Available Software</application> window. In the <application>Work with</application> combination box select <application>JBoss Developer Studio 5.0 Extras</application> or type the location of the Extras site <ulink url="https://devstudio.jboss.com/updates/5.0/extras/">https://devstudio.jboss.com/updates/5.0/extras/</ulink> to view packages for installation. Selecting the <application>Maven Integration - Extras</application> check box under <application>JBoss Selected Features</application> and completing the installation wizard will make m2e functionality available in JBoss Developer Studio 5. was: Downloading m2e from Eclipse Marketplace or other sites and installing in JBoss Developer Studio can fail due to incompatibility and missing requirements. m2e certified for use with JBoss Developer Studio 5 is available via the JBoss Developer Studio Extras website. This can be accessed from within JBoss Developer Studio by clicking <application>Help → Install New Software</application> to open the <application>Available Software</application> window. In the <application>Work with</application> combination box select <application>JBoss Developer Studio 5.0 Extras</application> or type the location of the Extras site <ulink url="https://devstudio.jboss.com/updates/5.0/extras/">https://devstudio.jboss.com/updates/5.0/extras/</ulink> to view packages for installation. Selecting the <application>Maven Integration - Extras</application> check box under <application>JBoss Selected Features</application> and completing the installation wizard will make m2e functionality available in JBoss Developer Studio 5. > Installing m2eclipse 1.0 from community site fails > -------------------------------------------------- > > Key: JBDS-1786 > URL: https://issues.jboss.org/browse/JBDS-1786 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite, Upstream > Affects Versions: 5.0.0.M2 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Fix For: 5.0.2.GA > > > Installing m2eclipse from http://eclipse.org/m2e/download/ fails with: > Missing requirement: m2e Marketplace 1.0.0.20110607-2117 (org.eclipse.m2e.discovery 1.0.0.20110607-2117) requires 'package org.eclipse.equinox.internal.p2.discovery.compatibility 0.0.0' but it could not be found -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13403) Code completion for jQuery Mobile HTML attributes

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13403?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13403: ----------------------------------- Description: For example: We can provide code completion for jQuery specific HTML5 attributes of html tags (such as data-*): {code} <a data-(role|transition|inline|...)> {code} and for attributes values: {code} <a data-transition="fade|pop|flip|..." ...> {code} See http://jquerymobile.com/demos/1.2.0/docs/api/data-attributes.html was: For example: We can provide code completion for jQuery specific HTML5 attributes of html tags (such as data-*): {code} <a data-(role|transition|inline|...)> {code} and for attributes values: {code} <a data-transition="fade|pop|flip|..." ...> {code} > Code completion for jQuery Mobile HTML attributes > ------------------------------------------------- > > Key: JBIDE-13403 > URL: https://issues.jboss.org/browse/JBIDE-13403 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.0.x > > > For example: > We can provide code completion for jQuery specific HTML5 attributes of html tags (such as data-*): > {code} > <a data-(role|transition|inline|...)> > {code} > and for attributes values: > {code} > <a data-transition="fade|pop|flip|..." ...> > {code} > See http://jquerymobile.com/demos/1.2.0/docs/api/data-attributes.html -- 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, 2 months

1
0
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 January 2013