[JBoss JIRA] Created: (JBIDE-6917) BPEL Editor does not start if extensionActivity is not defined
by Robert (Bob) Brodt (JIRA)
BPEL Editor does not start if extensionActivity is not defined
--------------------------------------------------------------
Key: JBIDE-6917
URL: https://jira.jboss.org/browse/JBIDE-6917
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel
Reporter: Robert (Bob) Brodt
Assignee: Robert (Bob) Brodt
Fix For: 3.2.x
I tried importing a BPEL source file (see attachment) that has extension activities defined, but the editor plugin did not contain serializer/deserializer classes or definitions for the extension activities. This caused an NPE during construction of the grapical EditParts.
This is unacceptable behavior - the editor should be able to display the parts of the process that are valid and create error markers for the missing extensions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBIDE-7164) move update site repos needed for JBDS aggregation into updates/staging/
by Nick Boldt (JIRA)
move update site repos needed for JBDS aggregation into updates/staging/
------------------------------------------------------------------------
Key: JBIDE-7164
URL: https://jira.jboss.org/browse/JBIDE-7164
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.2.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
There are three update site zips from JBoss Tools aggregated into JBDS, plus the new Usage tracker one.
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/updates/JBossTools-Drools
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/updates/JBossTools-JBPM
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/updates/JBossTools-TeiidDesigner
New zips should be placed in staging dir:
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/updates/staging
This affects both Beta1 and trunk branches.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBIDE-6966) [Designer] Exception thrown on workspace shutdown
by Brian Fitzpatrick (JIRA)
[Designer] Exception thrown on workspace shutdown
-------------------------------------------------
Key: JBIDE-6966
URL: https://jira.jboss.org/browse/JBIDE-6966
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: teiid
Affects Versions: 3.2.0.M2
Reporter: Brian Fitzpatrick
Assignee: Barry LaFond
When testing against the latest M2 build and shutting down a workbench, I see this in my development console:
!ENTRY org.teiid.designer.dqp.ui 4 0 2010-09-01 09:54:43.401
!MESSAGE
!STACK 0
java.lang.reflect.InvocationTargetException
at com.metamatrix.modeler.dqp.ui.DqpUiPlugin$1.run(DqpUiPlugin.java:194)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: java.lang.NullPointerException
at com.metamatrix.modeler.dqp.ui.DqpUiPlugin$1.run(DqpUiPlugin.java:189)
... 1 more
Root exception:
java.lang.NullPointerException
at com.metamatrix.modeler.dqp.ui.DqpUiPlugin$1.run(DqpUiPlugin.java:189)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBIDE-7022) NPE in error log on startup
by Max Andersen (JIRA)
NPE in error log on startup
---------------------------
Key: JBIDE-7022
URL: https://jira.jboss.org/browse/JBIDE-7022
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: teiid
Reporter: Max Andersen
Fix For: 3.2.0.M2
On startup of M2 the error log has various errors, one of them being this from teiid:
!ENTRY org.teiid.designer.dqp.ui 4 0 2010-09-07 17:04:20.777
!MESSAGE
!STACK 0
java.lang.reflect.InvocationTargetException
at com.metamatrix.modeler.dqp.ui.DqpUiPlugin$1.run(DqpUiPlugin.java:194)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: java.lang.NullPointerException
at com.metamatrix.modeler.dqp.ui.DqpUiPlugin$1.run(DqpUiPlugin.java:189)
... 1 more
Root exception:
java.lang.NullPointerException
at com.metamatrix.modeler.dqp.ui.DqpUiPlugin$1.run(DqpUiPlugin.java:189)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBIDE-7029) Properties File Editor gets confused with trailing double backslash
by Jeremy Nix (JIRA)
Properties File Editor gets confused with trailing double backslash
-------------------------------------------------------------------
Key: JBIDE-7029
URL: https://jira.jboss.org/browse/JBIDE-7029
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.2.0.M1
Environment: Linux - Fedora 13, JDK 1.6.0_20, Eclipse Helios
Reporter: Jeremy Nix
I have properties defined in a property file in the following fashion:
test.ontology=\\\\a\\b\\c\\
test.name=My Test Ontology
test2.ontology=\\\\a\\b\\c\\d\\
test2.name=My Test Ontology #2
If I copy and past this into a properties file, save, close and reopen, i get
the following properties file definition:
test.ontology=\\\\a\\b\\c\\
test2.ontology=\\\\a\\b\\c\\d\\
Now, I haven't been able to find documentation in the Java API's that says you
can't have a property end with an escaped backslash, so I assume that I'm not
defining these incorrectly. And, for those who would say use slashes, not
backslashes, these are conceptual paths, not file paths, and cannot be changed.
Is this a bug, or am I defining the entries incorrectly? (Confirmed by Eclipse team
that file is defined correctly, which means this is a bug)
Initially reported against Eclipse Properties File Editor: https://bugs.eclipse.org/bugs/show_bug.cgi?id=324418
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBIDE-7069) Application publishing is very slow
by Andre Albino Pereira (JIRA)
Application publishing is very slow
-----------------------------------
Key: JBIDE-7069
URL: https://jira.jboss.org/browse/JBIDE-7069
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.M2
Environment: Ubuntu 10.4 x64, jdk1.6.0_21, jboss-4.0.5-GA, Eclipse Helios (build 20100617-1415)
Reporter: Andre Albino Pereira
Assignee: Rob Stryker
It seems there's a bug when a resource to be published is moved to the deploy folder using PublishCopyUtil.safeRename(File, File, int), where a unnecessary Thread.sleep(100) is executed every time for each resource that is being moved:
private boolean safeRename(File from, File to, int retrys) {
boolean renamedSafely = false;
// make sure parent dir exists
File dir = to.getParentFile();
if (dir != null && !dir.exists())
dir.mkdirs();
int count = 0;
while (count < retrys && !renamedSafely) {
if (from.renameTo(to))
renamedSafely = true; // <------ it should return true right here, since it's not, a unnecessary Thread.sleep(100) is executed.
count++;
// delay if we are going to try again
if (count < retrys) {
try {
Thread.sleep(100);
} catch (Exception e) {
// ignore
}
}
}
return renamedSafely;
}
So, if a EAR with 1000 files is deployed, it will waste around 1.6 min executing Thread.sleep(100).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months