[jbosside-issues] [JBoss JIRA] Created: (JBIDE-389) Exploded deployment
by Sondre Eikanger Kvalø (JIRA)
Exploded deployment
-------------------
Key: JBIDE-389
URL: http://jira.jboss.com/jira/browse/JBIDE-389
Project: JBoss IDE
Issue Type: Feature Request
Components: JBossAS Adapter
Affects Versions: 2.0.0.Beta2
Environment: Any
Reporter: Sondre Eikanger Kvalø
Assigned To: Robert Stryker
Fix For: 2.0.0.GA
For Web devolopers it would be really time-saving to be able to do "exploded deployment" of Web applications..
Publishing to an exploded deployment should copy new CLASS/JSP/HTML/CSS files from your web project to a folder (called webprojectname.war) in the deploy folder of the chosen JBoss server instance..
Then you would not have to redeploy the webapplication for every minor change (ex. editing text on a JSP or HTML page)...
You schould also be able to make a complete redeployment of your web project where the server adapter would re-create the web application structure..
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[jbosside-issues] [JBoss JIRA] Created: (JBIDE-381) WTP breaks JBoss IDE publishing
by Sondre Eikanger Kvalø (JIRA)
WTP breaks JBoss IDE publishing
-------------------------------
Key: JBIDE-381
URL: http://jira.jboss.com/jira/browse/JBIDE-381
Project: JBoss IDE
Issue Type: Bug
Components: JBossAS Adapter
Affects Versions: 2.0.0.Beta1
Environment: Ubuntu Linux 6.06 (32 bit), Eclipse 3.2.1, WST 1.5.1, JBoss AS 4.0.4.GA, Sun J2sdk 5.0 (1.5.0_05)
Reporter: Sondre Eikanger Kvalø
Assigned To: Robert Stryker
Priority: Critical
After upgrading Eclipse SDK to version 3.2.1 and Web Standard Tools to version 1.5.1, publishing to JBoss AS using the JBoss Server View breaks..
If automatic publishing is enabled, you will no longer be able to start a JBoss AS server using this feature
Message:
An internal error occurred during: "Publishing to jboss default...".
Stacktrace:
java.lang.NoSuchMethodError: org.eclipse.jst.server.generic.core.internal.publishers.AbstractModuleAssembler: method <init>()V not found
at org.jboss.ide.eclipse.as.core.server.publishers.JstPublisher$JBossAntPublisher.<init>(JstPublisher.java:124)
at org.jboss.ide.eclipse.as.core.server.publishers.JstPublisher.publishModule(JstPublisher.java:99)
at org.jboss.ide.eclipse.as.core.server.JBossServerBehavior.publishModule(JBossServerBehavior.java:396)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:676)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:756)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:611)
at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:862)
at org.eclipse.wst.server.core.internal.Server.publish(Server.java:850)
at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:142)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Created: (JBIDE-501) Unable to start JBoss-Server 4.2GA
by Perry Rhodan (JIRA)
Unable to start JBoss-Server 4.2GA
----------------------------------
Key: JBIDE-501
URL: http://jira.jboss.com/jira/browse/JBIDE-501
Project: JBoss Tools
Issue Type: Bug
Components: JBossIDE Core
Affects Versions: 2.0.0.Beta3, 2.0.0.GA
Environment: Windows-XP, Eclipse 3.3 Europa, JBossTools-200706300254-nightly-ALL-win32.zip
Reporter: Perry Rhodan
Assigned To: Marshall Culpepper
It's impossible to start a Jboss 4.2GA Server with JBossTools-200706300254-nightly-ALL-win32.zip under Eclipse Europa release. Every time the startup will be interrupted by an <problem occured> dialog with "Server <servername> failed to start" as detail.
In the event-log will this failure be logged:
Failure: NamingException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicatinException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out.]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months