[jira] Commented: (SM-797) Jsr181 component should have a way to forward properties from in message to out message
[ https://issues.apache.org/activemq/browse/SM-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37844 ] Guillaume Nodet commented on SM-797: This is needed when using the splitter / aggregator. Note that other components may need to be enhanced too. Jsr181 component should have a way to forward properties from in message to out message --- Key: SM-797 URL: https://issues.apache.org/activemq/browse/SM-797 Project: ServiceMix Issue Type: Bug Components: servicemix-jsr181 Reporter: Guillaume Nodet -- 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-809) Add a way to copy properties using the EIP wire tap when using splitter / aggregator with a non well-behaving component
Add a way to copy properties using the EIP wire tap when using splitter / aggregator with a non well-behaving component --- Key: SM-809 URL: https://issues.apache.org/activemq/browse/SM-809 Project: ServiceMix Issue Type: New Feature Components: servicemix-eip 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-809) Add a way to copy properties using the EIP wire tap when using splitter / aggregator with a non well-behaving component
[ https://issues.apache.org/activemq/browse/SM-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-809. Resolution: Fixed Author: gnodet Date: Wed Jan 10 04:03:03 2007 New Revision: 494792 URL: http://svn.apache.org/viewvc?view=revrev=494792 Log: SM-809: Add a way to copy properties using the EIP wire tap when using splitter / aggregator with a non well-behaving component Modified: incubator/servicemix/trunk/deployables/serviceengines/servicemix-eip/src/main/java/org/apache/servicemix/eip/patterns/WireTap.java incubator/servicemix/trunk/deployables/serviceengines/servicemix-eip/src/test/resources/org/apache/servicemix/eip/spring.xml Add a way to copy properties using the EIP wire tap when using splitter / aggregator with a non well-behaving component --- Key: SM-809 URL: https://issues.apache.org/activemq/browse/SM-809 Project: ServiceMix Issue Type: New Feature Components: servicemix-eip 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] Commented: (SM-808) Servicemix jboss deployer
[
https://issues.apache.org/activemq/browse/SM-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37851
]
Eric Dofonsou commented on SM-808:
--
Yes indeed it is there, however is till get the following error when I send a
request to my endpoint :
10:05:49,687 ERROR [STDERR] Exception in thread
pool-flow.seda.servicemix-http-thread-1
10:05:49,694 ERROR [STDERR] java.lang.NoClassDefFoundError:
org/apache/xalan/xsltc/trax/SAX2DOM
10:05:49,695 ERROR [STDERR] at
org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMNodeFromSAX(SourceTransformer.java:248)
10:05:49,695 ERROR [STDERR] at
org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMSourceFromSAX(SourceTransformer.java:244)
10:05:49,695 ERROR [STDERR] at
org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMSource(SourceTransformer.java:134)
10:05:49,695 ERROR [STDERR] at
org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMNode(SourceTransformer.java:277)
The xalan.jar that is in the lib/endorsed of JBoss does not include the missing
SAX2DOM class. Do we have a version/trimmed dow issue here ?
The only way i've managed to solve this issue is to either include the
xalan-2.7.0.jar from the maven repository in the servicemix.sar file or in the
server/{servername}/lib folder.
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
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] Commented: (SM-808) Servicemix jboss deployer
[ https://issues.apache.org/activemq/browse/SM-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37852 ] Guillaume Nodet commented on SM-808: Maybe a better way would to remove the hard dependency that SourceTransformer has on xalan and use introspection to check if these classes are available, else default to some JAXP standard mechanism ... Fancy writing a patch for that ? Else, I guess we need to include the xalan jar in the sar, but i'd rather be able to remove this dependency. 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 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-810) Create single complete ServiceMix Shared Library
Create single complete ServiceMix Shared Library Key: SM-810 URL: https://issues.apache.org/activemq/browse/SM-810 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.0 Environment: ServiceMix 3.0 Reporter: James Lorenzen The current ServiceMix Shared Library is insufficient to support proper portability of existing ServiceMix components to other JBI containers, such as OpenESB. For example, when installing the ServiceMix HTTP BC in OpenESB, NoClassDefFoundErrors occur because the installed ServiceMix Shared Library does not contain all the necessary dependencies. Therefore it would be a good idea to create a single complete Shared Library. To accomplish this here are some ideas: 1) Combine the shared library and shared library compat projects together. 2) Ensure the new single complete Shared Library contains the following dependencies: a) activemq-core b) backport-util-concurrent c) commons-logging d) servicemix-core e) servicemix-services f) spring-2.0-rc3 g) wsdl4j h) xbean-classloader i) xbean-kernel j) xbean-server k) xbean-spring When complete the dependencies under /servicemix_home/lib should be smaller. -- 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-810) Create single complete ServiceMix Shared Library
[ https://issues.apache.org/activemq/browse/SM-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37855 ] James Lorenzen commented on SM-810: --- Generated from this thread: http://www.nabble.com/Modifying-Shared-Library-to-make-HTTP-BC-portable-to-OpenESB-tf2940435s12049.html Create single complete ServiceMix Shared Library Key: SM-810 URL: https://issues.apache.org/activemq/browse/SM-810 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.0 Environment: ServiceMix 3.0 Reporter: James Lorenzen Original Estimate: 1 day Remaining Estimate: 1 day The current ServiceMix Shared Library is insufficient to support proper portability of existing ServiceMix components to other JBI containers, such as OpenESB. For example, when installing the ServiceMix HTTP BC in OpenESB, NoClassDefFoundErrors occur because the installed ServiceMix Shared Library does not contain all the necessary dependencies. Therefore it would be a good idea to create a single complete Shared Library. To accomplish this here are some ideas: 1) Combine the shared library and shared library compat projects together. 2) Ensure the new single complete Shared Library contains the following dependencies: a) activemq-core b) backport-util-concurrent c) commons-logging d) servicemix-core e) servicemix-services f) spring-2.0-rc3 g) wsdl4j h) xbean-classloader i) xbean-kernel j) xbean-server k) xbean-spring When complete the dependencies under /servicemix_home/lib should be smaller. -- 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-811) servicemix-jms does not set SoapAction property for SOAP jms messages
[ https://issues.apache.org/activemq/browse/SM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37867 ] Christian Schneider commented on SM-811: I think I have located and solved the problem. In the jsr181 component I added a line to set the operation in the exchange. In the jms component I use the endpoint name and the operation to set the soap action. I am not sure this is exactly right. But something like that should be in SoapAction. 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
Re: svn commit: r494291 - in /geronimo/server/branches/1.2: assemblies/geronimo-boilerplate-minimal/ modules/geronimo-client-builder/src/main/java/org/apache/geronimo/client/builder/jsr88/ modules/ger
I am pretty busy this week (sorry for not yet having posted information about how to trial Jetty clustering). However, I am happy to give a shot at option #1 next week. Thanks, Gianny On 10/01/2007, at 3:17 PM, David Jencks wrote: I reversed this change and made it so the console can do jsr88, the online deployer works ok, and there are no apparent tck problems, and we don't need geronimo-deploy-config in lib. I think trunk and 1.2 are in sync with this code. Does anyone think getting remote jsr88 working is a high priority or want to work on it themselves? thanks david jencks On Jan 9, 2007, at 6:16 PM, David Jencks wrote: I'm going to start by disabling all the module configurers outside the running server. If we support jsr88 dconfigbeans outside the server, they need to be enabled in quite a different way than in the server. I agree that the jsr88 stuff should be in different jars than the builder stuff, we've known this for a while but there hasn't been much urgency. If we're going to support jsr88 out of the server, we need to find a way of registering the module configurers with the DeploymentManager outside the server. Some possibilities, I don't have a strong opinion on which is best. I'm very clear that all the classes needed for this support need to be loaded out of the g. repository, not lib. - start up a kernel with a list of modules to start, and use that to make the moduleConfigurers register. - have a bunch of stuff in a manifest that says what jars are needed and what moduleConfigurers to register - have some other configuration file for this purpose. I lean towards the first option, and think perhaps we should wait until kernel bootstrapping is less reliant on lib. IIRC dain and possibly other people have prototypes of how to have some kind of bootstrap repository that needs only one or two jars in lib, the rest coming from the repo. Anyone think remote dconfigbeans are a pressing issue? thanks david jencks On Jan 9, 2007, at 2:57 PM, Gianny Damour wrote: Hi, this is the content of the email that I sent with the title jsr88 - ModuleConfigurer - still some classpath problems. The online deployer, e.g. deployer.jar, needs to have geronimo- deploy-config along with all the modules providing an implementation of this interface added as MANIFEST ClassPath entries. It seems to me that to have the relevant geonimo-*- builder is not so great: builders are executed server side and actually install something on the server. It seems to me that ModuleConfigurers are intended to be used disconnected from the server during the configuration stage of modules. So, perhaps that ModuleConfigurers should be move to their own module in order to make that a little bit clearer. As you are working on this David J., I would like to know if this makes sense or if you have a better idea. Thanks, Gianny On 09/01/2007, at 3:00 PM, David Jencks wrote: On Jan 8, 2007, at 8:21 PM, [EMAIL PROTECTED] wrote: Author: kevan Date: Mon Jan 8 17:21:35 2007 New Revision: 494291 URL: http://svn.apache.org/viewvc?view=revrev=494291 Log: Fix some deploy problems. geronimo-deploy-config needs to be in lib. What goes wrong if it isn't? I wondered if this would be a problem. New Configurers needed to be serializable... what happens if they aren't? If we can't get away from this we should make ModuleConfigurer extend Serializable... I don't like adding more and more to lib. if this is only needed for jsr88 stuff I think we should consider starting up something on request to load the configurer gbeas and register them, using the repo. thanks david jencks
Re: REG.JBI Component
Thanks , I have gone through url what u gave and it is useful for me. gnodet wrote: Take a look at the wsdl-first demo in servicemix 3.1-SNAPSHOT distribution. On 1/9/07, Smruti [EMAIL PROTECTED] wrote: Hello, I want to expose my webservice as servicemix cmponent using JAXWS. but no documentation given for that .. anyone can help me to do that? Regards, Smruti -- View this message in context: http://www.nabble.com/REG.JBI-Component-tf2945358s12049.html#a8236236 Sent from the ServiceMix - Dev mailing list archive at Nabble.com. -- Cheers, Guillaume Nodet -- View this message in context: http://www.nabble.com/REG.JBI-Component-tf2945358s12049.html#a8254532 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
[jira] Commented: (GERONIMO-2717) Geronimo Axis2 Integration
[ https://issues.apache.org/jira/browse/GERONIMO-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463534 ] Davanum Srinivas commented on GERONIMO-2717: thanks lasantha. i will take a crack at this today. -- dims Geronimo Axis2 Integration -- Key: GERONIMO-2717 URL: https://issues.apache.org/jira/browse/GERONIMO-2717 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: webservices Reporter: Lasantha Ranaweera Attachments: geronimo-axis2.zip -- 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-2717) Geronimo Axis2 Integration
[ https://issues.apache.org/jira/browse/GERONIMO-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463551 ] Davanum Srinivas commented on GERONIMO-2717: Lasantha, checked in the contents of the zip (r494810). Will take a look at the TODO's to see if can help too. thanks, dims Geronimo Axis2 Integration -- Key: GERONIMO-2717 URL: https://issues.apache.org/jira/browse/GERONIMO-2717 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: webservices Reporter: Lasantha Ranaweera Attachments: geronimo-axis2.zip -- 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: Web Builders
--- 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. I changed j2ee-schema to use geronimo-schema-jee_5 jar. So I must change j2ee-builder, in other word the EarConfigBuilder should use org.apache.geronimo.xbeans.javaee.* This means the test war/jar/rars must be generated for javaee5. Does SchemaConversion need to be updated to handle conversion from 1.4 to 5 namespace? 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. Are the following tests still meaningful? GenericToSpecificPlanConverter WebAppDconfigTest Thanks Anita 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 Have a burning question? Go to www.Answers.yahoo.com and get answers from real people who know.
[jira] Closed: (GERONIMO-2628) Upgrade to tomcat 6.0.2 beta
[ https://issues.apache.org/jira/browse/GERONIMO-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-2628. -- Resolution: Fixed Fix Version/s: (was: 2.0) 2.0-M1 Upgrade to tomcat 6.0.2 beta Key: GERONIMO-2628 URL: https://issues.apache.org/jira/browse/GERONIMO-2628 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.0 Reporter: Paul McMahan Assigned To: Paul McMahan Priority: Critical Fix For: 2.0-M1 Geronimo's Java EE 5 implementation needs Servlet 2.5 and JSP 2.1. -- 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] Created: (GERONIMO-2718) Upgrade to tomcat 6.0.7 beta
Upgrade to tomcat 6.0.7 beta Key: GERONIMO-2718 URL: https://issues.apache.org/jira/browse/GERONIMO-2718 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: Tomcat Affects Versions: 2.0 Reporter: Paul McMahan Assigned To: Paul McMahan Priority: Critical Fix For: 2.0-M2 Upgrade to tomcat 6.0.7 beta. Also discontinue use of the private maven repo at people.apache.org/~pmcmahan since the tomcat team has now published the jars in the apache snapshot repo. -- 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] Created: (AMQCPP-39) Some AMQCPP includes not installed when doing make install on Linux
Some AMQCPP includes not installed when doing make install on Linux --- Key: AMQCPP-39 URL: https://issues.apache.org/activemq/browse/AMQCPP-39 Project: ActiveMQ C++ Client Issue Type: Bug Affects Versions: 1.1 Reporter: Albert Strasheim Assigned To: Nathan Mittler Priority: Minor Fix For: 1.1 Attachments: amqcpp-missing-includes.diff On Linux with the autotools build system, it seems that some headers aren't being installed. Patch for src/main/Makefile.am attached that fixes those that we ran into. There might be more -- maybe you want to make a script that checks that Makefile.am lists all the headers (or maybe use some kind of glob if that's possible). -- 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: (DAYTRADER-17) Dojo-based interface for Daytrader
[ https://issues.apache.org/jira/browse/DAYTRADER-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher James Blythe updated DAYTRADER-17: -- Attachment: daytrader-17-01092007.zip Dojo-based interface for Daytrader -- Key: DAYTRADER-17 URL: https://issues.apache.org/jira/browse/DAYTRADER-17 Project: DayTrader Issue Type: New Feature Components: Web Tier Affects Versions: 1.2 Reporter: Christopher James Blythe Attachments: daytrader-17-01092007.zip, daytrader-17.zip Have opened this to track work on the Dojo-based UI for Daytrader that I have been playing around with. -- 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] Updated: (DAYTRADER-17) Dojo-based interface for Daytrader
[ https://issues.apache.org/jira/browse/DAYTRADER-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher James Blythe updated DAYTRADER-17: -- Attachment: (was: daytrader-17.zip) Dojo-based interface for Daytrader -- Key: DAYTRADER-17 URL: https://issues.apache.org/jira/browse/DAYTRADER-17 Project: DayTrader Issue Type: New Feature Components: Web Tier Affects Versions: 1.2 Reporter: Christopher James Blythe Attachments: daytrader-17-01092007.zip, daytrader-17.zip Have opened this to track work on the Dojo-based UI for Daytrader that I have been playing around with. -- 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] Created: (AMQCPP-40) A few stray unix and sun defines
A few stray unix and sun defines
Key: AMQCPP-40
URL: https://issues.apache.org/activemq/browse/AMQCPP-40
Project: ActiveMQ C++ Client
Issue Type: Improvement
Affects Versions: 1.1
Reporter: Albert Strasheim
Assigned To: Nathan Mittler
Priority: Minor
Fix For: 1.1
The AMQCPP code still contains a few references to the unix and sun defines.
{noformat}
./src/main/activemq/concurrent/Mutex.h:#if (defined(__unix__) || defined(unix)
|| defined(MACOSX)) !defined(USG)
./src/main/activemq/concurrent/Thread.h:#if (defined(__unix__) || defined(unix)
|| defined(MACOSX) || defined(__APPLE__)) !defined(USG)
./src/main/activemq/util/Guid.h:#if defined( unix ) ||
defined(__APPLE__)
./src/main/activemq/util/Config.h: // used by unix like systems (including
cygwin)
./src/main/activemq/util/Config.h: #elif defined( unix )
./src/main/activemq/util/Endian.h:#if defined( unix ) || defined(__APPLE__)
./src/main/activemq/util/Endian.h:# if defined( unix ) || defined(__APPLE__)
./src/main/activemq/network/ServerSocket.h: #if !defined( unix ) ||
defined( __CYGWIN__ )
./src/main/activemq/network/SocketOutputStream.cpp:#elif defined( unix )
!defined( __CYGWIN__ ) !defined( sun )
{noformat}
These should probably be replaced by some kind of AMQ_ variant. It would nice
if one could define a single AMQ_something per platform, akin to Windows's
_WIN32 define.
--
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: (DAYTRADER-20) Daytrader ear includes lots of kitchen sinks
[ https://issues.apache.org/jira/browse/DAYTRADER-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463572 ] Christopher James Blythe commented on DAYTRADER-20: --- Hmmm. I haven't noted this at all when building from the 1.2 branch. The only jar/war files that are packaged inside the ear are the ones that should be there... Did you make any changes to the 1.2 branch to fix this? Can this issue be closed? Archive: daytrader-ear-1.2-SNAPSHOT.ear testing: META-INF/OK testing: META-INF/MANIFEST.MF OK testing: dt-ejb.jar OK testing: streamer.jar OK testing: wsappclient.jar OK testing: web.war OK testing: META-INF/LICENSE.txt OK testing: META-INF/application.xml OK testing: META-INF/NOTICE.txt OK testing: META-INF/maven/ OK testing: META-INF/maven/org.apache.geronimo.daytrader/ OK testing: META-INF/maven/org.apache.geronimo.daytrader/daytrader-ear/ OK testing: META-INF/maven/org.apache.geronimo.daytrader/daytrader-ear/pom.xml OK testing: META-INF/maven/org.apache.geronimo.daytrader/daytrader-ear/pom.properties OK Daytrader ear includes lots of kitchen sinks Key: DAYTRADER-20 URL: https://issues.apache.org/jira/browse/DAYTRADER-20 Project: DayTrader Issue Type: Bug Components: buildsystem Affects Versions: 1.2 Reporter: David Jencks Assigned To: David Jencks Fix For: 1.2 Currently the ear includes about 10-15 dependent jars it shouldn't. The m2 dependency scopes need to be adjusted to fix this. I'll fix this in trunk (2.0), also an issue in 1.2 branch -- 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] Assigned: (AMQCPP-39) Some AMQCPP includes not installed when doing make install on Linux
[ https://issues.apache.org/activemq/browse/AMQCPP-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reassigned AMQCPP-39: -- Assignee: Timothy Bish (was: Nathan Mittler) Some AMQCPP includes not installed when doing make install on Linux --- Key: AMQCPP-39 URL: https://issues.apache.org/activemq/browse/AMQCPP-39 Project: ActiveMQ C++ Client Issue Type: Bug Affects Versions: 1.1 Reporter: Albert Strasheim Assigned To: Timothy Bish Priority: Minor Fix For: 1.1 Attachments: amqcpp-missing-includes.diff On Linux with the autotools build system, it seems that some headers aren't being installed. Patch for src/main/Makefile.am attached that fixes those that we ran into. There might be more -- maybe you want to make a script that checks that Makefile.am lists all the headers (or maybe use some kind of glob if that's possible). -- 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: Geronimo Axis2 Integration
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
[jira] Resolved: (AMQCPP-39) Some AMQCPP includes not installed when doing make install on Linux
[ https://issues.apache.org/activemq/browse/AMQCPP-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-39. Resolution: Fixed Applied in Trunk. Some AMQCPP includes not installed when doing make install on Linux --- Key: AMQCPP-39 URL: https://issues.apache.org/activemq/browse/AMQCPP-39 Project: ActiveMQ C++ Client Issue Type: Bug Affects Versions: 1.1 Reporter: Albert Strasheim Assigned To: Timothy Bish Priority: Minor Fix For: 1.1 Attachments: amqcpp-missing-includes.diff On Linux with the autotools build system, it seems that some headers aren't being installed. Patch for src/main/Makefile.am attached that fixes those that we ran into. There might be more -- maybe you want to make a script that checks that Makefile.am lists all the headers (or maybe use some kind of glob if that's possible). -- 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-2716) Create javaee 5 test jars for j2ee-builder tests
[ https://issues.apache.org/jira/browse/GERONIMO-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha updated GERONIMO-2716: - Attachment: testsupport.diff 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 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
Geronimo Eclipse Plug-in: What next? A wizard to auto generate Geronimo deployment plans by scanning the corresponding Java-EE plans/annotations
Hi all, Geronimo Eclipse plug-in now has a full fledged Editor for editing geronimo-web.xml. User interface for the following schemas has been implemented: i) http://geronimo.apache.org/schemas-1.1/geronimo-web-1.1.xsd ii) http://geronimo.apache.org/schemas-1.1/geronimo-module-1.1.xsd iii) http://geronimo.apache.org/schemas-1.1/geronimo-naming-1.1.xsd iv) http://geronimo.apache.org/schemas-1.1/geronimo-security-1.1.xsd Sachin, Request you to review and commit the consolidated patch available in https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-129 and if possible please put a binary in http://people.apache.org/dist/geronimo/eclipse/unstable/ so that people can start using it and report any problems they face. So what next? Here is what I can think of next. Please add to this list any features that you think would simply developing Java EE apps on Geronimo. 1) Wizard for auto generating Geronimo deployment plan by scanning the corresponding Java-EE plan/annotation: Say for WARs, this could be achieved by scanning web.xml (in case of J2EE 1.4) or corresponding annotations (in case of Java EE 5) and then running the user through a Wizard where he can specify the missing data. Sachin, Is GERONIMODEVTOOLS-112 (Loading deployment plan editor on empty file should auto-create plan) addressing the same? 2) Editing of other deployment plans: Full fledged Editors for editing of i) openejb-jar.xml (EJB JAR), ii) geronimo-ra.xml (J2EE Connector), iii) geronimo-application-client.xml (Client Application) iv) geronimo-application.xml (Enterprise Application) 3) Extensive user help in various Wizards during create/edit of Geronimo deployment plans User help ((like instructions and snippets of xml-elements that will be generated) to be added in each of the wizards. This help text could be integrated into the corrersponding schemas in xs:documentation elements and then extracted from within Wizards to generate user help. I remember some discussions on the dev-list about documenting Geronimo xml-schemas. Please reply if someone is working on it. -- Thx, Shiva
[jira] Commented: (GERONIMO-2716) Create javaee 5 test jars for j2ee-builder tests
[ https://issues.apache.org/jira/browse/GERONIMO-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463578 ] Anita Kulshreshtha commented on GERONIMO-2716: -- Prasad, I have attached a patch to this issue. I am planning to make these changes to testsupport. I do not run testsuite hence do not know if these changes will break anything in it. Could you please take a look at the patch? Thanks Anita https://issues.apache.org/jira/browse/GERONIMO-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index 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 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: G specific annotations for 2.0, XDoclet or 175?
Wouldn't Geronimo specific annotations lead to porting problems? Having developers to edit and recompile source files inside App Server independent Java EE archives, whenever they want to port their apps from one App server to another, would be cumbersome. Isn't it? Rather than coming up with Geronimo specific annotations, why not put the same effort in automating the generation of Geronimo specific deployment plans. This could be achieved by scanning the corresponding Java-EE plans/annotations and then running the user through a Wizard where he can specify the missing data. I will start a separate thread on this. Others please comment. Finalizing on this would help us to concentrate on developing the required features in Geronimo Eclipse plug-in. -- Thx, Shiva On 11/29/06, Sachin Patel [EMAIL PROTECTED] 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
[jira] Created: (AMQCPP-41) Byte swap on float and double truncates values
Byte swap on float and double truncates values
--
Key: AMQCPP-41
URL: https://issues.apache.org/activemq/browse/AMQCPP-41
Project: ActiveMQ C++ Client
Issue Type: Bug
Affects Versions: 1.1
Reporter: Albert Strasheim
Assigned To: Nathan Mittler
Priority: Critical
Fix For: 1.1
Attachments: doublefloat-truncate.diff
activemq::util::Endian::byteSwap truncates float and double values due to the
C-style cast it uses.
Patch for BytesMessageCommandTest is attached that shows the problem. One might
consider expanding this test to check that the minimum, maximum, -1, 0, 1 (and
-inf and inf where appropriate) and a few other values can successfully be
serialised and deserialised for each of the types.
Also in the patch is our attempt at fixing byteSwap. You'll notice that we do
something very strange: we take the argument of byteSwap and make a copy on the
heap. The reason for this is that simply doing:
{noformat}
const uintxx_t swapped_val = byteSwap( *(uintxx_t*)(value) );
{noformat}
i.e. taking the address of value instead of using the copy on the heap, fails
with GCC 4.0.2 and GCC 4.0.3. I'm guessing GCC might be trying to inline the
call to byteSwap and then something goes very wrong when taking the address of
a variable on the stack. Hopefully someone has a better idea for a workaround.
--
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: (DAYTRADER-17) Dojo-based interface for Daytrader
[ https://issues.apache.org/jira/browse/DAYTRADER-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463565 ] Christopher James Blythe commented on DAYTRADER-17: --- I just uploaded a new patch (daytrader-17-01092007.zip ) which... - Assumes the dojo src is available at /dojo/dojo.js (src is no longer included in the patch) - Supports Dojo 0.4.1 Once installed, the new ui can be accessed at the following url: /dojotrader/trader.html Note: The only existing file updated in the patch is the top-level pom.xml file. Otherwise, the zip file creates three new sub-directories under the modules directory (dojo-ui-ear, dojo-ui-web, json-proxy). Dojo-based interface for Daytrader -- Key: DAYTRADER-17 URL: https://issues.apache.org/jira/browse/DAYTRADER-17 Project: DayTrader Issue Type: New Feature Components: Web Tier Affects Versions: 1.2 Reporter: Christopher James Blythe Attachments: daytrader-17-01092007.zip, daytrader-17.zip Have opened this to track work on the Dojo-based UI for Daytrader that I have been playing around with. -- 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-40) A few stray unix and sun defines
[
https://issues.apache.org/activemq/browse/AMQCPP-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37849
]
Timothy Bish commented on AMQCPP-40:
These are standard defines, so I don't think its all that important to tackle
this now.
A few stray unix and sun defines
Key: AMQCPP-40
URL: https://issues.apache.org/activemq/browse/AMQCPP-40
Project: ActiveMQ C++ Client
Issue Type: Improvement
Affects Versions: 1.1
Reporter: Albert Strasheim
Assigned To: Nathan Mittler
Priority: Minor
Fix For: 1.1
The AMQCPP code still contains a few references to the unix and sun defines.
{noformat}
./src/main/activemq/concurrent/Mutex.h:#if (defined(__unix__) ||
defined(unix) || defined(MACOSX)) !defined(USG)
./src/main/activemq/concurrent/Thread.h:#if (defined(__unix__) ||
defined(unix) || defined(MACOSX) || defined(__APPLE__)) !defined(USG)
./src/main/activemq/util/Guid.h:#if defined( unix ) ||
defined(__APPLE__)
./src/main/activemq/util/Config.h: // used by unix like systems
(including cygwin)
./src/main/activemq/util/Config.h: #elif defined( unix )
./src/main/activemq/util/Endian.h:#if defined( unix ) || defined(__APPLE__)
./src/main/activemq/util/Endian.h:# if defined( unix ) || defined(__APPLE__)
./src/main/activemq/network/ServerSocket.h: #if !defined( unix ) ||
defined( __CYGWIN__ )
./src/main/activemq/network/SocketOutputStream.cpp:#elif defined( unix )
!defined( __CYGWIN__ ) !defined( sun )
{noformat}
These should probably be replaced by some kind of AMQ_ variant. It would nice
if one could define a single AMQ_something per platform, akin to Windows's
_WIN32 define.
--
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] Assigned: (AMQCPP-41) Byte swap on float and double truncates values
[
https://issues.apache.org/activemq/browse/AMQCPP-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish reassigned AMQCPP-41:
--
Assignee: Timothy Bish (was: Nathan Mittler)
Byte swap on float and double truncates values
--
Key: AMQCPP-41
URL: https://issues.apache.org/activemq/browse/AMQCPP-41
Project: ActiveMQ C++ Client
Issue Type: Bug
Affects Versions: 1.1
Reporter: Albert Strasheim
Assigned To: Timothy Bish
Priority: Critical
Fix For: 1.1
Attachments: doublefloat-truncate.diff
activemq::util::Endian::byteSwap truncates float and double values due to the
C-style cast it uses.
Patch for BytesMessageCommandTest is attached that shows the problem. One
might consider expanding this test to check that the minimum, maximum, -1, 0,
1 (and -inf and inf where appropriate) and a few other values can
successfully be serialised and deserialised for each of the types.
Also in the patch is our attempt at fixing byteSwap. You'll notice that we do
something very strange: we take the argument of byteSwap and make a copy on
the heap. The reason for this is that simply doing:
{noformat}
const uintxx_t swapped_val = byteSwap( *(uintxx_t*)(value) );
{noformat}
i.e. taking the address of value instead of using the copy on the heap, fails
with GCC 4.0.2 and GCC 4.0.3. I'm guessing GCC might be trying to inline the
call to byteSwap and then something goes very wrong when taking the address
of a variable on the stack. Hopefully someone has a better idea for a
workaround.
--
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-41) Byte swap on float and double truncates values
[
https://issues.apache.org/activemq/browse/AMQCPP-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37853
]
Timothy Bish commented on AMQCPP-41:
You'll need to commit a new patch that works against the latest trunk. Changes
have been made that address some of this already.
Byte swap on float and double truncates values
--
Key: AMQCPP-41
URL: https://issues.apache.org/activemq/browse/AMQCPP-41
Project: ActiveMQ C++ Client
Issue Type: Bug
Affects Versions: 1.1
Reporter: Albert Strasheim
Assigned To: Timothy Bish
Priority: Critical
Fix For: 1.1
Attachments: doublefloat-truncate.diff
activemq::util::Endian::byteSwap truncates float and double values due to the
C-style cast it uses.
Patch for BytesMessageCommandTest is attached that shows the problem. One
might consider expanding this test to check that the minimum, maximum, -1, 0,
1 (and -inf and inf where appropriate) and a few other values can
successfully be serialised and deserialised for each of the types.
Also in the patch is our attempt at fixing byteSwap. You'll notice that we do
something very strange: we take the argument of byteSwap and make a copy on
the heap. The reason for this is that simply doing:
{noformat}
const uintxx_t swapped_val = byteSwap( *(uintxx_t*)(value) );
{noformat}
i.e. taking the address of value instead of using the copy on the heap, fails
with GCC 4.0.2 and GCC 4.0.3. I'm guessing GCC might be trying to inline the
call to byteSwap and then something goes very wrong when taking the address
of a variable on the stack. Hopefully someone has a better idea for a
workaround.
--
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-41) Byte swap on float and double truncates values
[
https://issues.apache.org/activemq/browse/AMQCPP-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37854
]
Albert Strasheim commented on AMQCPP-41:
Looking at the stack trace produced by Valgrind when it detects the error that
happens in byteSwap also seems to indicate that inlining is happening. Valgrind
reports the method at the top of the stack as readDouble from
BytesMessageCommand, but the source line as being in Endian.h.
Byte swap on float and double truncates values
--
Key: AMQCPP-41
URL: https://issues.apache.org/activemq/browse/AMQCPP-41
Project: ActiveMQ C++ Client
Issue Type: Bug
Affects Versions: 1.1
Reporter: Albert Strasheim
Assigned To: Timothy Bish
Priority: Critical
Fix For: 1.1
Attachments: doublefloat-truncate.diff
activemq::util::Endian::byteSwap truncates float and double values due to the
C-style cast it uses.
Patch for BytesMessageCommandTest is attached that shows the problem. One
might consider expanding this test to check that the minimum, maximum, -1, 0,
1 (and -inf and inf where appropriate) and a few other values can
successfully be serialised and deserialised for each of the types.
Also in the patch is our attempt at fixing byteSwap. You'll notice that we do
something very strange: we take the argument of byteSwap and make a copy on
the heap. The reason for this is that simply doing:
{noformat}
const uintxx_t swapped_val = byteSwap( *(uintxx_t*)(value) );
{noformat}
i.e. taking the address of value instead of using the copy on the heap, fails
with GCC 4.0.2 and GCC 4.0.3. I'm guessing GCC might be trying to inline the
call to byteSwap and then something goes very wrong when taking the address
of a variable on the stack. Hopefully someone has a better idea for a
workaround.
--
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: (GERONIMO-2719) Use released Jetty 6.1 in Geronimo 2.0-M2
Use released Jetty 6.1 in Geronimo 2.0-M2 - Key: GERONIMO-2719 URL: https://issues.apache.org/jira/browse/GERONIMO-2719 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Jetty Affects Versions: 2.0-M2 Reporter: Joe Bohn Assigned To: Joe Bohn For 2.0-M1 we released with the Jetty 6.1. Now that Jetty has released 6.1 we need to move to 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
[jira] Commented: (GERONIMO-2716) Create javaee 5 test jars for j2ee-builder tests
[ https://issues.apache.org/jira/browse/GERONIMO-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463606 ] Prasad Kashyap commented on GERONIMO-2716: -- Cool. Let me take a look and get back. Thanx Anita. 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 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
cxfPojoWS tests in testsuite
David (Jencks), The cxfPojoWS/server test in the testsuite has only 1 test and that too is commented out. This is currently under testsuite/itests. The other tests that Jarek contributed have now been renamed as more generic jaxws-tests and moved to the webservices-testsuite. What should happen to the cxfPojoWS/server tests ? a) delete them b) rename them and move them under webservices-testsuite. Thanx Prasad
Re: cxfPojoWS tests in testsuite
I dunno... but in the future lets avoid CamelCase for these dir names... I keep thinking cxfPojoWS is just some random chars. --jason On Jan 10, 2007, at 10:58 AM, Prasad Kashyap wrote: David (Jencks), The cxfPojoWS/server test in the testsuite has only 1 test and that too is commented out. This is currently under testsuite/itests. The other tests that Jarek contributed have now been renamed as more generic jaxws-tests and moved to the webservices-testsuite. What should happen to the cxfPojoWS/server tests ? a) delete them b) rename them and move them under webservices-testsuite. Thanx Prasad
[jira] Commented: (SM-810) Create single complete ServiceMix Shared Library
[
https://issues.apache.org/activemq/browse/SM-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37856
]
Guillaume Nodet commented on SM-810:
Have you tried with the servicemix-shared-compat library available at
http://fisheye3.cenqua.com/browse/servicemix/trunk/deployables/sharedlibraries/servicemix-shared-compat
?
Here is the list of jars included in the SL (building from svn head):
{code}
activeio-core-3.0.0-incubator.jar
activemq-core-4.1-incubator-20070103.jar
aopalliance-1.0.jar
backport-util-concurrent-2.2.jar
bcprov-jdk14-124.jar
commons-beanutils-core-1.7.0.jar
commons-collections-3.1.jar
commons-dbcp-1.2.jar
commons-lang-2.1.jar
commons-logging-1.1.jar
commons-pool-1.2.jar
geronimo-connector-1.2-beta.jar
geronimo-ejb_2.1_spec-1.1.jar
geronimo-j2ee-connector_1.5_spec-1.1.jar
geronimo-j2ee-jacc_1.0_spec-1.1.jar
geronimo-j2ee-management_1.0_spec-1.1.jar
geronimo-jms_1.1_spec-1.1.jar
geronimo-jta_1.0.1B_spec-1.1.jar
geronimo-transaction-1.2-beta.jar
howl-1.0.1-1.jar
jaxen-1.1-beta-9.jar
jencks-2.0.jar
log4j-1.2.12.jar
mx4j-3.0.1.jar
mx4j-remote-3.0.1.jar
opensaml-1.1.jar
regexp-1.3.jar
servicemix-common-3.1-incubating-SNAPSHOT.jar
servicemix-core-3.1-incubating-SNAPSHOT.jar
servicemix-services-3.1-incubating-SNAPSHOT.jar
servicemix-shared-compat-3.1-incubating-SNAPSHOT.jar
servicemix-soap-3.1-incubating-SNAPSHOT.jar
spring-beans-2.0.1.jar
spring-context-2.0.1.jar
spring-core-2.0.1.jar
spring-jmx-2.0.1.jar
stax-api-1.0.1.jar
wsdl4j-1.6.1.jar
wss4j-1.5.0.jar
wstx-asl-3.0.3.jar
xalan-2.7.0.jar
xbean-classloader-2.8.jar
xbean-kernel-2.8.jar
xbean-server-2.8.jar
xbean-spring-2.8.jar
xmlsec-1.3.0.jar
xstream-1.1.2.jar
{code}
It may need some modifications if there are missing or unneeded jars,
but it would be a better start.
Btw, I don't think it would reduce the jars in the lib folder,
as most of / all these jars are needed for the JBI container itself.
Create single complete ServiceMix Shared Library
Key: SM-810
URL: https://issues.apache.org/activemq/browse/SM-810
Project: ServiceMix
Issue Type: Improvement
Affects Versions: 3.0
Environment: ServiceMix 3.0
Reporter: James Lorenzen
Original Estimate: 1 day
Remaining Estimate: 1 day
The current ServiceMix Shared Library is insufficient to support proper
portability of existing ServiceMix components to other JBI containers, such
as OpenESB. For example, when installing the ServiceMix HTTP BC in OpenESB,
NoClassDefFoundErrors occur because the installed ServiceMix Shared Library
does not contain all the necessary dependencies.
Therefore it would be a good idea to create a single complete Shared Library.
To accomplish this here are some ideas:
1) Combine the shared library and shared library compat projects together.
2) Ensure the new single complete Shared Library contains the following
dependencies:
a) activemq-core
b) backport-util-concurrent
c) commons-logging
d) servicemix-core
e) servicemix-services
f) spring-2.0-rc3
g) wsdl4j
h) xbean-classloader
i) xbean-kernel
j) xbean-server
k) xbean-spring
When complete the dependencies under /servicemix_home/lib should be smaller.
--
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-808) Servicemix jboss deployer
[
https://issues.apache.org/activemq/browse/SM-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37857
]
Eric Dofonsou commented on SM-808:
--
I've done a quick check online for the jboss version of Xalan seems to be
missing the xsltc part :
http://jira.jboss.com/jira/browse/JBAS-2155
Judging from the size of the files, the one with jboss version is only 1.7 meg
while the one in servicemix repository is 2 megs.
{quote}
--([EMAIL PROTECTED])-(/media/DATA/devtools/jboss-4.0.5.GA/lib/endorsed)--
--(1045:Wed,10 Jan 07:$)-- ls -al xalan.jar
-rwxrwx--- 1 root plugdev 1713696 2006-12-19 14:38 xalan.jar
--([EMAIL PROTECTED])-(/media/DATA/devtools/jboss-4.0.5.GA/lib/endorsed)--
--(1048:Wed,10 Jan 07:$)-- ls -al
~/.m2/repository/xalan/xalan/2.7.0/xalan-2.7.0.jar
-rw-r--r-- 1 ewrick ewrick 2730442 2006-12-18 09:41
/home/ewrick/.m2/repository/xalan/xalan/2.7.0/xalan-2.7.0.jar
--([EMAIL PROTECTED])-(/media/DATA/devtools/jboss-4.0.5.GA/lib/endorsed)--
{quote}
What do you mean by removing that hard dependency ? do you want to provide an
external document builder wrapper around xalan ?
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
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
Re: Geronimo Axis2 Integration
Lin, We generated the jaxb code by hand since the SUN xsd's can't be checked in. -- dims On 1/10/07, Lin Sun [EMAIL PROTECTED] 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-2720) tomcat https connector needs additional param
tomcat https connector needs additional param - Key: GERONIMO-2720 URL: https://issues.apache.org/jira/browse/GERONIMO-2720 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Tomcat Affects Versions: 2.0-M1, 2.0-M2 Reporter: Paul McMahan Assigned To: Paul McMahan Priority: Critical Fix For: 2.0-M2 In tomcat 6.x the connector needs an additional parameter to enable https - SSLEnabled. Without setting that parameter the connector apparently falls back to http. See discussion at http://www.mail-archive.com/dev@tomcat.apache.org/msg12070.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
[jira] Updated: (AMQCPP-40) A few stray unix and sun defines
[
https://issues.apache.org/activemq/browse/AMQCPP-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQCPP-40:
---
Affects Version/s: (was: 1.1)
2.0
A few stray unix and sun defines
Key: AMQCPP-40
URL: https://issues.apache.org/activemq/browse/AMQCPP-40
Project: ActiveMQ C++ Client
Issue Type: Improvement
Affects Versions: 2.0
Reporter: Albert Strasheim
Assigned To: Nathan Mittler
Priority: Minor
Fix For: 2.0
The AMQCPP code still contains a few references to the unix and sun defines.
{noformat}
./src/main/activemq/concurrent/Mutex.h:#if (defined(__unix__) ||
defined(unix) || defined(MACOSX)) !defined(USG)
./src/main/activemq/concurrent/Thread.h:#if (defined(__unix__) ||
defined(unix) || defined(MACOSX) || defined(__APPLE__)) !defined(USG)
./src/main/activemq/util/Guid.h:#if defined( unix ) ||
defined(__APPLE__)
./src/main/activemq/util/Config.h: // used by unix like systems
(including cygwin)
./src/main/activemq/util/Config.h: #elif defined( unix )
./src/main/activemq/util/Endian.h:#if defined( unix ) || defined(__APPLE__)
./src/main/activemq/util/Endian.h:# if defined( unix ) || defined(__APPLE__)
./src/main/activemq/network/ServerSocket.h: #if !defined( unix ) ||
defined( __CYGWIN__ )
./src/main/activemq/network/SocketOutputStream.cpp:#elif defined( unix )
!defined( __CYGWIN__ ) !defined( sun )
{noformat}
These should probably be replaced by some kind of AMQ_ variant. It would nice
if one could define a single AMQ_something per platform, akin to Windows's
_WIN32 define.
--
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-40) A few stray unix and sun defines
[
https://issues.apache.org/activemq/browse/AMQCPP-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQCPP-40:
---
Fix Version/s: (was: 1.1)
2.0
A few stray unix and sun defines
Key: AMQCPP-40
URL: https://issues.apache.org/activemq/browse/AMQCPP-40
Project: ActiveMQ C++ Client
Issue Type: Improvement
Affects Versions: 2.0
Reporter: Albert Strasheim
Assigned To: Nathan Mittler
Priority: Minor
Fix For: 2.0
The AMQCPP code still contains a few references to the unix and sun defines.
{noformat}
./src/main/activemq/concurrent/Mutex.h:#if (defined(__unix__) ||
defined(unix) || defined(MACOSX)) !defined(USG)
./src/main/activemq/concurrent/Thread.h:#if (defined(__unix__) ||
defined(unix) || defined(MACOSX) || defined(__APPLE__)) !defined(USG)
./src/main/activemq/util/Guid.h:#if defined( unix ) ||
defined(__APPLE__)
./src/main/activemq/util/Config.h: // used by unix like systems
(including cygwin)
./src/main/activemq/util/Config.h: #elif defined( unix )
./src/main/activemq/util/Endian.h:#if defined( unix ) || defined(__APPLE__)
./src/main/activemq/util/Endian.h:# if defined( unix ) || defined(__APPLE__)
./src/main/activemq/network/ServerSocket.h: #if !defined( unix ) ||
defined( __CYGWIN__ )
./src/main/activemq/network/SocketOutputStream.cpp:#elif defined( unix )
!defined( __CYGWIN__ ) !defined( sun )
{noformat}
These should probably be replaced by some kind of AMQ_ variant. It would nice
if one could define a single AMQ_something per platform, akin to Windows's
_WIN32 define.
--
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-2720) tomcat https connector needs additional param
[ https://issues.apache.org/jira/browse/GERONIMO-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-2720. -- Resolution: Fixed tomcat https connector needs additional param - Key: GERONIMO-2720 URL: https://issues.apache.org/jira/browse/GERONIMO-2720 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.0-M1, 2.0-M2 Reporter: Paul McMahan Assigned To: Paul McMahan Priority: Critical Fix For: 2.0-M2 In tomcat 6.x the connector needs an additional parameter to enable https - SSLEnabled. Without setting that parameter the connector apparently falls back to http. See discussion at http://www.mail-archive.com/dev@tomcat.apache.org/msg12070.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
[jira] Created: (GERONIMO-2721) Unable to deploy anything
Unable to deploy anything - Key: GERONIMO-2721 URL: https://issues.apache.org/jira/browse/GERONIMO-2721 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment Affects Versions: 2.0-M2, 2.0 Reporter: Prasad Kashyap Priority: Blocker Fix For: 2.0-M2, 2.0 Geronimo Testsuite failed all testcases since it could not deploy any of the configurations. Please see the exception below. A similar exception is seen when a configuration is attempted to be started. Exception Detail org.apache.geronimo.kernel.InternalKernelException: java.rmi.UnmarshalException: error unmarshalling return; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.geronimo.client.builder.jsr88.ClientConfigurer at org.apache.geronimo.system.jmx.KernelDelegate.getGBean(KernelDelegate.java:87) at org.apache.geronimo.deployment.plugin.jmx.JMXDeploymentManager.initialize(JMXDeploymentManager.java:82) at org.apache.geronimo.deployment.plugin.jmx.RemoteDeploymentManager.init(RemoteDeploymentManager.java:73) at org.apache.geronimo.deployment.plugin.factories.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:130) at javax.enterprise.deploy.shared.factories.DeploymentFactoryManager.getDeploymentManager(DeploymentFactoryManager.java:109) at org.apache.geronimo.mavenplugins.geronimo.module.ModuleMojoSupport.getDeploymentManager(ModuleMojoSupport.java:93) at org.apache.geronimo.mavenplugins.geronimo.module.DeployModuleMojo.distribute(DeployModuleMojo.java:148) at org.apache.geronimo.mavenplugins.geronimo.module.DeployModuleMojo.doExecute(DeployModuleMojo.java:94) at org.apache.geronimo.mavenplugins.geronimo.reporting.ReportingMojoSupport.execute(ReportingMojoSupport.java:100) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.rmi.UnmarshalException: error unmarshalling return; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.geronimo.client.builder.jsr88.ClientConfigurer at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:157) at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:972) at org.apache.geronimo.system.jmx.KernelDelegate.invokeKernel(KernelDelegate.java:880) at org.apache.geronimo.system.jmx.KernelDelegate.getGBean(KernelDelegate.java:81) ... 26 more Caused by: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.geronimo.client.builder.jsr88.ClientConfigurer at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1309) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at sun.rmi.server.UnicastRef.unmarshalValue(UnicastRef.java:290) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:139) ... 31 more Caused by: java.io.NotSerializableException:
Fwd: svn commit: r493249 - in /geronimo/server/trunk/configs: client-deployer/src/plan/ connector-deployer/src/plan/ geronimo-gbean-deployer/ j2ee-deployer/ j2ee-deployer/src/plan/ jetty6-deployer/src
I wonder if this is the cause of the deployment failures I am seeing
in the Testsuite
https://issues.apache.org/jira/browse/GERONIMO-2721
Cheers
Prasad
-- Forwarded message --
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Jan 5, 2007 6:56 PM
Subject: svn commit: r493249 - in /geronimo/server/trunk/configs:
client-deployer/src/plan/ connector-deployer/src/plan/
geronimo-gbean-deployer/ j2ee-deployer/ j2ee-deployer/src/plan/
jetty6-deployer/src/plan/ openejb-deployer/src/plan/
tomcat6-deployer/src/pl...
To: scm@geronimo.apache.org
Author: djencks
Date: Fri Jan 5 15:56:05 2007
New Revision: 493249
URL: http://svn.apache.org/viewvc?view=revrev=493249
Log:
GERONIMO-2686 missed the configs changes in previous commit
Modified:
geronimo/server/trunk/configs/client-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/connector-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/geronimo-gbean-deployer/pom.xml
geronimo/server/trunk/configs/j2ee-deployer/pom.xml
geronimo/server/trunk/configs/j2ee-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/jetty6-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/openejb-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/tomcat6-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/webconsole-jetty6/pom.xml
Modified: geronimo/server/trunk/configs/client-deployer/src/plan/plan.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/configs/client-deployer/src/plan/plan.xml?view=diffrev=493249r1=493248r2=493249
==
--- geronimo/server/trunk/configs/client-deployer/src/plan/plan.xml (original)
+++ geronimo/server/trunk/configs/client-deployer/src/plan/plan.xml
Fri Jan 5 15:56:05 2007
@@ -88,4 +88,6 @@
/gbean
+gbean name=ClientConfigurer
class=org.apache.geronimo.client.builder.jsr88.ClientConfigurer/
+
/module
Modified: geronimo/server/trunk/configs/connector-deployer/src/plan/plan.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/configs/connector-deployer/src/plan/plan.xml?view=diffrev=493249r1=493248r2=493249
==
--- geronimo/server/trunk/configs/connector-deployer/src/plan/plan.xml
(original)
+++ geronimo/server/trunk/configs/connector-deployer/src/plan/plan.xml
Fri Jan 5 15:56:05 2007
@@ -85,4 +85,6 @@
attribute
name=eeNamespaceshttp://java.sun.com/xml/ns/j2ee/attribute
/gbean
+gbean name=RARConfigurer
class=org.apache.geronimo.connector.deployment.RARConfigurer/
+
/module
Modified: geronimo/server/trunk/configs/geronimo-gbean-deployer/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/configs/geronimo-gbean-deployer/pom.xml?view=diffrev=493249r1=493248r2=493249
==
--- geronimo/server/trunk/configs/geronimo-gbean-deployer/pom.xml (original)
+++ geronimo/server/trunk/configs/geronimo-gbean-deployer/pom.xml Fri
Jan 5 15:56:05 2007
@@ -54,6 +54,12 @@
artifactIdgeronimo-j2ee-deployment_1.1_spec/artifactId
/dependency
+!-- jsr88 dconfigbean support base classes --
+dependency
+groupIdorg.apache.geronimo.modules/groupId
+artifactIdgeronimo-deploy-config/artifactId
+version${version}/version
+/dependency
!-- Thirdparty Dependencies --
dependency
Modified: geronimo/server/trunk/configs/j2ee-deployer/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/configs/j2ee-deployer/pom.xml?view=diffrev=493249r1=493248r2=493249
==
--- geronimo/server/trunk/configs/j2ee-deployer/pom.xml (original)
+++ geronimo/server/trunk/configs/j2ee-deployer/pom.xml Fri Jan 5 15:56:05 2007
@@ -92,6 +92,7 @@
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-test-ddbean/artifactId
version${version}/version
+scopetest/scope
/dependency
dependency
Modified: geronimo/server/trunk/configs/j2ee-deployer/src/plan/plan.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/configs/j2ee-deployer/src/plan/plan.xml?view=diffrev=493249r1=493248r2=493249
==
--- geronimo/server/trunk/configs/j2ee-deployer/src/plan/plan.xml (original)
+++ geronimo/server/trunk/configs/j2ee-deployer/src/plan/plan.xml Fri
Jan 5 15:56:05 2007
@@ -145,4 +145,6 @@
attribute
name=eeNamespaceshttp://java.sun.com/xml/ns/j2ee/attribute
/gbean
+gbean name=EARConfigurer
class=org.apache.geronimo.j2ee.jsr88.EARConfigurer/
+
/module
Modified: geronimo/server/trunk/configs/jetty6-deployer/src/plan/plan.xml
URL:
[jira] Closed: (GERONIMO-2721) Unable to deploy anything
[ https://issues.apache.org/jira/browse/GERONIMO-2721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Kashyap closed GERONIMO-2721. Resolution: Fixed Fixed ! Unable to deploy anything - Key: GERONIMO-2721 URL: https://issues.apache.org/jira/browse/GERONIMO-2721 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0-M2, 2.0 Reporter: Prasad Kashyap Priority: Blocker Fix For: 2.0-M2, 2.0 Geronimo Testsuite failed all testcases since it could not deploy any of the configurations. Please see the exception below. A similar exception is seen when a configuration is attempted to be started. Exception Detail org.apache.geronimo.kernel.InternalKernelException: java.rmi.UnmarshalException: error unmarshalling return; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.geronimo.client.builder.jsr88.ClientConfigurer at org.apache.geronimo.system.jmx.KernelDelegate.getGBean(KernelDelegate.java:87) at org.apache.geronimo.deployment.plugin.jmx.JMXDeploymentManager.initialize(JMXDeploymentManager.java:82) at org.apache.geronimo.deployment.plugin.jmx.RemoteDeploymentManager.init(RemoteDeploymentManager.java:73) at org.apache.geronimo.deployment.plugin.factories.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:130) at javax.enterprise.deploy.shared.factories.DeploymentFactoryManager.getDeploymentManager(DeploymentFactoryManager.java:109) at org.apache.geronimo.mavenplugins.geronimo.module.ModuleMojoSupport.getDeploymentManager(ModuleMojoSupport.java:93) at org.apache.geronimo.mavenplugins.geronimo.module.DeployModuleMojo.distribute(DeployModuleMojo.java:148) at org.apache.geronimo.mavenplugins.geronimo.module.DeployModuleMojo.doExecute(DeployModuleMojo.java:94) at org.apache.geronimo.mavenplugins.geronimo.reporting.ReportingMojoSupport.execute(ReportingMojoSupport.java:100) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.rmi.UnmarshalException: error unmarshalling return; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.geronimo.client.builder.jsr88.ClientConfigurer at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:157) at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:972) at org.apache.geronimo.system.jmx.KernelDelegate.invokeKernel(KernelDelegate.java:880) at org.apache.geronimo.system.jmx.KernelDelegate.getGBean(KernelDelegate.java:81) ... 26 more Caused by: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.geronimo.client.builder.jsr88.ClientConfigurer at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1309) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at
Re: ClassLoader, JNDI and Dependency views in console
UIs look great and I'd like to see them included in the Admin Console for 2.0. If/When we start moving existing Portlets out as plug-ins, then at that time we should move this (along with the JMX and LDAP portlets) out as an optional plug-in -Donald Paul McMahan wrote: I think these new UIs look great and are very useful. I'm in favor of integrating them into Geronimo. However, I am concerned about how the patch integrates them. I would very strongly prefer that they be integrated as plugins instead of directly into the admin console. As a matter of fact I think several of the portlets in the current admin console should eventually be factored out as plugins. Then, as the admin console moves towards a more plugin-centric approach the user can integrate these UIs directly into the console or keep them as separate webapps. Best wishes, Paul On 1/5/07, Rakesh Midha [EMAIL PROTECTED] wrote: Hello First of all I am sorry for being missing from the list for last few days, actually I have been trying to get this work item done. I kinda liked the idea of having ClassLoader, JNDI and Dependency views in console. We have discussed this before in dev list, please read the discussion below. I got this thing working, so I created three JIRA's, Please have a look at https://issues.apache.org/jira/browse/GERONIMO-2689 https://issues.apache.org/jira/browse/GERONIMO-2690 https://issues.apache.org/jira/browse/GERONIMO-2691 These three JIRA's adds 3 view in console which shows 1. JNDIView This view shows all the JNDI names binded in various componet contexts as well as Global context. Have a look at https://issues.apache.org/jira/secure/attachment/12348327/12348327_jndi.gif to get idea of what it will show. As we can see it shows JNDI names for which are available at each component context level. For details of how this is implemented please have a look at comments of this JIRA. 2. ClassloaderView This view shows all the classloaders and classes/interfaces loaded by that classloader in heirarchical fashion. Have a look at https://issues.apache.org/jira/secure/attachment/12348333/12348333_classloader.gif to get idea of what it will show. As we can see it shows classes and interfaces for all the classloaders and its child classloaders. For details of how this is implemented please have a look at comments of this JIRA. 3. DependencyView This view shows all the components and repository items and its dependencies in hierarchical fashion in which they are loaded. To facilitate locating of items of interest the tree view can be searched.. Have a look at https://issues.apache.org/jira/secure/attachment/12348336/12348336_dependency.gif to get idea of what it will show. As we can see it shows dependencies for each component. For details of how this is implemented please have a look at comments of this JIRA. This is a request that please try these patches and let me know your comments on it. I think I liked it and these views will definatly be useful for debugging purpose, and from my expierance I can tell that all these views are trying to facilitate solving of problems which are difficult to tackle otherwise. Also notice that we may like to add another section in navigation for debug views as shown in https://issues.apache.org/jira/secure/attachment/12348329/12348329_navigation.gif this is not implemented for now but we may do it once we agree to put the above views in console. Thanks in advance, please do have a look and comment. Rakesh On 7/20/06, Erin Mulder [EMAIL PROTECTED] wrote: Aaron Mulder wrote: http://people.apache.org/~ammulder/classloaders.png However, I'm not sure how useful it will be -- it'll show you dependencies at the class loader level, but it won't tell you which class loaders hold a particular class or which class loader you're actually getting at some point when an error is uncovered. Also, it still needs arrows. :) Right now, the code for that graph produces SVG. It would be great to make it interactive so that you could drag the nodes around, click on a node to load a div that shows which classes are loaded in it, and maybe even collapse certain branches. At JavaOne, I got a few simple JavaScript behaviors working with the graph prototype, but I'm not sure how complex it would be to add full-out drag and drop. Perhaps you can throw the code into the sandbox so other people can check it out and build on it? If I recall correctly, I was careful to make sure that all of its dependencies have Apache-compatible licenses, (which was actually quite difficult). Alternatively, someone could create and share a non-ASF-hosted plugin that makes use of one of the many LGPL graph libraries out there. Cheers, Erin smime.p7s Description: S/MIME Cryptographic Signature
RE: Geronimo Axis2 Integration
Hi Dims, that's cool! Do you think Axis2 will provide and build this generated code for Geronimo to use, similar as what CXF does? This way, we don't necessarily need the java code in Geronimo. Lin -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 11:25 AM To: dev@geronimo.apache.org Subject: Re: Geronimo Axis2 Integration Lin, We generated the jaxb code by hand since the SUN xsd's can't be checked in. -- dims On 1/10/07, Lin Sun [EMAIL PROTECTED] 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: ClassLoader, JNDI and Dependency views in console
Just to be clear, I'm not suggesting that the new viewers should be implemented as plugins to the admin console. The admin console currently does not support pluggability, at least not in a very robust way. I am suggesting that the viewers be implemented as geronimo plugins similar to how the ca-helper application was implemented. It is a separate webapp that can be installed as a plugin and can be reached from the admin console's listing of webapps.My concern is that the admin console is becoming less focused on administrating the server and more of a launching point for all sorts of native UIs. If we really want to make the admin console more useful then IMHO our efforts would be better spent on improving the current function, such as the partially implemented JMS administration portlet for example. Ironically, I think the plugin administration portlet itself also really needs some improvement. :-) Best wishes, Paul On 1/10/07, Donald Woods [EMAIL PROTECTED] wrote: UIs look great and I'd like to see them included in the Admin Console for 2.0. If/When we start moving existing Portlets out as plug-ins, then at that time we should move this (along with the JMX and LDAP portlets) out as an optional plug-in -Donald Paul McMahan wrote: I think these new UIs look great and are very useful. I'm in favor of integrating them into Geronimo. However, I am concerned about how the patch integrates them. I would very strongly prefer that they be integrated as plugins instead of directly into the admin console. As a matter of fact I think several of the portlets in the current admin console should eventually be factored out as plugins. Then, as the admin console moves towards a more plugin-centric approach the user can integrate these UIs directly into the console or keep them as separate webapps. Best wishes, Paul On 1/5/07, Rakesh Midha [EMAIL PROTECTED] wrote: Hello First of all I am sorry for being missing from the list for last few days, actually I have been trying to get this work item done. I kinda liked the idea of having ClassLoader, JNDI and Dependency views in console. We have discussed this before in dev list, please read the discussion below. I got this thing working, so I created three JIRA's, Please have a look at https://issues.apache.org/jira/browse/GERONIMO-2689 https://issues.apache.org/jira/browse/GERONIMO-2690 https://issues.apache.org/jira/browse/GERONIMO-2691 These three JIRA's adds 3 view in console which shows 1. JNDIView This view shows all the JNDI names binded in various componet contexts as well as Global context. Have a look at https://issues.apache.org/jira/secure/attachment/12348327/12348327_jndi.gif to get idea of what it will show. As we can see it shows JNDI names for which are available at each component context level. For details of how this is implemented please have a look at comments of this JIRA. 2. ClassloaderView This view shows all the classloaders and classes/interfaces loaded by that classloader in heirarchical fashion. Have a look at https://issues.apache.org/jira/secure/attachment/12348333/12348333_classloader.gif to get idea of what it will show. As we can see it shows classes and interfaces for all the classloaders and its child classloaders. For details of how this is implemented please have a look at comments of this JIRA. 3. DependencyView This view shows all the components and repository items and its dependencies in hierarchical fashion in which they are loaded. To facilitate locating of items of interest the tree view can be searched.. Have a look at https://issues.apache.org/jira/secure/attachment/12348336/12348336_dependency.gif to get idea of what it will show. As we can see it shows dependencies for each component. For details of how this is implemented please have a look at comments of this JIRA. This is a request that please try these patches and let me know your comments on it. I think I liked it and these views will definatly be useful for debugging purpose, and from my expierance I can tell that all these views are trying to facilitate solving of problems which are difficult to tackle otherwise. Also notice that we may like to add another section in navigation for debug views as shown in https://issues.apache.org/jira/secure/attachment/12348329/12348329_navigation.gif this is not implemented for now but we may do it once we agree to put the above views in console. Thanks in advance, please do have a look and comment. Rakesh On 7/20/06, Erin Mulder [EMAIL PROTECTED] wrote: Aaron Mulder wrote: http://people.apache.org/~ammulder/classloaders.png However, I'm not sure how useful it will be -- it'll show you dependencies at the class loader level, but it won't tell you which class loaders hold a particular class or which class loader you're actually getting at some point when an error is uncovered. Also, it still
[jira] Commented: (GERONIMO-2716) Create javaee 5 test jars for j2ee-builder tests
[ https://issues.apache.org/jira/browse/GERONIMO-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463654 ] Prasad Kashyap commented on GERONIMO-2716: -- Anita, believe this is a partial patch. I was unable to apply it because the test-deployment-javaee_5/* files don't exist yet.. The patch tries to update files in that dir. I get the following when I try to apply the patch http://rifers.org/paste/show/3222 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 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] Commented: (AMQ-1078) Messages consumed with the Resource Adapter are intermittently not delivered
[ https://issues.apache.org/activemq/browse/AMQ-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37861 ] Christopher G. Stach II commented on AMQ-1078: -- Is this fixed, but not closed or not really fixed? Messages consumed with the Resource Adapter are intermittently not delivered Key: AMQ-1078 URL: https://issues.apache.org/activemq/browse/AMQ-1078 Project: ActiveMQ Issue Type: Bug Components: Broker, Connector Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1.1, 4.2.0 The cause is that the ActiveMQSessionExecutor was starting and using it's dispatch thread instead of the Thread managed by the resource adapter. -- 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: Geronimo Axis2 Integration
Sure, we can move things around once we get something working :) -- dims On 1/10/07, Lin Sun [EMAIL PROTECTED] wrote: Hi Dims, that's cool! Do you think Axis2 will provide and build this generated code for Geronimo to use, similar as what CXF does? This way, we don't necessarily need the java code in Geronimo. Lin -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 11:25 AM To: dev@geronimo.apache.org Subject: Re: Geronimo Axis2 Integration Lin, We generated the jaxb code by hand since the SUN xsd's can't be checked in. -- dims On 1/10/07, Lin Sun [EMAIL PROTECTED] 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) -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
[jira] Updated: (GERONIMO-2716) Create javaee 5 test jars for j2ee-builder tests
[ https://issues.apache.org/jira/browse/GERONIMO-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha updated GERONIMO-2716: - Attachment: testsupport.diff 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] Commented: (GERONIMO-2650) JSP 2.1 error in Jetty/Tomcat
[
https://issues.apache.org/jira/browse/GERONIMO-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463662
]
Joe Bohn commented on GERONIMO-2650:
The change in revision http://svn.apache.org/viewcvs?view=revrev=494909 which
listed this JIRA was not actually for this problem. The JIRA was listed
incorrectly in that change and should have been GERONIMO-2719.
JSP 2.1 error in Jetty/Tomcat
-
Key: GERONIMO-2650
URL: https://issues.apache.org/jira/browse/GERONIMO-2650
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: web
Affects Versions: 2.0-M1, 2.0-M2, 2.0
Reporter: Krishnakumar B
Assigned To: Joe Bohn
Fix For: 2.0-M2, 2.0
Attachments: SampleJSP.war
Deploying a web application with JSP 2.1 features throws error in Jetty and
Tomcat
On Tomcat 6:
---
org.apache.jasper.JasperException: /SampleJSP.jsp(12,35) #{..} is not allowed
in template text
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
org.apache.jasper.compiler.ErrorDispatcher.dispatch
(ErrorDispatcher.java:406)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:101)
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:710)
org.apache.jasper.compiler.Node$ELExpression.accept (Node.java:935)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
org.apache.jasper.compiler.Node$Root.accept (Node.java:489)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Validator.validate(Validator.java:1679)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:178)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
org.apache.jasper.JspCompilationContext.compile
(JspCompilationContext.java:566)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:314)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service (JspServlet.java:266)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
On Jetty 6.0:
org.apache.jasper.JasperException: /SampleJSP.jsp(12,35) #{..} is not allowed
in template text
at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
at org.apache.jasper.compiler.ErrorDispatcher.dispatch
(ErrorDispatcher.java:406)
at
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:101)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:710)
at org.apache.jasper.compiler.Node$ELExpression.accept (Node.java:935)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
at org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Validator.validate(Validator.java:1679)
at org.apache.jasper.compiler.Compiler.generateJava (Compiler.java:178)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java :273)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:314)
at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:320)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java :459)
at
org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:62)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
at org.apache.geronimo.jetty6.JettyServletHandler.doHandle
(JettyServletHandler.java:55)
at
org.apache.geronimo.jetty6.JettyServletHandler$ActualJettyServletHandler.handle(JettyServletHandler.java:62)
at org.apache.geronimo.jetty6.JettyServletHandler$NoOpChainedHandler.handle
(JettyServletHandler.java:70)
at
org.apache.geronimo.jetty6.JettyServletHandler.handle(JettyServletHandler.java:47)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:231)
at
[jira] Closed: (GERONIMO-2719) Use released Jetty 6.1 in Geronimo 2.0-M2
[ https://issues.apache.org/jira/browse/GERONIMO-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn closed GERONIMO-2719. -- Resolution: Fixed Fix Version/s: 2.0-M2 fixed in http://svn.apache.org/viewcvs?view=revrev=494909 Use released Jetty 6.1 in Geronimo 2.0-M2 - Key: GERONIMO-2719 URL: https://issues.apache.org/jira/browse/GERONIMO-2719 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.0-M2 Reporter: Joe Bohn Assigned To: Joe Bohn Fix For: 2.0-M2 For 2.0-M1 we released with the Jetty 6.1. Now that Jetty has released 6.1 we need to move to 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
[jira] Commented: (GERONIMO-2719) Use released Jetty 6.1 in Geronimo 2.0-M2
[ https://issues.apache.org/jira/browse/GERONIMO-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463663 ] Joe Bohn commented on GERONIMO-2719: The change in revision http://svn.apache.org/viewcvs?view=revrev=494909 was actually for this JIRA rather than GERONIMO-2650 (which was acidentally listed). Use released Jetty 6.1 in Geronimo 2.0-M2 - Key: GERONIMO-2719 URL: https://issues.apache.org/jira/browse/GERONIMO-2719 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.0-M2 Reporter: Joe Bohn Assigned To: Joe Bohn Fix For: 2.0-M2 For 2.0-M1 we released with the Jetty 6.1. Now that Jetty has released 6.1 we need to move to 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: openejb3 and web services
On Jan 9, 2007, at 8:44 PM, Jarek Gawor wrote: On 1/9/07, David Blevins [EMAIL PROTECTED] wrote: On Jan 9, 2007, at 7:28 AM, David Jencks wrote: On Jan 9, 2007, at 10:19 AM, Jarek Gawor wrote: Hi, I'm looking into integrating CXF with OpenEJB (OpenEJB3 specifically as that's the version that supposed to be integrated in M2). I see that OpenEJB2 has a bunch of code for web services support that's based on Axis1. However, I do not see such code for OpenEJB3. So I'm wondering what that means exactly as we still need support for JAX-RPC-based web services in 2.0. Perhaps the code hasn't been ported over yet or I'm just not finding the right code? Can someone please clarify? I think no one has looked at porting the code yet, but I could be wrong. I hope that whatever we come up with for openejb3 can work with axis1, cxf, and axis2, but I don't yet have an idea if this is practical. Right, it's not ported yet. Do you think this will be ported over before M2? We're most likely looking at M3 for that. -David
[jira] Commented: (GERONIMO-2716) Create javaee 5 test jars for j2ee-builder tests
[ https://issues.apache.org/jira/browse/GERONIMO-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463676 ] Prasad Kashyap commented on GERONIMO-2716: -- The mods in 1.3 and 1.4 apps look good. I had to specify the version for the jsp_2.1 spec dependencies. Maybe you are relying on it being defined at a higher level. 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: ClassLoader, JNDI and Dependency views in console
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: 16:39:38,000 ERROR [PortletFragment] Error in Portlet javax.portlet.PortletException at org.apache.pluto.core.impl.PortletRequestDispatcherImpl.include(Portl etRequestDispatcherImpl.java:76) at org.apache.geronimo.console.classloaderview.ClassLoaderViewPortlet.do View(ClassLoaderViewPortlet.java:64) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247) at javax.portlet.GenericPortlet.render(GenericPortlet.java:175) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218 ) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp atcher.java:683) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationD ispatcher.java:585) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDis patcher.java:505) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvoke rImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.render(PortletInvoke rImpl.java:73) at org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerI mpl.java:119) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.renderPo rtlet(PortletContainerWrapperImpl.java:70) at org.apache.pluto.portalImpl.aggregation.PortletFragment.service(Portl etFragment.java:168) at jsp.WEB_002dINF.aggregation.ColumnFragment_jsp._jspService(ColumnFrag ment_jsp.java:70) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp atcher.java:683) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationD ispatcher.java:585) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDis patcher.java:505) at org.apache.pluto.portalImpl.aggregation.AbstractFragment.service(Abst ractFragment.java:112) at jsp.WEB_002dINF.aggregation.RowFragment_jsp._jspService(RowFragment_j sp.java:67) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp atcher.java:683) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationD ispatcher.java:585) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDis patcher.java:505) at org.apache.pluto.portalImpl.aggregation.AbstractFragment.service(Abst ractFragment.java:112) at jsp.WEB_002dINF.aggregation.PageFragment_jsp._jspService(PageFragment _jsp.java:71) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp atcher.java:683) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationD ispatcher.java:585) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDis patcher.java:505) at org.apache.pluto.portalImpl.aggregation.AbstractFragment.service(Abst ractFragment.java:112) at
Re: NMS byte order for doubles
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
[jira] Created: (GERONIMO-2722) enable commons-logging in tomcat module
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 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. -- 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
[ https://issues.apache.org/jira/browse/GERONIMO-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463714 ] Anita Kulshreshtha commented on GERONIMO-2716: -- Fixed in rev 494959 and 494971. Thanks Prasad! 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-2716) Create javaee 5 test jars for j2ee-builder tests
[ https://issues.apache.org/jira/browse/GERONIMO-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha closed GERONIMO-2716. Resolution: Fixed 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] Created: (GERONIMO-2723) The j2ee-builder module should use geronimo-schema-jee_5 jar
The j2ee-builder module should use geronimo-schema-jee_5 jar - Key: GERONIMO-2723 URL: https://issues.apache.org/jira/browse/GERONIMO-2723 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 The j2ee-builder should use classes from geronimo-schema-jee_5 (see http://www.nabble.com/Web-Builders-p8230881.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
[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_37862
]
Albert Strasheim commented on AMQCPP-25:
The recent changes related to this issue seems to make the unit tests not
compile with Visual Studio 2005 anymore.
{noformat}
g:\activemq-cpp\src\test\activemq\io\dataoutputstreamtest.h(44) : error C2065:
'uint16_t' : undeclared identifier
g:\activemq-cpp\src\test\activemq\io\dataoutputstreamtest.h(44) : error C2146:
syntax error : missing ';' before identifier 'shortVal'
g:\activemq-cpp\src\test\activemq\io\dataoutputstreamtest.h(44) : error C2065:
'shortVal' : undeclared identifier
g:\activemq-cpp\src\test\activemq\io\dataoutputstreamtest.h(45) : error C2065:
'uint32_t' : undeclared identifier
g:\activemq-cpp\src\test\activemq\io\dataoutputstreamtest.h(45) : error C2146:
syntax error : missing ';' before identifier 'intVal'
g:\activemq-cpp\src\test\activemq\io\dataoutputstreamtest.h(45) : error C2065:
'intVal' : undeclared identifier
g:\activemq-cpp\src\test\activemq\io\dataoutputstreamtest.h(46) : error C2065:
'uint64_t' : undeclared identifier
g:\activemq-cpp\src\test\activemq\io\dataoutputstreamtest.h(46) : error C2146:
syntax error : missing ';' before identifier 'longVal'
g:\activemq-cpp\src\test\activemq\io\dataoutputstreamtest.h(46) : error C2065:
'longVal' : undeclared identifier
{noformat}
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
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_37863 ] Timothy Bish commented on AMQCPP-25: Its still work in progress. Should be fixed soon time permitting. 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 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-41) Byte swap on float and double truncates values
[
https://issues.apache.org/activemq/browse/AMQCPP-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37865
]
Albert Strasheim commented on AMQCPP-41:
Thanks, I'll take a look now. We ran into this issue about 6 hours before you
checked in the first stuff to fix AMQCPP-25.
Byte swap on float and double truncates values
--
Key: AMQCPP-41
URL: https://issues.apache.org/activemq/browse/AMQCPP-41
Project: ActiveMQ C++ Client
Issue Type: Bug
Affects Versions: 1.1
Reporter: Albert Strasheim
Assigned To: Timothy Bish
Priority: Critical
Fix For: 1.1
Attachments: doublefloat-truncate.diff
activemq::util::Endian::byteSwap truncates float and double values due to the
C-style cast it uses.
Patch for BytesMessageCommandTest is attached that shows the problem. One
might consider expanding this test to check that the minimum, maximum, -1, 0,
1 (and -inf and inf where appropriate) and a few other values can
successfully be serialised and deserialised for each of the types.
Also in the patch is our attempt at fixing byteSwap. You'll notice that we do
something very strange: we take the argument of byteSwap and make a copy on
the heap. The reason for this is that simply doing:
{noformat}
const uintxx_t swapped_val = byteSwap( *(uintxx_t*)(value) );
{noformat}
i.e. taking the address of value instead of using the copy on the heap, fails
with GCC 4.0.2 and GCC 4.0.3. I'm guessing GCC might be trying to inline the
call to byteSwap and then something goes very wrong when taking the address
of a variable on the stack. Hopefully someone has a better idea for a
workaround.
--
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_37866
]
Albert Strasheim commented on AMQCPP-25:
Running tests against revision 494993 now.
On Fedora Core 4 with GCC 4.0.2, I get the following failures:
{noformat}
1) test:
activemq::connector::stomp::commands::BytesMessageCommandTest::testReadOnly (F)
line: 299 activemq/connector/stomp/commands/BytesMessageCommandTest.h
assertion failed
- Expression: cmd.readFloat() == 2.0f
2) test:
activemq::connector::stomp::commands::BytesMessageCommandTest::testWriteOnly
(F) line: 389 activemq/connector/stomp/commands/BytesMessageCommandTest.h
assertion failed
- Expression: cmd.readFloat() == 2.0f
3) test: activemq::io::DataInputStreamTest::test (F) line: 121
activemq/io/DataInputStreamTest.h
assertion failed
- Expression: floatVal == 10.0f
{noformat}
On Fedora Core 6 with GCC 4.1.1, I get these failures:
{noformat}
1) test:
activemq::connector::stomp::commands::BytesMessageCommandTest::testReadOnly (F)
line: 299 activemq/connector/stomp/commands/BytesMessageCommandTest.h
assertion failed
- Expression: cmd.readFloat() == 2.0f
2) test:
activemq::connector::stomp::commands::BytesMessageCommandTest::testWriteOnly
(F) line: 389 activemq/connector/stomp/commands/BytesMessageCommandTest.h
assertion failed
- Expression: cmd.readFloat() == 2.0f
3) test: activemq::io::DataInputStreamTest::test (F) line: 121
activemq/io/DataInputStreamTest.h
assertion failed
- Expression: floatVal == 10.0f
4) test: activemq::io::DataOutputStreamTest::test (F) line: 93
activemq/io/DataOutputStreamTest.h
assertion failed
- Expression: tempFloat == floatVal
{noformat}
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
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_37868 ] Timothy Bish commented on AMQCPP-25: I don't have a machine with GCC 4.0.2 right at this very minute. Once I do, I'll test it and fix the errors. It currently passes tests on the platforms I have access to. 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 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: svn commit: r493249 - in /geronimo/server/trunk/configs: client-deployer/src/plan/ connector-deployer/src/plan/ geronimo-gbean-deployer/ j2ee-deployer/ j2ee-deployer/src/plan/ jetty6-deployer/src/
It looks like you marked 2721 fixed a couple hours before sending
this message??? I'm confused... is it currently fixed and if so by
what? I'd guess it was fixed by my commits last night in rev 494692
(trunk) and 494701 (1.2). IIRC I ran some Testsuite bits which
passed for me before committing.
thanks
david jencks
On Jan 10, 2007, at 11:58 AM, Prasad Kashyap wrote:
I wonder if this is the cause of the deployment failures I am seeing
in the Testsuite
https://issues.apache.org/jira/browse/GERONIMO-2721
Cheers
Prasad
-- Forwarded message --
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Jan 5, 2007 6:56 PM
Subject: svn commit: r493249 - in /geronimo/server/trunk/configs:
client-deployer/src/plan/ connector-deployer/src/plan/
geronimo-gbean-deployer/ j2ee-deployer/ j2ee-deployer/src/plan/
jetty6-deployer/src/plan/ openejb-deployer/src/plan/
tomcat6-deployer/src/pl...
To: scm@geronimo.apache.org
Author: djencks
Date: Fri Jan 5 15:56:05 2007
New Revision: 493249
URL: http://svn.apache.org/viewvc?view=revrev=493249
Log:
GERONIMO-2686 missed the configs changes in previous commit
Modified:
geronimo/server/trunk/configs/client-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/connector-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/geronimo-gbean-deployer/pom.xml
geronimo/server/trunk/configs/j2ee-deployer/pom.xml
geronimo/server/trunk/configs/j2ee-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/jetty6-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/openejb-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/tomcat6-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/webconsole-jetty6/pom.xml
Modified: geronimo/server/trunk/configs/client-deployer/src/plan/
plan.xml
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/configs/
client-deployer/src/plan/plan.xml?
view=diffrev=493249r1=493248r2=493249
==
--- geronimo/server/trunk/configs/client-deployer/src/plan/plan.xml
(original)
+++ geronimo/server/trunk/configs/client-deployer/src/plan/plan.xml
Fri Jan 5 15:56:05 2007
@@ -88,4 +88,6 @@
/gbean
+gbean name=ClientConfigurer
class=org.apache.geronimo.client.builder.jsr88.ClientConfigurer/
+
/module
Modified: geronimo/server/trunk/configs/connector-deployer/src/plan/
plan.xml
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/configs/
connector-deployer/src/plan/plan.xml?
view=diffrev=493249r1=493248r2=493249
==
--- geronimo/server/trunk/configs/connector-deployer/src/plan/plan.xml
(original)
+++ geronimo/server/trunk/configs/connector-deployer/src/plan/plan.xml
Fri Jan 5 15:56:05 2007
@@ -85,4 +85,6 @@
attribute
name=eeNamespaceshttp://java.sun.com/xml/ns/j2ee/attribute
/gbean
+gbean name=RARConfigurer
class=org.apache.geronimo.connector.deployment.RARConfigurer/
+
/module
Modified: geronimo/server/trunk/configs/geronimo-gbean-deployer/
pom.xml
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/configs/
geronimo-gbean-deployer/pom.xml?
view=diffrev=493249r1=493248r2=493249
==
--- geronimo/server/trunk/configs/geronimo-gbean-deployer/pom.xml
(original)
+++ geronimo/server/trunk/configs/geronimo-gbean-deployer/pom.xml Fri
Jan 5 15:56:05 2007
@@ -54,6 +54,12 @@
artifactIdgeronimo-j2ee-deployment_1.1_spec/artifactId
/dependency
+!-- jsr88 dconfigbean support base classes --
+dependency
+groupIdorg.apache.geronimo.modules/groupId
+artifactIdgeronimo-deploy-config/artifactId
+version${version}/version
+/dependency
!-- Thirdparty Dependencies --
dependency
Modified: geronimo/server/trunk/configs/j2ee-deployer/pom.xml
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/configs/
j2ee-deployer/pom.xml?view=diffrev=493249r1=493248r2=493249
==
--- geronimo/server/trunk/configs/j2ee-deployer/pom.xml (original)
+++ geronimo/server/trunk/configs/j2ee-deployer/pom.xml Fri Jan 5
15:56:05 2007
@@ -92,6 +92,7 @@
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-test-ddbean/artifactId
version${version}/version
+scopetest/scope
/dependency
dependency
Modified: geronimo/server/trunk/configs/j2ee-deployer/src/plan/
plan.xml
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/configs/
j2ee-deployer/src/plan/plan.xml?
view=diffrev=493249r1=493248r2=493249
==
--- geronimo/server/trunk/configs/j2ee-deployer/src/plan/plan.xml
(original)
+++
Re: svn commit: r493249 - in /geronimo/server/trunk/configs: client-deployer/src/plan/ connector-deployer/src/plan/ geronimo-gbean-deployer/ j2ee-deployer/ j2ee-deployer/src/plan/ jetty6-deployer/src/
I marked 2721 fixed after sending the msg. Hmm.. maybe the mail got
timestamped later.
Anyways, it has been fixed. Pls disregard the earlier msg.
Thanx
Prasad
On 1/10/07, David Jencks [EMAIL PROTECTED] wrote:
It looks like you marked 2721 fixed a couple hours before sending
this message??? I'm confused... is it currently fixed and if so by
what? I'd guess it was fixed by my commits last night in rev 494692
(trunk) and 494701 (1.2). IIRC I ran some Testsuite bits which
passed for me before committing.
thanks
david jencks
On Jan 10, 2007, at 11:58 AM, Prasad Kashyap wrote:
I wonder if this is the cause of the deployment failures I am seeing
in the Testsuite
https://issues.apache.org/jira/browse/GERONIMO-2721
Cheers
Prasad
-- Forwarded message --
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Jan 5, 2007 6:56 PM
Subject: svn commit: r493249 - in /geronimo/server/trunk/configs:
client-deployer/src/plan/ connector-deployer/src/plan/
geronimo-gbean-deployer/ j2ee-deployer/ j2ee-deployer/src/plan/
jetty6-deployer/src/plan/ openejb-deployer/src/plan/
tomcat6-deployer/src/pl...
To: scm@geronimo.apache.org
Author: djencks
Date: Fri Jan 5 15:56:05 2007
New Revision: 493249
URL: http://svn.apache.org/viewvc?view=revrev=493249
Log:
GERONIMO-2686 missed the configs changes in previous commit
Modified:
geronimo/server/trunk/configs/client-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/connector-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/geronimo-gbean-deployer/pom.xml
geronimo/server/trunk/configs/j2ee-deployer/pom.xml
geronimo/server/trunk/configs/j2ee-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/jetty6-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/openejb-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/tomcat6-deployer/src/plan/plan.xml
geronimo/server/trunk/configs/webconsole-jetty6/pom.xml
Modified: geronimo/server/trunk/configs/client-deployer/src/plan/
plan.xml
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/configs/
client-deployer/src/plan/plan.xml?
view=diffrev=493249r1=493248r2=493249
==
--- geronimo/server/trunk/configs/client-deployer/src/plan/plan.xml
(original)
+++ geronimo/server/trunk/configs/client-deployer/src/plan/plan.xml
Fri Jan 5 15:56:05 2007
@@ -88,4 +88,6 @@
/gbean
+gbean name=ClientConfigurer
class=org.apache.geronimo.client.builder.jsr88.ClientConfigurer/
+
/module
Modified: geronimo/server/trunk/configs/connector-deployer/src/plan/
plan.xml
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/configs/
connector-deployer/src/plan/plan.xml?
view=diffrev=493249r1=493248r2=493249
==
--- geronimo/server/trunk/configs/connector-deployer/src/plan/plan.xml
(original)
+++ geronimo/server/trunk/configs/connector-deployer/src/plan/plan.xml
Fri Jan 5 15:56:05 2007
@@ -85,4 +85,6 @@
attribute
name=eeNamespaceshttp://java.sun.com/xml/ns/j2ee/attribute
/gbean
+gbean name=RARConfigurer
class=org.apache.geronimo.connector.deployment.RARConfigurer/
+
/module
Modified: geronimo/server/trunk/configs/geronimo-gbean-deployer/
pom.xml
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/configs/
geronimo-gbean-deployer/pom.xml?
view=diffrev=493249r1=493248r2=493249
==
--- geronimo/server/trunk/configs/geronimo-gbean-deployer/pom.xml
(original)
+++ geronimo/server/trunk/configs/geronimo-gbean-deployer/pom.xml Fri
Jan 5 15:56:05 2007
@@ -54,6 +54,12 @@
artifactIdgeronimo-j2ee-deployment_1.1_spec/artifactId
/dependency
+!-- jsr88 dconfigbean support base classes --
+dependency
+groupIdorg.apache.geronimo.modules/groupId
+artifactIdgeronimo-deploy-config/artifactId
+version${version}/version
+/dependency
!-- Thirdparty Dependencies --
dependency
Modified: geronimo/server/trunk/configs/j2ee-deployer/pom.xml
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/configs/
j2ee-deployer/pom.xml?view=diffrev=493249r1=493248r2=493249
==
--- geronimo/server/trunk/configs/j2ee-deployer/pom.xml (original)
+++ geronimo/server/trunk/configs/j2ee-deployer/pom.xml Fri Jan 5
15:56:05 2007
@@ -92,6 +92,7 @@
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-test-ddbean/artifactId
version${version}/version
+scopetest/scope
/dependency
dependency
Modified: geronimo/server/trunk/configs/j2ee-deployer/src/plan/
plan.xml
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/configs/
[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_37869 ] Albert Strasheim commented on AMQCPP-25: Thanks very much. Which platforms are you currently testing on? Which compiler versions? 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 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_37870 ] Timothy Bish commented on AMQCPP-25: Windows XP : MSDev Studio 2005, and Cygwin, gcc 3.4.4 Solaris 10: GCC 3.4.3 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 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: ClassLoader, JNDI and Dependency views in console
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
[ https://issues.apache.org/jira/browse/GERONIMO-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher M. Cardona updated GERONIMO-2689: - Attachment: G2689-2690-2691.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, 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
[ https://issues.apache.org/jira/browse/GERONIMO-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463741 ] Christopher M. Cardona commented on GERONIMO-2689: -- Attached combined patch which fixes javascript error for using wrong Dojo widget names. 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, 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: ClassLoader, JNDI and Dependency views in console
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] 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_37871 ] Albert Strasheim commented on AMQCPP-25: If you're interested in shell access to a Fedora Core 4 machine with GCC 4.0.2 and Valgrind 2.4.0 installed, let me know. 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 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
webservices-testsuite failure
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 started in 1.219s Module 5/25 org.apache.geronimo.configs/openejb/2.0-SNAPSHOT/car started in 15.781s Module 6/25 org.apache.geronimo.configs/system-database/2.0-SNAPSHOT/car started in .000s Module 7/25 org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car started in 6.609s Module 8/25 org.apache.geronimo.configs/activemq/2.0-SNAPSHOT/car started in .296s Module 9/25 org.apache.geronimo.configs/jetty6/2.0-SNAPSHOT/car 2007-01-10 20:48:24.593::INFO: Logging to STDERR via org.mortbay.log.StdErrLog 2007-01-10 20:48:24.609::INFO: jetty-6.1.x 2007-01-10 20:48:25.687::INFO: Started
Re: Jetty 6- Clustering - How it works
really awesome work Gianny, I know you've worked very hard on it. Filip David Jencks wrote: Wow this is great!! Are there instructions somewhere on how to set up a demo system? Having an integration test would be even better :-) thanks david jencks On Jan 6, 2007, at 7:30 PM, Gianny Damour wrote: Hi, I think that support for clustered Web-applications with Jetty is now working. Here is a description of how this works; note that most of the described behavior is WADI specific. Group Communication Group communications are performed by Tribes, which is the Tomcat 6 group communication engine. I know very little of Tribes; however, I am pretty sure that Filip Hanik can give us an in-depth description, if requested. At a very high level, Tribes provides membership discovery and failure detection. It also provides basic message exchange communication primitives, that WADI builds upon to provide additional message exchange operations (e.g. request-reply). Logical group communication engines are layered on top of the above (physical) group communication engine. A logical group communication engine, a ServiceSpace in the WADI's terminology, provides the same features than a physical group communication engine and allows the definition of sub-groups. This means that at the physical level, you could have three nodes interconnected and at the logical level only two of them could appear as existing. Clustered Web-Application Discovery A clustered Web-application is placed into a logical group communication engine, which is uniquely identified by a URI. This URI is the Artifact id of the Web-application configuration. When this Web-application starts, the logical group communication engine starts and joins the logical sub-group identified by its unique id. Conversely, when the application stops, the logical group communication engine leaves the logical sub-group. Partitioned State WADI implements a partitioned session state topology. In a cluster all the session states are distributed across the cluster nodes and only one node holds the state of a given session. This design choice was made to improve scalability with respect to the size of data to be managed by a single node. Session locations, information required when a node requests a session that it does not hold, are also managed by a single node. When a node fails, the session states and session locations managed by this node are lost and WADI is able to recreate them. Session states are lazily recreated from replicas. Session locations are recreated by querying the cluster and asking each member what are the sessions that they are currently holding. Session Creation When an inbound request wants to create a new HttpSession, a WADI session is created. This session is hosted by the node receiving the inbound request. An HttpSession using under the cover the WADI session is then created and returned. Under the cover, WADI ensures that the session has a unique identifier cluster-wide. Session Migration When an inbound request wants to access an HttpSession and this session is not hosted by the node, The node hosting the requested session migrates it to the node receiving the request. Under the cover, WADI ensures correct handling of concurrent session migration requests via a locking approach and maintains its internal book keeping of session locations following migration events. Session Replication When a request complete, the WADI session used under the cover of the HttpSession is notified. The WADI session is then replicated synchronously to one or multiple nodes. The selection of the back-up nodes for each session is customizable via a plugin strategy. When a node fails, replicas are re-organized based on the new list of existing members. Fail-Over When an inbound request wants to access an HttpSession, which was hosted by a node which has died, the cluster is queried for a replica of the requested session and an HttpSession is recreated if possible. Session Evacuation When a Web-application stops, all the session that it holds are evacuated to the other nodes hosting the same clustered Web-application. It will take me 1 to 2 weeks to test specific error scenarios and ensure correctness; meanwhile, if anyone wants to know more of some specific areas, then please feel free to ask. Thanks, Gianny --No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.6/617 - Release Date: 1/5/2007 11:11 AM
Re: Web Builders
I am trying to use javaee5 xbeans in webservices-builder. 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
Re: Web Builders
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
[STATUS] (geronimo) Wed Jan 10 23:48:36 2007
APACHE GERONIMO STATUS: -*-text-*- Last modified at [$Date: 2006-12-07 13:03:14 -0500 (Thu, 07 Dec 2006) $] The current version of this file can be found at: * http://svn.apache.org/repos/asf/geronimo/server/trunk/STATUS Upcoming Releases: Geronimo 1.2 -- geronimo/server/trunk/ Release Manager: Dain Sundstrom and Alan Cabrera Estimated Date: Q4 2006 RELEASE SHOWSTOPPERS: Certification - Historically certification has been the most time consuming portion of a release, and his release is proving to be no different than the previous ones. The biggest problem area is code related to the new CORBA ORB implementation Yoko. Snapshots - Before a final release can be cut we need to resolve any SNAPSHOT dependencies must be replaced with final released versions. Legal Review - There are many items in this category, but at the very lease all source files must have the current Apache license header and all archives must contain LICENSE, NOTICE and DISCLAIMER files as required by the ASF. RELEASE HISTORY: 2006-09-18 Geronimo 1.1.1 2006-06-26 Geronimo 1.1 2006-01-05 Geronimo 1.0 2005-10-04 Geronimo 1.0 milestone 5 2005-08-10 Geronimo 1.0 milestone 4 2004-11-11 Geronimo 1.0 milestone 3 2004-09-09 Geronimo 1.0 milestone 2 2004-04-29 Geronimo 1.0 milestone 1 If you're a contributor looking for something to do: * Review the documentation and suggest improvements * Review the bug list and suggest fixes or report reproducibility * Report bugs yourself
Re: Assemblies assemblies everywhere and which one to ship?
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. 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)
Re: Assemblies assemblies everywhere and which one to ship?
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)
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
[jira] Commented: (GERONIMO-2689) New View for JNDI name in all the contexts
[ https://issues.apache.org/jira/browse/GERONIMO-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463822 ] Rakesh Midha commented on GERONIMO-2689: Thanks Kevan, for spending time and integrating this patch. 1) About finalize(), I didnt notice that I used upper case 'F', you are right it should be lower case finalize . Now about using destroy()/finalize(). I used all three technicques finalize(), destroy() and weak references to remove ClassLoaders from registry, not just because I am worried about circular reference, but also because I don't want to depend too much on weak references or finalize() implementation in GC and destroy() calling from Geronimo code. I want to leave no chance hence used all the precautions I could. (In no case I want Classloadere to be not GC'd because of its refernce in Registry). I hope this convince you for using combination of destroy()/finalize() and weak references. 2) You are right, I spent some time on this code and didnt took the latest from SVN before making patch, my mistake, do you want me to do that for me. I promise I will take care of this from next patch onways, forgive this time. Christopher, I could not figure out what dojo widgets names you changed. Can you list them please. Thanks 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, 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: ClassLoader, JNDI and Dependency views in console
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
Re: ClassLoader, JNDI and Dependency views in console
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 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
