[JBoss JIRA] Created: (JBIDE-4346) -Djava.library.path always overwritten with some default
by arne anka (JIRA)
-Djava.library.path always overwritten with some default
--------------------------------------------------------
Key: JBIDE-4346
URL: https://jira.jboss.org/jira/browse/JBIDE-4346
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.1.GA
Environment: jboss 4.2.2.GA
eclipse:
Version: 3.4.2
Build id: M20090211-1700
Reporter: arne anka
in the launch configuration for my configured jboss server i need to add another directory to the parameter -Djava.library.path.
after editing it looks like
-Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native:/foo/bar/"
saving and reopening shows instead
-Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native"
adding another parameter instead
-Djava.library.path="/foo/bar"
resulting in
-Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native"
-Djava.library.path="/foo/bar"
ends up with
-Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native"
-Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native"
after saving
obviously some simple logic checks for the existence of the -Djava.library.path parameter and overwrites it with a default instead of at least appending its default.
i don't really see what's the meaning behind that, and therefore am convinced it has to be a bug.
additionally, it stops me from running at least one webapp, that requires the parameter to be set correctly.
--
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, 11 months
[JBoss JIRA] Created: (JBDS-1676) NullPointerException in SmooksGraphicalEditorPart
by Martin Weiler (JIRA)
NullPointerException in SmooksGraphicalEditorPart
-------------------------------------------------
Key: JBDS-1676
URL: https://issues.jboss.org/browse/JBDS-1676
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: SOA Platform
Affects Versions: 4.0.0.GA
Environment: Windows 7
-vm "C:\Program Files (x86)\Java\jdk1.6.0_23\bin"
Reporter: Martin Weiler
Attachments: debugInfo.txt, example.jar, example.xsd
I have a problem using the 'Smooks Processing' tool to configure a smooks file (used for converting XML to Java) when the Java-class is located in a jar file.
The problem seems to relate to the 'Java Mapping' view of the 'Smooks Processing' tool and generates an OutOfMemoryException. The exception occurs when inside the 'Java Mapping' view and clicking or dragging input elements to corresponding output elements or selecting the connection between the elements. The exception sometimes occur at the first adjustments and sometimes it takes several adjustments before it occurs. When using a file where the elements already have been connected, the exception sometimes occur imidiatly when selecting the 'Java Mapping' icon.
I have not seen this problem when using a Java-class which is not located in a jar file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBIDE-9790) ClassCastException with VpeElementMapping use
by Vitali Yemialyanchyk (JIRA)
ClassCastException with VpeElementMapping use
---------------------------------------------
Key: JBIDE-9790
URL: https://issues.jboss.org/browse/JBIDE-9790
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core, Visual Page Editor Templates
Affects Versions: 3.3.0.M3
Reporter: Vitali Yemialyanchyk
Assignee: Yahor Radtsevich
Priority: Optional
VpeElementMapping expected VpeTemplate as one of parameters in constructor, but in VpeVisualDomBuilder in line function stopToggle (line 940) it cast elementMapping.getTemplate() to VpeTemplateSafeWrapper, i.e. by default it expect VpeTemplateSafeWrapper in VpeElementMapping. You should update VpeElementMapping so it expect VpeTemplateSafeWrapper or wrap VpeTemplate to VpeTemplateSafeWrapper in VpeElementMapping. Cause we get such exception:
java.lang.ClassCastException: com.hp.dcp.ve.ui.template.JSPCustomTagTemplate cannot be cast to org.jboss.tools.vpe.editor.template.VpeTemplateSafeWrapper
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.stopToggle(VpeVisualDomBuilder.java:940)
at org.jboss.tools.vpe.editor.VpeController.notifyChangedInUiThread(VpeController.java:730)
at org.jboss.tools.vpe.editor.VpeController$1.runInUIThread(VpeController.java:554)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
of course we can fix it on our side - but you should make your code safe to prevent such errors.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBIDE-7630) Quickfix for "Stereotype annotation type must be annotated with one of @Target..." error marker
by Daniel Azarov (JIRA)
Quickfix for "Stereotype annotation type must be annotated with one of @Target..." error marker
-----------------------------------------------------------------------------------------------
Key: JBIDE-7630
URL: https://jira.jboss.org/browse/JBIDE-7630
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: cdi (jsr-299)
Reporter: Daniel Azarov
Assignee: Daniel Azarov
Fix For: 3.3.x
Quickfix for "Stereotype annotation type must be annotated with one of @Target('{'TYPE, METHOD, FIELD'}'), @Target('{'METHOD, FIELD'}'), @Target('{'TYPE'}'), @Target('{'METHOD'}'), @Target('{'FIELD'}') [JSR-299 §2.7.1]" error marker.
This quickfix should offer next:
1. Add @Target({TYPE, METHOD, FIELD}) annotation
2. Add @Target({METHOD, FIELD}) annotation
3. Add @Target({TYPE}) annotation
4. Add @Target({METHOD}) annotation
5. Add @Target({FIELD}) annotation
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBIDE-7632) Quickfix for "Qualifier annotation type must be annotated with @Target..." error marker
by Daniel Azarov (JIRA)
Quickfix for "Qualifier annotation type must be annotated with @Target..." error marker
---------------------------------------------------------------------------------------
Key: JBIDE-7632
URL: https://jira.jboss.org/browse/JBIDE-7632
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: cdi (jsr-299)
Reporter: Daniel Azarov
Assignee: Daniel Azarov
Fix For: 3.3.x
Quickfix for "Qualifier annotation type must be annotated with @Target('{'TYPE, METHOD, FIELD, PARAMETER'}') or @Target('{'FIELD, PARAMETER'}') [JSR-299 §2.3.2, §10.1]" error marker.
If there is no @Target annotation this quickfix should offer next:
1. Add @Target({TYPE, METHOD, FIELD, PARAMETER}) annotation
2. Add @Target({FIELD, PARAMETER}) annotation
If current @Target annotation is not correct this quickfix should offer next:
1. Change current @Target to @Target({TYPE, METHOD, FIELD, PARAMETER}) annotation
2. Change current @Target to @Target({FIELD, PARAMETER}) annotation
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months