[JBoss JIRA] (JBIDE-10335) JBoss Central cannot be opened without hard dependency to its plugin because of JBossCentralEditorInput
by Max Rydahl Andersen (Created) (JIRA)
JBoss Central cannot be opened without hard dependency to its plugin because of JBossCentralEditorInput
-------------------------------------------------------------------------------------------------------
Key: JBIDE-10335
URL: https://issues.jboss.org/browse/JBIDE-10335
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: central
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Minor
Fix For: 3.3.0.Beta1
JBDS-1941 caused a hard dependency from product to central plugin because of:
"The question was about having a need to have hard dependency to org.jboss.tools.central plug-in because I must have JBossCentralEditorInput object to be given as editor input. I may pass null or some other IEditorInput implementation but doing so will rise an exception (IllegalArgumentException). Since there is no way to open the Central without having this dependency (and no protests to have it) I've added it to the product plug-in dependencies."
Snjezana - any reason why not allowing opening the editor without having the specific JBossCentralEditorInput ?
I could see usecases for having a JBossCentralEditorInput but for just opening it something more generic should be allowed to avoid hardcoupling.
Minor issue but annoying ;)
--
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
14 years
[JBoss JIRA] Created: (JBIDE-8656) Split SOA components out of JBoss Tools aggregate site; create 2nd aggregate for SOA Tooling
by Nick Boldt (JIRA)
Split SOA components out of JBoss Tools aggregate site; create 2nd aggregate for SOA Tooling
--------------------------------------------------------------------------------------------
Key: JBIDE-8656
URL: https://issues.jboss.org/browse/JBIDE-8656
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel, bpm, drools, esb, jbpm, modeshape, smooks, teiid
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
The following components should be aggregated in a NEW aggregate build and removed from the existing one:
Drools 5.2
Flow/jBPM
BPMN2 (there is no JIRA component for this yet)
BPEL (moving to Eclipse.org)
Teiid
Modeshape
ESB
Smooks
1. Fix ~/trunk/build/aggregate/ - remove components from site.xml
2. Create new ~/trunk/build/aggregate-soa/ - add components to site.xml
3. Create new http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.3... (or similar)
4. get new www.jboss.org/soatools/ site, publish there instead of www.jboss.org/tools/, and cross link project pages.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBDS-1538) ws user guide issues
by Lukas Jungmann (JIRA)
ws user guide issues
--------------------
Key: JBDS-1538
URL: https://issues.jboss.org/browse/JBDS-1538
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Doc - JBossWS
Affects Versions: 4.0.0.CR2
Reporter: Lukas Jungmann
JBoss Web Services User Guide
chapter 1: JBossWS Runtime Overview
-it is not true that JBossWS implements JAX-WS and JAX-RS - JBossWS implements JAX-WS and JAX-RPC, for JAX-RS there's RESTEasy
-would be good if other resources would list http://www.jboss.org/jbossws and perhaps also http://community.jboss.org/wiki/JBossWS-FAQ
chapter3:
3.3. Creating a Web Service from a WSDL document using JBossWS runtime
-there's a note about about simple ws wizard which does not make sense in from wsdl context, therefore this note should be removed
-no description of items from the screenshot - compare with sec 3.4 to see what I mean
3.4.
-the description of the stages of Web service development should be moved to sec. 3.3 where they can be seen on the screenshot for the first time; or do copy paste of the particular paragraph or provide a link between those two occurrences
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBDS-1829) CLONE - Navigation between links on welcome screen should be uninterrupted
by Denis Golovin (JIRA)
CLONE - Navigation between links on welcome screen should be uninterrupted
--------------------------------------------------------------------------
Key: JBDS-1829
URL: https://issues.jboss.org/browse/JBDS-1829
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ui/branding
Reporter: Lukas Jungmann
Assignee: Victor Rubezhny
Priority: Minor
Fix For: 5.0.0.M2
-shrink the JBDS window a bit and click on links on the welcome screen
I can see two issues here:
-the loading of the link should be uninterrupted, as of now one can see white/empty page between clicking on the link and displaying the contents of the link
-the white strip (the one containing the RH and JBoss logos) does not have fixed position at the bottom of the window, ie if one needs to scroll, he may not be able to follow link hidden by the strip
video from ubuntu 10.10 is attached
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-10137) Close input and output stream in all places where it used
by Vitali Yemialyanchyk (Created) (JIRA)
Close input and output stream in all places where it used
---------------------------------------------------------
Key: JBIDE-10137
URL: https://issues.jboss.org/browse/JBIDE-10137
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: common/jst/core, jsp/jsf/xml source editing
Affects Versions: 3.3.0.M4
Reporter: Vitali Yemialyanchyk
Assignee: Alexey Kazakov
Priority: Trivial
Unfortunately I've find a lot of places in JBossTools where InputStream & OutputStream are used and are not closed. Just make a search and inspect all over the code.
Here just list of places for org.jboss.tools.jsf plugin:
1) JSF2ComponentModelManager -> public static IDOMDocument getReadableDOMDocument(JarEntryFile file)
2) JSF2Util -> public static String readManifest(IProject project, String jarName) throws CoreException, IOException
3) JSF2TemplateManager -> public InputStream createStreamFromTemplate(String templateName)
4) JSF2ComponentsValidator -> protected boolean isValidate(IFile file)
5) XHTMLEntityResolver -> public static XMLInputSource _internalResolveEntity(... -> is.setByteStream(new LazyURLInputStream(physical));
6) XHTMLValidator -> stream = new FilteredInputStream(connect.getInputStream());
--
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
14 years, 1 month