[JBoss JIRA] Created: (JBIDE-6065) Default Invm Scope to GLOBAL - Usability
by Burr Sutter (JIRA)
Default Invm Scope to GLOBAL - Usability
----------------------------------------
Key: JBIDE-6065
URL: https://jira.jboss.org/jira/browse/JBIDE-6065
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.0.0.GA
Reporter: Burr Sutter
Attachments: INVM_Scope.png
I have found that I normally forget to set the INVM Scope to GLOBAL when creating a new service. Forgetting to set this attribute results in a runtime error message upon deployment.
It is very common to forget the attribute because of is placement - at the service level instead of the listener level.
User will tend to follow these steps:
- Add a Service
- Add a HTTP Listener with a urlpattern
- Add a SOAPProxy Action
and forget to go back to the Service screen and flip INVM scope to Global
see screen shot
--
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
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9797) Errors occurred during the build
by Ron Ratovsky (JIRA)
Errors occurred during the build
--------------------------------
Key: JBIDE-9797
URL: https://issues.jboss.org/browse/JBIDE-9797
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core, Webservices
Affects Versions: 3.3.0.M3
Environment: Windows 7 64 bit
Eclipse Indigo 3.7 SR1 64 bit
Java 1.6.0_26 64 bit
Reporter: Ron Ratovsky
Assignee: Alexey Kazakov
When restarting eclipse, it rebuilds the whole workspace and I encounter the following error:
Errors occurred during the build.
Errors running builder 'JAX-RS Builder' on project 'some-project-name'.
org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
Looking at the logs, I found the following:
!ENTRY org.eclipse.core.resources 4 75 2011-09-29 18:28:26.111
!MESSAGE Errors occurred during the build.
!SUBENTRY 1 org.jboss.tools.ws.jaxrs.core 4 75 2011-09-29 18:28:26.111
!MESSAGE Errors running builder 'JAX-RS Builder' on project 'some-project-name'.
!STACK 0
java.lang.ClassCastException: org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
at org.jboss.tools.ws.jaxrs.core.metamodel.ResourceMethod.merge(ResourceMethod.java:103)
at org.jboss.tools.ws.jaxrs.core.metamodel.ResourceMethod.<init>(ResourceMethod.java:58)
at org.jboss.tools.ws.jaxrs.core.metamodel.Resource.mergeMethods(Resource.java:210)
at org.jboss.tools.ws.jaxrs.core.metamodel.Resource.merge(Resource.java:160)
at org.jboss.tools.ws.jaxrs.core.metamodel.Resource$ResourceBuilder.build(Resource.java:101)
at org.jboss.tools.ws.jaxrs.core.metamodel.Resources.addFrom(Resources.java:53)
at org.jboss.tools.ws.jaxrs.core.metamodel.Metamodel.addElements(Metamodel.java:221)
at org.jboss.tools.ws.jaxrs.core.internal.builder.JaxrsMetamodelBuilder.fullBuild(JaxrsMetamodelBuilder.java:184)
at org.jboss.tools.ws.jaxrs.core.internal.builder.JaxrsMetamodelBuilder.build(JaxrsMetamodelBuilder.java:92)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Not sure what other information may be important here, so please let me know.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9480) CdiElResolver incorrectly resolves resource message bundle properties as Java Elements
by Victor Rubezhny (JIRA)
CdiElResolver incorrectly resolves resource message bundle properties as Java Elements
--------------------------------------------------------------------------------------
Key: JBIDE-9480
URL: https://issues.jboss.org/browse/JBIDE-9480
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi, jsp/jsf/xml source editing
Affects Versions: 3.3.0.M3
Reporter: Victor Rubezhny
Assignee: Alexey Kazakov
Fix For: 3.3.0.M3
EXECUTE: Import Seam-booking example (See http://seamframework.org/Seam3/Contribute for details how to get this example from Seam git repository.
EXECUTE: Open src/main/webapp/home.xhtml
EXECUTE: Ctrl+Left-Mouse-Click or press F3 while the text cursor is placed over 'home_header' resource bundle property in #{bundles.messages.home_header} EL.
ASSERT: There should be the only Resource Bundle Property Hyperlinks like 'Open property 'home_header' of bundle 'messages'' hyperlink which opens messages resource bundle and selects 'home_header' property in it.
FAIL: Actually there are two Hyperlinks listed: One for resource bundle property (correct, as described above) and another one saying: "Should not get here" (which is wrong and have nothing to open. It came from CdiElResolver)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9798) new *-tests profiles in trunk/build/pom.xml are breaking Hudson jobs
by Nick Boldt (JIRA)
new *-tests profiles in trunk/build/pom.xml are breaking Hudson jobs
--------------------------------------------------------------------
Key: JBIDE-9798
URL: https://issues.jboss.org/browse/JBIDE-9798
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, CDI
Affects Versions: 3.3.0.M4
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 3.3.0.M4
New profile:
{code}
<profile>
<id>cdi-tests</id>
<modules>
<module>libs</module>
<module>../cdi/tests</module>
<module>reports/emma-coverage</module>
</modules>
</profile>
{code}
Result:
{code}
[sources] $ /qa/tools/opt/apache-maven-3.0.3/bin/mvn -f /qa/local/hudson_workspace/workspace/jbosstools-3.3_trunk.component--cdi/build/pom.xml "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,jbosstools-nightly-staging-composite,local.site,cdi-tests -Dmaven.repo.local=${WORKSPACE}/m2-repository" install -B -U -fae -e -P hudson,jbosstools-nightly-staging-composite,local.site,cdi-tests -Dmaven.repo.local=/qa/local/hudson_workspace/workspace/jbosstools-3.3_trunk.component--cdi/m2-repository -DJOB_NAME=jbosstools-3.3_trunk.component--cdi -DBUILD_ID=2011-09-29_13-58-54 -DBUILD_NUMBER=578 -Dcoverage -Pcdi-tests
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[ERROR] Child module /qa/local/hudson_workspace/workspace/jbosstools-3.3_trunk.component--cdi/build/../cdi/tests of /qa/local/hudson_workspace/workspace/jbosstools-3.3_trunk.component--cdi/build/pom.xml does not exist
{code}
-- http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
Diffs:
http://source.jboss.org/browse/JBossTools/trunk/build/pom.xml?r1=34984&r2...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9739) CSS Properties Page->Edited Properties is incorrectly updating
by Yahor Radtsevich (JIRA)
CSS Properties Page->Edited Properties is incorrectly updating
--------------------------------------------------------------
Key: JBIDE-9739
URL: https://issues.jboss.org/browse/JBIDE-9739
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.3.0.M3
Reporter: Yahor Radtsevich
Assignee: Yahor Radtsevich
Fix For: 3.3.0.M4
*Steps to reproduce*
# Create a new CSS file and open it in CSS editor. Set the following content to the file:
{code:title=example.css}
#id1 {
color: red;
}
#id2 {
background-color: Yellow;
font-size: larger
}
{code}
# Open CSS Properties View->Edited Properties tab
# Point the text cursor to the #id1
# *Assert:* there is one line of properties in the tab: {{color: red;}}
# Point the text cursor to the #id2
*Actual result*
There is still one line of properties in the tab: {{color: }}.
*Expected result*
There are two lines of properties in the tab:
{code}
background-color: Yellow;
font-size: larger
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9188) add system property to allow explicit disabling of the visual page in VPE
by Max Rydahl Andersen (JIRA)
add system property to allow explicit disabling of the visual page in VPE
-------------------------------------------------------------------------
Key: JBIDE-9188
URL: https://issues.jboss.org/browse/JBIDE-9188
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Reporter: Max Rydahl Andersen
Assignee: Yahor Radtsevich
Priority: Critical
Fix For: 3.3.0.M2
Since we keep having OS's where xulrunner is having problems we should inlcude a way to disable it loading even though we have xul binaries available for it.
I suggest we look for system property: org.jboss.tools.vpe.loadvisualeditor if it is true (default) then we attempt to load the VPE as usual, but if false then we skip that page just as if the binaries were not available.
that would allow you do to eclipse -Dorg.jboss.tools.vpe.loadvisualeditor=false
Things to consider: if this property is set I guess xulrunner initializer should also not do anything ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months