[JBoss-dev] CVS update: manual/src/xdocs/howto howtovisualagedebug.xml
User: schaefera Date: 01/09/13 00:39:15 Modified:src/xdocs/howto howtovisualagedebug.xml Log: Adjustment because JMXAdaptor was deleted. Revision ChangesPath 1.5 +0 -1 manual/src/xdocs/howto/howtovisualagedebug.xml Index: howtovisualagedebug.xml === RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtovisualagedebug.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- howtovisualagedebug.xml 2001/09/12 02:10:22 1.4 +++ howtovisualagedebug.xml 2001/09/13 07:39:15 1.5 @@ -269,7 +269,6 @@ /listitem listitem paraFor classnameorg.jboss.jmx.connector.rmi.RMIConnectorImpl/classname, -classnameorg.jboss.jmx.JMXAdaptorImpl/classname, classnameorg.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker/classname, classnameorg.jbossmq.distributed.server.ConnectionReceiverRMIImpl/classname and classnameorg.jbossmq.distributed.server.DistributedJMSServerRMIImpl/classname, manually generate RMI stub/skeleton using VAJ's built-in RMI tool (Right click on the class and select Tools -- Generate RMI/JDK 1.2 -- stubs/skeleton). You might need to temporarily move java.transaction.* into the jboss project for the rmic compiler to function without errors for JRMPContainerInvoker or directly import the RMI stub from the binary jboss.jar (org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker_Stub.class). /para ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/xdocs/howto howtovisualagedebug.xml
User: schaefera Date: 01/09/11 19:10:22 Modified:src/xdocs/howto howtovisualagedebug.xml Log: Adjusted files because of the repackaging of the JMX Connector and Adaptors. Also the connector and adaptor service files (*.jsr) are separated into 3 different files because it is neccessary to allow the administrator to select which one to use (security, performance etc.). Now the admin can add or remove the service files as the need arise. Revision ChangesPath 1.4 +1 -1 manual/src/xdocs/howto/howtovisualagedebug.xml Index: howtovisualagedebug.xml === RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtovisualagedebug.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- howtovisualagedebug.xml 2001/09/05 08:37:55 1.3 +++ howtovisualagedebug.xml 2001/09/12 02:10:22 1.4 @@ -268,7 +268,7 @@ /orderedlist /listitem listitem - paraFor classnameorg.jboss.jmx.server.RMIConnectorImpl/classname, + paraFor classnameorg.jboss.jmx.connector.rmi.RMIConnectorImpl/classname, classnameorg.jboss.jmx.JMXAdaptorImpl/classname, classnameorg.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker/classname, classnameorg.jbossmq.distributed.server.ConnectionReceiverRMIImpl/classname and classnameorg.jbossmq.distributed.server.DistributedJMSServerRMIImpl/classname, manually generate RMI stub/skeleton using VAJ's built-in RMI tool (Right click on the class and select Tools -- Generate RMI/JDK 1.2 -- stubs/skeleton). You might need to temporarily move java.transaction.* into the jboss project for the rmic compiler to function without errors for JRMPContainerInvoker or directly import the RMI stub from the binary jboss.jar (org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker_Stub.class). ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/xdocs/howto howtovisualagedebug.xml
User: gropi Date: 01/09/05 01:37:55 Modified:src/xdocs/howto howtovisualagedebug.xml Log: broken links fixed. Revision ChangesPath 1.3 +2 -2 manual/src/xdocs/howto/howtovisualagedebug.xml Index: howtovisualagedebug.xml === RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtovisualagedebug.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- howtovisualagedebug.xml 2001/09/02 14:04:28 1.2 +++ howtovisualagedebug.xml 2001/09/05 08:37:55 1.3 @@ -68,9 +68,9 @@ listitem paraAll jBoss source (src subdirectory). /para - paraSource of org.jnp.server (both *.class and *.java files) from ulink url=/doco_files/vaj-jnpserver222.ziphere/ulink. + paraSource of org.jnp.server (both *.class and *.java files) from the ulink url=/doco_files/vaj-jnpserver222.jarvaj-jnpserver222.jar/ulink archive found in the files area on the documentation page on www.jboss.org. /para - paraSource of org.jbossmq.* from ulink url=/doco_files/vaj-jbossmq222.ziphere/ulink./para + paraSource of org.jbossmq.* from the ulink url=/doco_files/vaj-jbossmq222.jarvaj-jbossmq222.jar/ulink archive found in the files area on the documentation page on www.jboss.org./para paraorg.jboss.security.SecurityAssociation source from CVS (version 1.5, which can be found ulink url=http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/jboss/src/main/org/jboss/security/SecurityAssociation.java?rev=1.5amp;content-type=text/vnd.viewcvs-markup;here)/ulink/para paraorg.jboss.naming.NamingService from CVS (version 1.9, which can be found ulink url=http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/~checkout~/jboss/jboss/src/main/org/jboss/naming/NamingService.java?rev=1.9amp;content-type=text/x-java;here)/ulink/para ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/xdocs/howto howtovisualagedebug.xml
User: gropi Date: 01/09/02 07:04:28 Modified:src/xdocs/howto howtovisualagedebug.xml Log: Update by Craig Doremus and Chiew Kwooi Lee. Now there are two new files that simplify VAJ integration. Additional information about Tomcat. Revision ChangesPath 1.2 +374 -353 manual/src/xdocs/howto/howtovisualagedebug.xml Index: howtovisualagedebug.xml === RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtovisualagedebug.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- howtovisualagedebug.xml 2001/08/29 09:19:37 1.1 +++ howtovisualagedebug.xml 2001/09/02 14:04:28 1.2 @@ -1,353 +1,374 @@ -!-- DOCTYPE section SYSTEM D:\cvsroot\manual\src\docs\docbookx\docbookx.dtd -- -section id=vajdebug - title -How to Run and Debug EJBs using jBoss 2.2.2 inside of -Visual Age for Java version 3.5 (patch 2) -/title - para -Author: -author - firstnameCraig/firstname - surnameDoremus/surname - /author - email[EMAIL PROTECTED]/email - /para - paraImporting jBoss into Visual Age for Java (VAJ) allows you to develop and -debug EJBs using the latest Enterprise Java Beans standard (version 1.1 and Message Driven EJBs). -The Enterprise version of Visual Age has built-in EJB debugging, but that -edition of the IDE only supports version 1.0 of the EJB spec. Currently, Visual Age only -supports JDK 1.2.2. -/para - para -We created a jBoss Test Environment by manually importing jBoss source -into Visual Age for Java. This import also -involved a few code hacks to remove JDK 1.3 -code, to change the paths to configiration files and some - modification of paths inside of configuration files. -/para - para -Our jBoss import does not include an integrated -ulink url=http://jakarta.apache.org/tomcat/index.html;Jakarta-Tomcat/ulink servlet engine. -IBM provides a Test Environment for Tomcat version 3.1 on their web site (see below) -that allows debugging of JSP and servlets inside of VAJ. Both Tomcat -and jBoss can be run inside of VAJ to provide the ability to debug EJBs -called by servlets. -/para - section id=vajdebug-requirements - titleRequirements/title - itemizedlist - listitem - paraVisual Age for Java Professional or Enterprise Edition Version 3.5 with patch 2 installed. Version 3.5.3 has recently been released, but there are some RMI bugs in it so we can't recommend using it at this time./para - /listitem - listitem - paraJBoss-2.2.2.zip downloaded (NOT the one with integrated Tomcat) ulink url=http://prdownloads.sourceforge.net/jboss/JBoss-2.2.2.zip;Download it here/ulink - /para - /listitem - /itemizedlist - /section - !-- end of vajdebug-requirements section -- - !-- MANUAL IMPORT SECTION START -- - section id=vajdebug-manualimport - titleManually importing jBoss 2.2.2 source code into Visual Age/title - orderedlist - listitem - paraUnzip JBoss-2.2.2.zip into a temporary directory./para - /listitem - listitem - paraCreate a jBoss project in VAJ. If jBoss 2.0 is already installed, version it and delete all files and related projects before proceeding with the jBoss 2.2.2 install. - /para - /listitem - listitem - paraImport source, jar and class files into VAJ from the temporary directory including:/para - orderedlist - listitem - paraAll jBoss source (src subdirectory). - /para - paraSource from org.jnp.server from CVS (ver 1.2). Change org.jboss.naming.NamingService in the source distribution to CVS ver 1.9 to maintain compatibility with this class./para - paraSource for org.jbossmq.* from CVS/para - /listitem - listitem - paraIn lib or lib/ext directory import the class files: /para - programlisting - All files from minerva-1_0b3.jar - All files