January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13381) ESB Editor removes "http-client-property" property (JBDS-2446)

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13381: ------------------------------------------- Viachelsav - I tried applying the patch to 3.3.x in SVN and it doesn't like it. Keeps complaining about weird paths and not finding things. Can you apply it from your side? > ESB Editor removes "http-client-property" property (JBDS-2446) > -------------------------------------------------------------- > > Key: JBIDE-13381 > URL: https://issues.jboss.org/browse/JBIDE-13381 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: esb > Affects Versions: 3.3.0.Final-SOA > Reporter: Brian Fitzpatrick > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 3.3.x, 4.0.x > > Attachments: jbide-13381.patch > > > When editing an ESB file (jboss-esb.xml), we have two ways which are using the native XML editor or the visual way. > When we want to use the property X. We created our service and our SOAPClient using the visual editor, then we have to add the "http-client-property" manually > <?xml version="1.0"?> > <jbossesb parameterReloadSecs="5" > xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."> > <services> > <service category="c1" description="d1" name="s1"> > <actions> > <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client"> > <property name="wsdl" value="someWsdl"/> > <property name="SOAPAction" value="noAction"/> > <property name="endpointUrl" value="http://host/servername"> > <http-client-property name="file" value="httpclient.properties" /> > </property> > </action> > </actions> > </service> > </services> > </jbossesb> > Notice the "http-client-property" in the action property element. The problem is that when using visual editor of this file and adding something new or editing existing thing, the code related to this property is deleted. In the example above, I have the following result, showing what the editor removed: (in this case I just changed the service name from service-test to service-test-edited) > <?xml version="1.0"?> > <jbossesb parameterReloadSecs="5" > xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."> > <services> > <service category="c1" description="d1" name="s1-edited"> > <actions> > <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client"> > <property name="wsdl" value="someWsdl"/> > <property name="SOAPAction" value="noAction"/> > <property name="endpointUrl" value="http://host/servername"/> > </action> > </actions> > </service> > </services> > </jbossesb> > One test we have done is change the XSD used by the JBDS(1.3.1 to the one used in quickstars (1.0.1). The http-client-property worked fine, but other things stopped working. So we need to know what's wrong with the schema and what should make it works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10525) server editor Server behavior expansion too tall

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10525?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-10525: -------------------------------- Fix Version/s: 4.1.0.Alpha1 (was: 4.0.x) > server editor Server behavior expansion too tall > ------------------------------------------------ > > Key: JBIDE-10525 > URL: https://issues.jboss.org/browse/JBIDE-10525 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 3.3.0.M5 > Reporter: Martin Malina > Assignee: Snjezana Peco > Priority: Minor > Fix For: 4.1.0.Alpha1 > > Attachments: server-behavior-white-space.jpg > > > Cloned from JBIDE-10117 since this issue is similar. (Probably should have created a new issue, but too late now.) > When Server Behavior is expanded, it is too tall - there is a lot of blank space at the bottom. See screenshot. This happens only when the server is set to Local. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13213) Simple adding/removing Project Archives capabilities into project

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13213?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13213: ------------------------------------- Committed a fix to master. Awaiting approval for 4.0.x > Simple adding/removing Project Archives capabilities into project > ----------------------------------------------------------------- > > Key: JBIDE-13213 > URL: https://issues.jboss.org/browse/JBIDE-13213 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Reporter: Vlado Pakan > Assignee: Rob Stryker > Fix For: 4.0.x > > > It would be useful if we have "Configure -> Add/Remove Project Archive support" option. This option would add/remove Project Archive explorer into project in Project Explorer. Now, Project Archive explorer is visible only after creation of archive with Project Archives view. To remove Project Archives explorer now, .packages files has to be deleted. This approach is not much user friendly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13361) Update version of GWT archetype in JBT 3 / JBDS 5 Central

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13361?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13361: --------------------------------------- Actually, the version 1.0.0.M12-redhat-1 is available from the online repo: http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/jboss-ja... But I don't know where that version came from - as I said, EAP 6.0.0 had 1.0.0.M11-redhat-1 and EAP 6.0.1 has 1.0.2.Final-redhat-1 . > Update version of GWT archetype in JBT 3 / JBDS 5 Central > --------------------------------------------------------- > > Key: JBIDE-13361 > URL: https://issues.jboss.org/browse/JBIDE-13361 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, maven > Affects Versions: 3.3.2 > Environment: JBDS 5.0.2.CR2 H238 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 3.3.2 > > > I started testing JBDS 5.0.2 and found out I cannot run mvn package on the GWT project from JBoss Central. > I thought it was using the same mechanism as JBDS 6, but apparently not. And the archetype version is set to org.jboss.errai.archetypes:jboss-errai-kitchensink-archetype:2.0.0.Final while the current version in JBDs 6 is 2.1.1.Final. Can we update it? > The 2.0.0.Final gives this error when trying to run Maven Build... clean package: > {code} > [INFO] [ERROR] Errors in '/Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/target/.generated/org/jboss/tools/gwt/kitchensink/client/shared/_MemberValidatorImpl.java' > [INFO] [ERROR] Line 430: The method validate(GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, V, ConstraintValidator<A,? super V>, ConstraintDescriptorImpl<A>, Class<?>[]) in the type AbstractGwtSpecificValidator<Member> is not applicable for the arguments (GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, String, SizeValidatorForMap, ConstraintDescriptorImpl<Size>, Class<?>[]) > [INFO] [ERROR] Line 452: The method validate(GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, V, ConstraintValidator<A,? super V>, ConstraintDescriptorImpl<A>, Class<?>[]) in the type AbstractGwtSpecificValidator<Member> is not applicable for the arguments (GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, String, SizeValidatorForMap, ConstraintDescriptorImpl<Size>, Class<?>[]) > [INFO] [ERROR] Line 477: The method validate(GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, V, ConstraintValidator<A,? super V>, ConstraintDescriptorImpl<A>, Class<?>[]) in the type AbstractGwtSpecificValidator<Member> is not applicable for the arguments (GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, String, SizeValidatorForMap, ConstraintDescriptorImpl<Size>, Class<?>[]) > [INFO] [ERROR] Cannot proceed due to previous errors > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 33.994s > [INFO] Finished at: Wed Jan 09 15:11:42 CET 2013 > [INFO] Final Memory: 27M/205M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:2.4.0:compile (default) on project gwt-kitchensink: Command [[ > [ERROR] /bin/sh -c /Library/Java/JavaVirtualMachines/jdk1.7.0_07.jdk/Contents/Home/jre/bin/java -Xmx512m -classpath /Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/src/main/java:/Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/src/main/resources:/Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/target/classes:/Users/rasp/.m2/repository/javax/enterprise/cdi-api/1.0-SP4/cdi-api-1.0-SP4.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/interceptor/jboss-interceptors-api_1.1_spec/1.0.1.Final/jboss-interceptors-api_1.1_spec-1.0.1.Final.jar:/Users/rasp/.m2/repository/javax/inject/javax.inject/1/javax.inject-1.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/transaction/jboss-transaction-api_1.1_spec/1.0.1.Final/jboss-transaction-api_1.1_spec-1.0.1.Final.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/annotation/jboss-annotations-api_1.1_spec/1.0.1.Final/jboss-annotations-api_1.1_spec-1.0.1.Final.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/ws/rs/jboss-jaxrs-api_1.1_spec/1.0.0.Final/jboss-jaxrs-api_1.1_spec-1.0.0.Final.jar:/Users/rasp/.m2/repository/org/hibernate/javax/persistence/hibernate-jpa-2.0-api/1.0.1.Final/hibernate-jpa-2.0-api-1.0.1.Final.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/ejb/jboss-ejb-api_3.1_spec/1.0.2.Final/jboss-ejb-api_3.1_spec-1.0.2.Final.jar:/Users/rasp/.m2/repository/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA.jar:/Users/rasp/.m2/repository/org/hibernate/hibernate-validator/4.2.0.Final/hibernate-validator-4.2.0.Final.jar:/Users/rasp/.m2/repository/org/hibernate/hibernate-validator/4.2.0.Final/hibernate-validator-4.2.0.Final-sources.jar:/Users/rasp/.m2/repository/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA-sources.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-bus/2.0.0.Final/errai-bus-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-common/2.0.0.Final/errai-common-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/reflections/reflections/2.0.0.Final/reflections-2.0.0.Final.jar:/Users/rasp/.m2/repository/com/google/guava/guava/10.0.1/guava-10.0.1.jar:/Users/rasp/.m2/repository/com/google/code/findbugs/jsr305/1.3.9/jsr305-1.3.9.jar:/Users/rasp/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar:/Users/rasp/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-marshalling/2.0.0.Final/errai-marshalling-2.0.0.Final.jar:/Users/rasp/.m2/repository/com/google/inject/guice/3.0/guice-3.0.jar:/Users/rasp/.m2/repository/aopalliance/aopalliance/1.0/aopalliance-1.0.jar:/Users/rasp/.m2/repository/org/mvel/mvel2/2.1.Beta8/mvel2-2.1.Beta8.jar:/Users/rasp/.m2/repository/org/slf4j/slf4j-api/1.6.1/slf4j-api-1.6.1.jar:/Users/rasp/.m2/repository/org/slf4j/slf4j-log4j12/1.6.1/slf4j-log4j12-1.6.1.jar:/Users/rasp/.m2/repository/log4j/log4j/1.2.16/log4j-1.2.16.jar:/Users/rasp/.m2/repository/org/javassist/javassist/3.15.0-GA/javassist-3.15.0-GA.jar:/Users/rasp/.m2/repository/org/jboss/errai/io/netty/netty/4.0.0.Alpha1.errai.r1/netty-4.0.0.Alpha1.errai.r1.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-ioc/2.0.0.Final/errai-ioc-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-codegen/2.0.0.Final/errai-codegen-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-tools/2.0.0.Final/errai-tools-2.0.0.Final.jar:/Users/rasp/.m2/repository/hsqldb/hsqldb/1.8.0.7/hsqldb-1.8.0.7.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-cdi-client/2.0.0.Final/errai-cdi-client-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-javax-enterprise/2.0.0.Final/errai-javax-enterprise-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-weld-integration/2.0.0.Final/errai-weld-integration-2.0.0.Final.jar:/Users/rasp/.m2/repository/com/google/gwt/gwt-user/2.4.0/gwt-user-2.4.0.jar:/Users/rasp/.m2/repository/com/google/gwt/gwt-dev/2.4.0/gwt-dev-2.4.0.jar:/Users/rasp/.m2/repository/org/hibernate/hibernate-jpamodelgen/1.1.1.Final/hibernate-jpamodelgen-1.1.1.Final.jar:/Users/rasp/.m2/repository/com/google/gwt/gwt-user/2.4.0/gwt-user-2.4.0.jar:/Users/rasp/.m2/repository/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA.jar:/Users/rasp/.m2/repository/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA-sources.jar:/Users/rasp/.m2/repository/com/google/gwt/gwt-dev/2.4.0/gwt-dev-2.4.0.jar com.google.gwt.dev.Compiler -gen /Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/target/.generated -logLevel INFO -style OBF -war /Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/src/main/webapp -localWorkers 4 org.jboss.tools.gwt.kitchensink.KitchenSink > [ERROR] ]] failed with status 1 > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [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/MojoExecutionException > {code} > I tried doing this in JBDS 6 with the newer version and it worked for me. Then I removed my whole local maven repo and tried again in JBDS 5.0.2 and now it works. Something is wrong here - the idea of maven is that it should always get the right dependencies, no? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13406) BrowserSim: Integrate firebug-lite

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-13406: ---------------------------------------------- Summary: BrowserSim: Integrate firebug-lite Key: JBIDE-13406 URL: https://issues.jboss.org/browse/JBIDE-13406 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 4.1.0.Alpha1 Reporter: Konstantin Marmalyukov Assignee: Konstantin Marmalyukov Fix For: 4.1.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13213) Simple adding/removing Project Archives capabilities into project

by Jaroslav Jankovič (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13213?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič commented on JBIDE-13213: ------------------------------------------- Except of fresh workspace, there is another prerequisite to be able to reproduce this. You must not open Archives view. You have to work only with Archives explorer. > Simple adding/removing Project Archives capabilities into project > ----------------------------------------------------------------- > > Key: JBIDE-13213 > URL: https://issues.jboss.org/browse/JBIDE-13213 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Reporter: Vlado Pakan > Assignee: Rob Stryker > Fix For: 4.0.x > > > It would be useful if we have "Configure -> Add/Remove Project Archive support" option. This option would add/remove Project Archive explorer into project in Project Explorer. Now, Project Archive explorer is visible only after creation of archive with Project Archives view. To remove Project Archives explorer now, .packages files has to be deleted. This approach is not much user friendly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13405) Deploying a RAR with JAR inside fails using remote systems via SSH

by Chris Roberts (JIRA)

Chris Roberts created JBIDE-13405: ------------------------------------- Summary: Deploying a RAR with JAR inside fails using remote systems via SSH Key: JBIDE-13405 URL: https://issues.jboss.org/browse/JBIDE-13405 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 4.0.0.Final Environment: JBoss AS 7.1.1 Final, Eclipse Juno SR1, JBoss Tools 4.0.0 Final Reporter: Chris Roberts Assignee: Rob Stryker Exploding dependant jars seems to have issues for rars. I didn't work out if this is a problem in JBoss Tools or RSE. I suspect a little of both. It seems looking at the source that only the 'Local' RSE adapter correctly explodes deployments? 1) Create a maven project, set the packaging to rar 2) Create a second maven project, set the packaging to jar 3) Include the jar as a maven compile dependency of the rar 4) Import both into eclipse 5) Deploy to a remote (JBoss AS) server via RSE SSH/dstore/FTP fails It seems the JBoss Server Adapter (I think) creates the directory: xxxxx-1.0.rar/xxxxx-1.0.jar/ on deployment. It then requests upload for the jar over the top of the directory which fails. With FTP this looks like: CD xxxxx-1.0.rar/ MKD xxxxx-1.0.jar STOR xxxxx-1.0.jar <fails because directory exists> This is my first bug opened on JBoss/eclipse, so please point me on if you think this should be opened on RSE, but I think looking at the source it belongs here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13213) Simple adding/removing Project Archives capabilities into project

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13213?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13213: ------------------------------------- I'm not able to replicate "the node being present but the menu not showing". There are occasions where I can replicate no node showing. I am running 100% on clean workspaces every time. I have determined this is bc the view refreshes after the nature is changed, but does not refresh after archives is enabled. A fix for this would be to place the registration of the archives before the addition of the nature. But I am 100% unable to replicate your issue of a node being present but with no menu available. > Simple adding/removing Project Archives capabilities into project > ----------------------------------------------------------------- > > Key: JBIDE-13213 > URL: https://issues.jboss.org/browse/JBIDE-13213 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Reporter: Vlado Pakan > Assignee: Rob Stryker > Fix For: 4.0.x > > > It would be useful if we have "Configure -> Add/Remove Project Archive support" option. This option would add/remove Project Archive explorer into project in Project Explorer. Now, Project Archive explorer is visible only after creation of archive with Project Archives view. To remove Project Archives explorer now, .packages files has to be deleted. This approach is not much user friendly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13382) 'Server Behaviour' title in Server Editor should use American spelling

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13382?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-13382. --------------------------------- Resolution: Done pushed to master and also externalized the string. double trouble. ;) > 'Server Behaviour' title in Server Editor should use American spelling > ---------------------------------------------------------------------- > > Key: JBIDE-13382 > URL: https://issues.jboss.org/browse/JBIDE-13382 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Reporter: Michelle Murray > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.1.0.Alpha1 > > > One of the section titles on the Overview page of the Server Editor is misspelled: Server Behavi*our* should be Server Behavi*or* > American spellings should be followed, as you have with Application Reload Behavi*or* on the same page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13398) Document AS adapter main architecture

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13398?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13398: -------------------------------- Attachment: launch a server.png > Document AS adapter main architecture > ------------------------------------- > > Key: JBIDE-13398 > URL: https://issues.jboss.org/browse/JBIDE-13398 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: JBossAS/Servers > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Attachments: astools api.gliffy, astools api.png, launch a server.gliffy, launch a server.png, New Server Workflow.gliffy, New Server Workflow.png, runtime workflow.gliffy, runtime workflow.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2013