[JBoss JIRA] Created: (JBIDE-9334) Cannot publish to remote EAP 5.1
by Martin Malina (JIRA)
Cannot publish to remote EAP 5.1
--------------------------------
Key: JBIDE-9334
URL: https://issues.jboss.org/browse/JBIDE-9334
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M2
Environment: Mac OS X 10.6 Snow Leopard
Reporter: Martin Malina
Assignee: Rob Stryker
Attachments: errorMsg.jpg
Scenario:
1. Start JBT with a fresh workspace
2. Create a simple dynamic web project
3. Add a local EAP 5.1 server runtime + server adapter
4. Add a remote EAP 5.1 server adapter
5. Start the remote server
6. An error message will pop up
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9409) compile failed for org.jboss.tools.jsf
by Nick Boldt (JIRA)
compile failed for org.jboss.tools.jsf
--------------------------------------
Key: JBIDE-9409
URL: https://issues.jboss.org/browse/JBIDE-9409
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M3
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Priority: Blocker
Fix For: 3.3.0.M3
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--jsf...
[INFO] org.jboss.tools.jsf ............................... FAILURE [16.349s]
[ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-compiler-plugin:0.10.0:compile (default-compile) on project org.jboss.tools.jsf: Compilation failure: Compilation failure:
[ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--jsf/sources/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/model/JSFMessageELCompletionEngine.java (at line 508):[-1,-1]
[ERROR] segment.addObject(p);
[ERROR] ^^^^^^^^^
[ERROR] The method addObject(XModelObject) is undefined for the type MessagePropertyELSegmentImpl
[ERROR]
[ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--jsf/sources/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/model/JSFMessageELCompletionEngine.java (at line 546):[-1,-1]
[ERROR] segment.addObject(property);
[ERROR] ^^^^^^^^^
[ERROR] The method addObject(XModelObject) is undefined for the type MessagePropertyELSegmentImpl
[ERROR]
[ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--jsf/sources/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/model/JSF2CCAttrsELCompletionEngine.java (at line 44):[-1,-1]
[ERROR] import org.jboss.tools.common.el.core.resolver.IOpenableReference;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.jboss.tools.common.el.core.resolver.IOpenableReference cannot be resolved
[ERROR]
[ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--jsf/sources/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/model/JSF2CCAttrsELCompletionEngine.java (at line 674):[-1,-1]
[ERROR] public IOpenableReference[] getOpenable() {
[ERROR] ^^^^^^^^^^^^^^^^^^
[ERROR] IOpenableReference cannot be resolved to a type
[ERROR]
[ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--jsf/sources/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/model/JSF2CCAttrsELCompletionEngine.java (at line 677):[-1,-1]
[ERROR] IOpenableReference openable = new IOpenableReference() {
[ERROR] ^^^^^^^^^^^^^^^^^^
[ERROR] IOpenableReference cannot be resolved to a type
[ERROR]
[ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--jsf/sources/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/model/JSF2CCAttrsELCompletionEngine.java (at line 677):[-1,-1]
[ERROR] IOpenableReference openable = new IOpenableReference() {
[ERROR] ^^^^^^^^^^^^^^^^^^
[ERROR] IOpenableReference cannot be resolved to a type
[ERROR]
[ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--jsf/sources/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/model/JSF2CCAttrsELCompletionEngine.java (at line 679):[-1,-1]
[ERROR] public boolean open() {
[ERROR] ^^^^^^
[ERROR] The method open() of type new IOpenableReference(){} must override or implement a supertype method
[ERROR]
[ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--jsf/sources/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/model/JSF2CCAttrsELCompletionEngine.java (at line 684):[-1,-1]
[ERROR] public String getLabel() {
[ERROR] ^^^^^^^^^^
[ERROR] The method getLabel() of type new IOpenableReference(){} must override or implement a supertype method
[ERROR]
[ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--jsf/sources/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/model/JSF2CCAttrsELCompletionEngine.java (at line 688):[-1,-1]
[ERROR] public Image getImage() {
[ERROR] ^^^^^^^^^^
[ERROR] The method getImage() of type new IOpenableReference(){} must override or implement a supertype method
[ERROR]
[ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--jsf/sources/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/model/JSF2CCAttrsELCompletionEngine.java (at line 692):[-1,-1]
[ERROR] return new IOpenableReference[]{openable};
[ERROR] ^^^^^^^^^^^^^^^^^^
[ERROR] IOpenableReference cannot be resolved to a type
[ERROR]
[ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--jsf/sources/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/model/JSF2CCAttrsELCompletionEngine.java (at line 694):[-1,-1]
[ERROR] return new IOpenableReference[0];
[ERROR] ^^^^^^^^^^^^^^^^^^
[ERROR] IOpenableReference cannot be resolved to a type
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonatype.tycho:maven-osgi-compiler-plugin:0.10.0:compile (default-compile) on project org.jboss.tools.jsf: Compilation failure
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.codehaus.tycho.osgicompiler.copied.CompilationFailureException: Compilation failure
at org.codehaus.tycho.osgicompiler.copied.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:404)
at org.codehaus.tycho.osgicompiler.AbstractOsgiCompilerMojo.execute(AbstractOsgiCompilerMojo.java:157)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :org.jboss.tools.jsf
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9328) Can't run web project on JBoss AS 6
by Alexey Kazakov (JIRA)
Can't run web project on JBoss AS 6
-----------------------------------
Key: JBIDE-9328
URL: https://issues.jboss.org/browse/JBIDE-9328
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M3
Reporter: Alexey Kazakov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.M3
1. Create JBoss AS 6 Runtime/Server (I'm using 6.0.0.Final)
2. Create a Seam Web Project (WAR) and deploy it to the server.
3. Run the project on the server - HTTP Status 404. No any errors in console.
The project was deployed successfully but it seems that AS doesn't pick up the war from workspace folder.
If I change deploy folder from workspace to the JBoss deploy folder then I get "java.lang.OutOfMemoryError: PermGen space" error in the console:
{code}
16:19:01,115 INFO [AbstractJBossASServerBase] Server Configuration:
JBOSS_HOME URL: file:/home/igels/Downloads/Java/JBoss/AS/6/jboss-6.0.0.Final/
Bootstrap: $JBOSS_HOME/server/default/conf/bootstrap.xml
Common Base: $JBOSS_HOME/common/
Common Library: $JBOSS_HOME/common/lib/
Server Name: default
Server Base: $JBOSS_HOME/server/
Server Library: $JBOSS_HOME/server/default/lib/
Server Config: $JBOSS_HOME/server/default/conf/
Server Home: $JBOSS_HOME/server/default/
Server Data: $JBOSS_HOME/server/default/data/
Server Log: $JBOSS_HOME/server/default/log/
Server Temp: $JBOSS_HOME/server/default/tmp/
16:19:01,118 INFO [AbstractServer] Starting: JBossAS [6.0.0.Final "Neo"]
16:19:02,412 INFO [ServerInfo] Java version: 1.6.0_25,Sun Microsystems Inc.
16:19:02,412 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
16:19:02,420 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 20.0-b11,Sun Microsystems Inc.
16:19:02,420 INFO [ServerInfo] OS-System: Linux 2.6.38-8-generic,amd64
16:19:02,421 INFO [ServerInfo] VM arguments: -Djava.endorsed.dirs=/home/igels/Downloads/Java/JBoss/AS/6/jboss-6.0.0.Final/lib/endorsed -Dfile.encoding=UTF-8
16:19:02,449 INFO [JMXKernel] Legacy JMX core initialized
16:19:05,897 INFO [AbstractServerConfig] JBoss Web Services - Stack CXF Server 3.4.1.GA
16:19:06,499 INFO [JSFImplManagementDeployer] Initialized 3 JSF configurations: [Mojarra-1.2, MyFaces-2.0, Mojarra-2.0]
16:19:10,291 WARNING [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
16:19:57,748 WARN [ClassLoaderManager] Unexpected error during load of:org.jboss.seam.remoting.gwt.GWTService: java.lang.OutOfMemoryError: PermGen space
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f5a22153a42, pid=18893, tid=140024914777856
#
# JRE version: 6.0_25-b06
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.0-b11 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V [libjvm.so+0x3dca42] constantPoolOopDesc::klass_at_impl(constantPoolHandle, int, Thread*)+0x42
#
# An error report file with more information is saved as:
# /home/igels/Downloads/Java/JBoss/AS/6/jboss-6.0.0.Final/bin/hs_err_pid18893.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
{code}
bin/run.sh starts project w/o any problems and the application works fine.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9274) Touch descriptors button does not work for AS7
by Libor Zoubek (JIRA)
Touch descriptors button does not work for AS7
----------------------------------------------
Key: JBIDE-9274
URL: https://issues.jboss.org/browse/JBIDE-9274
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Fix For: 3.3.0.M3
Finger button was used to touch web.xml and actually trigger redeployment of war/ear. This does not work on AS7 anymore (web.xml is probably touched, but redeployment works different way).
What is the funcionality of this button within AS7?
I think we should create .dodeploy file when this button is pressed or it should be disabled at all.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9361) Imported project examples with multiple projects don't have build path set correctly
by Brian Fitzpatrick (JIRA)
Imported project examples with multiple projects don't have build path set correctly
------------------------------------------------------------------------------------
Key: JBIDE-9361
URL: https://issues.jboss.org/browse/JBIDE-9361
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 3.2.1.CR3, 3.3.0.M3
Environment: Windows 7, JBDS 4.1 CR3 build installed, 32-bit JDK
Reporter: Brian Fitzpatrick
Assignee: Snjezana Peco
While doing some testing of one of the ESB project examples (ESB for SOA-P 5.0 -> JBoss ESB HelloWorld Action Example - ESB and ESB for SOA-P 5.0 -> JBoss ESB Web Service consumer1 Example) in conjunction with JBDS-1716, I discovered an interesting issue when there are multiple projects in the project-example zip being imported.
The first project in the zip being imported (i.e. helloworld_action) is imported correctly with the runtime set properly in the build path. But the second project (i.e. helloworld_action_client) is not updated correctly and still pointing to the wrong runtime.
To reproduce:
1) In a new workspace with no SOA/EAP 5.x runtime defined, create a new EAP 5.x server in the Servers view. Name the server "one" and the server runtime "two".
2) Click on Help->Project Examples->ESB for SOA-P 5.0->JBoss ESB HelloWorld Action Example - ESB.
3) Note that when the projects are imported, helloworld_action is setup correctly and helloworld_action_client is not.
Now, is this a bug? Or is it working as designed? I would hope that the project examples code would peer into each project being imported to see if the build path needed to be updated.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months