Re: [JBoss-dev] CVS tagging
Rel_3_0_0_7. The cvs naming is somewhere in the developer section of the site. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Peter Antman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 05, 2002 8:06 AM Subject: [JBoss-dev] CVS tagging > Hi, > I made a patch to the Branch_3_0, but its a while since I did this and I > can't remember which stuff to use for tagging: should I step up > JBoss_3_0_0_8 or Rel_3_0_0_7, which is the tags that seems relevant? > > //Peter > -- > > Peter Antman Chief Systems Architect, Business Development > Technology in Media, Box 34105 100 26 Stockholm > WWW: http://www.tim.se WWW: http://www.backsource.org > Email: [EMAIL PROTECTED] > Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 > > > > > --- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(HEAD Matrix2) Testsuite Results: 7-September-2002
Number of tests run: 896 Successful tests: 872 Errors:20 Failures: 4 [time of test: 7 September 2002 2:36 GMT] [java.version: 1.3.1_03] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1_03-b03] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-34] Useful resources: - http://lubega.com/testarchive/sun_jdk131_03 for the junit report of this test. - http://lubega.com/testarchive/sun_jdk131_03/logs/ for the logs for this test. - http://lubega.com for general test information. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! Oh dear - still got some errors! Thanks for all your effort - we really do love you! --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-605878 ] Unable to start JBoss Server in ProgFile
Bugs item #605878, was opened at 2002-09-06 21:00 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=605878&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Archimedes Trajano (trajano) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to start JBoss Server in ProgFile Initial Comment: I can't seem to start the JBoss Server from C:\Program Files\JBoss but no problems when starting from C:\JBoss. I assume its because of the space in the path name. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=605878&group_id=22866 --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] MBeanServer and EAR-Scoping
Through RMIAdaptor. Object obj = ctx.lookup("jmx:local:rmi"); RMIAdaptor adaptor = ((RMIAdaptor)obj); RemoteMBeanServer connector = new RMIConnectorImpl(adaptor); ... blabla.invoke(...); When replacing the problematic parameter by byte[] and doing the serialization "by hand" in the ear and on the client everything works. The strage thing is: When the access fails, there is no log message on the server console. --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] MBeanServer and EAR-Scoping
Just to be a little more definite, how are you communicating with the jmx server? I think that is the part doing the deserialization... (and on the other end the serialization) thanks david jencks On 2002.09.06 15:55:46 -0400 Michael Bartmann wrote: > Hi everybody, > > I use JMX to manage an MBean inside an EAR-scope. > It has methods with arguments and return values > of a class which is only known inside the EAR-Scope > (and of course known to the client connecting to the MBeanServer). > > If objects of those "ear-private" classes are a return value > (server -> client) serialization works. This is no surprise, > each object knows where it came from. > > If the client puts parameters of those "ear-private" in the method > (client -> server) the server has to de-serialize and fails. > Even this is no surprise. > > But: could you think about allowing the JMX-server to access the > ears repository? > > Regards, > Michael Bartmann > > PS.: tested under Branch_3_2. > > > > --- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] MBeanServer and EAR-Scoping
Hi everybody, I use JMX to manage an MBean inside an EAR-scope. It has methods with arguments and return values of a class which is only known inside the EAR-Scope (and of course known to the client connecting to the MBeanServer). If objects of those "ear-private" classes are a return value (server -> client) serialization works. This is no surprise, each object knows where it came from. If the client puts parameters of those "ear-private" in the method (client -> server) the server has to de-serialize and fails. Even this is no surprise. But: could you think about allowing the JMX-server to access the ears repository? Regards, Michael Bartmann PS.: tested under Branch_3_2. --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss.net now supports Axis RC1
Title: Nachricht One of the most requested features is now in "head" (along with some bugfixes and some nice deployment structure changes that remove the dependency of AxisService to the WebContainer). Axis will go 1.0 in a week or so which should be trivial to incorporate then. Are there any special backport requirements? Otherwise, I would go reintegrating it into 3.2, then. Best, CGJ ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/
[JBoss-dev] [ jboss-Bugs-593916 ] Redeployment does not work
Bugs item #593916, was opened at 2002-08-12 08:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=593916&group_id=22866 Category: JBossSOAP Group: v3.0 Rabbit Hole >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Dr. Christoph Georg Jung (cgjung) Assigned to: Dr. Christoph Georg Jung (cgjung) Summary: Redeployment does not work Initial Comment: Some people get "cannot redeploy existing module" messages. -- >Comment By: Dr. Christoph Georg Jung (cgjung) Date: 2002-09-06 18:42 Message: Logged In: YES user_id=175199 Found it. It was the internal deploymentmap of the AxisService that was not correctly maintained in destroyService(). It´s now done in head. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=593916&group_id=22866 --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-581847 ] <ejb-link> doesn't work properly
Bugs item #581847, was opened at 2002-07-15 21:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=581847&group_id=22866 Category: JBossSOAP Group: v3.0 Rabbit Hole >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Mario Däpp (mdaepp) Assigned to: Dr. Christoph Georg Jung (cgjung) Summary:doesn't work properly Initial Comment: System Info: 21:12:20,813 INFO [Server] JBoss Release: JBoss-3.0.0 CVSTag=JBoss_3_0_0 21:12:29,812 INFO [ServerInfo] Java version: 1.4.0,Sun Microsystems Inc. 21:12:29,813 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.4.0-b92,Sun Microsystems Inc. 21:12:29,814 INFO [ServerInfo] OS-System: SunOS 5.8,sparc This is JBoss with Tomcat. I'm using a slightly altered version of the original jboss-net.sar (replaced AxisService to fix the /axis/* context root problem with Catalina) in in web-service.xml doesn't work propertly. If I enter the here (that's what I think belongs here), then it doesn't work (NamingException on the client side saying that UppercaseService is not bound). If I enter the JNDI name, it works. I expect this bug to be reproducible if the JNDI name in jboss.net.sample.hello.ejb.HelloBean is changed to something else than Hello. Excerpt from web-service.xml: ... ejb/UppercaseService local/oois/demo/UppercaseService ... Excerpt from UppercaseServiceBean: /** * @ejb:bean name="UppercaseService" type="Stateless" display-name="UppercaseServiceEJB" view-type="local" local-jndi-name="local/oois/demo/UppercaseService" * @ejb:interface generate="local" * @ejb:util generate="logical" */ public class UppercaseServiceBean implements SessionBean { ... -- >Comment By: Dr. Christoph Georg Jung (cgjung) Date: 2002-09-06 18:41 Message: Logged In: YES user_id=175199 feature is now marked deprecated and will vanish with next release. -- Comment By: Mario Däpp (mdaepp) Date: 2002-07-17 13:21 Message: Logged In: YES user_id=136508 Hi Christoph, basically, you're right. However, I like the idea of in web-service.xml. If I was able to specify in , then there would be no dependency between jboss.xml and web-service.xml in terms of the JNDI name (and one file change down when somebody needs to change the JNDI name for some reason ;-)). Don't know whether that argument is strong enough though... I'll check whether the same bug is present for in web.xml as well, because AFAIK the semantics should be no different from ejb-jar.xml. Mario -- Comment By: Dr. Christoph Georg Jung (cgjung) Date: 2002-07-17 12:23 Message: Logged In: YES user_id=175199 Hi, I have to admit that I "implemented" the feature in the web-service.xml by simple copying&pasting from the WebContainer code. Hence it follows the same semantics than in web- application.xml (which could be different from in ejb- jar.xml, me totally ignorant here) In the meantime, I have come to the conclusion that the feature doesn´t buy you anything in your web-service implementation. Unlike in a web-app: In your web-app, you will implement a servlet, hence java code, that runs against the link names instead of the mapped and changeable jndi names, right? In your web-service there is no additional Java code involved that hardcodes the JNDIname. Hence I would suggest that you use the fully-qualified jndiname to your bean directly in the EJBProvider service definition and leave the ejb-refs out. It doesnt matter if you have to change the ejb-ref or the jndiName entry in the web-service.xml, right? So will vanish in one of the next versions of jboss.net, unless you have another strong argument for it (security? I really dunno). CGJ -- Comment By: Dr. Christoph Georg Jung (cgjung) Date: 2002-07-17 12:22 Message: Logged In: YES user_id=175199 Hi, I have to admit that I "implemented" the feature in the web-service.xml by simple copying&pasting from the WebContainer code. Hence it follows the same semantics than in web- application.xml (which could be different from in ejb- jar.xml, me totally ignorant here) In the meantime, I have come to the conclusion that the feature doesn´t buy you anything in your web-service implementation. Unlike in a web-app: In your web-app, you will implement a servlet, hence java code, that runs against the link names instead of the mapped and changeable jndi names, right? In your web-service there is no additional Java code involved that hardcodes the JNDIname. Hence I would suggest that you use the fully-qualified jndiname to your bean directly in the EJBProvider service definition and leave the ejb-refs out. It doesnt matter if you have to change
[JBoss-dev] [ jboss-Feature Requests-605599 ] Timed delivery of JMS message
Feature Requests item #605599, was opened at 2002-09-06 10:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376688&aid=605599&group_id=22866 Category: JBossMQ Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Vikas Chawla (chawla1975) Assigned to: Nobody/Anonymous (nobody) Summary: Timed delivery of JMS message Initial Comment: Hi, It would be good to have a timed delivery of the JMS message to a consumer. The timed delivery of the message can be configurable at the time of pubishing of the message. In addition to this it would be helpful to have configurable number of retries & time interval between retries of the JMS message in case of message delivery failure. These two are very useful features, not yet part of the JMS specs but have been implemented by some J2EE vendors like Weblogic. Thanks, Vikas -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376688&aid=605599&group_id=22866 --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] ¥Nµoemail¼s§i¡A¸Õ¸Õ¬Ý«Â¤O¡C
¥Nµoemail¼s§i Åý±z¥H·¥§Cªº¦¨¥»¡A ÁA¸Ñ¥D°Ê¦¡¦æ¾Pªº«Â¤O¡C ¦]¬°ÀW¼e¦³¦h¡A Ä@·NÀ°§U¦³·NÄ@¶}©Ý¥«³õªºªB¤Í¡A ¸Õ¸Õ¬Ý®ÄªG¡C ¦WÃB¤T¦ì¡]¶Ç¾P¤º®e¥²¶·µ´¹ï¦Xªk¡^¡C ¹q¸Ü¡G02-27492314 --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-588511 ] NoClassDefFoundError class searches
Bugs item #588511, was opened at 2002-07-30 13:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=588511&group_id=22866 Category: JBossServer Group: None Status: Open Resolution: None Priority: 5 Submitted By: Gerald Benischke (beny23) Assigned to: Nobody/Anonymous (nobody) Summary: NoClassDefFoundError class searches Initial Comment: While playing around with JBoss3.0.1RC and catalina 4.0.4 (I downloaded the bundle) and playing with struts 1.1beta I came across the following problem: when loading a form-bean, the JBoss classloaders would not find the ActionForm base class and throw a java.lang.NoClassDefFoundError (the struts library Jars are in WEB-INF/lib). I investigated the problem and fixed (?) it by modifying: jmx/src/main/org/jboss/mx/loading BasicLoaderRepository.java HeirarchicalLoaderRepository.java HeirarchicalLoaderRepository2.java UnifiedLoaderRepository.java UnifiedLoaderRepository2.java to add catch blocks for NoClassDefFoundError after all catch blocks for ClassNotFoundException. this solved my problem as the dynamic classloader is not interrupted by NoClassDefFoundErrors anymore. any thoughts? -- Comment By: Elton Plath (eplath) Date: 2002-09-06 16:01 Message: Logged In: YES user_id=145731 I am also experiencing this problem. Is anyone looking at a fix for this? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=588511&group_id=22866 --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-605539 ] XADatasourceLoader stopService() Bug
Bugs item #605539, was opened at 2002-09-06 14:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=605539&group_id=22866 Category: None Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jens Viebig (jsurf) Assigned to: Nobody/Anonymous (nobody) Summary: XADatasourceLoader stopService() Bug Initial Comment: I found a bug in XADatasourceLoader of JBoss 2.4.8: The connection pool is not correctly unbound when using the stop()-Method of the MBean: It uses NonSerializableFactory for binding the Datasource to JNDI but not for unbind: private void bind(Context ctx, String name, Object val) throws NamingException { // Ah ! Session isn't serializable, so we use a helper class NonSerializableFactory.bind(name, val); ... } Here is the bug: public void stopService() { // Unbind from JNDI try { String name = getSource().getPoolName(); new InitialContext().unbind("java:/"+name); ... } should be: public void stopService() { // Unbind from JNDI try { String name = getSource().getPoolName(); new InitialContext().unbind("java:/"+name); NonSerializableFactory.unbind("java:/"+name); ... } so that it is removed from the internal map of NonSerializableFactory -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=605539&group_id=22866 --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Mp3 lere..
3mp3.net haber listesinden: Yerli ve yabanci albümler tamamen yenilendi. Artik istediginiz mp3 leri zip olarakta sitemizden indirebilirsiniz. Dosya indirme hizi yaklasik 2.5 kat artti. Boylece kisa zamanda tam albümlere sahip olacaksiniz. Istekleriniz dogrultusunda Top25 yenilendi. Beklemeye gerek yok. Sitemizde gezintiye baslayabilirsiniz. http://www.3mp3.net +,~wzf¢+,¦ì¢·o# Ôâçh~ØZ¶Æ¦z]qée¦'xgjw° êÞ~ÅDA!¶Úlÿü0Â)éâqÊ&þ¶¬¦»(º·~à{ZÞ}Ê{[ìßt%º,±×¯zZ)éí¨¥x%ËIn,uëÞfz{eËl²«qç讧zØm¶?þX¬¶Ë(º·~àzwþX¬¶ÏåËbú?º,±×¯zZ)éí
[JBoss-dev] Manual JBoss(HEAD Matrix2) Testsuite Results: 6-September-2002
Number of tests run: 899 Successful tests: 849 Errors:43 Failures: 7 [time of test: 6 September 2002 10:1 GMT] [java.version: 1.4.0_00] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.0_00-b05] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: SunOS] [os.arch: sparc] [os.version: 5.9] NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! Oh dear - still got some errors! Thanks for all your effort - we really do love you! --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-605446 ] run.sh incompatibilty with bash 2.05.0
Bugs item #605446, was opened at 2002-09-06 08:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=605446&group_id=22866 Category: Build System Group: CVS HEAD Status: Open Resolution: None Priority: 5 Submitted By: Holger Baxmann (hbaxmann) Assigned to: Jason Dillon (user57) Summary: run.sh incompatibilty with bash 2.05.0 Initial Comment: in jboss-4.0.0alpha : $ bash --version GNU bash, version 2.05.0(1)-release (sparc-sun- solaris2.9) $ run.sh give a: run.sh: test: unknown operator bin/run.conf because of the following lines: if [ -e $RUN_CONF -a -r $RUN_CONF ]; then . $RUN_CONF fi -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=605446&group_id=22866 --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development