[JBoss JIRA] (JBIDE-12452) Add support for creating and auto-discovering JBoss AS "user instances"
by Dan Allen (JIRA)
Dan Allen created JBIDE-12452:
---------------------------------
Summary: Add support for creating and auto-discovering JBoss AS "user instances"
Key: JBIDE-12452
URL: https://issues.jboss.org/browse/JBIDE-12452
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 3.3.1
Environment: Fedora 17 and above
Fedora JBoss AS package (jboss-as)
Reporter: Dan Allen
Assignee: Rob Stryker
The Fedora JBoss AS package supports creating user instances of JBoss AS. A user instance allows an unprivileged user to run JBoss AS out of that user's home directory. An instance is created using the jboss-as-cp script. For example:
{code}
jboss-as-cp -l $HOME/applications/jboss-as-user-instance
{code}
The user instance is skinny, meaning it only contains the configuration files for the instance. The libraries are kept in the system instance and referenced by the custom startup script:
{code}
JBOSS_BASE_DIR=$HOME/applications/jboss-as-user-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml
{code}
JBoss Tools does not currently auto-detect these instances. However, it could offer to create and/or auto-discover them.
It's possible to get JBoss Tools to control the user instance, but it requires tweaking the startup flags in the server configuration. Here's how:
1. Have JBoss AS auto-discover the system instance at /usr/share/java
2. Open the server launch configuration
3. Uncheck the box "Always update arguments related to the runtime" so our changes don't get overwritten
4. Replace the VM arguments that contain "jboss" with:
-Dorg.jboss.boot.log.file=${env_var:HOME}/applications/jboss-as-user-instance/log/boot.log -Dlogging.configuration=file:${env_var:HOME}/applications/jboss-as-user-instance/configuration/logging.properties -Djboss.home.dir=/usr/share/jboss-as -Djboss.server.base.dir=${env_var:HOME}/applications/jboss-as-user-instance
Having native support for JBoss AS to auto-detect and configure user instances would be ideal.
If changes are required in the jboss-as-cp script, please use this issue tracker: https://bugzilla.redhat.com/buglist.cgi?component=jboss-as&product=Fedora...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (JBIDE-9443) Wizard for creating Service implementations (ServiceLoader / Service file)
by Lincoln Baxter III (JIRA)
Wizard for creating Service implementations (ServiceLoader / Service file)
--------------------------------------------------------------------------
Key: JBIDE-9443
URL: https://issues.jboss.org/browse/JBIDE-9443
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M2
Reporter: Lincoln Baxter III
It would be very nice if we had a wizard or hotkey to create a new service implementation:
CTRL-N
--> New Service Implementation Class
1. Wizard asks you to specify the service Interface you wish to implement, and then lets you give the typical new-class information (with Interface already populated and greyed out.)
2. When submitted, the wizard creates the implementing class, and also creates a service file in the java-resources 'META-INF/services' directory, containing the name of your service implementation class. If the Service file already exists, your class should be added to it on a new line:
META-INF/services/org.example.service.spi.Interface
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (JBIDE-12347) Unable to invoke SOAP web service
by Jaroslav Jankovič (JIRA)
Jaroslav Jankovič created JBIDE-12347:
-----------------------------------------
Summary: Unable to invoke SOAP web service
Key: JBIDE-12347
URL: https://issues.jboss.org/browse/JBIDE-12347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.3.1
Reporter: Jaroslav Jankovič
Assignee: Brian Fitzpatrick
Fix For: 3.3.2
I am unable to invoke SOAP web service in WS Tester from http://www.webservicex.net/BibleWebservice.asmx?WSDL.
In Response Body of WS Tester I got the message:
{code}
javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: .
at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest()
at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message)
at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
{code}
In error log I got the error:
{code}
java.lang.Exception: javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: .
at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest()
at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message)
at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:205)
at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1803)
at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1789)
at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1706)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: .
at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest()
at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message)
at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:111)
at com.sun.xml.internal.ws.client.dispatch.DispatchImpl$DispatchAsyncInvoker$1.onCompletion(DispatchImpl.java:450)
at com.sun.xml.internal.ws.client.Stub$1.onCompletion(Stub.java:381)
at com.sun.xml.internal.ws.api.pipe.Fiber.completionCheck(Fiber.java:502)
at com.sun.xml.internal.ws.api.pipe.Fiber.run(Fiber.java:420)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (JBIDE-12466) Find a new home for org.jboss.tools.runtime.as.ui.bot.test
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-12466:
-----------------------------------
Summary: Find a new home for org.jboss.tools.runtime.as.ui.bot.test
Key: JBIDE-12466
URL: https://issues.jboss.org/browse/JBIDE-12466
Project: Tools (JBoss Tools)
Issue Type: Task
Components: runtime detection
Affects Versions: 4.0.0.M1
Reporter: Rob Stryker
Assignee: Len DiMaggio
Fix For: 4.0.0.M1
JIRA JBIDE-12465 will soon disable the org.jboss.tools.runtime.as.ui.bot.test plugin test. It is not the intention that this test plugin disappear; just that it get moved.
The test plugin will be disabled shortly. Once it is removed from the build, it will be safe for QE to find a new home for it. The given test plugin is more of an integration test plugin and belongs with other integration tests and integration swtbot tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (JBIDE-12505) ensure all JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-12505:
----------------------------------
Summary: ensure all JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/
Key: JBIDE-12505
URL: https://issues.jboss.org/browse/JBIDE-12505
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, SOA Tooling, updatesite
Affects Versions: 3.3.0.Final-SOA, 4.0.0.M1-SOA
Reporter: Nick Boldt
Assignee: Nick Boldt
For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/.
This issue should be a container for child issues assigned to each project's releng person.
Done:
* SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw...
Publishes elsewhere, manually symlinked:
* Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr...
Publishes elsewhere:
* Modeshape Tools - JBBUILD-720, MODE-1506 - http://download.jboss.org/modeshape/builds/staging/modeshape-tools-contin... ?
* Savara - http://download.jboss.org/savara/releases/updates/2.0.x/
* pi4soa - http://pi4soa.sourceforge.net/updates/
Publishes as zip only:
* Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi...
No publishing strategy (staging only):
* ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
* jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
* JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (JBIDE-8654) New Instance wizard: add capability to create server adapter from instance
by Andre Dietisheim (JIRA)
New Instance wizard: add capability to create server adapter from instance
--------------------------------------------------------------------------
Key: JBIDE-8654
URL: https://issues.jboss.org/browse/JBIDE-8654
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Final, 3.3.0.M1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.x
Currently you may create a new server adapter in 2 ways:
1) fully automatically when launching the instance: check "Create Server Adapter"
2) manually:
* launch an instance
* show in remote system explorer (creates the RSE connection)
* create server adapter, switch it to remote mode and use the RSE connection as host
Option 1) is pretty error prone. If 1 of the 3 tasks fail no server adapter is created and it's hard to find out why it went wrong. IMHO the process is too automatic, too long, too intrasparent.
Option 2) is pretty transparent, but not obvious.
We would improve the situation if we would offer an action "Create Server Adapter" in the context menu of the instances.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months