[JBoss JIRA] Created: (JBDS-983) Console not showing up when staritng a EAP/SOA-P Instance
by Jim Tyrrell (JIRA)
Console not showing up when staritng a EAP/SOA-P Instance
---------------------------------------------------------
Key: JBDS-983
URL: https://jira.jboss.org/jira/browse/JBDS-983
Project: JBoss Developer Studio
Issue Type: Feature Request
Affects Versions: 3.0.0.M4
Reporter: Jim Tyrrell
For some reason starting a SOA-P instance by right clicking in the server view does not start/open the console for the output of the server as it is starting. For EAP and Seam projects this does not seem to be the case as often, but I think I have seen it. The current JBDS 3.0 M4 release does seem to not show the console unless I open the console via the Window -> Show View -> General -> Console and then I have to click an icon to enable the "Java Stack Trace Console". Once I have setup the console once as just noted even if I close it it will open as I expect. If I close JBDS and make sure that the console was not left open, I get the same behaviour when I try to right click on the SOA-P instance.
--
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
1 week, 4 days
[JBoss JIRA] Created: (JBIDE-7870) Several Properties view does not work synchronously
by Vitali Yemialyanchyk (JIRA)
Several Properties view does not work synchronously
---------------------------------------------------
Key: JBIDE-7870
URL: https://issues.jboss.org/browse/JBIDE-7870
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.2.0.Beta2
Reporter: Vitali Yemialyanchyk
Assignee: Alexey Kazakov
Priority: Minor
Properties View -> View Menu -> New Properties View; in both should be one content for one selected item if no pin - but this is not true, or better to say - it is not always a true - try to open one more properties view for "Web Page Editor", switch between VPE and WPE...
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (JBIDE-5809) Add clearer error message when edi mapping model schema version is not supported.
by Daniel Bevenius (JIRA)
Add clearer error message when edi mapping model schema version is not supported.
---------------------------------------------------------------------------------
Key: JBIDE-5809
URL: https://jira.jboss.org/jira/browse/JBIDE-5809
Project: Tools (JBoss Tools)
Issue Type: Task
Components: smooks
Reporter: Daniel Bevenius
Attachments: Screen shot 2010-02-08 at 1.48.16 PM.png
When using a edi mapping model that has a higher schema version number then the Smooks runtime bundled with the eclipse plugin supports, the error message is simply:
Check Input Task configuration. Error creating Input Model from Sample Input Data. Error "..." I'll attached a screenshot of the error.
I noticed this when trying the Smook plugin using the edi-to-java example in Smooks trunk. This example uses the following schema version:
http://www.milyn.org/schema/edi-message-mapping-1.3.xsd
and the version of Smooks bundled with the eclipse plugin only supports 1.2 (I think).
I asked Tom about this and he said that there already is some checking of the versions and perhaps this is only a case on making the error message a little more informative.
The version of the Smooks plugin I used is: 1.1.0.v201002050900N-H208-CR2.
--
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
13 years, 1 month