date:20070111

[
https://issues.apache.org/activemq/browse/SM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Guillaume Nodet updated SM-811:
---

Patch Info: [Patch Available]

servicemix-jms does not set SoapAction property for SOAP jms messages
-

Key: SM-811
URL: https://issues.apache.org/activemq/browse/SM-811
Project: ServiceMix
Issue Type: Bug
Components: servicemix-jms
Affects Versions: 3.0, 3.0.1, 3.1
Environment: Tested with Tibco EMS as jms server and Tibco Business
works as system providing the service. The error should also occur with
ActiveMQ.
Reporter: Christian Schneider
Priority: Critical
Attachments: servicemix-jms-sm-811.patch,
servicemix-jsr181-sm-811.patch

When tibco is the client all works well but when tibco implements the service
it rejects the soap/jms message as it wants the SoapAction jms property to be
set.
I have added a dummy SoapAction in StandardProviderProcessor:
...
MessageProducer producer = session.createProducer(destination);
TextMessage msg = session.createTextMessage();
NormalizedMessage nm = exchange.getMessage(in);
fromNMS(nm, msg);
String soapAction = default;
msg.setStringProperty(SoapAction, soapAction);
...
I was able to do a complete request/reply with tibco in this way. Of course
the default SoapAction will only help if my service has only one method.
From what I see in Tibco the SoapAction should at least contain the method
name of the service being called.
The servicemix-jms component should by default set this property to make it
more compatible with other soap/jms compatible systems.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Closed: (SM-620) Issues with ServiceMix startup shell script on Solaris


 [ 
https://issues.apache.org/activemq/browse/SM-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet closed SM-620.
--

Resolution: Duplicate

 Issues with ServiceMix startup shell script on Solaris
 --

 Key: SM-620
 URL: https://issues.apache.org/activemq/browse/SM-620
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-assembly
Affects Versions: 3.0
Reporter: Bruce Snyder

 Problems with Solaris:
 1. The following command does not work in Solaris: 
 {code}
 export JAVA_MIN_MEM=64M 
 {code}
 Solution:
 {code}
 if [ x$JAVA_MIN_MEM = x ]; then
 JAVA_MIN_MEM=64M
 export JAVA_MIN_MEM
 fi
 if [ x$JAVA_MAX_MEM = x ]; then
 JAVA_MAX_MEM=256M
 export JAVA_MAX_MEM
 fi
 {code}
 2. Also, in locateHome() 
 if [ ! -e  ]
 does not work for Solaris (not supported option for test). Instead, the -e 
 should be -d 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (SM-812) [patch] JAAS Login for Batch Processes


[ 
https://issues.apache.org/activemq/browse/SM-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37874
 ] 

Guillaume Nodet commented on SM-812:


Cool :)

Just a question: did you handle the case where the EJB itself is secured in the 
J2EE server ? If so, how ?
I think this component only solves the case where the jsr181 endpoint is 
secured by servicemix, right ?

 [patch] JAAS Login for Batch Processes 
 ---

 Key: SM-812
 URL: https://issues.apache.org/activemq/browse/SM-812
 Project: ServiceMix
  Issue Type: New Feature
  Components: servicemix-components
Reporter: Kristian Koehler
 Attachments: patch.zip, patch.zip


 Hi
 the attached patch includes a PassThroughJAASLoginComponent which forwards a
 Message through the NMR and performs a JAAS login. The JAAS Subject is added 
 to
 the message properties (javax.jbi.security.subject).
 This component can be used if you have a batch process which should call an 
 JAAS
 secured component (for example a EJB service called with JSR-181). The
 attached StaticValueCallbackHandler for example enables you to configure 
 static
 login information.
 Sample Config:
 --- 8 (start) ---
 ...
 sm:activationSpec componentName=login service=foo:login
  sm:component
   bean 
 class=org.apache.servicemix.components.security.PassThroughJAASLoginComponent
   property name=loginContext ref=loginContext /
   /bean
  /sm:component
 /sm:activationSpec
 ...
 bean id=loginContext
   class=javax.security.auth.login.LoginContext
   constructor-arg
   valueservicemix-domain/value
   /constructor-arg
   constructor-arg
   ref local=callbackHandler /
   /constructor-arg
 /bean
 bean id=callbackHandler
   
 class=org.apache.servicemix.components.security.StaticValueCallbackHandler
   property name=name value=first /
   property name=password value=secret /
 /bean
 ...
 --- 8 (end) ---
 After the PassThroughJAASLoginComponent is invoked and the login could be
 performed you can call JAAS secured endpoints.
 The patch includes test cases for the component.
 Kristian

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (SM-813) [patch] Unique Column Names for JdbcComponent

2007-01-11 Thread Kristian Koehler (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Koehler updated SM-813:


Attachment: patch.txt

 [patch] Unique Column Names for JdbcComponent
 -

 Key: SM-813
 URL: https://issues.apache.org/activemq/browse/SM-813
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-components
Reporter: Kristian Koehler
 Attachments: patch.txt


 HI 
 using the JdbcComponent with a SQL Statement returing a ResultSet with two or 
 more equal columnnames results in an invalid XML document.
 Example:
 SQL Statement
 SELECT * FROM TABLE1, TABLE2 WHERE TABLE1.ID = TABLE2.ID
 Resulting XML:
 --- 8 ---
 sqlResults
   resultSet
row id=1 id=1/
 ...
 --- 8 ---
 The column Names in this example are not unique.
 The attached patch solves this issue.
 The resulting document would look like this:
 --- 8 ---
 sqlResults
   resultSet
row id=1 id_1=1/
 ...
 --- 8 ---
 Test Case available.
 Kristian

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (SM-812) [patch] JAAS Login for Batch Processes


[ 
https://issues.apache.org/activemq/browse/SM-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37882
 ] 

Guillaume Nodet commented on SM-812:


Do you use  ST flow, acegi ?
What happen if you dont set the subject property on the exchange, 
but only perfom the login call in the component ?
I don't really understand who / how / when the subject is given to the
EJB container 

 [patch] JAAS Login for Batch Processes 
 ---

 Key: SM-812
 URL: https://issues.apache.org/activemq/browse/SM-812
 Project: ServiceMix
  Issue Type: New Feature
  Components: servicemix-components
Reporter: Kristian Koehler
 Attachments: patch.zip, patch.zip


 Hi
 the attached patch includes a PassThroughJAASLoginComponent which forwards a
 Message through the NMR and performs a JAAS login. The JAAS Subject is added 
 to
 the message properties (javax.jbi.security.subject).
 This component can be used if you have a batch process which should call an 
 JAAS
 secured component (for example a EJB service called with JSR-181). The
 attached StaticValueCallbackHandler for example enables you to configure 
 static
 login information.
 Sample Config:
 --- 8 (start) ---
 ...
 sm:activationSpec componentName=login service=foo:login
  sm:component
   bean 
 class=org.apache.servicemix.components.security.PassThroughJAASLoginComponent
   property name=loginContext ref=loginContext /
   /bean
  /sm:component
 /sm:activationSpec
 ...
 bean id=loginContext
   class=javax.security.auth.login.LoginContext
   constructor-arg
   valueservicemix-domain/value
   /constructor-arg
   constructor-arg
   ref local=callbackHandler /
   /constructor-arg
 /bean
 bean id=callbackHandler
   
 class=org.apache.servicemix.components.security.StaticValueCallbackHandler
   property name=name value=first /
   property name=password value=secret /
 /bean
 ...
 --- 8 (end) ---
 After the PassThroughJAASLoginComponent is invoked and the login could be
 performed you can call JAAS secured endpoints.
 The patch includes test cases for the component.
 Kristian

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (SM-808) Servicemix jboss deployer

2007-01-11 Thread Eric Dofonsou (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Dofonsou updated SM-808:
-

Attachment: SourceTransformer.diff

 Servicemix jboss deployer
 -

 Key: SM-808
 URL: https://issues.apache.org/activemq/browse/SM-808
 Project: ServiceMix
  Issue Type: Bug
 Environment: JBoss 4.0.5 GA
Reporter: Eric Dofonsou
 Fix For: 3.1

 Attachments: SourceTransformer.diff


 The servicemix-jboss-deployer-3.1-SNAPSHOT.sar file generated by the jboss 
 depolyer  does not include the xalan-2.7.0.jar file in the lib.  This is 
 required by servicemix and is not included in jboss.
 Adding the jar to the .sar file fixed the issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (SM-808) Remove Xalan dependency in SourceTransformer (was: Servicemix jboss deployer)


 [ 
https://issues.apache.org/activemq/browse/SM-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved SM-808.


Resolution: Fixed
  Assignee: Guillaume Nodet

Author: gnodet
Date: Thu Jan 11 07:00:30 2007
New Revision: 495245

URL: http://svn.apache.org/viewvc?view=revrev=495245
Log:
SM-808: Remove Xalan dependency in SourceTransformer
Thanks to Eric Dofonsu !

Modified:
   
incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/jaxp/SourceTransformer.java
   
incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/jaxp/StAXSourceTransformer.java
   
incubator/servicemix/trunk/core/servicemix-core/src/test/java/org/apache/servicemix/jbi/jaxp/StaxSourceTest.java


I have slightly modified your patch to keep the xalan optimization if available 
on the classpath.
Thanks !

 Remove Xalan dependency in SourceTransformer (was: Servicemix jboss deployer)
 -

 Key: SM-808
 URL: https://issues.apache.org/activemq/browse/SM-808
 Project: ServiceMix
  Issue Type: Bug
 Environment: JBoss 4.0.5 GA
Reporter: Eric Dofonsou
 Assigned To: Guillaume Nodet
 Fix For: 3.1

 Attachments: SourceTransformer.diff


 The servicemix-jboss-deployer-3.1-SNAPSHOT.sar file generated by the jboss 
 depolyer  does not include the xalan-2.7.0.jar file in the lib.  This is 
 required by servicemix and is not included in jboss.
 Adding the jar to the .sar file fixed the issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (SM-815) Externalize values from main configuration file into a single property file

Externalize values  from main configuration file into a single property file


 Key: SM-815
 URL: https://issues.apache.org/activemq/browse/SM-815
 Project: ServiceMix
  Issue Type: Improvement
  Components: servicemix-assembly
Reporter: Guillaume Nodet
 Assigned To: Guillaume Nodet
 Fix For: 3.1




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (SM-815) Externalize values from main configuration file into a single property file


 [ 
https://issues.apache.org/activemq/browse/SM-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved SM-815.


Resolution: Fixed

Author: gnodet
Date: Thu Jan 11 08:05:55 2007
New Revision: 495271

URL: http://svn.apache.org/viewvc?view=revrev=495271
Log:
SM-815: Externalize values from main configuration file into a single property 
file

Added:
   
incubator/servicemix/trunk/distributions/apache-servicemix/src/main/release/conf/servicemix.properties
   (with props)
Modified:
   
incubator/servicemix/trunk/distributions/apache-servicemix/src/main/release/conf/jmx.xml
   
incubator/servicemix/trunk/distributions/apache-servicemix/src/main/release/conf/jndi.xml
   
incubator/servicemix/trunk/distributions/apache-servicemix/src/main/release/conf/servicemix.xml


 Externalize values  from main configuration file into a single property file
 

 Key: SM-815
 URL: https://issues.apache.org/activemq/browse/SM-815
 Project: ServiceMix
  Issue Type: Improvement
  Components: servicemix-assembly
Reporter: Guillaume Nodet
 Assigned To: Guillaume Nodet
 Fix For: 3.1




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (SM-813) [patch] Unique Column Names for JdbcComponent


 [ 
https://issues.apache.org/activemq/browse/SM-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved SM-813.


   Resolution: Fixed
Fix Version/s: 3.1
 Assignee: Guillaume Nodet

Author: gnodet
Date: Thu Jan 11 09:35:41 2007
New Revision: 495303

URL: http://svn.apache.org/viewvc?view=revrev=495303
Log:
SM-813: Unique Column Names for JdbcComponent
Patch provided by Kristian Koehler

Added:
   
incubator/servicemix/trunk/common/servicemix-components/src/test/java/org/apache/servicemix/components/jdbc/
   
incubator/servicemix/trunk/common/servicemix-components/src/test/java/org/apache/servicemix/components/jdbc/JdbcComponentUniqueNamesTest.java
   (with props)
Modified:
   
incubator/servicemix/trunk/common/servicemix-components/src/main/java/org/apache/servicemix/components/jdbc/JdbcComponent.java


 [patch] Unique Column Names for JdbcComponent
 -

 Key: SM-813
 URL: https://issues.apache.org/activemq/browse/SM-813
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-components
Reporter: Kristian Koehler
 Assigned To: Guillaume Nodet
 Fix For: 3.1

 Attachments: patch.txt


 HI 
 using the JdbcComponent with a SQL Statement returing a ResultSet with two or 
 more equal columnnames results in an invalid XML document.
 Example:
 SQL Statement
 SELECT * FROM TABLE1, TABLE2 WHERE TABLE1.ID = TABLE2.ID
 Resulting XML:
 --- 8 ---
 sqlResults
   resultSet
row id=1 id=1/
 ...
 --- 8 ---
 The column Names in this example are not unique.
 The attached patch solves this issue.
 The resulting document would look like this:
 --- 8 ---
 sqlResults
   resultSet
row id=1 id_1=1/
 ...
 --- 8 ---
 Test Case available.
 Kristian

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: log4j

2007-01-11 Thread Thomas TERMIN

So I implemted it. It works fine until now. I still have to do some
improvements on it but I guess I can provide it to you tomorrow.

Cheers,
Thomas

Thomas TERMIN wrote:
 I found it. ;-)
 
 I'm implementing at the moment the new service.
 
 Guillaume Nodet wrote:
 Forwarding to the dev list ...

 I think you may want to take a look at how the
 JdbcAuditor, DotViewService or StatisticsService
 are implemented.  They all inherit the
 o.a.s.jbi.management.BaseSystemService
 abstract class.  They come in different flavous wrt configuration however.
 I would recommend to look at the StatisticsService, which can be configured
 that way:

   sm:container ...
 sm:services
   sm:statistics .. /
 /sm:services
   /sm:container

 This way, the service is automatically registered in JMX and has its own
 lifecycle (which is tied to the container), so that you can stop / start
 the
 service from jmx.

 On 1/11/07, Thomas TERMIN [EMAIL PROTECTED] wrote:
 What I want to do is to implement a MBean which configure the log4j
 system periodicaly with a scheduler. But before I will look if there is
 a log4j.xml or log4j.properties in the conf directory if there is
 nothing in it then I assume that there is no log4j system and don't
 reconfigure log4j (I will give you a better explanation later ;-) ).

 The Problem what I have is to register a MBean in conf/servicemix.xml.
 How do I have to do this? I tried this with the spring MBeanExporter but
 it doesn't work for me.

 Cheers,
 Thomas

 Btw, if you don't mind, i'd rather have such discussion on
 servicemix-dev / servicemix-users ;-)
 No problem at all! If you open the thread...

 Cheers,
 Thomas

 Guillaume Nodet wrote:
 Did you implement something useful ?  Would you
 consider giving it back to ServiceMix ?

 On 10/20/06, Thomas TERMIN [EMAIL PROTECTED] wrote:
 Sorry I did not mean a servicemix component. I use allways the word
 component ;-) since I started working with servicemix. What you
 said is
 exactly what I meant. So I will have a look on it!

 Thanks,
 Thomas

 Guillaume Nodet wrote:
 I would rather use a ServiceMix service instead of
 a component, as this is more related to management /
 configuration than a component if I understand you
 correctly.  ... and use a timer to reload the log4j config.
 But iirc, log4j already has this feature, we just need to
 enable it.

 On 10/20/06, Thomas TERMIN [EMAIL PROTECTED] wrote:
 Hello Guillaume,

 We would need a log4j Component where you can change the debug
 level at
 runtime. I would implement a MBean which initialise the log4j
 system at
 startup and also have a scheduler which looks if the
 log4j.xml has
 changed and then reinitialise the log4j system.

 If I would provide you a patch would you accept this in
 servicemix?
 Cheers,
 Thomas Termin

[jira] Resolved: (SM-783) build fails under java 6


 [ 
https://issues.apache.org/activemq/browse/SM-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved SM-783.


   Resolution: Fixed
Fix Version/s: 3.1
 Assignee: Guillaume Nodet

Author: gnodet
Date: Thu Jan 11 12:23:43 2007
New Revision: 495362

URL: http://svn.apache.org/viewvc?view=revrev=495362
Log:
SM-783: build fails under Java6

Modified:
   incubator/servicemix/trunk/common/servicemix-components/pom.xml
   
incubator/servicemix/trunk/common/servicemix-components/src/main/java/org/apache/servicemix/components/groovy/GroovyComponent.java
   
incubator/servicemix/trunk/common/servicemix-components/src/main/java/org/apache/servicemix/components/script/ScriptComponent.java


 build fails under java 6
 

 Key: SM-783
 URL: https://issues.apache.org/activemq/browse/SM-783
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-components
Affects Versions: 3.0
 Environment: x86 linux - FC5, sun jdk 1.6.0, 
 apache-servicemix-3.0-incubating-src.tar.gz
Reporter: tim biernat
 Assigned To: Guillaume Nodet
Priority: Minor
 Fix For: 3.1


 mvn -Dmaven.test.skip=true -Dprofile=step2 install
 ...
 [INFO] [compiler:compile]
 Compiling 114 source files to 
 /home/tbiernat/work/servicemix/apache-servicemix-3.0-incubating/src/servicemix-components/target/classes
 [INFO] 
 
 [ERROR] BUILD FAILURE
 [INFO] 
 
 [INFO] Compilation failure
 /home/tbiernat/work/servicemix/apache-servicemix-3.0-incubating/src/servicemix-components/src/main/java/org/apache/servicemix/components/script/ScriptComponent.java:[210,36]
  cannot find symbol
 symbol  : method createNamespace()
 location: interface javax.script.ScriptEngine
 /home/tbiernat/work/servicemix/apache-servicemix-3.0-incubating/src/servicemix-components/src/main/java/org/apache/servicemix/components/script/ScriptComponent.java:[261,26]
  cannot find symbol
 symbol  : method eval(javax.script.Namespace)
 location: class javax.script.CompiledScript
 /home/tbiernat/work/servicemix/apache-servicemix-3.0-incubating/src/servicemix-components/src/main/java/org/apache/servicemix/components/script/ScriptComponent.java:[269,14]
  cannot find symbol
 symbol  : method eval(java.lang.String,javax.script.Namespace)
 location: interface javax.script.ScriptEngine 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

question about servicemix-jsr181 component...

2007-01-11 Thread eburgos


Hi,
I have a question regarding servicemix-jsr181 component. I want to know if
it has a thread pool or if I need to define several instances of it in order
to be able to attend simultaneous messages. 
If it has a threadpool, is that the default behavior for any servicemix
component?
-- 
View this message in context: 
http://www.nabble.com/question-about-servicemix-jsr181-component...-tf2961908s12049.html#a8286938
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.

Re: question about servicemix-jsr181 component...

2007-01-11 Thread Guillaume Nodet


The threading is the same as for servlets.
A single instance will server multiple concurrent requests.
If you need pooling, use spring pooling support when declaring
your pojo.

On 1/11/07, eburgos [EMAIL PROTECTED] wrote:


Hi,
I have a question regarding servicemix-jsr181 component. I want to know if
it has a thread pool or if I need to define several instances of it in order
to be able to attend simultaneous messages.
If it has a threadpool, is that the default behavior for any servicemix
component?
--
View this message in context: 
http://www.nabble.com/question-about-servicemix-jsr181-component...-tf2961908s12049.html#a8286938
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.





--
Cheers,
Guillaume Nodet

Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/

Re: Release ServiceMix 3.1

2007-01-11 Thread macdoor


+1.

I will test smx+geronimo


gnodet wrote:
 
 I think it's time to start the release process for 3.1.
 I have been working on the distribution a bit, but
 it needs more work to check that the samples all
 work well, etc ...
 So please test the release to ensure everything
 is working well, that all legal stuff is ok
 (need to check all jars included in the distribution),
 etc ...
 This is a hard work, so help is really welcome :-)
 
 -- 
 Cheers,
 Guillaume Nodet
 
 Architect, LogicBlaze (http://www.logicblaze.com/)
 Blog: http://gnodet.blogspot.com/
 
 

-- 
View this message in context: 
http://www.nabble.com/Release-ServiceMix-3.1-tf2962129s12049.html#a8288910
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.

[jira] Updated: (SM-816) useless include log framwork into jboss deployer

2007-01-11 Thread JIRA


 [ 
https://issues.apache.org/activemq/browse/SM-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grégoire A. updated SM-816:
---

Attachment: pom.diff

 useless include log framwork into jboss deployer
 

 Key: SM-816
 URL: https://issues.apache.org/activemq/browse/SM-816
 Project: ServiceMix
  Issue Type: Bug
Affects Versions: incubation
 Environment: linux, jdk5, jboss 4-0-5 GA
Reporter: Grégoire A.
 Fix For: 3.1

 Attachments: pom.diff

   Original Estimate: 15 minutes
  Remaining Estimate: 15 minutes

 Exception raise when commons-logging and log4j jar are included into sar 
 jboss deployer
 00:51:07,136 INFO  [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: 
 CVSTag=Branch_4_0 date=200610162339)] Started in 1m:58s:2ms
 00:51:22,446 ERROR [STDERR] log4j:ERROR A 
 org.jboss.logging.util.OnlyOnceErrorHandler object is not assignable to a 
 org.apache.log4j.spi.ErrorHandler variable.
 00:51:22,447 ERROR [STDERR] log4j:ERROR The class 
 org.apache.log4j.spi.ErrorHandler was loaded by 
 00:51:22,447 ERROR [STDERR] log4j:ERROR [EMAIL PROTECTED] 
 url=file:/home/keo/EclipseWorkspace/workspace_3.2.SMX.TEST/jboss-4.0.5.GA/server/default/tmp/deploy/tmp61318servicemix-jboss-deployer-3.1-SNAPSHOT.sar
  ,addedOrder=40}] whereas object of type 
 00:51:22,447 ERROR [STDERR] log4j:ERROR 
 org.jboss.logging.util.OnlyOnceErrorHandler was loaded by [EMAIL PROTECTED]
 00:51:22,489 ERROR [STDERR] log4j:ERROR Could not create an Appender. 
 Reported error follows.
 00:51:22,489 ERROR [STDERR] java.lang.ClassCastException: 
 org.jboss.logging.appender.DailyRollingFileAppender
 00:51:22,490 ERROR [STDERR] at 
 org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:175)
 00:51:22,490 ERROR [STDERR] at 
 org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:150)
 00:51:22,490 ERROR [STDERR] at 
 org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:163)
 00:51:22,490 ERROR [STDERR] at 
 org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:425)
 00:51:22,491 ERROR [STDERR] at 
 org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:394)
 00:51:22,491 ERROR [STDERR] at 
 org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:829)
 00:51:22,491 ERROR [STDERR] at 
 org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:712)
 00:51:22,491 ERROR [STDERR] at 
 org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618)
 00:51:22,491 ERROR [STDERR] at 
 org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468)
 00:51:22,491 ERROR [STDERR] at 
 org.apache.log4j.LogManager.clinit(LogManager.java:122)
 00:51:22,491 ERROR [STDERR] at 
 org.apache.log4j.Logger.getLogger(Logger.java:104)
 00:51:22,491 ERROR [STDERR] at 
 org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:283)
 00:51:22,491 ERROR [STDERR] at 
 org.apache.commons.logging.impl.Log4JLogger.init(Log4JLogger.java:108)
 00:51:22,491 ERROR [STDERR] at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 00:51:22,491 ERROR [STDERR] at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 00:51:22,491 ERROR [STDERR] at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 00:51:22,492 ERROR [STDERR] at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:494)
 00:51:22,492 ERROR [STDERR] at 
 org.apache.commons.logging.impl.LogFactoryImpl.createLogFromClass(LogFactoryImpl.java:1040)
 00:51:22,492 ERROR [STDERR] at 
 org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:838)
 00:51:22,492 ERROR [STDERR] at 
 org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:601)
 00:51:22,492 ERROR [STDERR] at 
 org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:333)
 00:51:22,492 ERROR [STDERR] at 
 org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:307)
 00:51:22,492 ERROR [STDERR] at 
 org.apache.commons.logging.LogFactory.getLog(LogFactory.java:645)
 00:51:22,492 ERROR [STDERR] at 
 org.apache.servicemix.jbi.container.JBIContainer.clinit(JBIContainer.java:95)
 00:51:22,492 ERROR [STDERR] at 
 org.servicemix.jboss.deployment.JBIService.init(JBIService.java:45)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (SM-761) JRuby support

2007-01-11 Thread Kit Plummer (JIRA)


[ 
https://issues.apache.org/activemq/browse/SM-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37900
 ] 

Kit Plummer commented on SM-761:


Not sure if it is really related to this particular thread of discussion, but I 
can see where creating a JBI component (with the lifecycle features) in Ruby 
would be very handy.

Not that writing simple services in Java is painful, but the deployment 
process, including the Maven build can be quite tedious.  Swapping a file out 
of a Service Assembly and redeploying to ServiceMix would be very efficient 
from a development/testing perspective.

 JRuby support
 -

 Key: SM-761
 URL: https://issues.apache.org/activemq/browse/SM-761
 Project: ServiceMix
  Issue Type: Improvement
  Components: servicemix-script
Reporter: Guillaume Nodet

 JRuby support should work with spring 2.0.2 + jruby 0.9.1
 See http://forum.springframework.org/showthread.php?t=28798

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQCPP-36) Cleanup whitespace and member function definitions in header files


[ 
https://issues.apache.org/activemq/browse/AMQCPP-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37872
 ] 

Albert Strasheim commented on AMQCPP-36:


I think I have two new reasons for possibly moving code from headers to cpp 
files: code size and build time.

The latest activemq-cpp.lib is 41,112 KB, which seems rather... large.

While we were chasing down the bug we were seeing related to AMQCPP-25, we had 
to make changes to functions that were implemented in headers, causing large 
parts of the library that didn't really change to be rebuilt.

 Cleanup whitespace and member function definitions in header files
 --

 Key: AMQCPP-36
 URL: https://issues.apache.org/activemq/browse/AMQCPP-36
 Project: ActiveMQ C++ Client
  Issue Type: Improvement
Reporter: Albert Strasheim
 Assigned To: Timothy Bish
Priority: Minor
 Fix For: 1.1

 Attachments: activemq-concurrent-cleanup.diff, 
 StompFrame-signmismatch.diff


 The AMQCPP code looks great in general, but many files have some stray 
 whitespace. Also, there are quite a few headers that contain member function 
 definitions. Some are simple, but there's also some big ones in there. I 
 usually follow the rule that anything that can go into the .cpp should.
 Attached is a patch to clean up the files in activemq::concurrent. If 
 Timothy/Nathan agrees that doing this is useful, I'll submit patches for the 
 rest.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: NMS byte order for doubles

2007-01-11 Thread rousseau


Sure. It's the same as AMQ-866. Comment added on that case.

thx
Steve



Hiram Chirino wrote:
 
 Hi Steve,
 
 I would be happy to apply your patch but could you open a JIRA issue at:
 http://issues.apache.org/activemq/browse/AMQ
 
 And attach your patch to that so that we have it properly documented
 that you want to contribute your patch to the ASF.
 
 Thanks!
 Hiram
 
 On 1/10/07, rousseau [EMAIL PROTECTED] wrote:

 I've found a byte-order problem sending a double from Java ActiveMQ to a
 NMS/CSharp receiver:

 (NMS) ActiveMQ.OpenWire.OpenWireBinaryReader has no definition for
 ReadDouble(), and by default calls the MS .NET BinaryReader.ReadDouble()
 which reads the bytes in the wrong order. Here is the fix:

 add a new method to OpenWireBinaryReader.cs:

 public override double ReadDouble()
 {
 return EndianSupport.SwitchEndian(base.ReadBytes(8));
 }

 add a new method to EndianSupport.cs:

 public static double SwitchEndian(byte[] bytes)
 {
 //Reverse byte array
 byte[] reverse = new byte[8];
 reverse[0] = bytes[7];
 reverse[1] = bytes[6];
 reverse[2] = bytes[5];
 reverse[3] = bytes[4];
 reverse[4] = bytes[3];
 reverse[5] = bytes[2];
 reverse[6] = bytes[1];
 reverse[7] = bytes[0];
 BinaryReader br = new BinaryReader(new
 MemoryStream(reverse));
 return br.ReadDouble();
 }

 If anyone knows a cleaner way of doing this, please let me know.

 thx
 /Steve
 --
 View this message in context:
 http://www.nabble.com/NMS-byte-order-for-doubles-tf2951266.html#a8253895
 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.


 
 
 -- 
 Regards,
 Hiram
 
 Blog: http://hiramchirino.com
 
 

-- 
View this message in context: 
http://www.nabble.com/NMS-byte-order-for-doubles-tf2951266.html#a8273932
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] Commented: (AMQ-866) Problem from open wire dotnet send float properties message to java

2007-01-11 Thread steve cook (JIRA)


[ 
https://issues.apache.org/activemq/browse/AMQ-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37873
 ] 

steve cook commented on AMQ-866:


Same problem with doubles.

This is just a byte order problem - here is a patch for doubles. floats can be 
fixed in the same way:



 I've found a byte-order problem sending a double from Java ActiveMQ to a
 NMS/CSharp receiver:

 (NMS) ActiveMQ.OpenWire.OpenWireBinaryReader has no definition for
 ReadDouble(), and by default calls the MS .NET BinaryReader.ReadDouble()
 which reads the bytes in the wrong order. Here is the fix:

 add a new method to OpenWireBinaryReader.cs:

 public override double ReadDouble()
 {
 return EndianSupport.SwitchEndian(base.ReadBytes(8));
 }

 add a new method to EndianSupport.cs:

 public static double SwitchEndian(byte[] bytes)
 {
 //Reverse byte array
 byte[] reverse = new byte[8];
 reverse[0] = bytes[7];
 reverse[1] = bytes[6];
 reverse[2] = bytes[5];
 reverse[3] = bytes[4];
 reverse[4] = bytes[3];
 reverse[5] = bytes[2];
 reverse[6] = bytes[1];
 reverse[7] = bytes[0];
 BinaryReader br = new BinaryReader(new MemoryStream(reverse));
 return br.ReadDouble();
 }

 If anyone knows a cleaner way of doing this, please let me know.

 thx
 /Steve 


 Problem from open wire dotnet send float properties message to java
 ---

 Key: AMQ-866
 URL: https://issues.apache.org/activemq/browse/AMQ-866
 Project: ActiveMQ
  Issue Type: Bug
  Components: NMS (C# client)
Reporter: Denis Abramov

 Am also interested in this issue (from Discussion forum):
 I found a problem while i using open wire dotnet api to send float property 
 message to java platform, the value i recieved that is deffrent with the 
 value setting in dotnet platform. 
 here is send value(dotnet) is:  float floatvalue = 2.1F 
 recieved value(java) is value is: 1.757237E-26 
 is this a bug or i make some mistake in my test? 
 follow is my test code: 
 dotnet: 
 float value= 2.12F; 
 Uri uri = new Uri(tcp:// + ip + 
 :61616?jms.useAsyncSend=true); 
 factory = new ConnectionFactory(uri); 
 using (IConnection connection = factory.CreateConnection()) 
 { 
 ISession session = 
 connection.CreateSession(acknowledgementMode); 
 IDestination destination = session.GetQueue(queueName); 
 IMessageProducer producer = 
 session.CreateProducer(destination); 
 producer.Persistent = true; 
 // lets send a message 
 String text = text; 
 ITextMessage request = session.CreateTextMessage(text); 
 request.NMSPersistent = true; 
 request.NMSCorrelationID = abc; 
 
 request.Properties[custom8] = custom8; 
 producer.Send(request); 
 } 
 java: 
 public void onMessage(Message message) { 
System.out.println(message.getFloatProperty(custom8)); 
 } 
 could someone do me a favor? 
 Thx! 
 Matt

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (AMQCPP-25) Bus error on Solaris OS from DataInput and DataOutput streams


 [ 
https://issues.apache.org/activemq/browse/AMQCPP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Albert Strasheim updated AMQCPP-25:
---

Attachment: optobug.cpp

 Bus error on Solaris OS from DataInput and DataOutput streams
 -

 Key: AMQCPP-25
 URL: https://issues.apache.org/activemq/browse/AMQCPP-25
 Project: ActiveMQ C++ Client
  Issue Type: Bug
  Components: CMS Impl
Affects Versions: 1.1
 Environment: Solaris 10 OS
Reporter: Timothy Bish
 Assigned To: Timothy Bish
Priority: Minor
 Fix For: 1.1

 Attachments: optobug.cpp


 Due to misaligned memory reads, there is a bus error that can occur in using 
 the new DataInputStream and DataOutputStream classes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQCPP-25) Bus error on Solaris OS from DataInput and DataOutput streams


[ 
https://issues.apache.org/activemq/browse/AMQCPP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37877
 ] 

Albert Strasheim commented on AMQCPP-25:


Figured it out! Looks like a strict aliasing (whatever that is) issue with GCC 
4 optimization.

Example code to be attached. Compiling with GCC 4.1.1 with different 
optimization levels:

{noformat}
[EMAIL PROTECTED] ~]$ gcc --version
gcc (GCC) 4.1.1 20061011 (Red Hat 4.1.1-30)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[EMAIL PROTECTED] ~]$ g++ -O0 -Wall -ansi -o optobug optobug.cpp  ./optobug
i1 == i3 OK
ll1 == ll3 OK
f1 == f3 OK
d1 == d3 OK
[EMAIL PROTECTED] ~]$ g++ -O1 -Wall -ansi -o optobug optobug.cpp  ./optobug
i1 == i3 OK
ll1 == ll3 OK
f1 == f3 OK
d1 == d3 OK
[EMAIL PROTECTED] ~]$ g++ -O2 -Wall -ansi -o optobug optobug.cpp  ./optobug
optobug.cpp: In static member function 'static float Endian::byteSwap(float)':
optobug.cpp:26: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
optobug.cpp:32: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
optobug.cpp: In static member function 'static double Endian::byteSwap(double)':
optobug.cpp:36: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
optobug.cpp:42: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
i1 == i3 OK
ll1 == ll3 OK
f1 != f3 ERROR
d1 != d3 ERROR
[EMAIL PROTECTED] ~]$ g++ -O2 -fno-strict-aliasing -Wall -ansi -o optobug 
optobug.cpp  ./optobug
i1 == i3 OK
ll1 == ll3 OK
f1 == f3 OK
d1 == d3 OK
{noformat}

The idea I get from [dereferencing type-punned pointer will break 
strict-aliasing 
rules|http://lists.freebsd.org/pipermail/freebsd-current/2003-July/007561.html] 
is that the right way to fix this is to use a union containing a float/unsigned 
int or double/unsigned long long.

Alternatively, AMQCPP's compiler flags can be changed to pass 
-fno-strict-aliasing to the compiler. There's an issue to be aware of (I 
think): no code that needs strict aliasing to be turned off can live in a 
AMQCPP header, since this will force anyone using the library to also compile 
with with -fno-strict-aliasing flag, because if they forget, things will break 
mysteriously with older versions of GCC 4.

 Bus error on Solaris OS from DataInput and DataOutput streams
 -

 Key: AMQCPP-25
 URL: https://issues.apache.org/activemq/browse/AMQCPP-25
 Project: ActiveMQ C++ Client
  Issue Type: Bug
  Components: CMS Impl
Affects Versions: 1.1
 Environment: Solaris 10 OS
Reporter: Timothy Bish
 Assigned To: Timothy Bish
Priority: Minor
 Fix For: 1.1

 Attachments: optobug.cpp


 Due to misaligned memory reads, there is a bus error that can occur in using 
 the new DataInputStream and DataOutputStream classes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-1046) Consolidate the ActiveMQ admin scripts to a single command line script

2007-01-11 Thread Adrian Co (JIRA)

[
https://issues.apache.org/activemq/browse/AMQ-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Adrian Co resolved AMQ-1046.

Resolution: Fixed

Fix added to r495172

Admin commands can be success using:
activemq-admin bstat
activemq-admin stop
activemq-admin list
activemq-admin query ...
activemq-admin purge
etc..

Consolidate the ActiveMQ admin scripts to a single command line script
--

Key: AMQ-1046
URL: https://issues.apache.org/activemq/browse/AMQ-1046
Project: ActiveMQ
Issue Type: Improvement
Reporter: Hiram Chirino
Assigned To: Adrian Co
Fix For: 4.2.0

Right now we have serveral command line scripts in the ActiveMQ bin directory
of the binary distribution. They are used for admin purposes. They are less
than ideal because some of them have very generic names and might clash with
existing commands if the activemq bin directory is added to the PATH of a
unix system.
I think it would be more idea if we consolidated all the command so that are
executed using just 1 script. Something like:
$ activemq-admin list
$ activemq-admin stat
$ activemq-admin browse
etc. etc. etc. This way only 2 executable scripts are added to the path:
(1) activemq - the binary that starts up ActiveMQ
(2) activemq-admin - the binary used to manage the ActiveMQ instance.

[jira] Resolved: (AMQ-1096) activemq-console only has limited classpath/extensions directory functionality

2007-01-11 Thread Adrian Co (JIRA)

[
https://issues.apache.org/activemq/browse/AMQ-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Adrian Co resolved AMQ-1096.

Resolution: Fixed

Fix added to r495172

Added a activemq.classpath system property to extend the classpath of activemq

By default it contains activemq.home/conf.

It can be extended by specifying additional paths via the ACTIVEMQ_CLASSPATH
environment variable separated by semi-colons.

activemq-console only has limited classpath/extensions directory functionality
--

Key: AMQ-1096
URL: https://issues.apache.org/activemq/browse/AMQ-1096
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.1.0
Reporter: John Heitmann
Assigned To: Adrian Co
Priority: Minor
Attachments: logpatch.diff

Reproduction:
1) Untar the binary distribution.
2) Run bin/activemq and note what logging looks like (you should see output
to the console)
3) Stop the broker.
4) mv conf/log4j.properties foo/log4j.properties
5) export CLASSPATH=/path/to/foo/
6) export ACTIVEMQ_CLASSPATH=/path/to/foo/
7) Run './activemq --extdir /path/to/foo
Now note there is no log output even though there are 3 different attempts to
set the proper directory. This is a regression from 4.0 to 4.1.
There are 2 root problems in Main.java. First, 'classpaths' doesn't actually
pull from the classpath. The only thing that ever gets added to classpaths is
the hard coded 'conf' directory. Second, directories specified with --extdir
have jars and zips added, but not the directories themselves.
The attached patch totally removes the vestigial classpaths, and fixes extdir
to pull in directories. This means that step 7 now works, but steps 5 and 6
are still useless. I like having only one way to specify classpath, but I
could see others wanting the CLASSPATH and ACTIVEMQ_CLASSPATH settings to
work.

[jira] Commented: (AMQCPP-25) Bus error on Solaris OS from DataInput and DataOutput streams


[ 
https://issues.apache.org/activemq/browse/AMQCPP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37880
 ] 

Albert Strasheim commented on AMQCPP-25:


http://www.cellperformance.com/mike_acton/2006/06/understanding_strict_aliasing.html

 Bus error on Solaris OS from DataInput and DataOutput streams
 -

 Key: AMQCPP-25
 URL: https://issues.apache.org/activemq/browse/AMQCPP-25
 Project: ActiveMQ C++ Client
  Issue Type: Bug
  Components: CMS Impl
Affects Versions: 1.1
 Environment: Solaris 10 OS
Reporter: Timothy Bish
 Assigned To: Timothy Bish
Priority: Minor
 Fix For: 1.1

 Attachments: optobug.cpp


 Due to misaligned memory reads, there is a bus error that can occur in using 
 the new DataInputStream and DataOutputStream classes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (GERONIMO-2577) Geronimo cluster (Tomcat Version)cannot continue the HttpSession when current node is down.

2007-01-11 Thread Kaoru Matsumura (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463857
 ] 

Kaoru Matsumura commented on GERONIMO-2577:
---

Hello Jeff and Shiva, I'm sorry to be late for reply.

I tried your new-config.xml and geronimo-web-hostlevel.xml(Host level 
Clustering)on my RHEL environment.
Good! The clustering works perfectly. The same as your case , session gets 
preserved successfully even onto the 3rd remaining node. 

Would you please tell me why clustering doesn't work successfully (Context 
level Clustering + DeltaManager) ? 

Thanks

 Geronimo cluster (Tomcat Version)cannot continue the HttpSession when current 
 node is down.
 ---

 Key: GERONIMO-2577
 URL: https://issues.apache.org/jira/browse/GERONIMO-2577
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Clustering, Tomcat
Affects Versions: 1.1, 1.1.1
 Environment: JDK - Sun java version 1_5_0_09(32bit)
 OS- Red Hat Enterprise Linux ES4 update4(32bit)
 Http Server - Apache 2.0.59 +mod_jk 1.2.19
Reporter: Kaoru Matsumura
 Attachments: config.xml, context.xml, geronimo-new.log, 
 geronimo-web-hostlevel.xml, geronimo-web-new.xml, geronimo-web-nodeB.xml, 
 geronimo-web-nodeC.xml, geronimo-web.xml, new-config.xml, server-nodeA.xml, 
 server-nodeB.xml, server-nodeC.xml


 We run Geronimo cluster with three nodes.
 In our environment, with DeltaManager set for replication module, we found 
 that the last node cound not continue the processes when the other nodes is 
 intentionally halted in order.
 We recognize Tomcat 5.5.15 is OK with the same configuration and operations.
 Test Application
 
 The Web application program, which was used for the test, simply reads the 
 number of access count, and then write the count to HttpSession object.
 Configuration?Files
 ==
 We refer http://cwiki.apache.org/GMOxDOC11/clustering-sample-application.html
 * config.xml
 We add the following parameters to the standard configuration. 
 gbean name=TomcatEngine
 attribute name=initParamsname=Geronimo
   jvmRoute=nodeA/attribute
 /gbean
 Operations
 ===
 1 Have browser access to Test Application , and reload several times.(*1) 
 HttpSession object is created on the nodeA.
 2 And then, We kill the process of geronimo on the nodeA  with $kill -9 
 Process ID.(*2)
 3 Reload the browser at one time. The node changes to nodeB.(*3)
 4 Reload the browser several times.(*4)
 5 And then, We kill the process of geronimo on the nodeB  with $kill -9 
 Process ID.(*5)
 6 Reload the browser at one time.(And then, We expect that the process 
 continues at the nodeC.)
   But the HttpSessionID of the HttpSession object is changed to another ID 
 and the counter value is back to 1.(*6)
   As a result, the geronimo cluster cannot continue the process.
 For avoidance
 ===
 When replication module is SimpleTcpReplicationManager, the geronimo cluster 
 can continue the process.
 Debug levels logs
 ==
 (*1)
  nodeA
 --
 20:06:17,736 DEBUG [CoyoteAdapter]  Requested cookie session id is 
 7160C8614D20687D3548E8488AB65AC3.nodeA
 20:06:17,736 DEBUG [JvmRouteBinderValve] Found Cluster DeltaManager [EMAIL 
 PROTECTED] at /ClusterCheck
 20:06:17,736 DEBUG [JvmRouteBinderValve] Turnover Check time 0 msec
 20:06:17,737 DEBUG [MsgContext] COMMIT 
 20:06:17,737 DEBUG [JkInputStream] COMMIT sending headers [EMAIL PROTECTED] 
 === MimeHeaders ===
 20:06:17,737 DEBUG [MsgContext] CLOSE 
 20:06:17,738 DEBUG [REQ_TIME] Time pre=0/ service=2 242 /ClusterCheck/counter
 20:06:17,738 DEBUG [ReplicationValve] Invoking replication request on 
 /ClusterCheck/counter
 20:06:17,738 DEBUG [DeltaManager] Manager [/ClusterCheck]: create session 
 message [7160C8614D20687D3548E8488AB65AC3.nodeA] delta request.
 20:06:17,757 DEBUG [McastService] Mcast receive ping from member 
 org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.1.3:4001,catalina,192.168.1.3,4001,
  alive=58960]
 ---
  nodeC
 ---
 20:06:17,655 DEBUG [SimpleTcpCluster] Assuming clocks are synched: 
 Replication for 7160C8614D20687D3548E8488AB65AC3.nodeA-1162811177738 took=-83 
 ms.
 20:06:17,655 DEBUG [DeltaManager] Manager [/ClusterCheck]: Received 
 SessionMessage of type=(SESSION-DELTA) from 
 [org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.1.1:4001,catalina,192.168.1.1,4001,
  alive=130441]]
 20:06:17,655 DEBUG [DeltaManager] Manager [/ClusterCheck]: received session 
 [7160C8614D20687D3548E8488AB65AC3.nodeA] delta.
 ---
 (*2)
  nodeB (same as nodeC)
 ---
 20:06:39,817 INFO  [SimpleTcpCluster] Received member

[jira] Commented: (GERONIMO-2577) Geronimo cluster (Tomcat Version)cannot continue the HttpSession when current node is down.

2007-01-11 Thread Shiva Kumar H R (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463879
 ] 

Shiva Kumar H R commented on GERONIMO-2577:
---

Kaoru,
Thanks for testing this.

Looks like Context level Clustering is a not yet supported feature or a bug in 
Tomcat itself. I tested Context/Application level clustering in Tomcat 5.5.20 
on my 3-node Win-XP cluster and the testing fails.

I used the following configuration files for enabling Context level clustering 
in Tomcat:
1) appClustering_context.xml (edit lines 12 and 25 of this file in case you 
want to give it a try. copy this file into the conf folder of Tomcat and 
rename it as config.xml
2) appClustering_server.xml (copy this file to Tomcat's conf folder and 
rename it as server.xml)

Upon deploying the sample application in 
http://cwiki.apache.org/GMOxDOC11/clustering-sample-application.html and 
running http://Yourhost/servlets-examples-cluster/servlet/SessionExample, I 
observe that session-ids are getting changed upon hitting page-refreshes or 
upon adding attributes. I tried this app level clustering in Tomcat multiple 
times, but same results every time, with even sticky sessions not being in 
effect.

Jeff,
How can we confirm if it is a Bug OR not supported Feature in Tomcat?

If it turns out to be a not supported feature in Tomcat, then shouldn't we 
claim that Geronimo supports Clustering at the Host or Engine level only and 
accordingly update the tutorial in 
http://cwiki.apache.org/GMOxDOC11/clustering-sample-application.html. Please 
suggest.

Thx,
Shiva


 Geronimo cluster (Tomcat Version)cannot continue the HttpSession when current 
 node is down.
 ---

 Key: GERONIMO-2577
 URL: https://issues.apache.org/jira/browse/GERONIMO-2577
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Clustering, Tomcat
Affects Versions: 1.1, 1.1.1
 Environment: JDK - Sun java version 1_5_0_09(32bit)
 OS- Red Hat Enterprise Linux ES4 update4(32bit)
 Http Server - Apache 2.0.59 +mod_jk 1.2.19
Reporter: Kaoru Matsumura
 Attachments: config.xml, context.xml, geronimo-new.log, 
 geronimo-web-hostlevel.xml, geronimo-web-new.xml, geronimo-web-nodeB.xml, 
 geronimo-web-nodeC.xml, geronimo-web.xml, new-config.xml, server-nodeA.xml, 
 server-nodeB.xml, server-nodeC.xml


 We run Geronimo cluster with three nodes.
 In our environment, with DeltaManager set for replication module, we found 
 that the last node cound not continue the processes when the other nodes is 
 intentionally halted in order.
 We recognize Tomcat 5.5.15 is OK with the same configuration and operations.
 Test Application
 
 The Web application program, which was used for the test, simply reads the 
 number of access count, and then write the count to HttpSession object.
 Configuration?Files
 ==
 We refer http://cwiki.apache.org/GMOxDOC11/clustering-sample-application.html
 * config.xml
 We add the following parameters to the standard configuration. 
 gbean name=TomcatEngine
 attribute name=initParamsname=Geronimo
   jvmRoute=nodeA/attribute
 /gbean
 Operations
 ===
 1 Have browser access to Test Application , and reload several times.(*1) 
 HttpSession object is created on the nodeA.
 2 And then, We kill the process of geronimo on the nodeA  with $kill -9 
 Process ID.(*2)
 3 Reload the browser at one time. The node changes to nodeB.(*3)
 4 Reload the browser several times.(*4)
 5 And then, We kill the process of geronimo on the nodeB  with $kill -9 
 Process ID.(*5)
 6 Reload the browser at one time.(And then, We expect that the process 
 continues at the nodeC.)
   But the HttpSessionID of the HttpSession object is changed to another ID 
 and the counter value is back to 1.(*6)
   As a result, the geronimo cluster cannot continue the process.
 For avoidance
 ===
 When replication module is SimpleTcpReplicationManager, the geronimo cluster 
 can continue the process.
 Debug levels logs
 ==
 (*1)
  nodeA
 --
 20:06:17,736 DEBUG [CoyoteAdapter]  Requested cookie session id is 
 7160C8614D20687D3548E8488AB65AC3.nodeA
 20:06:17,736 DEBUG [JvmRouteBinderValve] Found Cluster DeltaManager [EMAIL 
 PROTECTED] at /ClusterCheck
 20:06:17,736 DEBUG [JvmRouteBinderValve] Turnover Check time 0 msec
 20:06:17,737 DEBUG [MsgContext] COMMIT 
 20:06:17,737 DEBUG [JkInputStream] COMMIT sending headers [EMAIL PROTECTED] 
 === MimeHeaders ===
 20:06:17,737 DEBUG [MsgContext] CLOSE 
 20:06:17,738 DEBUG [REQ_TIME] Time pre=0/ service=2 242 /ClusterCheck/counter
 20:06:17,738 DEBUG [ReplicationValve] Invoking replication request on 
 /ClusterCheck/counter
 20:06:17,738 DEBUG [DeltaManager] Manager

[jira] Updated: (GERONIMO-2577) Geronimo cluster (Tomcat Version)cannot continue the HttpSession when current node is down.

2007-01-11 Thread Shiva Kumar H R (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shiva Kumar H R updated GERONIMO-2577:
--

Attachment: appClustering_server.xml
appClustering_context.xml

 Geronimo cluster (Tomcat Version)cannot continue the HttpSession when current 
 node is down.
 ---

 Key: GERONIMO-2577
 URL: https://issues.apache.org/jira/browse/GERONIMO-2577
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Clustering, Tomcat
Affects Versions: 1.1, 1.1.1
 Environment: JDK - Sun java version 1_5_0_09(32bit)
 OS- Red Hat Enterprise Linux ES4 update4(32bit)
 Http Server - Apache 2.0.59 +mod_jk 1.2.19
Reporter: Kaoru Matsumura
 Attachments: appClustering_context.xml, appClustering_server.xml, 
 config.xml, context.xml, geronimo-new.log, geronimo-web-hostlevel.xml, 
 geronimo-web-new.xml, geronimo-web-nodeB.xml, geronimo-web-nodeC.xml, 
 geronimo-web.xml, new-config.xml, server-nodeA.xml, server-nodeB.xml, 
 server-nodeC.xml


 We run Geronimo cluster with three nodes.
 In our environment, with DeltaManager set for replication module, we found 
 that the last node cound not continue the processes when the other nodes is 
 intentionally halted in order.
 We recognize Tomcat 5.5.15 is OK with the same configuration and operations.
 Test Application
 
 The Web application program, which was used for the test, simply reads the 
 number of access count, and then write the count to HttpSession object.
 Configuration?Files
 ==
 We refer http://cwiki.apache.org/GMOxDOC11/clustering-sample-application.html
 * config.xml
 We add the following parameters to the standard configuration. 
 gbean name=TomcatEngine
 attribute name=initParamsname=Geronimo
   jvmRoute=nodeA/attribute
 /gbean
 Operations
 ===
 1 Have browser access to Test Application , and reload several times.(*1) 
 HttpSession object is created on the nodeA.
 2 And then, We kill the process of geronimo on the nodeA  with $kill -9 
 Process ID.(*2)
 3 Reload the browser at one time. The node changes to nodeB.(*3)
 4 Reload the browser several times.(*4)
 5 And then, We kill the process of geronimo on the nodeB  with $kill -9 
 Process ID.(*5)
 6 Reload the browser at one time.(And then, We expect that the process 
 continues at the nodeC.)
   But the HttpSessionID of the HttpSession object is changed to another ID 
 and the counter value is back to 1.(*6)
   As a result, the geronimo cluster cannot continue the process.
 For avoidance
 ===
 When replication module is SimpleTcpReplicationManager, the geronimo cluster 
 can continue the process.
 Debug levels logs
 ==
 (*1)
  nodeA
 --
 20:06:17,736 DEBUG [CoyoteAdapter]  Requested cookie session id is 
 7160C8614D20687D3548E8488AB65AC3.nodeA
 20:06:17,736 DEBUG [JvmRouteBinderValve] Found Cluster DeltaManager [EMAIL 
 PROTECTED] at /ClusterCheck
 20:06:17,736 DEBUG [JvmRouteBinderValve] Turnover Check time 0 msec
 20:06:17,737 DEBUG [MsgContext] COMMIT 
 20:06:17,737 DEBUG [JkInputStream] COMMIT sending headers [EMAIL PROTECTED] 
 === MimeHeaders ===
 20:06:17,737 DEBUG [MsgContext] CLOSE 
 20:06:17,738 DEBUG [REQ_TIME] Time pre=0/ service=2 242 /ClusterCheck/counter
 20:06:17,738 DEBUG [ReplicationValve] Invoking replication request on 
 /ClusterCheck/counter
 20:06:17,738 DEBUG [DeltaManager] Manager [/ClusterCheck]: create session 
 message [7160C8614D20687D3548E8488AB65AC3.nodeA] delta request.
 20:06:17,757 DEBUG [McastService] Mcast receive ping from member 
 org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.1.3:4001,catalina,192.168.1.3,4001,
  alive=58960]
 ---
  nodeC
 ---
 20:06:17,655 DEBUG [SimpleTcpCluster] Assuming clocks are synched: 
 Replication for 7160C8614D20687D3548E8488AB65AC3.nodeA-1162811177738 took=-83 
 ms.
 20:06:17,655 DEBUG [DeltaManager] Manager [/ClusterCheck]: Received 
 SessionMessage of type=(SESSION-DELTA) from 
 [org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.1.1:4001,catalina,192.168.1.1,4001,
  alive=130441]]
 20:06:17,655 DEBUG [DeltaManager] Manager [/ClusterCheck]: received session 
 [7160C8614D20687D3548E8488AB65AC3.nodeA] delta.
 ---
 (*2)
  nodeB (same as nodeC)
 ---
 20:06:39,817 INFO  [SimpleTcpCluster] Received member 
 disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.1.1:4001,catalina,192.168.1.1,4001,
  alive=149288]
 20:06:39,818 DEBUG [MapperListener] Handle 
 geronimo:type=IDataSender,senderAddress=192.168.1.1,senderPort=4001 type : 
 JMX.mbean.unregistered
 20:06:39,818 DEBUG [MapperListener] Handle

[jira] Commented: (AMQCPP-25) Bus error on Solaris OS from DataInput and DataOutput streams

2007-01-11 Thread Nathan Mittler (JIRA)


[ 
https://issues.apache.org/activemq/browse/AMQCPP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37883
 ] 

Nathan Mittler commented on AMQCPP-25:
--

Hi Albert,
Great work!  Looks like you might be onto something here.  Just out of 
curiosity, where did you get the idea for your patch (char c = new char, delete 
c) - I didn't see that solution called out in the links you posted.  Perhaps I 
just missed it.

Thanks!

 Bus error on Solaris OS from DataInput and DataOutput streams
 -

 Key: AMQCPP-25
 URL: https://issues.apache.org/activemq/browse/AMQCPP-25
 Project: ActiveMQ C++ Client
  Issue Type: Bug
  Components: CMS Impl
Affects Versions: 1.1
 Environment: Solaris 10 OS
Reporter: Timothy Bish
 Assigned To: Timothy Bish
Priority: Minor
 Fix For: 1.1

 Attachments: optobug.cpp


 Due to misaligned memory reads, there is a bus error that can occur in using 
 the new DataInputStream and DataOutputStream classes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQCPP-25) Bus error on Solaris OS from DataInput and DataOutput streams

2007-01-11 Thread Nathan Mittler (JIRA)


[ 
https://issues.apache.org/activemq/browse/AMQCPP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37884
 ] 

Nathan Mittler commented on AMQCPP-25:
--

As indicated in the links Albert provided, we should add the following compiler 
flags:

-fstrict-aliasing
-Wstrict-aliasing


 Bus error on Solaris OS from DataInput and DataOutput streams
 -

 Key: AMQCPP-25
 URL: https://issues.apache.org/activemq/browse/AMQCPP-25
 Project: ActiveMQ C++ Client
  Issue Type: Bug
  Components: CMS Impl
Affects Versions: 1.1
 Environment: Solaris 10 OS
Reporter: Timothy Bish
 Assigned To: Timothy Bish
Priority: Minor
 Fix For: 1.1

 Attachments: optobug.cpp


 Due to misaligned memory reads, there is a bus error that can occur in using 
 the new DataInputStream and DataOutputStream classes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Assemblies assemblies everywhere and which one to ship?


I agree with david.

-- dims

On 1/11/07, David Jencks [EMAIL PROTECTED] wrote:


On Jan 11, 2007, at 12:01 AM, Jarek Gawor wrote:

 How hard is it to switch between the different assemblies once the TCK
 testing environment is setup? If it is easy enough, maybe we should
 first test all 8 assemblies and then concentrate on only those that
 pass the most tests.

I guess I have the opposite point of view :-).  I suspect if we get
all the tests passing for each component in one configuration, they
will pretty much pass in all the other configurations, e.g. if cxf +
jetty + openjpa works then cxf + tomcat + cayenne will work too, so
the main chore will be to verify this.  If it's simple enough to run
the tck this won't be impossibly difficult to test all the
combinations, just take a bunch of machine time.

thanks
david jencks


 Jarek

 On 1/9/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
 I think testing say (Tomcat+Axis2+OpenJPA) and (Jetty+CXF+Cayenne) is
 enough. All components should be tested at least once. If we get
 time,
 we could do more :)

 -- dims

 On 1/8/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
  On Jan 7, 2007, at 9:38 PM, David Jencks wrote:
 
   On Jan 7, 2007, at 11:33 PM, Matt Hogstrom wrote:
  
   I was thinking about M2 this weekend and was considering many of
   the challenges we face in putting out certified releases.  Up
 till
   now the number of permutations has been pretty limited and that
   has been Jetty and Tomcat.  With Java EE 5.0 life is no longer
   that simple.  Here are the choices I know of today:
  
   Web Container (Tomcat / Jetty)
   WebServices (Axis 2 / CXF)
   EJB 3.0 Persistence (OpenJPA / Cayenne)
  
   I think this makes 6 different assemblies and of course 6
 separate
   certification efforts.  Perhaps we can do this and perhaps we
   can't.  Based on where projects are at and their desire to
   participate in helping to integrate (and do TCK testing :).
  
   ummm 2 * 2 * 2 == 8
  
   I could be very wrong but I thought that the cmp 2.1 support in
   openejb3 was relying on openjpa-specific features.  If so I
 wonder
   if it will be tricky to run the tck on other jpa implementations.
 
  Well, we depend on being able to listen to events on the EM which
  there is no spec interface for.  I'm sure Cayanne has and interface
  that can provide us with the events, and when they send us the info
  we can add a hook for their Impl.
 
  In general, I think we should just pick a single JPA implementation
  to ship with G because it is very easy for an application to
 request
  a different implementation using specification defined properties.
 
  Of course that will leave us with 4 javaee assemblies and 2 minimal
  assemblies.
 
  -dain
 


 --
 Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
 Developers)






--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

RE: Geronimo Axis2 Integration

2007-01-11 Thread Lin Sun

Hi Lasantha,

I've been doing some integration test and build (enable the four modules in
modules\pom.xml and configs\pom.xml) yesterday and I found that I am having
trouble to start the axis2-deployer during the start of the server.  Is that
why you didn't update modules\pom.xml for the 2 modules?

I haven't been able to figure out the fix yet that is why I didn't submit
the patch yet. I'll keep looking into it.

Lin

-Original Message-
From: Lasantha Ranaweera [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 11, 2007 12:55 AM
To: dev@geronimo.apache.org
Subject: Re: Geronimo Axis2 Integration

Hi Lin,

Sorry for the late reply. I hope Dims has answered all your problems. 
Let us know when you submit your patch too. ;-)

Thanks,
Lasantha
Lin Sun wrote:
 Hi Lasantha,

 This is great!  Thanks.  I have been also looking into Axis2 integration
w/
 G lately and started w/ the CXF integration code.  The work I've done is
 similar as what you have, except that I also created config dir for axis2
 and axis2-deployer.  I'll submit that as a patch today.

 By looking at your patch, how did you get the jaxb generated code?  I
 haven't been figured out how yet so I had planned to use the xmlbean
 generated code, similar as Axis1.   

 Since there are some common code between CXF and Axis integration, I think
 it would be good to have one portInfo, parseWebServiceDescriptor at the
 Geronimo webservices level.

 Lin

 -Original Message-
 From: Lasantha Ranaweera [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, January 10, 2007 2:30 AM
 To: dev@geronimo.apache.org
 Subject: Geronimo Axis2 Integration

 Hi,

 The initial implementation of the Axis2 integration with Geronimo 
 uploaded in to the JIRA (Geronimo-2717). Most of the source code is 
 taken out from the CXF project of  the Geronimo and it is only a maven2 
 skeleton.

 I am expecting some help from person who knows Axis2 to implement 
 Axis2WebServiceContainer.java class and hoping to contribute Geronimo in 
 this area.

 Thanks,
 Lasantha Ranaweera

Re: Web Builders

2007-01-11 Thread anita kulshreshtha

Thanks David J.! I managed to get the webservices-builder to
compile and pass the tests by using dependency exclusion and some code
hack. 
   Now the connector-builder needs the following classes:
ActivationspecType;
AdminobjectType;
ConfigPropertyType;
ConnectionDefinitionType;
ConnectorDocument;
ConnectorType;
MessagelistenerType;
ResourceadapterType;
Where can I fine these?

Thanks
Anita

--- David Jencks [EMAIL PROTECTED] wrote:

 
 On Jan 10, 2007, at 10:36 PM, anita kulshreshtha wrote:
 
  I am trying to use javaee5 xbeans in webservices-builder.
 
 I don't think that will work.  the current webservices-builder module
  
 is for jaxrpc and it uses different xml than javaee, and javaee  
 doesn't include any version of that xml (something we can all be very
  
 happy about :-)
 
 Most of the stuff in webservices-builder was to support the jaxrpc  
 mapping mess, which has been totally replaced by jaxb.  I think we  
 can leave webservices-builder as is, perhaps labeling it so its clear
  
 it refers to jaxrpc and not jaxws, and see if we need a universal  
 module for jaxws.  At this point I don't know: it's quite possible  
 that both cxf and axis2 include 90% of the stuff they need and the  
 remaining 10% is easier to implement specific to the ws container.   
 It's also possible we can use a common module.  I think we need to  
 get more of both working before we know unless some experts who  
 actually know cxf and axis2 speak up :-)
 
 thanks
 david jencks
 
 
 
  The
  following classes are not in geronimo-schema-jee_5 jar. Where can I
  find them?
 
  ExceptionMappingType;
  JavaWsdlMappingDocument JavaWsdlMappingType;
  PackageMappingType;
  ServiceEndpointInterfaceMappingType;
  ServiceEndpointMethodMappingType;
 
  Thanks
  Anita
 
  --- anita kulshreshtha [EMAIL PROTECTED] wrote:
 
 The following classes are missing in geronimo-schema-jee-5 jar:
  ConnectorDocument$Facty.class
  ConnectorDocument.class
  ConnectorType$Factory.class
  ConnectorType.class
 Have they been renamed/moved?
 
  Thanks
  Anita
 
  --- anita kulshreshtha [EMAIL PROTECTED] wrote:
 
  --- David Jencks [EMAIL PROTECTED] wrote:
 
 
  On Jan 8, 2007, at 9:20 PM, anita kulshreshtha wrote:
 
 Geronimo-web-2.5-builder uses geronimo-web-builder as a
  dependency.
 
  Yikes!!
  It brings in geronimo-servlet_2.4_spec and
  geronimo-schema-j2ee_1.4
  as
  follows:
  web-builder - geronimo-servlet_2.4_spec
naming-builder -- j2ee-schema --
  geronimo-schema-j2ee_1.4
  Should naming-builder be changed to use 1.5?
 
  yes.
 
  Should we remove
  dependency on web-builder and move all the stuff to
  web-2.5-builder?
 
  Very definitely!!  It looks like both the jetty and tomcat
  builders
 
  are already using the web25 AbstractWebBuilder so there should
 be
  no
 
  problems there.
 
  Can you do this?  Thanks for noticing this problem!!!
 
  Sure..
 
  Anita
 
 
  thanks
  david jencks
 
 
  Thanks
  Anita
 
  __
  Do You Yahoo!?
  Tired of spam?  Yahoo! Mail has the best spam protection around
  http://mail.yahoo.com
 
 
 
 
  __
  Do You Yahoo!?
  Tired of spam?  Yahoo! Mail has the best spam protection around
  http://mail.yahoo.com
 
 
 
  __
  Do You Yahoo!?
  Tired of spam?  Yahoo! Mail has the best spam protection around
  http://mail.yahoo.com
 
 
 
 
 
 

__
 
  __
  Yahoo! Music Unlimited
  Access over 1 million songs.
  http://music.yahoo.com/unlimited
 
 



 

Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index

Re: Web Builders

2007-01-11 Thread David Jencks



On Jan 11, 2007, at 9:05 AM, anita kulshreshtha wrote:


Thanks David J.! I managed to get the webservices-builder to
compile and pass the tests by using dependency exclusion and some code
hack.
   Now the connector-builder needs the following classes:
ActivationspecType;
AdminobjectType;
ConfigPropertyType;
ConnectionDefinitionType;
ConnectorDocument;
ConnectorType;
MessagelistenerType;
ResourceadapterType;
Where can I fine these?


hm. the connector spec is unchanged between 1.4 and 5 so I didn't  
include it in the 5 schema class jar.  I think this means we need  
both the schema jars for 2.0.  Alternatively I guess we could add the  
schemas from 1.4 to the 5 jar?  I don't know how many problems this  
will cause like 2 description classes.


For me anyway what to do here needs some more thought.  I'm tempted  
to say we should just use both schema jars and leave connector  
unchanged.


thanks
david jencks



Thanks
Anita

--- David Jencks [EMAIL PROTECTED] wrote:



On Jan 10, 2007, at 10:36 PM, anita kulshreshtha wrote:


I am trying to use javaee5 xbeans in webservices-builder.


I don't think that will work.  the current webservices-builder module

is for jaxrpc and it uses different xml than javaee, and javaee
doesn't include any version of that xml (something we can all be very

happy about :-)

Most of the stuff in webservices-builder was to support the jaxrpc
mapping mess, which has been totally replaced by jaxb.  I think we
can leave webservices-builder as is, perhaps labeling it so its clear

it refers to jaxrpc and not jaxws, and see if we need a universal
module for jaxws.  At this point I don't know: it's quite possible
that both cxf and axis2 include 90% of the stuff they need and the
remaining 10% is easier to implement specific to the ws container.
It's also possible we can use a common module.  I think we need to
get more of both working before we know unless some experts who
actually know cxf and axis2 speak up :-)

thanks
david jencks




The
following classes are not in geronimo-schema-jee_5 jar. Where can I
find them?

ExceptionMappingType;
JavaWsdlMappingDocument JavaWsdlMappingType;
PackageMappingType;
ServiceEndpointInterfaceMappingType;
ServiceEndpointMethodMappingType;

Thanks
Anita

--- anita kulshreshtha [EMAIL PROTECTED] wrote:


   The following classes are missing in geronimo-schema-jee-5 jar:
ConnectorDocument$Facty.class
ConnectorDocument.class
ConnectorType$Factory.class
ConnectorType.class
   Have they been renamed/moved?

Thanks
Anita

--- anita kulshreshtha [EMAIL PROTECTED] wrote:


--- David Jencks [EMAIL PROTECTED] wrote:



On Jan 8, 2007, at 9:20 PM, anita kulshreshtha wrote:


   Geronimo-web-2.5-builder uses geronimo-web-builder as a

dependency.

Yikes!!

It brings in geronimo-servlet_2.4_spec and

geronimo-schema-j2ee_1.4

as

follows:
web-builder - geronimo-servlet_2.4_spec
  naming-builder -- j2ee-schema --
geronimo-schema-j2ee_1.4
Should naming-builder be changed to use 1.5?


yes.


Should we remove
dependency on web-builder and move all the stuff to

web-2.5-builder?

Very definitely!!  It looks like both the jetty and tomcat

builders



are already using the web25 AbstractWebBuilder so there should

be

no


problems there.

Can you do this?  Thanks for noticing this problem!!!


Sure..

Anita



thanks
david jencks



Thanks
Anita

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com






__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com




__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com










__



__
Yahoo! Music Unlimited
Access over 1 million songs.
http://music.yahoo.com/unlimited








__ 
__

Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index

Re: ClassLoader, JNDI and Dependency views in console

2007-01-11 Thread David Jencks



On Jan 11, 2007, at 2:39 AM, Rakesh Midha wrote:


Hello Chris,

Is there some specific scenerio where you are getting java heap  
space error.


What I am guessing is that there can be a scenerio where  
classloaders are cyclic. Is it possible, that

Classloader C1 is a parent of  Classloader C2
Classloader C2 is a parent of  Classloader C3
Classloader C3 is a parent of  Classloader C1


That's definitely not allowed.  The classloaders form a directed  
acyclic graph.


thanks
david jencks



If it is a possible, I need to figure out a way to know it and make  
changes in tree, else it will continue filling the tree in cyclic  
order.


Anyone please let me know if the above scenerio is allowed or not.  
(If it is allowed how is classes loaded, it will continue looking  
for class in cyclic order forever and never load it.)


Thanks
Rakesh

On 1/11/07, Rakesh Midha [EMAIL PROTECTED] wrote:
Oh I didnt see the JavaHeap space error about, let me check it out.
thanks
Rakesh


On 1/11/07, Christopher M. Cardona  [EMAIL PROTECTED] wrote:
Kevan,

FYI, I updated https://issues.apache.org/jira/browse/GERONIMO-2689 to
include a patch that will fix the javascript error. You should be able
to view the new portlets at least. Please let me know if you still get
problems.

Best wishes,
chris

Kevan Miller wrote:

 On Jan 10, 2007, at 2:37 PM, Christopher M. Cardona wrote:

 Hi Rakesh,

 I was able to run the new portlets using trunk rev494034 but needed
 to change all view.jsps because I get javascript errors related to
 your calls to dojo.require(). The console uses Dojo 0.4.1 right now
 and I'm guessing you used a different version during development.
 Some widget names changed in 0.4.1.

 I'm getting a different problem this time using the ClassLoader
 viewer. I get javax.servlet.ServletException: Java heap space:

 I've seen this error, also. None of the views were working for me.
 Wasn't sure if it was a Safari issue or something else. Rakesh, can
 you take a look at these issues (javascript errors and memory
 consumption by ClassLoader viewer)?

 Paul,
 Are you suggesting that we should start architecting the console  
to be

 more pluggable? Or suggesting that Rakesh rewrite these viewers?

 --kevan

[jira] Updated: (GERONIMO-2689) New View for JNDI name in all the contexts

2007-01-11 Thread Rakesh Midha (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh Midha updated GERONIMO-2689:
---

Attachment: G2689-2690-2691_updated.patch

 New View for JNDI name in all the contexts
 --

 Key: GERONIMO-2689
 URL: https://issues.apache.org/jira/browse/GERONIMO-2689
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.0
 Environment: Any
Reporter: Rakesh Midha
 Assigned To: Kevan Miller
 Fix For: 2.0

 Attachments: allviews.patch, common.patch, G2689-2690-2691.patch, 
 G2689-2690-2691_updated.patch, jndi.gif, jndiview2689.patch, navigation.gif


 So many times we hit the Exception NamingNotFound, most of the times it 
 happens because of user error, missing references, wrong names or path or 
 user working in different context and system looking in some other context.
 I think it would be nice if in a console we can have a view of what all names 
 are binded or available in contexts of each application / module or component.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (GERONIMO-2689) New View for JNDI name in all the contexts

2007-01-11 Thread Rakesh Midha (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463908
 ] 

Rakesh Midha commented on GERONIMO-2689:



minor change in all patch, check for null J2EE

 New View for JNDI name in all the contexts
 --

 Key: GERONIMO-2689
 URL: https://issues.apache.org/jira/browse/GERONIMO-2689
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.0
 Environment: Any
Reporter: Rakesh Midha
 Assigned To: Kevan Miller
 Fix For: 2.0

 Attachments: allviews.patch, common.patch, G2689-2690-2691.patch, 
 G2689-2690-2691_updated.patch, jndi.gif, jndiview2689.patch, navigation.gif


 So many times we hit the Exception NamingNotFound, most of the times it 
 happens because of user error, missing references, wrong names or path or 
 user working in different context and system looking in some other context.
 I think it would be nice if in a console we can have a view of what all names 
 are binded or available in contexts of each application / module or component.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Geronimo Axis2 Integration


Lin,

Please go ahead and upload the patch and add the stack trace in the comments.

thanks,
dims

On 1/11/07, Lin Sun [EMAIL PROTECTED] wrote:

Hi Lasantha,

I've been doing some integration test and build (enable the four modules in
modules\pom.xml and configs\pom.xml) yesterday and I found that I am having
trouble to start the axis2-deployer during the start of the server.  Is that
why you didn't update modules\pom.xml for the 2 modules?

I haven't been able to figure out the fix yet that is why I didn't submit
the patch yet. I'll keep looking into it.

Lin

-Original Message-
From: Lasantha Ranaweera [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 11, 2007 12:55 AM
To: dev@geronimo.apache.org
Subject: Re: Geronimo Axis2 Integration

Hi Lin,

Sorry for the late reply. I hope Dims has answered all your problems.
Let us know when you submit your patch too. ;-)

Thanks,
Lasantha
Lin Sun wrote:
 Hi Lasantha,

 This is great!  Thanks.  I have been also looking into Axis2 integration
w/
 G lately and started w/ the CXF integration code.  The work I've done is
 similar as what you have, except that I also created config dir for axis2
 and axis2-deployer.  I'll submit that as a patch today.

 By looking at your patch, how did you get the jaxb generated code?  I
 haven't been figured out how yet so I had planned to use the xmlbean
 generated code, similar as Axis1.

 Since there are some common code between CXF and Axis integration, I think
 it would be good to have one portInfo, parseWebServiceDescriptor at the
 Geronimo webservices level.

 Lin

 -Original Message-
 From: Lasantha Ranaweera [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, January 10, 2007 2:30 AM
 To: dev@geronimo.apache.org
 Subject: Geronimo Axis2 Integration

 Hi,

 The initial implementation of the Axis2 integration with Geronimo
 uploaded in to the JIRA (Geronimo-2717). Most of the source code is
 taken out from the CXF project of  the Geronimo and it is only a maven2
 skeleton.

 I am expecting some help from person who knows Axis2 to implement
 Axis2WebServiceContainer.java class and hoping to contribute Geronimo in
 this area.

 Thanks,
 Lasantha Ranaweera








--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

Re: G specific annotations for 2.0, XDoclet or 175?

Is this issue still on the table?  I haven't seen any specifics.  In  
general I'd prefer to stay away from G specific stuff and leave them  
in deployment plans.  However, if we make them available they should  
be totally optional and users can make their own choices.


On Nov 29, 2006, at 11:18 AM, Sachin Patel wrote:

What are people's thoughts on annotation support we should provide  
in Geronimo 2.0? I'm not referring to the spec annotations, but  
container specific annotations (configuration in our g-deployment  
plans).  From a users perspective, our deployment plans are massive  
and one of the options to simply using them is through annotations.


Is this something people agree on?

If so, then we need to have the XDoclet / JSR-175 debate.  From my  
viewpoint, XDoclet is a legacy technology with the introduction of  
JSR-175.  There are misconceptions that XDoclet still plays a role  
in that its purpose is a code-generation facility and JSR-175  
cannot be used for this purpose is not the case.  With JSR-175 and  
Sun's APT code/xml generation can be done as well.  (Even though  
its much more complex to do).  I'd like to provide XDoclet support  
in Geronimo 2.0 as its the easier solution, however my concern is  
that JEE 5 Developers will not want to deal with mixed type  
annotations.  Do people see this as a valid concern?  Or should our  
approach be Geronimo Specific 175 Annotations, that can either  
generate xml or  introspected during runtime as an alternative  
dealing directly with the deployment plans.


-sachin




Matt Hogstrom
[EMAIL PROTECTED]

Console config failed to start (formerly : webservices-testsuite failure)

2007-01-11 Thread Prasad Kashyap


Srinivas,

Your console config failed to start. It doesn't seem to be related to
the webservices-testsuite.

I suspect you may be encountering the long-path problem on windows.

By default, the geronimo-maven-plugin will unpack the Geronimo server
into the target directory of the project invoking it. So in your case,
it would be under
C:\APACHE\geronimo\testsuite\webservices-testsuite\target. Prepend
this to the already long path that we have and you'll have the long
path problem.

Can you please try the following command from your
webservices-testsuite instead-
$mvn -DinstallDirectory=c:\apache

Cheers
Prasad



On 1/10/07, Davanum Srinivas [EMAIL PROTECTED] wrote:

Here i go again on a wild goose chase :( Anyone have a clue?

- Fresh svn checkout of trunk
- nuked .m2 repo
- mvn install from root works fine.
- mvn install from testsuite\webservices-testsuite throws the
following exception:

Booting Geronimo Kernel (in Java 1.5.0_10)...
20:47:55,187 INFO  [root] --
20:47:55,187 INFO  [root] Started Logging Service
20:47:55,187 INFO  [root] Runtime Information:
20:47:55,187 INFO  [root]   Install Directory =
C:\APACHE\geronimo\testsuite\webservices-testsuite\target\geronimo-jetty6-jee5-2.0-SNAPSHOT
20:47:55,187 INFO  [root]   JVM in use = Sun Microsystems Inc. Java 1.5.0_10
20:47:55,187 INFO  [root] Java Information:
20:47:55,187 INFO  [root]   System property [java.runtime.name]  =
Java(TM) 2 Runtime Environment, Standard Edition
20:47:55,187 INFO  [root]   System property [java.runtime.version]  =
1.5.0_10-b03
20:47:55,187 INFO  [root]   System property [os.name] = Windows XP
20:47:55,187 INFO  [root]   System property [os.version]  = 5.1
20:47:55,203 INFO  [root]   System property [sun.os.patch.level]  =
Service Pack 2
20:47:55,203 INFO  [root]   System property [os.arch] = x86
20:47:55,203 INFO  [root]   System property [java.class.version]  = 49.0
20:47:55,203 INFO  [root]   System property [locale]  = en_US
20:47:55,203 INFO  [root]   System property [unicode.encoding]=
UnicodeLittle
20:47:55,203 INFO  [root]   System property [file.encoding]   = Cp1252
20:47:55,203 INFO  [root]   System property [java.vm.name]=
Java HotSpot(TM) Client VM
20:47:55,203 INFO  [root]   System property [java.vm.vendor]  =
Sun Microsystems Inc.
20:47:55,203 INFO  [root]   System property [java.vm.version] = 1.5.0_10-b03
20:47:55,203 INFO  [root]   System property [java.vm.info]= mixed mode
20:47:55,203 INFO  [root]   System property [java.home]   = C:\JDK15\jre
20:47:55,203 INFO  [root]   System property [java.classpath]  = null
20:47:55,203 INFO  [root]   System property [java.library.path]   =
C:\JDK15\jre\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\JDK15\BIN;C:\MAVEN\BIN;C:\MAVEN-2.0.4\BIN;C:\JDK15\BIN;C:\Program
Files\Support Tools 2\;C:\Program
Files\ThinkPad\Utilities;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program
Files\ATI Technologies\ATI Control Panel;C:\WINDOWS\Downloaded Program
Files;C:\Program Files\PC-Doctor for
Windows\services;C:\BIN;C:\SVN\BIN;C:\MAVEN\BIN;C:\ANT\BIN;C:\CYGWIN\BIN;C:\Program
Files\Support Tools\;C:\WINCVS\CVSNT;C:\Program
Files\QuickTime\QTSystem\;C:\Program
Files\ThinkPad\ConnectUtilities;C:\Program Files\Common
Files\Lenovo;C:\Program Files\Lenovo\Client Security
Solution;C:\Program Files\Common
Files\Adobe\AGL;C:\jwsdp-2.0\jwsdp-shared\bin;
20:47:55,218 INFO  [root]   System property [java.endorsed.dirs]  =
C:\JDK15\jre\lib\endorsed;C:\APACHE\geronimo\testsuite\webservices-testsuite\target\geronimo-jetty6-jee5-2.0-SNAPSHOT\lib\endorsed
20:47:55,218 INFO  [root]   System property [java.ext.dirs]   =
C:\JDK15\jre\lib\ext;C:\APACHE\geronimo\testsuite\webservices-testsuite\target\geronimo-jetty6-jee5-2.0-SNAPSHOT\lib\ext
20:47:55,218 INFO  [root]   System property [sun.boot.class.path] =
C:\APACHE\geronimo\testsuite\webservices-testsuite\target\geronimo-jetty6-jee5-2.0-SNAPSHOT\lib\endorsed\xercesImpl-2.8.1.jar;C:\APACHE\geronimo\testsuite\webservices-testsuite\target\geronimo-jetty6-jee5-2.0-SNAPSHOT\lib\endorsed\yoko-rmi-spec-1.0-incubating-M2-SNAPSHOT.jar;C:\APACHE\geronimo\testsuite\webservices-testsuite\target\geronimo-jetty6-jee5-2.0-SNAPSHOT\lib\endorsed\yoko-spec-corba-1.0-incubating-M2-SNAPSHOT.jar;C:\JDK15\jre\lib\rt.jar;C:\JDK15\jre\lib\i18n.jar;C:\JDK15\jre\lib\sunrsasign.jar;C:\JDK15\jre\lib\jsse.jar;C:\JDK15\jre\lib\jce.jar;C:\JDK15\jre\lib\charsets.jar;C:\JDK15\jre\classes
20:47:55,218 INFO  [root] --
Module  1/25 org.apache.geronimo.configs/rmi-naming/2.0-SNAPSHOT/car
  started in  2.063s
Module  2/25 org.apache.geronimo.configs/j2ee-server/2.0-SNAPSHOT/car
  started in   .297s
Module  3/25 org.apache.geronimo.configs/transaction-jta11/2.0-SNAPSHOT/car
 started in   .609s
Module  4/25 org.apache.geronimo.configs/j2ee-security/2.0-SNAPSHOT/car

Re: Assemblies assemblies everywhere and which one to ship?


Geir,

What are the specifics around claiming certification?  My  
understanding is that to claim an assembly as certified that specific  
configuration is tested and made available.  Apart from that we can  
ship any permutation but cannot claim those as certified.  So if we  
TCK tested:


Tomcat Axis OpenJPA and
Jetty CXF Cayenne

then

Tomcat CXF OpenJPA would not be considered a certified release.   It  
would most likely work but we couldn't claim that specific assembly  
as certified.


Is that correct?


On Jan 11, 2007, at 12:53 AM, David Jencks wrote:



On Jan 11, 2007, at 12:01 AM, Jarek Gawor wrote:

How hard is it to switch between the different assemblies once the  
TCK

testing environment is setup? If it is easy enough, maybe we should
first test all 8 assemblies and then concentrate on only those that
pass the most tests.


I guess I have the opposite point of view :-).  I suspect if we get  
all the tests passing for each component in one configuration, they  
will pretty much pass in all the other configurations, e.g. if cxf  
+ jetty + openjpa works then cxf + tomcat + cayenne will work too,  
so the main chore will be to verify this.  If it's simple enough to  
run the tck this won't be impossibly difficult to test all the  
combinations, just take a bunch of machine time.


thanks
david jencks



Jarek

On 1/9/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
I think testing say (Tomcat+Axis2+OpenJPA) and (Jetty+CXF 
+Cayenne) is
enough. All components should be tested at least once. If we get  
time,

we could do more :)

-- dims

On 1/8/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
 On Jan 7, 2007, at 9:38 PM, David Jencks wrote:

  On Jan 7, 2007, at 11:33 PM, Matt Hogstrom wrote:
 
  I was thinking about M2 this weekend and was considering  
many of
  the challenges we face in putting out certified releases.   
Up till

  now the number of permutations has been pretty limited and that
  has been Jetty and Tomcat.  With Java EE 5.0 life is no longer
  that simple.  Here are the choices I know of today:
 
  Web Container (Tomcat / Jetty)
  WebServices (Axis 2 / CXF)
  EJB 3.0 Persistence (OpenJPA / Cayenne)
 
  I think this makes 6 different assemblies and of course 6  
separate

  certification efforts.  Perhaps we can do this and perhaps we
  can't.  Based on where projects are at and their desire to
  participate in helping to integrate (and do TCK testing :).
 
  ummm 2 * 2 * 2 == 8
 
  I could be very wrong but I thought that the cmp 2.1 support in
  openejb3 was relying on openjpa-specific features.  If so I  
wonder
  if it will be tricky to run the tck on other jpa  
implementations.


 Well, we depend on being able to listen to events on the EM which
 there is no spec interface for.  I'm sure Cayanne has and  
interface
 that can provide us with the events, and when they send us the  
info

 we can add a hook for their Impl.

 In general, I think we should just pick a single JPA  
implementation
 to ship with G because it is very easy for an application to  
request

 a different implementation using specification defined properties.

 Of course that will leave us with 4 javaee assemblies and 2  
minimal

 assemblies.

 -dain



--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service  
Developers)







Matt Hogstrom
[EMAIL PROTECTED]

[jira] Commented: (GERONIMO-2716) Create javaee 5 test jars for j2ee-builder tests

2007-01-11 Thread Prasad Kashyap (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463915
 ] 

Prasad Kashyap commented on GERONIMO-2716:
--

Anita, on second thoughts, I wonder if we should have left the schemas and 
dependencies in the  j2ee_1.3 and j2ee_1.4 apps as is. We could have used this 
as a regression test app to ensure that we are backward compatible. We could 
even beef up those apps with deprecated (if any) j2ee features to see how we 
handle it on the jee5 server.

Anyway, you have your new jee5 app to test the latest schemas and specs.

What say you ?

 Create javaee 5 test jars for j2ee-builder tests
 

 Key: GERONIMO-2716
 URL: https://issues.apache.org/jira/browse/GERONIMO-2716
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 2.0-M2
 Environment: All
Reporter: Anita Kulshreshtha
 Assigned To: Anita Kulshreshtha
 Fix For: 2.0-M2

 Attachments: testsupport.diff, testsupport.diff


 Create ear, ejb-jar, rar, and war files for j2ee-builder tests that use 
 javaee 5 schema. Use servlet 2.5 and jsp 2.1 specs for all wars.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: NMS byte order for doubles

2007-01-11 Thread Hiram Chirino


Could you attach your patch to that issue and make sue your click the
Grant license to ASF for inclusion in ASF works (as per the Apache
Software License ) option.

Thanks.

On 1/11/07, rousseau [EMAIL PROTECTED] wrote:


Sure. It's the same as AMQ-866. Comment added on that case.

thx
Steve



Hiram Chirino wrote:

 Hi Steve,

 I would be happy to apply your patch but could you open a JIRA issue at:
 http://issues.apache.org/activemq/browse/AMQ

 And attach your patch to that so that we have it properly documented
 that you want to contribute your patch to the ASF.

 Thanks!
 Hiram

 On 1/10/07, rousseau [EMAIL PROTECTED] wrote:

 I've found a byte-order problem sending a double from Java ActiveMQ to a
 NMS/CSharp receiver:

 (NMS) ActiveMQ.OpenWire.OpenWireBinaryReader has no definition for
 ReadDouble(), and by default calls the MS .NET BinaryReader.ReadDouble()
 which reads the bytes in the wrong order. Here is the fix:

 add a new method to OpenWireBinaryReader.cs:

 public override double ReadDouble()
 {
 return EndianSupport.SwitchEndian(base.ReadBytes(8));
 }

 add a new method to EndianSupport.cs:

 public static double SwitchEndian(byte[] bytes)
 {
 //Reverse byte array
 byte[] reverse = new byte[8];
 reverse[0] = bytes[7];
 reverse[1] = bytes[6];
 reverse[2] = bytes[5];
 reverse[3] = bytes[4];
 reverse[4] = bytes[3];
 reverse[5] = bytes[2];
 reverse[6] = bytes[1];
 reverse[7] = bytes[0];
 BinaryReader br = new BinaryReader(new
 MemoryStream(reverse));
 return br.ReadDouble();
 }

 If anyone knows a cleaner way of doing this, please let me know.

 thx
 /Steve
 --
 View this message in context:
 http://www.nabble.com/NMS-byte-order-for-doubles-tf2951266.html#a8253895
 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.




 --
 Regards,
 Hiram

 Blog: http://hiramchirino.com



--
View this message in context: 
http://www.nabble.com/NMS-byte-order-for-doubles-tf2951266.html#a8273932
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Updated: (GERONIMO-2722) enable commons-logging in tomcat module

2007-01-11 Thread Paul McMahan (JIRA)

[
https://issues.apache.org/jira/browse/GERONIMO-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paul McMahan updated GERONIMO-2722:
---

Description: Tomcat 6 does not support log4j by default. Instead it
provides support for log4j via an extras module. Geronimo needs to enable
this extras module so that tomcat logging can be configured via
var/log/server-log4j.properties, and so that INFO level messages are not shown
in the server's output window by default. (was: Tomcat 6 does not support
commons logging by default. Instead it provides support for commons logging
via an extras module. Geronimo needs to enable this extras module so that
tomcat logging can be configured via var/log/server-log4j.properties, and so
that INFO level messages are not shown in the server's output window by
default.)

enable commons-logging in tomcat module
---

Key: GERONIMO-2722
URL: https://issues.apache.org/jira/browse/GERONIMO-2722
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: Tomcat
Affects Versions: 2.0-M1
Reporter: Paul McMahan
Assigned To: Paul McMahan
Fix For: 2.0-M2

Tomcat 6 does not support log4j by default. Instead it provides support for
log4j via an extras module. Geronimo needs to enable this extras module so
that tomcat logging can be configured via var/log/server-log4j.properties,
and so that INFO level messages are not shown in the server's output window
by default.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (GERONIMO-2716) Create javaee 5 test jars for j2ee-builder tests

2007-01-11 Thread Anita Kulshreshtha (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463926
 ] 

Anita Kulshreshtha commented on GERONIMO-2716:
--

Prasad,
I made these changes:
schemas:
geronimo-schemas - 1.1 was probalbly an error, hence I changed application 
and deployment to 1.2.
DTD - I left them As Is in test-deployment-j2ee-1.3.
j2ee - web-app  2.3.dtd  in test-deployment-j2ee-1.4 was also probably an 
error, hence I chaged it to use 2.4 schema.

dependency :
  If the goal is to have old DDs working in the latest server, we would 
have to use servlet 2.5 and jsp 2.1.  But if it is breaking something, you can 
change it back.
 I hope that soon I will be successful in banishing servlet 2.4, jsp 2.0 
antd geronimo-schema-j2ee-1.4 jar! 

 Create javaee 5 test jars for j2ee-builder tests
 

 Key: GERONIMO-2716
 URL: https://issues.apache.org/jira/browse/GERONIMO-2716
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 2.0-M2
 Environment: All
Reporter: Anita Kulshreshtha
 Assigned To: Anita Kulshreshtha
 Fix For: 2.0-M2

 Attachments: testsupport.diff, testsupport.diff


 Create ear, ejb-jar, rar, and war files for j2ee-builder tests that use 
 javaee 5 schema. Use servlet 2.5 and jsp 2.1 specs for all wars.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Closed: (GERONIMO-2722) enable commons-logging in tomcat module

2007-01-11 Thread Paul McMahan (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul McMahan closed GERONIMO-2722.
--

Resolution: Fixed

 enable commons-logging in tomcat module
 ---

 Key: GERONIMO-2722
 URL: https://issues.apache.org/jira/browse/GERONIMO-2722
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Tomcat
Affects Versions: 2.0-M1
Reporter: Paul McMahan
 Assigned To: Paul McMahan
 Fix For: 2.0-M2


 Tomcat 6 does not support log4j by default.  Instead it provides support for 
 log4j via an extras module.  Geronimo needs to enable this extras module so 
 that tomcat logging can be configured via var/log/server-log4j.properties, 
 and so that INFO level messages are not shown in the server's output window 
 by default.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQCPP-25) Bus error on Solaris OS from DataInput and DataOutput streams

[
https://issues.apache.org/activemq/browse/AMQCPP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37891
]

Albert Strasheim commented on AMQCPP-25:

Re: your first question. As we tried to debug this issue, we added some printfs
to check values of variables and we noticed that the bugs would go away.
Basically, any bit of code that changes the way the compiler optimizes the
function can make the bug disappear (but it's still a bug). char c = new char,
delete c is just the smallest bit of code we could come up with that would make
the bug disappear.

As for how to fix this, I did some further reading.

Check this page:

http://www.cellperformance.com/mike_acton/2006/05/demystifying_the_restrict_keyw.html

In the summary they say:

... Enable strict aliasing related warnings with -Wstrict-aliasing, but do not
expect to be warned in all cases.

Most of the GCC versions I've tried *don't* warn on the strict aliasing
violations in the current AMQCPP code. If we want to leave strict aliasing
enabled, we'll have to give the code a quick review and carefully look at any
future changes for strict aliasing bugs, since the compiler won't necessarily
warn us.

The Python folks went for the opposite approach: any C module you build with
distuils is compiled with -fno-strict-aliasing, as people were probably running
into this problem frequently.

If AMQCPP goes the -fno-strict-aliasing route, we'll still have to check that
we don't leak code that requires this option outside of the library.
Fortunately this is easy -- put function implementations in cpp files so that
users don't compile bits of the library when compiling their code. Linking
against a library is fine, regardless of its strict aliasing flags.

Of course if you have any templated stuff, you should probably make sure to not
write code that depends on strict aliasing flags.

Bus error on Solaris OS from DataInput and DataOutput streams
-

Key: AMQCPP-25
URL: https://issues.apache.org/activemq/browse/AMQCPP-25
Project: ActiveMQ C++ Client
Issue Type: Bug
Components: CMS Impl
Affects Versions: 1.1
Environment: Solaris 10 OS
Reporter: Timothy Bish
Assigned To: Timothy Bish
Priority: Minor
Fix For: 1.1

Attachments: optobug.cpp

Due to misaligned memory reads, there is a bus error that can occur in using
the new DataInputStream and DataOutputStream classes.

Re: Console config failed to start (formerly : webservices-testsuite failure)

2007-01-11 Thread anita kulshreshtha

Dims,
   I also noticed a while ago that the server was being unpacked in a
directory with name longer than 10 chars. I thought I was the only one
using Windows! You can do a grep -r for any string in
C:\APACHE\geronimo\testsuite\webservices-testsuite\target directory and
it will start complaining about all the files with long names..

Thanks
Anita

--- Prasad Kashyap [EMAIL PROTECTED] wrote:

 Srinivas,
 
 Your console config failed to start. It doesn't seem to be related to
 the webservices-testsuite.
 
 I suspect you may be encountering the long-path problem on windows.
 
 By default, the geronimo-maven-plugin will unpack the Geronimo server
 into the target directory of the project invoking it. So in your
 case,
 it would be under
 C:\APACHE\geronimo\testsuite\webservices-testsuite\target. Prepend
 this to the already long path that we have and you'll have the long
 path problem.
 
 Can you please try the following command from your
 webservices-testsuite instead-
 $mvn -DinstallDirectory=c:\apache
 
 Cheers
 Prasad
 
 
 
 On 1/10/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
  Here i go again on a wild goose chase :( Anyone have a clue?
 
  - Fresh svn checkout of trunk
  - nuked .m2 repo
  - mvn install from root works fine.
  - mvn install from testsuite\webservices-testsuite throws the
  following exception:
 
  Booting Geronimo Kernel (in Java 1.5.0_10)...
  20:47:55,187 INFO  [root]
 --
  20:47:55,187 INFO  [root] Started Logging Service
  20:47:55,187 INFO  [root] Runtime Information:
  20:47:55,187 INFO  [root]   Install Directory =
 

C:\APACHE\geronimo\testsuite\webservices-testsuite\target\geronimo-jetty6-jee5-2.0-SNAPSHOT
  20:47:55,187 INFO  [root]   JVM in use = Sun Microsystems Inc. Java
 1.5.0_10
  20:47:55,187 INFO  [root] Java Information:
  20:47:55,187 INFO  [root]   System property [java.runtime.name]  =
  Java(TM) 2 Runtime Environment, Standard Edition
  20:47:55,187 INFO  [root]   System property [java.runtime.version] 
 =
  1.5.0_10-b03
  20:47:55,187 INFO  [root]   System property [os.name] =
 Windows XP
  20:47:55,187 INFO  [root]   System property [os.version]  =
 5.1
  20:47:55,203 INFO  [root]   System property [sun.os.patch.level]  =
  Service Pack 2
  20:47:55,203 INFO  [root]   System property [os.arch] =
 x86
  20:47:55,203 INFO  [root]   System property [java.class.version]  =
 49.0
  20:47:55,203 INFO  [root]   System property [locale]  =
 en_US
  20:47:55,203 INFO  [root]   System property [unicode.encoding]=
  UnicodeLittle
  20:47:55,203 INFO  [root]   System property [file.encoding]   =
 Cp1252
  20:47:55,203 INFO  [root]   System property [java.vm.name]=
  Java HotSpot(TM) Client VM
  20:47:55,203 INFO  [root]   System property [java.vm.vendor]  =
  Sun Microsystems Inc.
  20:47:55,203 INFO  [root]   System property [java.vm.version] =
 1.5.0_10-b03
  20:47:55,203 INFO  [root]   System property [java.vm.info]=
 mixed mode
  20:47:55,203 INFO  [root]   System property [java.home]   =
 C:\JDK15\jre
  20:47:55,203 INFO  [root]   System property [java.classpath]  =
 null
  20:47:55,203 INFO  [root]   System property [java.library.path]   =
 

C:\JDK15\jre\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\JDK15\BIN;C:\MAVEN\BIN;C:\MAVEN-2.0.4\BIN;C:\JDK15\BIN;C:\Program
  Files\Support Tools 2\;C:\Program
 

Files\ThinkPad\Utilities;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program
  Files\ATI Technologies\ATI Control Panel;C:\WINDOWS\Downloaded
 Program
  Files;C:\Program Files\PC-Doctor for
 

Windows\services;C:\BIN;C:\SVN\BIN;C:\MAVEN\BIN;C:\ANT\BIN;C:\CYGWIN\BIN;C:\Program
  Files\Support Tools\;C:\WINCVS\CVSNT;C:\Program
  Files\QuickTime\QTSystem\;C:\Program
  Files\ThinkPad\ConnectUtilities;C:\Program Files\Common
  Files\Lenovo;C:\Program Files\Lenovo\Client Security
  Solution;C:\Program Files\Common
  Files\Adobe\AGL;C:\jwsdp-2.0\jwsdp-shared\bin;
  20:47:55,218 INFO  [root]   System property [java.endorsed.dirs]  =
 

C:\JDK15\jre\lib\endorsed;C:\APACHE\geronimo\testsuite\webservices-testsuite\target\geronimo-jetty6-jee5-2.0-SNAPSHOT\lib\endorsed
  20:47:55,218 INFO  [root]   System property [java.ext.dirs]   =
 

C:\JDK15\jre\lib\ext;C:\APACHE\geronimo\testsuite\webservices-testsuite\target\geronimo-jetty6-jee5-2.0-SNAPSHOT\lib\ext
  20:47:55,218 INFO  [root]   System property [sun.boot.class.path] =

Re: webservices-testsuite failure

2007-01-11 Thread Prasad Kashyap


http://mail-archives.apache.org/mod_mbox/geronimo-dev/200701.mbox/[EMAIL 
PROTECTED]

Cheers
Prasad


On 1/11/07, Kevan Miller [EMAIL PROTECTED] wrote:


On Jan 10, 2007, at 8:55 PM, Davanum Srinivas wrote:

 Here i go again on a wild goose chase :( Anyone have a clue?

 - Fresh svn checkout of trunk
 - nuked .m2 repo
 - mvn install from root works fine.
 - mvn install from testsuite\webservices-testsuite throws the
 following exception:

Dims,
I've not yet run any testsuite tests. Looks like webservices was just
added.

Prasad,
Were these tests working?

--kevan

ApacheDS - LDAP - Geronimo Plugins

2007-01-11 Thread Hernan Cunico


Howdy,
I've been playing around with the integrated LDAP from the begining. It got 
pulled out from the build when we came out with Geronimo plugins (somewhere 
around v1.1.1)
Now I see it back in the branch for v1.2 and trunk, this feature is already 
in the build however it still is available for download/install as a plugin.

So the question is what do we want to do with it, offer LDAP as part of the 
dist or separate as a plugin?

Another question is, if I already see it available in the build (fresh from 
trunk) why it still shows up as available for install in the Install Plugin 
portlet?
(it will fail to install since the destination already exist)

Cheers!
Hernan

RE: ApacheDS - LDAP - Geronimo Plugins

2007-01-11 Thread Jeff Genender

Until we have an official Apache plugin repo, I think we should leave it in the 
distro.  I wrote the integration as an Apache piece of code and thus I feel 
that should be the official distribution channel.

Jeff
-Original Message-
From: Hernan Cunico [EMAIL PROTECTED]
To: dev list dev@geronimo.apache.org
Sent: 1/11/2007 10:02 AM
Subject: ApacheDS - LDAP - Geronimo Plugins

Howdy,
I've been playing around with the integrated LDAP from the begining. It got 
pulled out from the build when we came out with Geronimo plugins (somewhere 
around v1.1.1)
Now I see it back in the branch for v1.2 and trunk, this feature is already 
in the build however it still is available for download/install as a plugin.

So the question is what do we want to do with it, offer LDAP as part of the 
dist or separate as a plugin?

Another question is, if I already see it available in the
[truncated by sender]

Re: Assemblies assemblies everywhere and which one to ship?


Matt,

I don't think there is any requirement of exact combination of
components for TCK compliance. AFAIK, we need to ship the exact code
we tested, that's it. FWIW, it's self-certification as well :) So i am
happy if all the components are put thru the grinder at least once.

thanks,
-- dims

On 1/11/07, Matt Hogstrom [EMAIL PROTECTED] wrote:

Geir,

What are the specifics around claiming certification?  My
understanding is that to claim an assembly as certified that specific
configuration is tested and made available.  Apart from that we can
ship any permutation but cannot claim those as certified.  So if we
TCK tested:

Tomcat Axis OpenJPA and
Jetty CXF Cayenne

then

Tomcat CXF OpenJPA would not be considered a certified release.   It
would most likely work but we couldn't claim that specific assembly
as certified.

Is that correct?


On Jan 11, 2007, at 12:53 AM, David Jencks wrote:


 On Jan 11, 2007, at 12:01 AM, Jarek Gawor wrote:

 How hard is it to switch between the different assemblies once the
 TCK
 testing environment is setup? If it is easy enough, maybe we should
 first test all 8 assemblies and then concentrate on only those that
 pass the most tests.

 I guess I have the opposite point of view :-).  I suspect if we get
 all the tests passing for each component in one configuration, they
 will pretty much pass in all the other configurations, e.g. if cxf
 + jetty + openjpa works then cxf + tomcat + cayenne will work too,
 so the main chore will be to verify this.  If it's simple enough to
 run the tck this won't be impossibly difficult to test all the
 combinations, just take a bunch of machine time.

 thanks
 david jencks


 Jarek

 On 1/9/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
 I think testing say (Tomcat+Axis2+OpenJPA) and (Jetty+CXF
 +Cayenne) is
 enough. All components should be tested at least once. If we get
 time,
 we could do more :)

 -- dims

 On 1/8/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
  On Jan 7, 2007, at 9:38 PM, David Jencks wrote:
 
   On Jan 7, 2007, at 11:33 PM, Matt Hogstrom wrote:
  
   I was thinking about M2 this weekend and was considering
 many of
   the challenges we face in putting out certified releases.
 Up till
   now the number of permutations has been pretty limited and that
   has been Jetty and Tomcat.  With Java EE 5.0 life is no longer
   that simple.  Here are the choices I know of today:
  
   Web Container (Tomcat / Jetty)
   WebServices (Axis 2 / CXF)
   EJB 3.0 Persistence (OpenJPA / Cayenne)
  
   I think this makes 6 different assemblies and of course 6
 separate
   certification efforts.  Perhaps we can do this and perhaps we
   can't.  Based on where projects are at and their desire to
   participate in helping to integrate (and do TCK testing :).
  
   ummm 2 * 2 * 2 == 8
  
   I could be very wrong but I thought that the cmp 2.1 support in
   openejb3 was relying on openjpa-specific features.  If so I
 wonder
   if it will be tricky to run the tck on other jpa
 implementations.
 
  Well, we depend on being able to listen to events on the EM which
  there is no spec interface for.  I'm sure Cayanne has and
 interface
  that can provide us with the events, and when they send us the
 info
  we can add a hook for their Impl.
 
  In general, I think we should just pick a single JPA
 implementation
  to ship with G because it is very easy for an application to
 request
  a different implementation using specification defined properties.
 
  Of course that will leave us with 4 javaee assemblies and 2
 minimal
  assemblies.
 
  -dain
 


 --
 Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
 Developers)




Matt Hogstrom
[EMAIL PROTECTED]






--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

Re: webservices-testsuite failure


Thanks Prasad!

On 1/11/07, Prasad Kashyap [EMAIL PROTECTED] wrote:

http://mail-archives.apache.org/mod_mbox/geronimo-dev/200701.mbox/[EMAIL 
PROTECTED]

Cheers
Prasad


On 1/11/07, Kevan Miller [EMAIL PROTECTED] wrote:

 On Jan 10, 2007, at 8:55 PM, Davanum Srinivas wrote:

  Here i go again on a wild goose chase :( Anyone have a clue?
 
  - Fresh svn checkout of trunk
  - nuked .m2 repo
  - mvn install from root works fine.
  - mvn install from testsuite\webservices-testsuite throws the
  following exception:

 Dims,
 I've not yet run any testsuite tests. Looks like webservices was just
 added.

 Prasad,
 Were these tests working?

 --kevan








--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

Re: Console config failed to start (formerly : webservices-testsuite failure)


Thanks Anita!

On 1/11/07, anita kulshreshtha [EMAIL PROTECTED] wrote:

Dims,
   I also noticed a while ago that the server was being unpacked in a
directory with name longer than 10 chars. I thought I was the only one
using Windows! You can do a grep -r for any string in
C:\APACHE\geronimo\testsuite\webservices-testsuite\target directory and
it will start complaining about all the files with long names..

Thanks
Anita

--- Prasad Kashyap [EMAIL PROTECTED] wrote:

 Srinivas,

 Your console config failed to start. It doesn't seem to be related to
 the webservices-testsuite.

 I suspect you may be encountering the long-path problem on windows.

 By default, the geronimo-maven-plugin will unpack the Geronimo server
 into the target directory of the project invoking it. So in your
 case,
 it would be under
 C:\APACHE\geronimo\testsuite\webservices-testsuite\target. Prepend
 this to the already long path that we have and you'll have the long
 path problem.

 Can you please try the following command from your
 webservices-testsuite instead-
 $mvn -DinstallDirectory=c:\apache

 Cheers
 Prasad



 On 1/10/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
  Here i go again on a wild goose chase :( Anyone have a clue?
 
  - Fresh svn checkout of trunk
  - nuked .m2 repo
  - mvn install from root works fine.
  - mvn install from testsuite\webservices-testsuite throws the
  following exception:
 
  Booting Geronimo Kernel (in Java 1.5.0_10)...
  20:47:55,187 INFO  [root]
 --
  20:47:55,187 INFO  [root] Started Logging Service
  20:47:55,187 INFO  [root] Runtime Information:
  20:47:55,187 INFO  [root]   Install Directory =
 

C:\APACHE\geronimo\testsuite\webservices-testsuite\target\geronimo-jetty6-jee5-2.0-SNAPSHOT
  20:47:55,187 INFO  [root]   JVM in use = Sun Microsystems Inc. Java
 1.5.0_10
  20:47:55,187 INFO  [root] Java Information:
  20:47:55,187 INFO  [root]   System property [java.runtime.name]  =
  Java(TM) 2 Runtime Environment, Standard Edition
  20:47:55,187 INFO  [root]   System property [java.runtime.version]
 =
  1.5.0_10-b03
  20:47:55,187 INFO  [root]   System property [os.name] =
 Windows XP
  20:47:55,187 INFO  [root]   System property [os.version]  =
 5.1
  20:47:55,203 INFO  [root]   System property [sun.os.patch.level]  =
  Service Pack 2
  20:47:55,203 INFO  [root]   System property [os.arch] =
 x86
  20:47:55,203 INFO  [root]   System property [java.class.version]  =
 49.0
  20:47:55,203 INFO  [root]   System property [locale]  =
 en_US
  20:47:55,203 INFO  [root]   System property [unicode.encoding]=
  UnicodeLittle
  20:47:55,203 INFO  [root]   System property [file.encoding]   =
 Cp1252
  20:47:55,203 INFO  [root]   System property [java.vm.name]=
  Java HotSpot(TM) Client VM
  20:47:55,203 INFO  [root]   System property [java.vm.vendor]  =
  Sun Microsystems Inc.
  20:47:55,203 INFO  [root]   System property [java.vm.version] =
 1.5.0_10-b03
  20:47:55,203 INFO  [root]   System property [java.vm.info]=
 mixed mode
  20:47:55,203 INFO  [root]   System property [java.home]   =
 C:\JDK15\jre
  20:47:55,203 INFO  [root]   System property [java.classpath]  =
 null
  20:47:55,203 INFO  [root]   System property [java.library.path]   =
 

C:\JDK15\jre\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\JDK15\BIN;C:\MAVEN\BIN;C:\MAVEN-2.0.4\BIN;C:\JDK15\BIN;C:\Program
  Files\Support Tools 2\;C:\Program
 

Files\ThinkPad\Utilities;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program
  Files\ATI Technologies\ATI Control Panel;C:\WINDOWS\Downloaded
 Program
  Files;C:\Program Files\PC-Doctor for
 

Windows\services;C:\BIN;C:\SVN\BIN;C:\MAVEN\BIN;C:\ANT\BIN;C:\CYGWIN\BIN;C:\Program
  Files\Support Tools\;C:\WINCVS\CVSNT;C:\Program
  Files\QuickTime\QTSystem\;C:\Program
  Files\ThinkPad\ConnectUtilities;C:\Program Files\Common
  Files\Lenovo;C:\Program Files\Lenovo\Client Security
  Solution;C:\Program Files\Common
  Files\Adobe\AGL;C:\jwsdp-2.0\jwsdp-shared\bin;
  20:47:55,218 INFO  [root]   System property [java.endorsed.dirs]  =
 

C:\JDK15\jre\lib\endorsed;C:\APACHE\geronimo\testsuite\webservices-testsuite\target\geronimo-jetty6-jee5-2.0-SNAPSHOT\lib\endorsed
  20:47:55,218 INFO  [root]   System property [java.ext.dirs]   =
 

C:\JDK15\jre\lib\ext;C:\APACHE\geronimo\testsuite\webservices-testsuite\target\geronimo-jetty6-jee5-2.0-SNAPSHOT\lib\ext
  20:47:55,218 INFO  [root]   System property [sun.boot.class.path] =

Re: ClassLoader, JNDI and Dependency views in console


On 1/10/07, Kevan Miller [EMAIL PROTECTED] wrote:


Paul,
Are you suggesting that we should start architecting the console to
be more pluggable? Or suggesting that Rakesh rewrite these viewers?


We've talked about architecting the console to be more pluggable and
I'm definitely in favor of that.  But until that effort gets underway
we still have the capability to make UIs pluggable into Geronimo by
implementing them as standalone webapps.  ca-helper is a good example
of this approach.   So really my question was whether or not Rakesh
would consider wrappering the viewers as webapps that can then be
installed as Geronimo plugins instead of integrating them directly
into the console as portlets.  If that's not going to work out then
I'm fine with Donald's suggestion of integrating in their current form
and making them into plugins later.  The viewers are definitely a
value contribution to Geronimo and I look forward to seeing them in
our next release.

Best wishes,
Paul

Re: [jira] Commented: (GERONIMO-2577) Geronimo cluster (Tomcat Version)cannot continue the HttpSession when current node is down.

2007-01-11 Thread Jeff Genender


 Jeff,
 How can we confirm if it is a Bug OR not supported Feature in Tomcat?

Ask on their lists.

Jeff

2.0 geronimo-qname_1.1_spec

Do we need to include qname anymore?  Looks like that is part of se 5  
now...


Anyone know?

--jason

[jira] Commented: (AMQ-1121) Kaha DB hangs on restart

2007-01-11 Thread Homer (JIRA)


[ 
https://issues.apache.org/activemq/browse/AMQ-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37893
 ] 

Homer commented on AMQ-1121:


I have run into a similar issue where AMQ gets hung on restart.  In my case, 
the KahaStore is stuck in an infinite loop because it finds two IndexItem 
objects from the file that point to each other.  It's a potential show stopper 
because there is no way to recover the data in the queue.

Here's a dump of the object variables from Eclipse:

itemIndexItem  (id=212) 

active  false   

keyFile 1   

keyOffset   153495  

keySize 61  

nextnull

nextItem612 

offset  765 

prevnull

previousItem51  

valueFile   1   

valueOffset 153561  

valueSize   468 



itemIndexItem  (id=240) 

active  false   

keyFile 1   

keyOffset   114687  

keySize 61  

nextnull

nextItem765 

offset  612 

prevnull

previousItem51  

valueFile   1   

valueOffset 114753  

valueSize   468 



 Kaha DB hangs on restart
 

 Key: AMQ-1121
 URL: https://issues.apache.org/activemq/browse/AMQ-1121
 Project: ActiveMQ
  Issue Type: Bug
  Components: Message Store
Affects Versions: 4.1.0
 Environment: Windows XP, NetApp
Reporter: Vadim Pesochinskiy
 Assigned To: Rob Davies
Priority: Blocker
 Fix For: 4.1.0


 I run a bunch or messages through AMQ, then restarted AMQ and it hangs. 
 Following are the last messages that I see. AMQ is not listening on the 
 configured port.
 2007-01-06 01:35:29,723 [main   ] DEBUG DataManager   
  - End of data file reached at (header was invalid): offset = 810, file = 1, 
 size = 219
 2007-01-06 01:35:29,754 [JMX connector  ] INFO  ManagementContext 
  - JMX consoles can connect to 
 service:jmx:rmi:///jndi/rmi://localhost:11099/jmxrmi
 2007-01-06 01:35:32,660 [main   ] DEBUG DataManager   
  - End of data file reached at (header was invalid): offset = 88244949, file 
 = 5, size = 100856

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] Commented: (GERONIMO-2577) Geronimo cluster (Tomcat Version)cannot continue the HttpSession when current node is down.

2007-01-11 Thread Shiva Kumar H R


Yep I will do that.

- Shiva

On 1/11/07, Jeff Genender [EMAIL PROTECTED] wrote:



 Jeff,
 How can we confirm if it is a Bug OR not supported Feature in Tomcat?

Ask on their lists.

Jeff





--
Thx,
Shiva

[jira] Created: (GERONIMO-2724) create axis2 config and axis2-deployer config folders

2007-01-11 Thread Lin Sun (JIRA)

create axis2 config and axis2-deployer config folders
-

 Key: GERONIMO-2724
 URL: https://issues.apache.org/jira/browse/GERONIMO-2724
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public (Regular issues)
  Components: webservices
Affects Versions: 2.0
 Environment: Winxp + sun 1.5 JDK
Reporter: Lin Sun


This is a patch on top of G2717 to create axis2 config and axis2-deployer 
config based on the two cxf config modules.   I also enabled the 
modules\pom.xml + configs\pom.xml to include the two axis2 modules and two 
axis2 configs.  I tried to remove some unnecessary dependencies in 
modules\geronimo-axis2\pom.xml to keep it as simple as possible.

This built fine on my machine (patch created against revision 494904).   After 
a successful build, I tried to turn on the axis2-deployer module in config.xml 
in jetty-jee5 assembly, but the axis2-deployer module failed to start.  Here's 
the stack trace:

[*-  ] 60%  24s Startup failed
org.apache.geronimo.kernel.config.LifecycleException: load of org.apache.geronim
o.configs/axis2-deployer/2.0-SNAPSHOT/car failed
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf
iguration(SimpleConfigurationManager.java:271)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf
iguration(SimpleConfigurationManager.java:250)
at org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConf
iguration(KernelConfigurationManager.java:112)
at org.apache.geronimo.kernel.config.KernelConfigurationManager$$FastCla
ssByCGLIB$$b117102f.invoke(generated)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod
Invoker.java:38)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio
n.java:127)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
java:820)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5
7)
at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat
ionInvoker.java:35)
at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro
xyMethodInterceptor.java:96)
at org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan
cerByCGLIB$$854c5ac.loadConfiguration(generated)
at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:283)
at org.apache.geronimo.system.main.Daemon.init(Daemon.java:74)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366)
Caused by: org.apache.geronimo.kernel.config.NoSuchConfigException: org.apache.g
eronimo.configs/axis2-deployer/2.0-SNAPSHOT/car
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf
igurationData(SimpleConfigurationManager.java:454)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf
iguration(SimpleConfigurationManager.java:268)
... 14 more

Will look into that.  


 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: 2.0 geronimo-qname_1.1_spec


Yes, we don't need it. AFAIK. It was being used in Axis1...

-- dims

On 1/11/07, Jason Dillon [EMAIL PROTECTED] wrote:

Do we need to include qname anymore?  Looks like that is part of se 5
now...

Anyone know?

--jason




--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

Re: 2.0 geronimo-qname_1.1_spec

FYI, we are currently including this in lib/* and 12 modules  
reference it in their poms.


I think we should remove these refs.

--jason


On Jan 11, 2007, at 1:21 PM, Jason Dillon wrote:

Do we need to include qname anymore?  Looks like that is part of se  
5 now...


Anyone know?

--jason

[jira] Updated: (GERONIMO-2724) create axis2 config and axis2-deployer config folders

2007-01-11 Thread Lin Sun (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2724:
--

Attachment: g2724.zip

 create axis2 config and axis2-deployer config folders
 -

 Key: GERONIMO-2724
 URL: https://issues.apache.org/jira/browse/GERONIMO-2724
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: webservices
Affects Versions: 2.0
 Environment: Winxp + sun 1.5 JDK
Reporter: Lin Sun
 Attachments: g2724.zip


 This is a patch on top of G2717 to create axis2 config and axis2-deployer 
 config based on the two cxf config modules.   I also enabled the 
 modules\pom.xml + configs\pom.xml to include the two axis2 modules and two 
 axis2 configs.  I tried to remove some unnecessary dependencies in 
 modules\geronimo-axis2\pom.xml to keep it as simple as possible.
 This built fine on my machine (patch created against revision 494904).   
 After a successful build, I tried to turn on the axis2-deployer module in 
 config.xml in jetty-jee5 assembly, but the axis2-deployer module failed to 
 start.  Here's the stack trace:
 [*-  ] 60%  24s Startup failed
 org.apache.geronimo.kernel.config.LifecycleException: load of 
 org.apache.geronim
 o.configs/axis2-deployer/2.0-SNAPSHOT/car failed
 at 
 org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf
 iguration(SimpleConfigurationManager.java:271)
 at 
 org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf
 iguration(SimpleConfigurationManager.java:250)
 at 
 org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConf
 iguration(KernelConfigurationManager.java:112)
 at 
 org.apache.geronimo.kernel.config.KernelConfigurationManager$$FastCla
 ssByCGLIB$$b117102f.invoke(generated)
 at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
 at 
 org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod
 Invoker.java:38)
 at 
 org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio
 n.java:127)
 at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
 java:820)
 at 
 org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5
 7)
 at 
 org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat
 ionInvoker.java:35)
 at 
 org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro
 xyMethodInterceptor.java:96)
 at 
 org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan
 cerByCGLIB$$854c5ac.loadConfiguration(generated)
 at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:283)
 at org.apache.geronimo.system.main.Daemon.init(Daemon.java:74)
 at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366)
 Caused by: org.apache.geronimo.kernel.config.NoSuchConfigException: 
 org.apache.g
 eronimo.configs/axis2-deployer/2.0-SNAPSHOT/car
 at 
 org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf
 igurationData(SimpleConfigurationManager.java:454)
 at 
 org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf
 iguration(SimpleConfigurationManager.java:268)
 ... 14 more
 Will look into that.  
  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

RE: Geronimo Axis2 Integration

2007-01-11 Thread Lin Sun

Dims, I've submitted it as G2724.  I don't think the patch will hurt
anything as the axis2-deployer isn't turned on in the config.xml files.
I'll continue investigating why the axis2-deployer won't start.  

Thanks, Lin

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 11, 2007 9:52 AM
To: dev@geronimo.apache.org
Subject: Re: Geronimo Axis2 Integration

Lin,

Please go ahead and upload the patch and add the stack trace in the
comments.

thanks,
dims

On 1/11/07, Lin Sun [EMAIL PROTECTED] wrote:
 Hi Lasantha,

 I've been doing some integration test and build (enable the four modules
in
 modules\pom.xml and configs\pom.xml) yesterday and I found that I am
having
 trouble to start the axis2-deployer during the start of the server.  Is
that
 why you didn't update modules\pom.xml for the 2 modules?

 I haven't been able to figure out the fix yet that is why I didn't submit
 the patch yet. I'll keep looking into it.

 Lin

 -Original Message-
 From: Lasantha Ranaweera [mailto:[EMAIL PROTECTED]
 Sent: Thursday, January 11, 2007 12:55 AM
 To: dev@geronimo.apache.org
 Subject: Re: Geronimo Axis2 Integration

 Hi Lin,

 Sorry for the late reply. I hope Dims has answered all your problems.
 Let us know when you submit your patch too. ;-)

 Thanks,
 Lasantha
 Lin Sun wrote:
  Hi Lasantha,

  This is great!  Thanks.  I have been also looking into Axis2 integration
 w/
  G lately and started w/ the CXF integration code.  The work I've done is
  similar as what you have, except that I also created config dir for
axis2
  and axis2-deployer.  I'll submit that as a patch today.

  By looking at your patch, how did you get the jaxb generated code?  I
  haven't been figured out how yet so I had planned to use the xmlbean
  generated code, similar as Axis1.

  Since there are some common code between CXF and Axis integration, I
think
  it would be good to have one portInfo, parseWebServiceDescriptor at the
  Geronimo webservices level.

  Lin

  -Original Message-
  From: Lasantha Ranaweera [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, January 10, 2007 2:30 AM
  To: dev@geronimo.apache.org
  Subject: Geronimo Axis2 Integration

  Hi,

  The initial implementation of the Axis2 integration with Geronimo
  uploaded in to the JIRA (Geronimo-2717). Most of the source code is
  taken out from the CXF project of  the Geronimo and it is only a maven2
  skeleton.

  I am expecting some help from person who knows Axis2 to implement
  Axis2WebServiceContainer.java class and hoping to contribute Geronimo in
  this area.

  Thanks,
  Lasantha Ranaweera

-- 
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

[jira] Created: (GERONIMO-2725) Remove geronimo-qname_1.1_spec usage

2007-01-11 Thread Jason Dillon (JIRA)

Remove geronimo-qname_1.1_spec usage 
-

 Key: GERONIMO-2725
 URL: https://issues.apache.org/jira/browse/GERONIMO-2725
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
Affects Versions: 2.0-M1
Reporter: Jason Dillon
 Assigned To: Jason Dillon
 Fix For: 2.0-M2


Do not need the geronimo-qname_1.1_spec anymore since it is included in the 
standard edition 5, which is now required to run Geronimo.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

2.0-M1 configs in the maven snapshot repo


The 2.0-M1 configs published in the snapshot repo don't work with 2.0
any more because of the serialVersionUID added to GOperationInfo in
rev487505.  Looks like the configs were published one day before this
change (just my luck).As a result, when I try to start a config
imported from the snapshot repo I see :

13:28:12,673 ERROR [GBeanInstanceState] Error while starting; GBean is
now in the FAILED state:
abstractName=org.apache.geronimo.configs/servlet-examples-tomcat/2.0-M1-SNAPSHOT/car?configurationName=org.apache.geronimo.configs/servlet-examples-tomcat/2.0-M1-SNAPSHOT/car
org.apache.geronimo.kernel.config.InvalidConfigException: Unable to
deserialize GBeanState
   at 
org.apache.geronimo.kernel.config.SerializedGBeanState.loadGBeans(SerializedGBeanState.java:120)
   at 
org.apache.geronimo.kernel.config.SerializedGBeanState.getGBeans(SerializedGBeanState.java:65)
[...]
Caused by: java.io.InvalidClassException:
org.apache.geronimo.gbean.GOperationInfo; local class incompatible:
stream classdesc serialVersionUID = 5185515581104192976, local class
serialVersionUID = -5593225815559931812
   at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:519)
[...]

I think that republishing the configs built from trunk to the snapshot
repo would clear this up.  What's the procedure for doing that?  If
someone wants to handle it then that would be just fine with me :-)
But if I do it myself then are there things I should pay extra
attention to?  I don't want to break anyone's development environment.

Best wishes,
Paul

Re: 2.0-M1 configs in the maven snapshot repo

I can publish a new set of snaps in a few... waiting for my server  
build to finish first to make sure its happy, then I will publish new  
snaps.


--jason


On Jan 11, 2007, at 2:00 PM, Paul McMahan wrote:


The 2.0-M1 configs published in the snapshot repo don't work with 2.0
any more because of the serialVersionUID added to GOperationInfo in
rev487505.  Looks like the configs were published one day before this
change (just my luck).As a result, when I try to start a config
imported from the snapshot repo I see :

13:28:12,673 ERROR [GBeanInstanceState] Error while starting; GBean is
now in the FAILED state:
abstractName=org.apache.geronimo.configs/servlet-examples-tomcat/ 
2.0-M1-SNAPSHOT/car?configurationName=org.apache.geronimo.configs/ 
servlet-examples-tomcat/2.0-M1-SNAPSHOT/car

org.apache.geronimo.kernel.config.InvalidConfigException: Unable to
deserialize GBeanState
   at  
org.apache.geronimo.kernel.config.SerializedGBeanState.loadGBeans 
(SerializedGBeanState.java:120)
   at  
org.apache.geronimo.kernel.config.SerializedGBeanState.getGBeans 
(SerializedGBeanState.java:65)

[...]
Caused by: java.io.InvalidClassException:
org.apache.geronimo.gbean.GOperationInfo; local class incompatible:
stream classdesc serialVersionUID = 5185515581104192976, local class
serialVersionUID = -5593225815559931812
   at java.io.ObjectStreamClass.initNonProxy 
(ObjectStreamClass.java:519)

[...]

I think that republishing the configs built from trunk to the snapshot
repo would clear this up.  What's the procedure for doing that?  If
someone wants to handle it then that would be just fine with me :-)
But if I do it myself then are there things I should pay extra
attention to?  I don't want to break anyone's development environment.

Best wishes,
Paul

Re: 2.0-M1 configs in the maven snapshot repo


Thanks!

On 1/11/07, Jason Dillon [EMAIL PROTECTED] wrote:

I can publish a new set of snaps in a few... waiting for my server
build to finish first to make sure its happy, then I will publish new
snaps.

--jason


On Jan 11, 2007, at 2:00 PM, Paul McMahan wrote:

 The 2.0-M1 configs published in the snapshot repo don't work with 2.0
 any more because of the serialVersionUID added to GOperationInfo in
 rev487505.  Looks like the configs were published one day before this
 change (just my luck).As a result, when I try to start a config
 imported from the snapshot repo I see :

 13:28:12,673 ERROR [GBeanInstanceState] Error while starting; GBean is
 now in the FAILED state:
 abstractName=org.apache.geronimo.configs/servlet-examples-tomcat/
 2.0-M1-SNAPSHOT/car?configurationName=org.apache.geronimo.configs/
 servlet-examples-tomcat/2.0-M1-SNAPSHOT/car
 org.apache.geronimo.kernel.config.InvalidConfigException: Unable to
 deserialize GBeanState
at
 org.apache.geronimo.kernel.config.SerializedGBeanState.loadGBeans
 (SerializedGBeanState.java:120)
at
 org.apache.geronimo.kernel.config.SerializedGBeanState.getGBeans
 (SerializedGBeanState.java:65)
 [...]
 Caused by: java.io.InvalidClassException:
 org.apache.geronimo.gbean.GOperationInfo; local class incompatible:
 stream classdesc serialVersionUID = 5185515581104192976, local class
 serialVersionUID = -5593225815559931812
at java.io.ObjectStreamClass.initNonProxy
 (ObjectStreamClass.java:519)
 [...]

 I think that republishing the configs built from trunk to the snapshot
 repo would clear this up.  What's the procedure for doing that?  If
 someone wants to handle it then that would be just fine with me :-)
 But if I do it myself then are there things I should pay extra
 attention to?  I don't want to break anyone's development environment.

 Best wishes,
 Paul

meta-modules to group dependencies

Anyone have any oppinon on creating meta-modules to group  
dependencies that are commonly used together?


For example, in most places where xmlbeans is a dep, so is stax, as in:

dependency
groupIdxmlbeans/groupId
artifactIdxbean/artifactId
/dependency

dependency
groupIdstax/groupId
artifactIdstax-api/artifactId
/dependency

We could create a meta-module, which simply defines these as  
dependencies, then use the meta-module as a dependency to simplify  
some of the commonly used dependencies.


This could also be used to allow better support for picking up  
versions of dependencies when we build the CTS server for TCK  
testing.  For example, right now we have to include versions for  
openejb and yoko in the CTS build:


   dependency
groupIdorg.apache.openejb/groupId
artifactIdopenejb-core/artifactId
version2.3-incubating-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.openejb/groupId
artifactIdopenejb-corba/artifactId
version2.3-incubating-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.openejb/groupId
artifactIdopenejb-yoko/artifactId
version2.3-incubating-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.yoko/groupId
artifactIdyoko-core/artifactId
version1.0-incubating-M2-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.yoko/groupId
artifactIdyoko-spec-corba/artifactId
version1.0-incubating-M2-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.yoko/groupId
artifactIdyoko-rmi-spec/artifactId
version1.0-incubating-M2-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.yoko/groupId
artifactIdyoko-rmi-impl/artifactId
version1.0-incubating-M2-SNAPSHOT/version
/dependency

IMO it would be better if there was some module in the server build  
which had these dependencies so that CTS always gets built with the  
correct version.


 * * *

Anyways, just a thought... meta-modules might help reduce some  
dependency configuration by centralizing dependency groupings.


Any thoughts?

--jason

[jira] Commented: (AMQCPP-25) Bus error on Solaris OS from DataInput and DataOutput streams

2007-01-11 Thread Timothy Bish (JIRA)


[ 
https://issues.apache.org/activemq/browse/AMQCPP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37894
 ] 

Timothy Bish commented on AMQCPP-25:


I've submitted changes that hopefully resolve the issues.  So far it tests fine 
on Solaris, Windows, Windows+Cygwin.  Will test on an FC6 machine tonight.

 Bus error on Solaris OS from DataInput and DataOutput streams
 -

 Key: AMQCPP-25
 URL: https://issues.apache.org/activemq/browse/AMQCPP-25
 Project: ActiveMQ C++ Client
  Issue Type: Bug
  Components: CMS Impl
Affects Versions: 1.1
 Environment: Solaris 10 OS
Reporter: Timothy Bish
 Assigned To: Timothy Bish
Priority: Minor
 Fix For: 1.1

 Attachments: optobug.cpp


 Due to misaligned memory reads, there is a bus error that can occur in using 
 the new DataInputStream and DataOutputStream classes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Closed: (GERONIMO-2725) Remove geronimo-qname_1.1_spec usage

2007-01-11 Thread Jason Dillon (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GERONIMO-2725.
--

Resolution: Fixed

 Remove geronimo-qname_1.1_spec usage 
 -

 Key: GERONIMO-2725
 URL: https://issues.apache.org/jira/browse/GERONIMO-2725
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
Affects Versions: 2.0-M1
Reporter: Jason Dillon
 Assigned To: Jason Dillon
 Fix For: 2.0-M2


 Do not need the geronimo-qname_1.1_spec anymore since it is included in the 
 standard edition 5, which is now required to run Geronimo.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: 2.0 geronimo-qname_1.1_spec

2007-01-11 Thread Kevan Miller



On Jan 11, 2007, at 1:33 PM, Jason Dillon wrote:

FYI, we are currently including this in lib/* and 12 modules  
reference it in their poms.


I think we should remove these refs.


Agreed.

--kevan

geronimo j2ee javaee schema versions for 2.0


Are we sorted on the schema versions for 2.0?

I just noticed we are still using snapshot versions:

dependency
groupIdorg.apache.geronimo.schema/groupId
artifactIdgeronimo-schema-j2ee_1.4/artifactId
version1.1-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.geronimo.schema/groupId
artifactIdgeronimo-schema-jee_5/artifactId
version1.0-SNAPSHOT/version
/dependency

Should we be using 1.1 and 1.0 instead?

--jason

jpa and annotation specs in 2.0

Are these two specs sorted?  Can we switch to using the released 1.0  
for them?  server/trunk is still using:


 dependency
groupIdorg.apache.geronimo.specs/groupId
artifactIdgeronimo-jpa_3.0_spec/artifactId
version1.0-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.geronimo.specs/groupId
artifactIdgeronimo-annotation_1.0_spec/artifactId
version1.0-SNAPSHOT/version
/dependency

--jason

Re: jpa and annotation specs in 2.0


Same with geronimo-jta_1.1_spec

Also, looks like some of these specs are listed twice in the  
dependencyManagement section... :-(


--jason


On Jan 11, 2007, at 2:49 PM, Jason Dillon wrote:

Are these two specs sorted?  Can we switch to using the released  
1.0 for them?  server/trunk is still using:


 dependency
groupIdorg.apache.geronimo.specs/groupId
artifactIdgeronimo-jpa_3.0_spec/artifactId
version1.0-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.geronimo.specs/groupId
artifactIdgeronimo-annotation_1.0_spec/artifactId
version1.0-SNAPSHOT/version
/dependency

--jason

More than one version of stax:stax-api in dependencyManagement ?!


I've found both of these:

dependency
groupIdstax/groupId
artifactIdstax-api/artifactId
version1.0.1/version
/dependency

dependency
groupIdstax/groupId
artifactIdstax-api/artifactId
version1.0/version
exclusions
exclusion
groupIdxmlbeans/groupId
artifactIdxmlbeans-jsr173-api/artifactId
/exclusion
/exclusions
/dependency

Please pay more attention to what artifacts are already configured  
when you add/update dependencyManagement.


--jason

[jira] Commented: (AMQCPP-25) Bus error on Solaris OS from DataInput and DataOutput streams


[ 
https://issues.apache.org/activemq/browse/AMQCPP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37895
 ] 

Albert Strasheim commented on AMQCPP-25:


We might consider using -Wstrict-aliasing=2. Warns in more cases, with some 
chance of false positives.

I still get the following warnings with GCC 4.1.1 on FC6 with revision 495335:

{noformat}
activemq/network/ServerSocket.cpp: In member function 'virtual void 
activemq::network::ServerSocket::bind(const char*, int, int)':
activemq/network/ServerSocket.cpp:162: warning: dereferencing type-punned 
pointer might break strict-aliasing rules
activemq/network/ServerSocket.cpp: In member function 'virtual 
activemq::network::Socket* activemq::network::ServerSocket::accept()':
activemq/network/ServerSocket.cpp:208: warning: dereferencing type-punned 
pointer might break strict-aliasing rules
activemq/io/DataInputStreamTest.h:85: warning: dereferencing type-punned 
pointer will break strict-aliasing rules
activemq/io/DataInputStreamTest.h:86: warning: dereferencing type-punned 
pointer will break strict-aliasing rules
{noformat}

I noticed you used a memcpys to fix this issue. Did you consider trying a 
union? Without knowing for certain (maybe we'll do some benchmarks tomorrow), a 
union might be faster than a call to memcpy.

Anyway, tests pass on FC6. Thanks very much.

 Bus error on Solaris OS from DataInput and DataOutput streams
 -

 Key: AMQCPP-25
 URL: https://issues.apache.org/activemq/browse/AMQCPP-25
 Project: ActiveMQ C++ Client
  Issue Type: Bug
  Components: CMS Impl
Affects Versions: 1.1
 Environment: Solaris 10 OS
Reporter: Timothy Bish
 Assigned To: Timothy Bish
Priority: Minor
 Fix For: 1.1

 Attachments: optobug.cpp


 Due to misaligned memory reads, there is a bus error that can occur in using 
 the new DataInputStream and DataOutputStream classes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQCPP-25) Bus error on Solaris OS from DataInput and DataOutput streams

2007-01-11 Thread Timothy Bish (JIRA)


 [ 
https://issues.apache.org/activemq/browse/AMQCPP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved AMQCPP-25.


Resolution: Fixed

Tests now pass, using latest trunk.

No BUS errors on Solaris.  



 Bus error on Solaris OS from DataInput and DataOutput streams
 -

 Key: AMQCPP-25
 URL: https://issues.apache.org/activemq/browse/AMQCPP-25
 Project: ActiveMQ C++ Client
  Issue Type: Bug
  Components: CMS Impl
Affects Versions: 1.1
 Environment: Solaris 10 OS
Reporter: Timothy Bish
 Assigned To: Timothy Bish
Priority: Minor
 Fix For: 1.1

 Attachments: optobug.cpp


 Due to misaligned memory reads, there is a bus error that can occur in using 
 the new DataInputStream and DataOutputStream classes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (GERONIMO-2726) Update JAXB and StAX implementation versions

2007-01-11 Thread Jarek Gawor (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek Gawor updated GERONIMO-2726:
--

Attachment: update.patch

 Update JAXB and StAX implementation versions
 

 Key: GERONIMO-2726
 URL: https://issues.apache.org/jira/browse/GERONIMO-2726
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: webservices
Affects Versions: 2.0-M2
Reporter: Jarek Gawor
 Attachments: update.patch




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (GERONIMO-2726) Update JAXB and StAX implementation versions

2007-01-11 Thread Jarek Gawor (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464006
 ] 

Jarek Gawor commented on GERONIMO-2726:
---

The attached patch updates JAXB implementation to 2.0.3 version and StAX 
implementation to 3.2.0.



 Update JAXB and StAX implementation versions
 

 Key: GERONIMO-2726
 URL: https://issues.apache.org/jira/browse/GERONIMO-2726
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: webservices
Affects Versions: 2.0-M2
Reporter: Jarek Gawor
 Attachments: update.patch




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: ApacheDS - LDAP - Geronimo Plugins


On 1/11/07, Hernan Cunico [EMAIL PROTECTED] wrote:

Howdy,
I've been playing around with the integrated LDAP from the begining. It got 
pulled out from the build when we came out with Geronimo plugins (somewhere 
around v1.1.1)
Now I see it back in the branch for v1.2 and trunk, this feature is already 
in the build however it still is available for download/install as a plugin.


As far as I can tell the directory module was never removed from the
build.  It just got removed from the list of components that are
enabled in the tomcat and jetty assemblies.  See rev 412604.  A
geronimo-plugin.xml file was also added to the directory module at
that time so that it could be exported as a plugin and offered from a
plugin repository.  But it doesn't have to be installed as a plugin,
you could reenable it in the assemblies just as well.  Same for the
other modules that used to be enabled in the assemblies by default
such as servlet and jsp samples, etc.


So the question is what do we want to do with it, offer LDAP as part of the 
dist or separate as a plugin?


Do you mean should it be reenabled in the default assemblies?
Strictly speaking its not required for JEE5 and if someone needs it
then its pretty easy to install as a plugin from the Geronimo plugin
repository at http://geronimo.apache.org/plugins/.  Actually,
installing it as a plugin in this way is equivalent to reenabling it
in the assembly since that repository's catalog just points to the
maven repo where Geronimo's artifacts are published.  The plugin
approach just lets the user decide what Geronimo artifacts get enabled
in the assembly instead of the person that typed mvn  :-)


Another question is, if I already see it available in the build (fresh from 
trunk) why it still shows up as available for install in the Install Plugin 
portlet?
(it will fail to install since the destination already exist)


There might be an error in the plugin catalog.  If the module-id
that's listed in the catalog matches the module-id for a component
that's already deployed in the server then it should not show us as
available.  Actually I wasn't able to install the plugin for a
different reason -- the 2.0-M1 configs published in the snapshot repo
aren't compatible with 2.0 any more.  Are you sure that's not related
to the error you're seeing?  If so then that should be fixed when we
republish the configs (hopefully later today).

Best wishes,
Paul

Re: 2.0-M1 configs in the maven snapshot repo


This is done... only took 62 minutes to deploy it all... :-(

--jason


On Jan 11, 2007, at 2:21 PM, Paul McMahan wrote:


Thanks!

On 1/11/07, Jason Dillon [EMAIL PROTECTED] wrote:

I can publish a new set of snaps in a few... waiting for my server
build to finish first to make sure its happy, then I will publish new
snaps.

--jason


On Jan 11, 2007, at 2:00 PM, Paul McMahan wrote:

 The 2.0-M1 configs published in the snapshot repo don't work  
with 2.0

 any more because of the serialVersionUID added to GOperationInfo in
 rev487505.  Looks like the configs were published one day before  
this

 change (just my luck).As a result, when I try to start a config
 imported from the snapshot repo I see :

 13:28:12,673 ERROR [GBeanInstanceState] Error while starting;  
GBean is

 now in the FAILED state:
 abstractName=org.apache.geronimo.configs/servlet-examples-tomcat/
 2.0-M1-SNAPSHOT/car?configurationName=org.apache.geronimo.configs/
 servlet-examples-tomcat/2.0-M1-SNAPSHOT/car
 org.apache.geronimo.kernel.config.InvalidConfigException: Unable to
 deserialize GBeanState
at
 org.apache.geronimo.kernel.config.SerializedGBeanState.loadGBeans
 (SerializedGBeanState.java:120)
at
 org.apache.geronimo.kernel.config.SerializedGBeanState.getGBeans
 (SerializedGBeanState.java:65)
 [...]
 Caused by: java.io.InvalidClassException:
 org.apache.geronimo.gbean.GOperationInfo; local class incompatible:
 stream classdesc serialVersionUID = 5185515581104192976, local  
class

 serialVersionUID = -5593225815559931812
at java.io.ObjectStreamClass.initNonProxy
 (ObjectStreamClass.java:519)
 [...]

 I think that republishing the configs built from trunk to the  
snapshot

 repo would clear this up.  What's the procedure for doing that?  If
 someone wants to handle it then that would be just fine with me :-)
 But if I do it myself then are there things I should pay extra
 attention to?  I don't want to break anyone's development  
environment.


 Best wishes,
 Paul

Re: ApacheDS - LDAP - Geronimo Plugins

2007-01-11 Thread Hernan Cunico


Paul McMahan wrote:

On 1/11/07, Hernan Cunico [EMAIL PROTECTED] wrote:

Howdy,
...
download/install as a plugin.


As far as I can tell the directory module was never removed from the
build.  It just got removed from the list of components that are
enabled in the tomcat and jetty assemblies.  See rev 412604.  A


Time out! If I'm a user that only cares about the binary dist there is no way 
for me to know that, am I right!?
Either way, the service is already there in the assembly, it is just not 
starting by default.


geronimo-plugin.xml file was also added to the directory module at
that time so that it could be exported as a plugin and offered from a
plugin repository.  But it doesn't have to be installed as a plugin,
you could reenable it in the assemblies just as well.  Same for the
other modules that used to be enabled in the assemblies by default
such as servlet and jsp samples, etc.


This might be related to the issue you are seeing. At first I tried to export 
the already available directory service but it was not listed for export in the 
modules pull-down menu from the plugin portlet.



So the question is what do we want to do with it, offer LDAP as part 
of the dist or separate as a plugin?


Do you mean should it be reenabled in the default assemblies?


It is already there, in the assemblies for 1.2 and trunk. I'm personally happy 
to have it there and not having to install it as a plugin every time.
Checking at the pom.xml in the assemblies directory for Tomcat and and Jetty 
you can see

   dependency
   groupIdorg.apache.geronimo.configs/groupId
   artifactIddirectory/artifactId
   version${version}/version
   typecar/type
   /dependency

   dependency
   groupIdorg.apache.geronimo.configs/groupId
   artifactIdldap-realm/artifactId
   version${version}/version
   typecar/type
   /dependency



Strictly speaking its not required for JEE5 and if someone needs it


Agreed, not required for JEE 5 but again, and personal view, nice to have ;-)


then its pretty easy to install as a plugin from the Geronimo plugin
repository at http://geronimo.apache.org/plugins/.  Actually,
installing it as a plugin in this way is equivalent to reenabling it
in the assembly since that repository's catalog just points to the
maven repo where Geronimo's artifacts are published.  The plugin
approach just lets the user decide what Geronimo artifacts get enabled
in the assembly instead of the person that typed mvn  :-)

Another question is, if I already see it available in the build (fresh 
from trunk) why it still shows up as available for install in the 
Install Plugin portlet?

(it will fail to install since the destination already exist)


There might be an error in the plugin catalog.  If the module-id
that's listed in the catalog matches the module-id for a component


yeah, I just realized the moduleId in the catalog is 
org.apache.geronimo.configs/directory/2.0-M1-SNAPSHOT/car and the one already 
in the assembly is org.apache.geronimo.configs/directory/2.0-SNAPSHOT/car


that's already deployed in the server then it should not show us as
available.  Actually I wasn't able to install the plugin for a
different reason -- the 2.0-M1 configs published in the snapshot repo
aren't compatible with 2.0 any more.  Are you sure that's not related
to the error you're seeing?  If so then that should be fixed when we
republish the configs (hopefully later today).


It could be a combination of the two errors, however it did fail the first time 
(installing the plugin over the assembly with the service already there) 
complaining the destination already existed. Haven't re-tested it yet.

I'll give it a shot again later today.

Cheers!
Hernan


Best wishes,
Paul

Re: More than one version of stax:stax-api in dependencyManagement ?!


Axis2 needs 1.0.1. Can we please use that?

thanks,
dims

On 1/11/07, Jason Dillon [EMAIL PROTECTED] wrote:

I've found both of these:

 dependency
 groupIdstax/groupId
 artifactIdstax-api/artifactId
 version1.0.1/version
 /dependency

 dependency
 groupIdstax/groupId
 artifactIdstax-api/artifactId
 version1.0/version
 exclusions
 exclusion
 groupIdxmlbeans/groupId
 artifactIdxmlbeans-jsr173-api/artifactId
 /exclusion
 /exclusions
 /dependency

Please pay more attention to what artifacts are already configured
when you add/update dependencyManagement.

--jason




--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

Re: meta-modules to group dependencies

That would certainly help people understand why dependencies are  
there and how they are related.  Although, shouldn't the dependencies  
be in the poms already?  So if XMLBeans needed Stax they would have  
already declared that and it could be derived transitively?


On Jan 11, 2007, at 2:22 PM, Jason Dillon wrote:

Anyone have any oppinon on creating meta-modules to group  
dependencies that are commonly used together?


For example, in most places where xmlbeans is a dep, so is stax, as  
in:


dependency
groupIdxmlbeans/groupId
artifactIdxbean/artifactId
/dependency

dependency
groupIdstax/groupId
artifactIdstax-api/artifactId
/dependency

We could create a meta-module, which simply defines these as  
dependencies, then use the meta-module as a dependency to simplify  
some of the commonly used dependencies.


This could also be used to allow better support for picking up  
versions of dependencies when we build the CTS server for TCK  
testing.  For example, right now we have to include versions for  
openejb and yoko in the CTS build:


   dependency
groupIdorg.apache.openejb/groupId
artifactIdopenejb-core/artifactId
version2.3-incubating-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.openejb/groupId
artifactIdopenejb-corba/artifactId
version2.3-incubating-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.openejb/groupId
artifactIdopenejb-yoko/artifactId
version2.3-incubating-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.yoko/groupId
artifactIdyoko-core/artifactId
version1.0-incubating-M2-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.yoko/groupId
artifactIdyoko-spec-corba/artifactId
version1.0-incubating-M2-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.yoko/groupId
artifactIdyoko-rmi-spec/artifactId
version1.0-incubating-M2-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.yoko/groupId
artifactIdyoko-rmi-impl/artifactId
version1.0-incubating-M2-SNAPSHOT/version
/dependency

IMO it would be better if there was some module in the server build  
which had these dependencies so that CTS always gets built with the  
correct version.


 * * *

Anyways, just a thought... meta-modules might help reduce some  
dependency configuration by centralizing dependency groupings.


Any thoughts?

--jason



Matt Hogstrom
[EMAIL PROTECTED]

Re: 2.0 geronimo-qname_1.1_spec


+1 to remove it.

On Jan 11, 2007, at 1:21 PM, Jason Dillon wrote:

Do we need to include qname anymore?  Looks like that is part of se  
5 now...


Anyone know?

--jason



Matt Hogstrom
[EMAIL PROTECTED]

CXF and Axis2 (dogs and cats?)

I am not overly knowledgeable about WebServices so I'll bear my  
ignorance directly.  Given that we'll have two options that users  
will be able to choose from is there some way to abstract CXF and  
Axis2 to a common point so users could install their preference  
through a plugin?  It would certainly simplify the user experience as  
well as reduce the number of assemblies.  Any CXF / Axis guys have  
thoughts on this?



Matt Hogstrom
[EMAIL PROTECTED]

Re: More than one version of stax:stax-api in dependencyManagement ?!


Do we need the excludes?

--jason


On Jan 11, 2007, at 4:11 PM, Davanum Srinivas wrote:


Axis2 needs 1.0.1. Can we please use that?

thanks,
dims

On 1/11/07, Jason Dillon [EMAIL PROTECTED] wrote:

I've found both of these:

 dependency
 groupIdstax/groupId
 artifactIdstax-api/artifactId
 version1.0.1/version
 /dependency

 dependency
 groupIdstax/groupId
 artifactIdstax-api/artifactId
 version1.0/version
 exclusions
 exclusion
 groupIdxmlbeans/groupId
 artifactIdxmlbeans-jsr173-api/artifactId
 /exclusion
 /exclusions
 /dependency

Please pay more attention to what artifacts are already configured
when you add/update dependencyManagement.

--jason




--  
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service  
Developers)

Re: More than one version of stax:stax-api in dependencyManagement ?!


Nope.

On 1/11/07, Jason Dillon [EMAIL PROTECTED] wrote:

Do we need the excludes?

--jason


On Jan 11, 2007, at 4:11 PM, Davanum Srinivas wrote:

 Axis2 needs 1.0.1. Can we please use that?

 thanks,
 dims

 On 1/11/07, Jason Dillon [EMAIL PROTECTED] wrote:
 I've found both of these:

  dependency
  groupIdstax/groupId
  artifactIdstax-api/artifactId
  version1.0.1/version
  /dependency

  dependency
  groupIdstax/groupId
  artifactIdstax-api/artifactId
  version1.0/version
  exclusions
  exclusion
  groupIdxmlbeans/groupId
  artifactIdxmlbeans-jsr173-api/artifactId
  /exclusion
  /exclusions
  /dependency

 Please pay more attention to what artifacts are already configured
 when you add/update dependencyManagement.

 --jason



 --
 Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
 Developers)





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

Re: CXF and Axis2 (dogs and cats?)


Am at a point where i am struggling to get a test up and running in
the geronimo harness and connect to it from my debugger :) So am
absolutely the wrong person to ask :)

-- dims

On 1/11/07, Matt Hogstrom [EMAIL PROTECTED] wrote:

I am not overly knowledgeable about WebServices so I'll bear my
ignorance directly.  Given that we'll have two options that users
will be able to choose from is there some way to abstract CXF and
Axis2 to a common point so users could install their preference
through a plugin?  It would certainly simplify the user experience as
well as reduce the number of assemblies.  Any CXF / Axis guys have
thoughts on this?


Matt Hogstrom
[EMAIL PROTECTED]






--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

Re: meta-modules to group dependencies

It may or may not be in the dependencies pom... depends on if its a  
native m2 artifact or if its configured in the right scope.


--jason


On Jan 11, 2007, at 4:11 PM, Matt Hogstrom wrote:

That would certainly help people understand why dependencies are  
there and how they are related.  Although, shouldn't the  
dependencies be in the poms already?  So if XMLBeans needed Stax  
they would have already declared that and it could be derived  
transitively?


On Jan 11, 2007, at 2:22 PM, Jason Dillon wrote:

Anyone have any oppinon on creating meta-modules to group  
dependencies that are commonly used together?


For example, in most places where xmlbeans is a dep, so is stax,  
as in:


dependency
groupIdxmlbeans/groupId
artifactIdxbean/artifactId
/dependency

dependency
groupIdstax/groupId
artifactIdstax-api/artifactId
/dependency

We could create a meta-module, which simply defines these as  
dependencies, then use the meta-module as a dependency to simplify  
some of the commonly used dependencies.


This could also be used to allow better support for picking up  
versions of dependencies when we build the CTS server for TCK  
testing.  For example, right now we have to include versions for  
openejb and yoko in the CTS build:


   dependency
groupIdorg.apache.openejb/groupId
artifactIdopenejb-core/artifactId
version2.3-incubating-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.openejb/groupId
artifactIdopenejb-corba/artifactId
version2.3-incubating-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.openejb/groupId
artifactIdopenejb-yoko/artifactId
version2.3-incubating-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.yoko/groupId
artifactIdyoko-core/artifactId
version1.0-incubating-M2-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.yoko/groupId
artifactIdyoko-spec-corba/artifactId
version1.0-incubating-M2-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.yoko/groupId
artifactIdyoko-rmi-spec/artifactId
version1.0-incubating-M2-SNAPSHOT/version
/dependency

dependency
groupIdorg.apache.yoko/groupId
artifactIdyoko-rmi-impl/artifactId
version1.0-incubating-M2-SNAPSHOT/version
/dependency

IMO it would be better if there was some module in the server  
build which had these dependencies so that CTS always gets built  
with the correct version.


 * * *

Anyways, just a thought... meta-modules might help reduce some  
dependency configuration by centralizing dependency groupings.


Any thoughts?

--jason



Matt Hogstrom
[EMAIL PROTECTED]

[jira] Closed: (GERONIMO-1386) Docs produced by Confluence contain spaces in file names

2007-01-11 Thread Hernan Cunico (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hernan Cunico closed GERONIMO-1386.
---

Resolution: Fixed

Issue addressed using autoexport plugin. All documentation now is available at 
http://cwiki.apache.org/geronimo

 Docs produced by Confluence contain spaces in file names
 

 Key: GERONIMO-1386
 URL: https://issues.apache.org/jira/browse/GERONIMO-1386
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: documentation
Affects Versions: 1.0
Reporter: John Sisson
 Assigned To: Hernan Cunico
 Fix For: Wish List


 This was reported to the dev list in:
 http://www.mail-archive.com/dev%40geronimo.apache.org/msg14471.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: More than one version of stax:stax-api in dependencyManagement ?!

Aight, I running a new build to check that nothing freaks out and  
will commit it shortly.


--jason


On Jan 11, 2007, at 4:21 PM, Davanum Srinivas wrote:


Nope.

On 1/11/07, Jason Dillon [EMAIL PROTECTED] wrote:

Do we need the excludes?

--jason


On Jan 11, 2007, at 4:11 PM, Davanum Srinivas wrote:

 Axis2 needs 1.0.1. Can we please use that?

 thanks,
 dims

 On 1/11/07, Jason Dillon [EMAIL PROTECTED] wrote:
 I've found both of these:

  dependency
  groupIdstax/groupId
  artifactIdstax-api/artifactId
  version1.0.1/version
  /dependency

  dependency
  groupIdstax/groupId
  artifactIdstax-api/artifactId
  version1.0/version
  exclusions
  exclusion
  groupIdxmlbeans/groupId
  artifactIdxmlbeans-jsr173-api/ 
artifactId

  /exclusion
  /exclusions
  /dependency

 Please pay more attention to what artifacts are already configured
 when you add/update dependencyManagement.

 --jason



 --
 Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
 Developers)





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service  
Developers)

Re: ApacheDS - LDAP - Geronimo Plugins


OK now that I'm looking deeper into this things are becoming clearer.
First of all, as you pointed out the directory module is already
included in the jee5 assembly, which I wasn't aware of.  Apparently
the commit that was supposed to have removed it from the dist only
updated the config.xml and not the pom, which seems to have left it in
the repo even though it's not listed in the server configuration.  Or
maybe just removing it from the config.xml was sufficient to prune it
from the dist before we started building with m2(?).   So at any rate,
its in the assembly now just not listed in config.xml or started by
default.

And I think you've already sniffed out the reason why the directory
plugin was marked as being available for install.  The version of the
plugin in the catalog was 2.0-M1-SNAPSHOT but in the repo it was
2.0-SNAPSHOT.  I've adjusted the catalog now so that it works with
trunk.  Please give it another try.  The plugin schema really needs
some work so that versioning is easier to handle.

Best wishes,
Paul

On 1/11/07, Hernan Cunico [EMAIL PROTECTED] wrote:

Paul McMahan wrote:
 On 1/11/07, Hernan Cunico [EMAIL PROTECTED] wrote:
 Howdy,
 ...
 download/install as a plugin.

 As far as I can tell the directory module was never removed from the
 build.  It just got removed from the list of components that are
 enabled in the tomcat and jetty assemblies.  See rev 412604.  A

Time out! If I'm a user that only cares about the binary dist there is no way 
for me to know that, am I right!?
Either way, the service is already there in the assembly, it is just not 
starting by default.

 geronimo-plugin.xml file was also added to the directory module at
 that time so that it could be exported as a plugin and offered from a
 plugin repository.  But it doesn't have to be installed as a plugin,
 you could reenable it in the assemblies just as well.  Same for the
 other modules that used to be enabled in the assemblies by default
 such as servlet and jsp samples, etc.

This might be related to the issue you are seeing. At first I tried to export 
the already available directory service but it was not listed for export in the 
modules pull-down menu from the plugin portlet.


 So the question is what do we want to do with it, offer LDAP as part
 of the dist or separate as a plugin?

 Do you mean should it be reenabled in the default assemblies?

It is already there, in the assemblies for 1.2 and trunk. I'm personally happy 
to have it there and not having to install it as a plugin every time.
Checking at the pom.xml in the assemblies directory for Tomcat and and Jetty 
you can see

dependency
groupIdorg.apache.geronimo.configs/groupId
artifactIddirectory/artifactId
version${version}/version
typecar/type
/dependency

dependency
groupIdorg.apache.geronimo.configs/groupId
artifactIdldap-realm/artifactId
version${version}/version
typecar/type
/dependency


 Strictly speaking its not required for JEE5 and if someone needs it

Agreed, not required for JEE 5 but again, and personal view, nice to have ;-)

 then its pretty easy to install as a plugin from the Geronimo plugin
 repository at http://geronimo.apache.org/plugins/.  Actually,
 installing it as a plugin in this way is equivalent to reenabling it
 in the assembly since that repository's catalog just points to the
 maven repo where Geronimo's artifacts are published.  The plugin
 approach just lets the user decide what Geronimo artifacts get enabled
 in the assembly instead of the person that typed mvn  :-)

 Another question is, if I already see it available in the build (fresh
 from trunk) why it still shows up as available for install in the
 Install Plugin portlet?
 (it will fail to install since the destination already exist)

 There might be an error in the plugin catalog.  If the module-id
 that's listed in the catalog matches the module-id for a component

yeah, I just realized the moduleId in the catalog is 
org.apache.geronimo.configs/directory/2.0-M1-SNAPSHOT/car and the one already 
in the assembly is org.apache.geronimo.configs/directory/2.0-SNAPSHOT/car

 that's already deployed in the server then it should not show us as
 available.  Actually I wasn't able to install the plugin for a
 different reason -- the 2.0-M1 configs published in the snapshot repo
 aren't compatible with 2.0 any more.  Are you sure that's not related
 to the error you're seeing?  If so then that should be fixed when we
 republish the configs (hopefully later today).

It could be a combination of the two errors, however it did fail the first time 
(installing the plugin over the assembly with the service already there) 
complaining the destination already existed. Haven't re-tested it yet.

I'll give it a shot again later today.

Cheers!
Hernan

 Best wishes,
 Paul

Re: 2.0 geronimo-qname_1.1_spec

2007-01-11 Thread Dain Sundstrom


+1

-dain

On Jan 11, 2007, at 10:33 AM, Jason Dillon wrote:

FYI, we are currently including this in lib/* and 12 modules  
reference it in their poms.


I think we should remove these refs.

--jason


On Jan 11, 2007, at 1:21 PM, Jason Dillon wrote:

Do we need to include qname anymore?  Looks like that is part of  
se 5 now...


Anyone know?

--jason

Re: CXF and Axis2 (dogs and cats?)

2007-01-11 Thread Dain Sundstrom

It would be very nice if this could work like JPA where I set a  
single property in my application to switch implementations.


-dain

On Jan 11, 2007, at 1:16 PM, Matt Hogstrom wrote:

I am not overly knowledgeable about WebServices so I'll bear my  
ignorance directly.  Given that we'll have two options that users  
will be able to choose from is there some way to abstract CXF and  
Axis2 to a common point so users could install their preference  
through a plugin?  It would certainly simplify the user experience  
as well as reduce the number of assemblies.  Any CXF / Axis guys  
have thoughts on this?



Matt Hogstrom
[EMAIL PROTECTED]

Re: svn commit: r495390 - in /geronimo/server/trunk: configs/ configs/axis2-deployer/ configs/axis2-deployer/src/ configs/axis2-deployer/src/plan/ configs/axis2/ configs/axis2/src/ configs/axis2/src/p


Yikes!!!

Why are we including 2 legacy repos here?

--jason


On Jan 11, 2007, at 4:45 PM, [EMAIL PROTECTED] wrote:


Author: dims
Date: Thu Jan 11 13:45:01 2007
New Revision: 495390

URL: http://svn.apache.org/viewvc?view=revrev=495390
Log:
patch from Lin Sun for GERONIMO-2724 - create axis2 config and  
axis2-deployer config folders


Added:
geronimo/server/trunk/configs/axis2/
geronimo/server/trunk/configs/axis2-deployer/
geronimo/server/trunk/configs/axis2-deployer/LICENSE.txt
geronimo/server/trunk/configs/axis2-deployer/NOTICE.txt
geronimo/server/trunk/configs/axis2-deployer/pom.xml
geronimo/server/trunk/configs/axis2-deployer/src/
geronimo/server/trunk/configs/axis2-deployer/src/plan/
geronimo/server/trunk/configs/axis2-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/axis2/LICENSE.txt
geronimo/server/trunk/configs/axis2/NOTICE.txt
geronimo/server/trunk/configs/axis2/pom.xml
geronimo/server/trunk/configs/axis2/src/
geronimo/server/trunk/configs/axis2/src/plan/
geronimo/server/trunk/configs/axis2/src/plan/plan.xml
Modified:
geronimo/server/trunk/configs/pom.xml
geronimo/server/trunk/modules/pom.xml

Added: geronimo/server/trunk/configs/axis2-deployer/LICENSE.txt
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/configs/ 
axis2-deployer/LICENSE.txt?view=autorev=495390
== 


--- geronimo/server/trunk/configs/axis2-deployer/LICENSE.txt (added)
+++ geronimo/server/trunk/configs/axis2-deployer/LICENSE.txt Thu  
Jan 11 13:45:01 2007

@@ -0,0 +1,203 @@
+
+ Apache License
+   Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+  License shall mean the terms and conditions for use,  
reproduction,
+  and distribution as defined by Sections 1 through 9 of this  
document.

+
+  Licensor shall mean the copyright owner or entity  
authorized by

+  the copyright owner that is granting the License.
+
+  Legal Entity shall mean the union of the acting entity and  
all
+  other entities that control, are controlled by, or are under  
common

+  control with that entity. For the purposes of this definition,
+  control means (i) the power, direct or indirect, to cause the
+  direction or management of such entity, whether by contract or
+  otherwise, or (ii) ownership of fifty percent (50%) or more  
of the
+  outstanding shares, or (iii) beneficial ownership of such  
entity.

+
+  You (or Your) shall mean an individual or Legal Entity
+  exercising permissions granted by this License.
+
+  Source form shall mean the preferred form for making  
modifications,
+  including but not limited to software source code,  
documentation

+  source, and configuration files.
+
+  Object form shall mean any form resulting from mechanical
+  transformation or translation of a Source form, including but
+  not limited to compiled object code, generated documentation,
+  and conversions to other media types.
+
+  Work shall mean the work of authorship, whether in Source or
+  Object form, made available under the License, as indicated  
by a

+  copyright notice that is included in or attached to the work
+  (an example is provided in the Appendix below).
+
+  Derivative Works shall mean any work, whether in Source or  
Object
+  form, that is based on (or derived from) the Work and for  
which the
+  editorial revisions, annotations, elaborations, or other  
modifications
+  represent, as a whole, an original work of authorship. For  
the purposes
+  of this License, Derivative Works shall not include works  
that remain
+  separable from, or merely link (or bind by name) to the  
interfaces of,

+  the Work and Derivative Works thereof.
+
+  Contribution shall mean any work of authorship, including
+  the original version of the Work and any modifications or  
additions

+  to that Work or Derivative Works thereof, that is intentionally
+  submitted to Licensor for inclusion in the Work by the  
copyright owner
+  or by an individual or Legal Entity authorized to submit on  
behalf of
+  the copyright owner. For the purposes of this definition,  
submitted
+  means any form of electronic, verbal, or written  
communication sent
+  to the Licensor or its representatives, including but not  
limited to
+  communication on electronic mailing lists, source code  
control systems,
+  and issue tracking systems that are managed by, or on behalf  
of, the
+  Licensor for the purpose of discussing and improving the  
Work, but
+  excluding communication that is conspicuously marked or  
otherwise
+  designated in writing by the

Re: CXF and Axis2 (dogs and cats?)