[jira] Commented: (SM-999) InOut to InOnly pattern Endpoint for eip-su
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39650 ] Andrea Zoppello commented on SM-999: Hi Guillaume, Take a look at the code of the class it.eng.spagosoa.smx.components.sync.Synchronizer in the spagic-components distribution. We need this component basically to address the use case where 1) client applications need to call a webservice binding component and to get a response 2) the process behind binding component could be quite complex ( not just only one se ) 3) the process need to be modelled in visual tool ( Spagic Studio ) By the way if you look at the code you can see that basically the syncronizer that basically it manage an InOutExchange this is keep in and an InOnly exchange is created. If you want more details the Spagic Components Guide contains an example of that. InOut to InOnly pattern Endpoint for eip-su --- Key: SM-999 URL: https://issues.apache.org/activemq/browse/SM-999 Project: ServiceMix Issue Type: Improvement Components: servicemix-eip Reporter: Netflexity Attachments: InOutToInEndpoint.java Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (SM-999) InOut to InOnly pattern Endpoint for eip-su
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39650 ] Andrea Zoppello edited comment on SM-999 at 7/12/07 12:19 AM: -- Hi Guillaume, Take a look at the code of the class it.eng.spagosoa.smx.components.sync.Synchronizer in the spagic-components distribution. We need this component basically to address the use case where 1) client applications need to call a webservice binding component and to get a response 2) the process behind binding component could be quite complex ( not just only one se ) 3) the process need to be modelled in visual tool ( Spagic Studio ) By the way if you look at the code you can see that basically it manage an InOutExchange this is keep in and an InOnly exchange is created. If you want more details the Spagic Components Guide contains an example of that. was: Hi Guillaume, Take a look at the code of the class it.eng.spagosoa.smx.components.sync.Synchronizer in the spagic-components distribution. We need this component basically to address the use case where 1) client applications need to call a webservice binding component and to get a response 2) the process behind binding component could be quite complex ( not just only one se ) 3) the process need to be modelled in visual tool ( Spagic Studio ) By the way if you look at the code you can see that basically the syncronizer that basically it manage an InOutExchange this is keep in and an InOnly exchange is created. If you want more details the Spagic Components Guide contains an example of that. InOut to InOnly pattern Endpoint for eip-su --- Key: SM-999 URL: https://issues.apache.org/activemq/browse/SM-999 Project: ServiceMix Issue Type: Improvement Components: servicemix-eip Reporter: Netflexity Attachments: InOutToInEndpoint.java Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: SecuredBroker and responses
Sounds like a good idea for me. Piotr Bzdyl wrote: Hi, I am trying to use SecuredBroker but I have one problem with its current implementation. If the user is not authorized to send the exchange do the endpoint, then the SecurityException is thrown and the exchange is not sent back to the calling component. This is the cause that the caller won't get any response. Shouldn't it return the exchange to the caller with status set to ERROR and the security exception set as an error on the message exchange? Thanks and regards, Piotr -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 GeschÀftsfÌhrer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: SecuredBroker and responses
I tried to change existing code to not throw the exception but to set the error on the exchange being routed but as I expected an IllegalStateException is thrown since SecuredBroker is not the owner of the message exchange. Do you know how it can be handled? Piotr On 7/12/07, Thomas Termin [EMAIL PROTECTED] wrote: Sounds like a good idea for me. Piotr Bzdyl wrote: Hi, I am trying to use SecuredBroker but I have one problem with its current implementation. If the user is not authorized to send the exchange do the endpoint, then the SecurityException is thrown and the exchange is not sent back to the calling component. This is the cause that the caller won't get any response. Shouldn't it return the exchange to the caller with status set to ERROR and the security exception set as an error on the message exchange? Thanks and regards, Piotr -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 GeschÀftsfÌhrer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Commented: (SM-990) FilePoller with Archiving
[ https://issues.apache.org/activemq/browse/SM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39651 ] Gert Vanthienen commented on SM-990: Perhaps we can create a more generic solution for this: with SM-751 we have a correlation id that allows us to do flow tracing, so it should be possible to build an auditor that is triggered whenever a new message arrives (at any kind of endpoint: FTP, File, HTTP, ...) and sends a copy of the message to an archiving endpoint. FilePoller with Archiving - Key: SM-990 URL: https://issues.apache.org/activemq/browse/SM-990 Project: ServiceMix Issue Type: Improvement Components: servicemix-components, servicemix-file Affects Versions: 3.1 Reporter: Juergen Mayrbaeurl Priority: Minor The various FilePoller implementations should archive the files before deleting them (e.g. by copying them to another directory) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-935) Allow to specify additional JNDI properties
[
https://issues.apache.org/activemq/browse/SM-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated SM-935:
---
Attachment: SM-935.patch
Phiroze,
The attached patch should enable you to specify jndiProperties=... on the
jms:endpoint/. Can you help me try it out before I commit it?
Gert
Allow to specify additional JNDI properties
---
Key: SM-935
URL: https://issues.apache.org/activemq/browse/SM-935
Project: ServiceMix
Issue Type: New Feature
Components: servicemix-jms
Affects Versions: 3.1
Reporter: Gert Vanthienen
Priority: Minor
Attachments: SM-935.patch
In addition to using initialContext and jndiProviderUrl to configure a JMS
endpoint, it should be possible to specify additional JNDI properties (e.g
{{java.naming.security.principal}}, {{java.naming.security.credentials}})
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1002) Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost
Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost -- Key: SM-1002 URL: https://issues.apache.org/activemq/browse/SM-1002 Project: ServiceMix Issue Type: Bug Components: servicemix-core Environment: Unix, Java 1.5 Reporter: Ruwan Linton When I am doing a performance test I have sent more than 40 concurrent requests from a single host to servicemix, and the maxConnectionsPerHost was 40. It is acceptable the failing to respond when it exceeds 40 (maxConnectionsPerHost) concurrent requests. But afterward, SM hangs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1002) Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost
[ https://issues.apache.org/activemq/browse/SM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39658 ] Thomas Termin commented on SM-1002: --- Maybe you could add an example which I could try. Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost -- Key: SM-1002 URL: https://issues.apache.org/activemq/browse/SM-1002 Project: ServiceMix Issue Type: Bug Components: servicemix-core Environment: Unix, Java 1.5 Reporter: Ruwan Linton When I am doing a performance test I have sent more than 40 concurrent requests from a single host to servicemix, and the maxConnectionsPerHost was 40. It is acceptable the failing to respond when it exceeds 40 (maxConnectionsPerHost) concurrent requests. But afterward, SM hangs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1002) Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost
[ https://issues.apache.org/activemq/browse/SM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39656 ] Thomas Termin commented on SM-1002: --- Can you give a bit more information. For example describe the involved components. Could you provide a threaddump for it? (kill -3) Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost -- Key: SM-1002 URL: https://issues.apache.org/activemq/browse/SM-1002 Project: ServiceMix Issue Type: Bug Components: servicemix-core Environment: Unix, Java 1.5 Reporter: Ruwan Linton When I am doing a performance test I have sent more than 40 concurrent requests from a single host to servicemix, and the maxConnectionsPerHost was 40. It is acceptable the failing to respond when it exceeds 40 (maxConnectionsPerHost) concurrent requests. But afterward, SM hangs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1000) ServiceMix :: Maven2 JBI Plugin checkstyle issues
[
https://issues.apache.org/activemq/browse/SM-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39659
]
Rabi commented on SM-1000:
--
Gret,
Yes, this checkout was from the trunk. I am still having the same error.
I can see this method in GraphArtifactCollector.java with 8 parameters..
public ArtifactResolutionResult collect(
Set artifacts,
Artifact originatingArtifact,
Map managedVersions,
ArtifactRepository localRepository,
List remoteRepositories,
ArtifactMetadataSource source,
ArtifactFilter filter,
List listeners) throws ArtifactResolutionException {
I am using maven 2.0.6 and jdk 1.6.0.. Do you think this could be a
probem with the java version.
Regards,
Rabi Mishra
http://rabisblog.blogspot.com/
c++; /* this makes c bigger but returns the old value */
ServiceMix :: Maven2 JBI Plugin checkstyle issues
--
Key: SM-1000
URL: https://issues.apache.org/activemq/browse/SM-1000
Project: ServiceMix
Issue Type: Bug
Components: tooling
Affects Versions: 3.2
Environment: Windows
Reporter: Rabi
[INFO] Building ServiceMix :: Maven2 JBI Plugin
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] Ignoring available plugin update: 2.3 as it requires Maven version
2.0.5
[INFO] [checkstyle:checkstyle {execution: validate}]
[INFO] Starting audit...
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:58:37: More than
7 p
arameters.
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:96:18: More than
7 p
arameters.
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37: method
def
modifier at indentation level 2 not at correct indentation, 4
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37:15: More
th
an 7 parameters.
Audit done.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error has occurred in Checkstyle report generation.
Embedded error: There are 4 checkstyle errors.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 28 seconds
[INFO] Finished at: Wed Jul 11 16:34:15 IST 2007
[INFO] Final Memory: 13M/24M
[INFO]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1002) Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost
[ https://issues.apache.org/activemq/browse/SM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39660 ] Ruwan Linton commented on SM-1002: -- I just deployed a http consumer and a provider linked directly to create a proxy for an existing service xbean config for the http-consumer ?xml version=1.0? beans xmlns:http=http://servicemix.apache.org/http/1.0; xmlns:b=http://esb.wso2.org/perf/proxy; http:endpoint service=b:http endpoint=endpoint targetService=b:SimpleStockQuoteService role=consumer locationURI=http://10.100.1.43:8192/proxy; defaultMep=http://www.w3.org/2004/08/wsdl/in-out; soap=true/ /beans and here is the xbean config for the provider ?xml version=1.0 encoding=UTF-8? beans xmlns:http=http://servicemix.apache.org/http/1.0; xmlns:b=http://esb.wso2.org/perf/proxy; http:endpoint service=b:SimpleStockQuoteService endpoint=soap role=provider locationURI=http://10.100.1.44:9000/soap/SimpleStockQuoteService; defaultMep=http://www.w3.org/2004/08/wsdl/in-out; soap=true soapVersion=1.1/ /beans and the component.properties file entry servicemix-http.maxConnectionsPerHost was set to 30 and after 36 requests it fails and hangs, To get more information about our perf test please refer to the article http://wso2.org/library/1721 Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost -- Key: SM-1002 URL: https://issues.apache.org/activemq/browse/SM-1002 Project: ServiceMix Issue Type: Bug Components: servicemix-core Environment: Unix, Java 1.5 Reporter: Ruwan Linton When I am doing a performance test I have sent more than 40 concurrent requests from a single host to servicemix, and the maxConnectionsPerHost was 40. It is acceptable the failing to respond when it exceeds 40 (maxConnectionsPerHost) concurrent requests. But afterward, SM hangs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1000) ServiceMix :: Maven2 JBI Plugin checkstyle issues
[
https://issues.apache.org/activemq/browse/SM-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39661
]
Gert Vanthienen commented on SM-1000:
-
Rabi,
My checkout has a CheckStyle suppresion for this particular check in the
GraphArtifactCollector class registered in
{{build/src/main/resources/smx-checkstyle-suppressions.xml}}. Can you check if
you have that too? Perhaps your build/ directory needs another update...
Gert
ServiceMix :: Maven2 JBI Plugin checkstyle issues
--
Key: SM-1000
URL: https://issues.apache.org/activemq/browse/SM-1000
Project: ServiceMix
Issue Type: Bug
Components: tooling
Affects Versions: 3.2
Environment: Windows
Reporter: Rabi
[INFO] Building ServiceMix :: Maven2 JBI Plugin
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] Ignoring available plugin update: 2.3 as it requires Maven version
2.0.5
[INFO] [checkstyle:checkstyle {execution: validate}]
[INFO] Starting audit...
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:58:37: More than
7 p
arameters.
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:96:18: More than
7 p
arameters.
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37: method
def
modifier at indentation level 2 not at correct indentation, 4
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37:15: More
th
an 7 parameters.
Audit done.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error has occurred in Checkstyle report generation.
Embedded error: There are 4 checkstyle errors.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 28 seconds
[INFO] Finished at: Wed Jul 11 16:34:15 IST 2007
[INFO] Final Memory: 13M/24M
[INFO]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
configuring sevicemix-jms to IBM MQ
Hi, I'm facing some problems when jms xbean is configured to IBM MQ. following is my xbean contents. jms:endpoint service=iq:jms endpoint=endpoint role=provider destinationStyle=queue jmsProviderDestinationName=Q1.SQ processorName=standard connectionFactory=#connectionFactory / bean id=connectionFactory class=com.ibm.mq.jms.MQQueueConnectionFactory property name=queueManager value=SampleQM1 / property name=transportType value=1 / property name=hostName value=localhost / property name=port value=1417 / /bean Is there something else i need to configure in it. Thanks in anticipation Varun -- View this message in context: http://www.nabble.com/configuring-sevicemix-jms-to-IBM-MQ-tf4068169s12049.html#a11560239 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
[jira] Commented: (SM-1003) soapVersion http endpoint attribute fails when using wsdl deployment
[ https://issues.apache.org/activemq/browse/SM-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39676 ] Dan M commented on SM-1003: --- See SM-348 for introduction of the soapVersion feature. soapVersion http endpoint attribute fails when using wsdl deployment Key: SM-1003 URL: https://issues.apache.org/activemq/browse/SM-1003 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.1 Environment: Fedora 6, Java 1.5.0_11, ServiceMix 3.1 Reporter: Dan M Priority: Minor The soapVersion attribute works only when the su is deployed using an xbean. Wsdl deployment seems to ignore the attribute. From service description: smix:endpoint soapVersion=1.1 role=provider defaultMep=in-out/ From log: DEBUG - content - ?xml version='1.0' encoding='UTF-8'?env:Envelope xmlns:env=http://www.w3.org/2003/05/soap-envelope; -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo 2.0 License and Notice Files
On Jul 11, 2007, at 10:08 PM, Matt Hogstrom wrote: On Jul 11, 2007, at 12:24 PM, Kevan Miller wrote: If some people could review, that would be great. on the Active-IO question there is some coding work to be done. http://issues.apache.org/jira/browse/GERONIMO-2944 Ya. I've started looking into this... All of the OpenEJB mods should be AL 2.0 but it sounds like there is some work to do in OEJB. I'll ping the list. Yes. Would certainly be fixed before OpenEJB could be released. I'm planning on fixing when I have a few minutes... Next steps and pseudo-random license trivia: Many jar archives included by Geronimo do not include LICENSE or NOTICE files. In most cases, I've tracked down the appropriate LICENSE information for the resource, and included a url for the LICENSE file. I haven't always done this. So, some work still remains. Most/all of this remaining work involves Apache projects. So, I don't invision a big problem. In some of the cases, the work is not chasing down the license information, but insuring that appropriate LICENSE/NOTICE files are generated in the original jar archive (e.g. OpenEJB). For the rather long list of jars that don't have any embedded files is there a recommendation ? Unlikely we'll get them fixed. We don't need to insure that all jar files contain license/notice information. That's not our job -- it's the responsibility of the individual projects. One exception might be any jar files which we are generating (e.g. Tomcat). Apache's current policy is that all released artifacts need to include LICENSE/NOTICE files. Jar files used to be bundled in a binary distribution. The binary distribution would contain any LICENSE/NOTICE files, but lots of times the jar files did not. Now-a- days, jar files should be treated as separately released artifacts -- they're placed individually in maven repos, etc. So, most projects put LICENSE/NOTICE information into jar files, also. Since we embed so many projects, I must say that this practice is great. To gather license/notice information, we just need to crack open the jars and aggregate the license/notice information. For jars that don't self-document their license, we need to obtain the license/ notice information for the jars we're using. I think that I've done this for all non-apache jar files. We need to do the same research for the apache jars. I'll take this opportunity to point out what I think is good practice -- jar files should contain license/notice information specific to the jar file (i.e. they should not re-use the project-wide license/ notice files). Worst case is those projects (myfaces is an example) who have something like the following in their NOTICE file: See the file LICENSE.txt See licenses for accompanying products in the /licenses subdirectory. where there is no /licenses subdirectory in the jar. So, we're still forced to download source or the entire binary to obtain the necessary information... We currently include all of our LICENSE information in a single root LICENSE.txt file. Some Apache projects include a licenses/ directory, instead. This directory includes all of the non-ASL licenses for the project. Although it's probably a bit more work, I personally prefer a single file. However, this is a debatable point. If others have an opinion, they are welcome to voice it. One file would be my preference. The root LICENSE.txt and NOTICE.txt files (by root I mean the license/notice file in the bottom level directory of our source and binary distributions) contain the license info for the entire assembly. We don't currently have different license/notice files that are specific to our Jetty/Tomcat CXF/Axis distributions. Nor do we attempt to generate license/notice files specific to our minimal assemblies. So current course and speed, our root license/notice files will be a superset of all of our various assemblies. This seems fine, to me. If anyone sees a problem with this, speak now... Perhaps a comment that this assembly includes some or all of That sounds like a good approach... --kevan Once all of the data in the google spreadsheet is complete, and we've had a chance to review. I'll plan on generating new LICENSE.txt, NOTICE.txt, and DISCLAIMER.txt files for our 2.0 release. I'd guess this will be towards the end of the week/over the weekend. If anyone else is interested in grabbing a shovel and pitching in, let me know... --kevan
Re: SNAPSHOT dependencies that need to be released.
Hi, When do you want to get released versions of these dependencies? I can take care of the WADI dependencies and cut a release a couple of days before the creation of the 2.0 branch if it is OK with you. Thanks, Gianny On 11/07/2007, at 12:42 PM, Prasad Kashyap wrote: The following Geronimo dependencies uses SNAPSHOT versions. Can we please chase these projects and get them to release the artifacts, whatever it takes; contacts, muscles, bribes, favors, etc :-) If enough people on this list volunteer to get some of these released, then I'll create a wiki page where they can sign up. openejbVersion3.0-incubating-SNAPSHOT/openejbVersion groupIdorg.apache.cxf/groupId artifactIdcxf-api/artifactId version2.0-incubator-SNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-java2wsdl/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-kernel/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-adb/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-jaxws-api/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-jaxws/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-metadata/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-saaj/artifactId versionSNAPSHOT/version groupIdorg.apache.geronimo.javamail/groupId artifactIdgeronimo-javamail_1.4_mail/artifactId version1.1-SNAPSHOT/version groupIdorg.apache.geronimo.schema/groupId artifactIdgeronimo-schema-jee_5/artifactId version1.1-SNAPSHOT/version groupIdorg.apache.geronimo.schema/groupId artifactIdgeronimo-schema-j2ee_1.4/artifactId version1.1-SNAPSHOT/version groupIdorg.apache.openjpa/groupId artifactIdopenjpa/artifactId version1.0.0-SNAPSHOT/version groupIdorg.apache.xbean/groupId artifactIdxbean-finder/artifactId version3.0-SNAPSHOT/version groupIdorg.apache.xbean/groupId artifactIdxbean-naming/artifactId version3.0-SNAPSHOT/version groupIdorg.apache.xbean/groupId artifactIdxbean-reflect/artifactId version3.1-SNAPSHOT/version groupIdorg.apache.ws.scout/groupId artifactIdscout/artifactId versionSNAPSHOT/version groupIdorg.apache.yoko/groupId artifactIdyoko-core/artifactId version1.0-incubating-SNAPSHOT/version groupIdorg.apache.yoko/groupId artifactIdyoko-spec-corba/artifactId version1.0-incubating-SNAPSHOT/version groupIdorg.apache.yoko/groupId artifactIdyoko-rmi-spec/artifactId version1.0-incubating-SNAPSHOT/version groupIdorg.apache.yoko/groupId artifactIdyoko-rmi-impl/artifactId version1.0-incubating-SNAPSHOT/version groupIdorg.mortbay.jetty/groupId artifactIdjetty/artifactId version6.1-SNAPSHOT/version groupIdorg.mortbay.jetty/groupId artifactIdjetty-ajp/artifactId version6.1-SNAPSHOT/version groupIdorg.mortbay.jetty/groupId artifactIdjetty-sslengine/artifactId version6.1-SNAPSHOT/version groupIdorg.mortbay.jetty/groupId artifactIdjetty-util/artifactId version6.1-SNAPSHOT/version groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-api/artifactId version1.2.0-SNAPSHOT/version groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-impl/artifactId version1.2.0-SNAPSHOT/version Cheers Prasad
Offline build failure due to missing geronimo-javamail_1.4_mail-1.2-SNAPSHOT.jar
When I do an offline build, I am getting the following build error. If I do
an online build, the build is successful, but, geronimo-javamail_1.4_mail-
1.2-SNAPSHOT.jar is not downloaded to m2repo. Any ideas how to fix this?
[INFO]
-
---
[INFO] Building Geronimo Configs :: JavaEE Specs
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] [enforcer:enforce {execution: default}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [car:prepare-plan]
[INFO] Generated: C:\G\trunk\configs\jee-specs\target\plan\plan.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) org.apache.geronimo.javamail:geronimo-javamail_1.4_mail:jar:1.2-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.geronimo.javamail-Dartifact
Id=geronimo-javamail_1.4_mail \
-Dversion=1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) org.apache.geronimo.configs:jee-specs:car:2.0-SNAPSHOT
2)
org.apache.geronimo.javamail:geronimo-javamail_1.4_mail:jar:1.2-SNAPS
HOT
--
1 required artifact is missing.
for artifact:
org.apache.geronimo.configs:jee-specs:car:2.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
java.net (http://download.java.net/maven/1/),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository ),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
codehaus-snapshots ( http://snapshots.repository.codehaus.org),
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/
),
tomcat-m2-repo ( http://tomcat.apache.org/dev/dist/m2-repository)
NOTE: Maven is executing in offline mode. Any artifacts not already in your
loca
l
repository will be inaccessible.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 30 seconds
[INFO] Finished at: Thu Jul 12 15:57:15 IST 2007
[INFO] Final Memory: 38M/68M
[INFO]
[jira] Created: (GERONIMO-3311) Security Realms portlet is broken. Unable to edit realm.
Security Realms portlet is broken. Unable to edit realm. - Key: GERONIMO-3311 URL: https://issues.apache.org/jira/browse/GERONIMO-3311 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console, security Affects Versions: 2.0-M7 Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Fix For: 2.0-M7 Security Realms portlet is broken. I guess the problem is introduced by recent changes for GERONIMO-3303 Simplify security authentication framework by removing mixed local/remote logins. When I click on edit link, the following exception is logged. 16:23:37,613 ERROR [edit_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.realmwizard.edit_jsp threw exception javax.el.PropertyNotFoundException: Property 'serverSide' not found on type org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet$LoginModuleDetails at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) at javax.el.BeanELResolver.property(BeanELResolver.java:279) at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at org.apache.el.parser.AstValue.getValue(AstValue.java:97) at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:923) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspx_meth_c_005fif_005f6(edit_jsp.java:850) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspx_meth_c_005fforEach_005f2(edit_jsp.java:586) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspService(edit_jsp.java:146) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.pluto.core.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:65) at org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.renderEdit(SecurityRealmPortlet.java:585) at org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.doView(SecurityRealmPortlet.java:260) 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(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.render(PortletInvokerImpl.java:73) at org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:119) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.renderPortlet(PortletContainerWrapperImpl.java:70) at org.apache.pluto.portalImpl.aggregation.PortletFragment.service(PortletFragment.java:168) at jsp.WEB_002dINF.aggregation.ColumnFragment_jsp._jspService(ColumnFragment_jsp.java:70) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at
Re: Offline build failure due to missing geronimo-javamail_1.4_mail-1.2-SNAPSHOT.jar
On 7/12/07, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: When I do an offline build, I am getting the following build error. If I do an online build, the build is successful, but, geronimo-javamail_1.4_mail-1.2-SNAPSHOT.jar is not downloaded to m2repo. Any ideas how to fix this? Nope, but you may want to run mvn dependencies:go-offline or some other maven's dependency plugin [1] and see if that helps moving closer to a solution. [1] http://maven.apache.org/plugins/maven-dependency-plugin/ Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
[jira] Commented: (GERONIMO-3303) Simplify security authentication framework by removing mixed local/remote logins.
[ https://issues.apache.org/jira/browse/GERONIMO-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512041 ] Vamsavardhana Reddy commented on GERONIMO-3303: --- Removed empty packages/directories. Completed: At revision: 83 in trunk. Simplify security authentication framework by removing mixed local/remote logins. --- Key: GERONIMO-3303 URL: https://issues.apache.org/jira/browse/GERONIMO-3303 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: security Affects Versions: 2.0-M6 Reporter: David Jencks Assignee: David Jencks Fix For: 2.0-M7 Back at apachecon 2005 there was a big discussion where we decided to remove the parts of the geronimo authentication framework that let clients run login modules on the server. See the email from me dated Dec 23, 2005, at 6:37 PM, Geronimo Security plans (from ApacheCon). I've finally replaced the remote login with something using the openejb protocol and removed the no longer needed code. This is a big simplification. I've refactored the authentication stuff so that: - we still have a GeronimoLoginConfiguration - we can still (optionally) wrap principals to determine exactly which login module and realm they came from - all authentication happens in a single vm, no sneaky remoting stuff - we use the LoginContext to create the login modules directly from the AppConfigurationEntry[] - registering and unregistering the subject and inserting the identification principal is done by a login module automatically added by the GenericSecurityRealm, rather than the JaasSecuritySession This eliminates most of the hard to understand code including: JaasLoginCoordinator JaasSecuritySession JaasLoginService I've also removed the subject carrying protocol and the remoting jmx code since it isn't used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3312) Eliminate obselete org.apache.geronimo.management.geronimo.J2EEServer.getLoginService() method
Eliminate obselete org.apache.geronimo.management.geronimo.J2EEServer.getLoginService() method -- Key: GERONIMO-3312 URL: https://issues.apache.org/jira/browse/GERONIMO-3312 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: management Affects Versions: 2.0-M7 Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Priority: Minor Fix For: 2.0-M7 org.apache.geronimo.management.geronimo.J2EEServer.getLoginService() method is made obselete by GERONIMO-3303. A call to this method from SecurityRealmPortlet is resulting in NullPointerException as there is no LoginService defined now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3313) Getting InitialContext without explicitly passing the System Properties fails.
Getting InitialContext without explicitly passing the System Properties fails. -- Key: GERONIMO-3313 URL: https://issues.apache.org/jira/browse/GERONIMO-3313 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 1.2 Environment: Kubuntu Linux 2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 GNU/Linux Java java version 1.6.0 Java(TM) SE Runtime Environment (build 1.6.0-b105) Java HotSpot(TM) Server VM (build 1.6.0-b105, mixed mode) Reporter: Francisco Borges Geronimo1.2 will *fail* if: 1. From a sample application (outside Geronimo) trying to connect to a EJB in the server; 2. I try to get the InitialContext without explicitly passing the System properties: jndiCntx = new InitialContext(); [java] javax.naming.AuthenticationException: Cannot read the response from the server (OEJP/2.0) : null; nested exception is: [java] java.io.EOFException [java] at org.apache.openejb.client.JNDIContext.authenticate(JNDIContext.java:178) [java] at org.apache.openejb.client.JNDIContext.getInitialContext(JNDIContext.java:163) [java] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) [java] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) [java] at javax.naming.InitialContext.init(InitialContext.java:223) [java] at javax.naming.InitialContext.init(InitialContext.java:175) [java] at com.xhive.j2eesamples.XhiveSampleSessionTest.init(XhiveSampleSessionTest.java:38) [java] at com.xhive.j2eesamples.XhiveSampleSessionTest.main(XhiveSampleSessionTest.java:80) If I use: InitialContext jndiCntx = new InitialContext(System.getProperties()); The code behaves as expected. I don't know for sure if this is Geronimo's fault or OpenEjb but it certainly happens, and is perfectly reproducible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1000) ServiceMix :: Maven2 JBI Plugin checkstyle issues
[
https://issues.apache.org/activemq/browse/SM-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39657
]
Gert Vanthienen commented on SM-1000:
-
Rabi,
Was this a checkout from trunk? I cannot reproduce the CheckStyle errors with
my latest checkout here. Could you try to do an 'svn up' and retry it?
Gert
ServiceMix :: Maven2 JBI Plugin checkstyle issues
--
Key: SM-1000
URL: https://issues.apache.org/activemq/browse/SM-1000
Project: ServiceMix
Issue Type: Bug
Components: tooling
Affects Versions: 3.2
Environment: Windows
Reporter: Rabi
[INFO] Building ServiceMix :: Maven2 JBI Plugin
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] Ignoring available plugin update: 2.3 as it requires Maven version
2.0.5
[INFO] [checkstyle:checkstyle {execution: validate}]
[INFO] Starting audit...
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:58:37: More than
7 p
arameters.
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:96:18: More than
7 p
arameters.
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37: method
def
modifier at indentation level 2 not at correct indentation, 4
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37:15: More
th
an 7 parameters.
Audit done.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error has occurred in Checkstyle report generation.
Embedded error: There are 4 checkstyle errors.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 28 seconds
[INFO] Finished at: Wed Jul 11 16:34:15 IST 2007
[INFO] Final Memory: 13M/24M
[INFO]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Offline build failure due to missing geronimo-javamail_1.4_mail-1.2-SNAPSHOT.jar
If you are doing an offline build on a clean repo, you will have to
build javamail separately from it's own svn tree. It is not a part of
the Geronimo tree.
Cheers
Prasad
On 7/12/07, Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
When I do an offline build, I am getting the following build error. If I do
an online build, the build is successful, but,
geronimo-javamail_1.4_mail-1.2-SNAPSHOT.jar is not downloaded to m2repo.
Any ideas how to fix this?
[INFO]
-
---
[INFO] Building Geronimo Configs :: JavaEE Specs
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] [enforcer:enforce {execution: default}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [car:prepare-plan]
[INFO] Generated:
C:\G\trunk\configs\jee-specs\target\plan\plan.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1)
org.apache.geronimo.javamail:geronimo-javamail_1.4_mail:jar:1.2-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.geronimo.javamail
-Dartifact
Id=geronimo-javamail_1.4_mail \
-Dversion=1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1)
org.apache.geronimo.configs:jee-specs:car:2.0-SNAPSHOT
2)
org.apache.geronimo.javamail:geronimo-javamail_1.4_mail:jar:1.2-SNAPS
HOT
--
1 required artifact is missing.
for artifact:
org.apache.geronimo.configs:jee-specs:car:2.0-SNAPSHOT
from the specified remote repositories:
central ( http://repo1.maven.org/maven2),
java.net ( http://download.java.net/maven/1/),
apache.snapshots
(http://people.apache.org/repo/m2-snapshot-repository ),
apache-snapshots
(http://people.apache.org/repo/m2-snapshot-repository ),
codehaus-snapshots (
http://snapshots.repository.codehaus.org),
apache-incubator
(http://people.apache.org/repo/m2-incubating-repository/ ),
tomcat-m2-repo (
http://tomcat.apache.org/dev/dist/m2-repository)
NOTE: Maven is executing in offline mode. Any artifacts not already in your
loca
l
repository will be inaccessible.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 30 seconds
[INFO] Finished at: Thu Jul 12 15:57:15 IST 2007
[INFO] Final Memory: 38M/68M
[INFO]
Re: svn commit: r555430 - in /geronimo/sandbox/portals/geronimo-console/src/main: java/org/apache/geronimo/console/jsr77/Jsr77Lookup.java webapp/graphs/memoryGraphJS.jsp
Thanks Paul! I am very interested in getting this to work. However, I am
having a problem building the geronimo-console. I am getting the following
error
Any ideas as to what went wrong. do I need to update anything else?
~Daniel
[INFO] Compiling 97 source files to
C:\g\portals\geronimo-console\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet.java:[479,19]
setControlFlag(java.lang.String) in
org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.LoginModuleDetailscannot
be applied to (
org.apache.geronimo.security.jaas.LoginModuleControlFlag)
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet.java:[483,40]
cannot find symbol
symbol : method isServerSide()
location: interface org.apache.geronimo.security.jaas.LoginModuleSettings
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet.java:[485,19]
setOptions(java.util.Properties) in
org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.LoginModuleDetailscannot
be applied to (
java.util.Mapjava.lang.String,java.lang.Object)
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet.java:[540,20]
setControlFlag(org.apache.geronimo.security.jaas.LoginModuleControlFlag) in
org.apache.geronimo.security.jaas.JaasLoginModuleChain cannot be applied to
(java.lang.String)
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet.java:[542,22]
setOptions(java.util.Mapjava.lang.String,java.lang.Object) in
org.apache.geronimo.security.jaas.LoginModuleSettings cannot be applied to (
java.util.Properties)
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet.java:[543,22]
cannot find symbol
symbol : method setServerSide(boolean)
location: interface org.apache.geronimo.security.jaas.LoginModuleSettings
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 minute 51 seconds
[INFO] Finished at: Thu Jul 12 08:30:14 EDT 2007
[INFO] Final Memory: 33M/67M
[INFO]
On 7/11/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: pmcmahan
Date: Wed Jul 11 15:56:27 2007
New Revision: 555430
URL: http://svn.apache.org/viewvc?view=revrev=555430
Log:
fix DWR usage in server info portlet
Modified:
geronimo/sandbox/portals/geronimo-console/src/main/java/org/apache/geronimo/console/jsr77/Jsr77Lookup.java
geronimo/sandbox/portals/geronimo-console/src/main/webapp/graphs/memoryGraphJS.jsp
Modified:
geronimo/sandbox/portals/geronimo-console/src/main/java/org/apache/geronimo/console/jsr77/Jsr77Lookup.java
URL:
http://svn.apache.org/viewvc/geronimo/sandbox/portals/geronimo-console/src/main/java/org/apache/geronimo/console/jsr77/Jsr77Lookup.java?view=diffrev=555430r1=555429r2=555430
==
---
geronimo/sandbox/portals/geronimo-console/src/main/java/org/apache/geronimo/console/jsr77/Jsr77Lookup.java
(original)
+++
geronimo/sandbox/portals/geronimo-console/src/main/java/org/apache/geronimo/console/jsr77/Jsr77Lookup.java
Wed Jul 11 15:56:27 2007
@@ -34,7 +34,7 @@
*/
public class Jsr77Lookup {
public DynamicServerInfo getJavaVMStatistics() {
-HttpSession session = WebContextFactory.get().getSession(false);
+HttpSession session = WebContextFactory.get().getSession(true);
ManagementHelper helper = PortletManager.getManagementHelper
(session);
J2EEDomain[] domains = helper.getDomains();
J2EEServer[] servers = domains[0].getServerInstances();
Modified:
geronimo/sandbox/portals/geronimo-console/src/main/webapp/graphs/memoryGraphJS.jsp
URL:
http://svn.apache.org/viewvc/geronimo/sandbox/portals/geronimo-console/src/main/webapp/graphs/memoryGraphJS.jsp?view=diffrev=555430r1=555429r2=555430
==
---
geronimo/sandbox/portals/geronimo-console/src/main/webapp/graphs/memoryGraphJS.jsp
(original)
+++
geronimo/sandbox/portals/geronimo-console/src/main/webapp/graphs/memoryGraphJS.jsp
Wed Jul 11 15:56:27 2007
@@ -21,7 +21,7 @@
metadata = {};
metadata.callback=updateValues;
metadata.errorHandler=onError;
-Jsr77Stats.getJavaVMStatistics(metadata);
+top.Jsr77Stats.getJavaVMStatistics(metadata);
}
[DISCUSS] Geronimo 2.0 Release Plans - Release around August 3rd - Just a thought
I saw a note from Gianny this morning about WADI and making a versioned release. His comment was that he could make ait available a few days ahead of time. So I guess that beg's the question when will we release. I thought I'd summarize my thoughts and solicit input from folks. Since we passed CTS in early June on 2.0-M6-rc1 I think the remaining items that I've been thinking we needed to release are: * Fit and finish items - look at reducing footprint - Running DayTrader and validating the server functioning, being consistent with 1.x where appropriate and being stable - Performance is better than 1.x where appropriate - Get the legal stuff out of the way. * Functional items - Axis indicated they were almost there with JAXWS and Dims has been involved in the G integration - Complete CTS testing - Testing and documentation On the Axis front I've been watching their dev list and there seems to be some notion of being complete around July 20 (Friday). If we assume that is around the right time I expect we can start a set of TCK runs on the 23rd. Allow a few weeks to finish that process and we can put together a binary for vote around the end of July. I guess a target release date would be around August 3rd (nothing hard but it seems about right). Once we have the major kinks knocked out wrt to CTS we should probably branch (around the 30th ?) and focus on getting our binaries out. Based on previous e-mails I believe we are shipping the following certified releases: Tomcat - Axis 2 - OpenJPA Jetty - CXF - OpenJPA Along with the minimal assemblies. Prasad has put together a Wiki so we can track down our outstanding SNAPSHOTs and start getting them locked down as well. For projects that won't be releasing I suggest we look for folks to grab and build those projects and get the artifacts into our repo in the SVN tree so we minimize external disruptions. Other thoughts?
Re: [DISCUSS] Geronimo 2.0 Release Plans - Release around August 3rd - Just a thought
Matt Hogstrom wrote: Based on previous e-mails I believe we are shipping the following certified releases: Tomcat - Axis 2 - OpenJPA Jetty - CXF - OpenJPA I think if we are going to ship these assemblies, we also should very clearly document how to switch between web service containers (i.e. the switch property) as there is quite a bit of religious war as to which people desire. Jeff
Re: svn commit: r555430 - in /geronimo/sandbox/portals/geronimo-console/src/main: java/org/apache/geronimo/console/jsr77/Jsr77Lookup.java webapp/graphs/memoryGraphJS.jsp
needed to merge 554977. should be fixed now.
Best wishes,
Paul
On Jul 12, 2007, at 8:59 AM, Daniel Larsen wrote:
Thanks Paul! I am very interested in getting this to work.
However, I am having a problem building the geronimo-console. I am
getting the following error
Any ideas as to what went wrong. do I need to update anything else?
~Daniel
[INFO] Compiling 97 source files to C:\g\portals\geronimo-console
\target\classes
[INFO]
--
--
[ERROR] BUILD FAILURE
[INFO]
--
--
[INFO] Compilation failure
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo
\console\securitymanager\realm\SecurityRealmPortlet.java:[479,19]
setControlFlag( java.lang.String) in
org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet
.LoginModuleDetails cannot be applied to
(org.apache.geronimo.security.jaas.LoginModuleControlFlag)
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo
\console\securitymanager\realm\SecurityRealmPortlet.java:[483,40]
cannot find symbol
symbol : method isServerSide()
location: interface
org.apache.geronimo.security.jaas.LoginModuleSettings
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo
\console\securitymanager\realm\SecurityRealmPortlet.java:[485,19]
setOptions( java.util.Properties) in
org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet
.LoginModuleDetails cannot be applied to
(java.util.Mapjava.lang.String,java.lang.Object)
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo
\console\securitymanager\realm\SecurityRealmPortlet.java:[540,20]
setControlFlag
( org.apache.geronimo.security.jaas.LoginModuleControlFlag) in
org.apache.geronimo.security.jaas.JaasLoginModuleChain cannot be
applied to (java.lang.String)
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo
\console\securitymanager\realm\SecurityRealmPortlet.java:[542,22]
setOptions( java.util.Mapjava.lang.String,java.lang.Object) in
org.apache.geronimo.security.jaas.LoginModuleSettings cannot be
applied to (java.util.Properties)
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo
\console\securitymanager\realm\SecurityRealmPortlet.java:[543,22]
cannot find symbol
symbol : method setServerSide(boolean)
location: interface
org.apache.geronimo.security.jaas.LoginModuleSettings
[INFO]
--
--
[INFO] For more information, run Maven with the -e switch
[INFO]
--
--
[INFO] Total time: 1 minute 51 seconds
[INFO] Finished at: Thu Jul 12 08:30:14 EDT 2007
[INFO] Final Memory: 33M/67M
[INFO]
--
--
On 7/11/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: pmcmahan
Date: Wed Jul 11 15:56:27 2007
New Revision: 555430
URL: http://svn.apache.org/viewvc?view=revrev=555430
Log:
fix DWR usage in server info portlet
Modified:
geronimo/sandbox/portals/geronimo-console/src/main/java/org/
apache/geronimo/console/jsr77/Jsr77Lookup.java
geronimo/sandbox/portals/geronimo-console/src/main/webapp/
graphs/memoryGraphJS.jsp
Modified: geronimo/sandbox/portals/geronimo-console/src/main/java/
org/apache/geronimo/console/jsr77/Jsr77Lookup.java
URL: http://svn.apache.org/viewvc/geronimo/sandbox/portals/geronimo-
console/src/main/java/org/apache/geronimo/console/jsr77/
Jsr77Lookup.java?view=diffrev=555430r1=555429r2=555430
==
--- geronimo/sandbox/portals/geronimo-console/src/main/java/org/
apache/geronimo/console/jsr77/Jsr77Lookup.java (original)
+++ geronimo/sandbox/portals/geronimo-console/src/main/java/org/
apache/geronimo/console/jsr77/Jsr77Lookup.java Wed Jul 11 15:56:27
2007
@@ -34,7 +34,7 @@
*/
public class Jsr77Lookup {
public DynamicServerInfo getJavaVMStatistics() {
-HttpSession session = WebContextFactory.get().getSession
(false);
+HttpSession session = WebContextFactory.get().getSession
(true);
ManagementHelper helper =
PortletManager.getManagementHelper(session);
J2EEDomain[] domains = helper.getDomains();
J2EEServer[] servers = domains[0].getServerInstances();
Modified: geronimo/sandbox/portals/geronimo-console/src/main/webapp/
graphs/memoryGraphJS.jsp
URL: http://svn.apache.org/viewvc/geronimo/sandbox/portals/geronimo-
console/src/main/webapp/graphs/memoryGraphJS.jsp?
view=diffrev=555430r1=555429r2=555430
==
--- geronimo/sandbox/portals/geronimo-console/src/main/webapp/
graphs/memoryGraphJS.jsp (original)
+++ geronimo/sandbox/portals/geronimo-console/src/main/webapp/
Re: SNAPSHOT dependencies that need to be released.
I'll raise the issue on the Yoko dev list. Last time, this took a long time to get done because the discussions on how the release should be bundled and whether the tools were ready for release or not. I'm not sure of the status of the tools, as the people who've been working on them have not been very good about doing the work on list. It might be necessary to spin an M3 release of just the run time like the last time Geronimo needed a release. This is further complicated by the project incubating status, since it requires two levels of voting to get released. Rick Prasad Kashyap wrote: The following Geronimo dependencies uses SNAPSHOT versions. Can we please chase these projects and get them to release the artifacts, whatever it takes; contacts, muscles, bribes, favors, etc :-) If enough people on this list volunteer to get some of these released, then I'll create a wiki page where they can sign up. openejbVersion3.0-incubating-SNAPSHOT/openejbVersion groupIdorg.apache.cxf/groupId artifactIdcxf-api/artifactId version2.0-incubator-SNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-java2wsdl/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-kernel/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-adb/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-jaxws-api/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-jaxws/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-metadata/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-saaj/artifactId versionSNAPSHOT/version groupIdorg.apache.geronimo.javamail/groupId artifactIdgeronimo-javamail_1.4_mail/artifactId version1.1-SNAPSHOT/version groupIdorg.apache.geronimo.schema/groupId artifactIdgeronimo-schema-jee_5/artifactId version1.1-SNAPSHOT/version groupIdorg.apache.geronimo.schema/groupId artifactIdgeronimo-schema-j2ee_1.4/artifactId version1.1-SNAPSHOT/version groupIdorg.apache.openjpa/groupId artifactIdopenjpa/artifactId version1.0.0-SNAPSHOT/version groupIdorg.apache.xbean/groupId artifactIdxbean-finder/artifactId version3.0-SNAPSHOT/version groupIdorg.apache.xbean/groupId artifactIdxbean-naming/artifactId version3.0-SNAPSHOT/version groupIdorg.apache.xbean/groupId artifactIdxbean-reflect/artifactId version3.1-SNAPSHOT/version groupIdorg.apache.ws.scout/groupId artifactIdscout/artifactId versionSNAPSHOT/version groupIdorg.apache.yoko/groupId artifactIdyoko-core/artifactId version1.0-incubating-SNAPSHOT/version groupIdorg.apache.yoko/groupId artifactIdyoko-spec-corba/artifactId version1.0-incubating-SNAPSHOT/version groupIdorg.apache.yoko/groupId artifactIdyoko-rmi-spec/artifactId version1.0-incubating-SNAPSHOT/version groupIdorg.apache.yoko/groupId artifactIdyoko-rmi-impl/artifactId version1.0-incubating-SNAPSHOT/version groupIdorg.mortbay.jetty/groupId artifactIdjetty/artifactId version6.1-SNAPSHOT/version groupIdorg.mortbay.jetty/groupId artifactIdjetty-ajp/artifactId version6.1-SNAPSHOT/version groupIdorg.mortbay.jetty/groupId artifactIdjetty-sslengine/artifactId version6.1-SNAPSHOT/version groupIdorg.mortbay.jetty/groupId artifactIdjetty-util/artifactId version6.1-SNAPSHOT/version groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-api/artifactId version1.2.0-SNAPSHOT/version groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-impl/artifactId version1.2.0-SNAPSHOT/version Cheers Prasad
Re: configuring sevicemix-jms to IBM MQ
I'm getting Null Pointer Exception in JMS SU. -- View this message in context: http://www.nabble.com/configuring-sevicemix-jms-to-IBM-MQ-tf4068169s12049.html#a11561406 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
[jira] Updated: (GERONIMO-3304) ability to update openejb-jar.xml by examining annotations
[ https://issues.apache.org/jira/browse/GERONIMO-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3304: --- Attachment: geronimo-3304-3.patch this patch warns users if the source code contains references to JBoss's extension to EJB annotations. ability to update openejb-jar.xml by examining annotations -- Key: GERONIMO-3304 URL: https://issues.apache.org/jira/browse/GERONIMO-3304 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: J2G Environment: windows xp, linux Reporter: Viet Hung Nguyen Attachments: geronimo-3304-2.patch, geronimo-3304-3.patch, geronimo-3304.patch As of now, when there is a jboss.xml in a JBoss project, the geronimo equivalent is written to openejb-jar.xml. However, that only covers EJB 2.1's features. We need a way to update the openejb-jar.xml by looking at the annotations because there is still some configuring left to do. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-623) Unit test that fails when building using maven2.
[ https://issues.apache.org/activemq/browse/SM-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39662 ] Gert Vanthienen commented on SM-623: It appears the servicemix-eip tests were failing when no additional memory was reserved for the unit tests (currently: -Xmx512m). With Adrian's centralized surefire configuration in place, all these tests now work fine. I have removed the exclusion/s from the pom.xml (cfr. http://svn.apache.org/viewvc?view=revrevision=555652) Unit test that fails when building using maven2. Key: SM-623 URL: https://issues.apache.org/activemq/browse/SM-623 Project: ServiceMix Issue Type: Test Reporter: Fritz Oconer Check the sub tasks. These are unit tests that fails when building using maven 2 and jdk1.5 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-652) org.apache.servicemix.eip.StaticRoutingSlipTxTest
[ https://issues.apache.org/activemq/browse/SM-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-652. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 org.apache.servicemix.eip.StaticRoutingSlipTxTest - Key: SM-652 URL: https://issues.apache.org/activemq/browse/SM-652 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-653) org.apache.servicemix.eip.WireTapJmsFlowTest
[ https://issues.apache.org/activemq/browse/SM-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-653. Resolution: Fixed Cfr. explanation on SM-623 org.apache.servicemix.eip.WireTapJmsFlowTest Key: SM-653 URL: https://issues.apache.org/activemq/browse/SM-653 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-654) org.apache.servicemix.eip.PipelineTxTest
[ https://issues.apache.org/activemq/browse/SM-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-654: --- Fix Version/s: 3.2 org.apache.servicemix.eip.PipelineTxTest Key: SM-654 URL: https://issues.apache.org/activemq/browse/SM-654 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-623) Unit test that fails when building using maven2.
[ https://issues.apache.org/activemq/browse/SM-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39666 ] Resigned Employee commented on SM-623: -- Please be informed that I am no longer accessible through this email address. Pls refrain from sending further messages. I will just personally contact you with my new email address. For any concerns / issues / inputs relating to your transactions with Exist, kindly forward email to [EMAIL PROTECTED] Thank you HR Dept Unit test that fails when building using maven2. Key: SM-623 URL: https://issues.apache.org/activemq/browse/SM-623 Project: ServiceMix Issue Type: Test Reporter: Fritz Oconer Check the sub tasks. These are unit tests that fails when building using maven 2 and jdk1.5 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-654) org.apache.servicemix.eip.PipelineTxTest
[ https://issues.apache.org/activemq/browse/SM-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-654. Resolution: Fixed Cfr. explanation on SM-623 org.apache.servicemix.eip.PipelineTxTest Key: SM-654 URL: https://issues.apache.org/activemq/browse/SM-654 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2757) Enhance plugin schema to allow for multiple versions of a plugin
[ https://issues.apache.org/jira/browse/GERONIMO-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512138 ] Paul McMahan commented on GERONIMO-2757: thanks for the patch Jason. after applying it I'm concerned that the export portlet will be overwhelming to the average user because of the 18 new inputs for version. I think the expanded capabilities of the geronimo-versions element will be mostly needed by repository catalogs and probably not for individually exported plugins.if a simplified UI can support the most common scenarios then I think its OK to rely on the user to crack open the exported car and edit the geronimo-plugin.xml for more advanced scenarios. so I wonder can the plugin export portlet be simplified to only prompt for one geronimo-version and also compress the multiple inputs for it? Enhance plugin schema to allow for multiple versions of a plugin Key: GERONIMO-2757 URL: https://issues.apache.org/jira/browse/GERONIMO-2757 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.0-M5 Reporter: Paul McMahan Assignee: Jason Warner Fix For: 2.0-M7 Attachments: geronimo-2757.patch, Geronimo-2757.patch, Geronimo-2757.patch, Geronimo-2757Export.patch, Geronimo-2757Update.patch plugins-1.1.xsd currently allows for a single version of a plugin to be described from within a plugin element. For example, if there were a different version of plugin for each version of geronimo then the plugin catalog would like something like: plugin module-idorg.apache.geronimo.configs/ca-helper-tomcat/1.1/car/module-id geronimo-version1.1/geronimo-version source-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.1/source-repository [...] /plugin plugin module-idorg.apache.geronimo.configs/ca-helper-tomcat/1.2/car/module-id geronimo-version1.2/geronimo-version source-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.2/source-repository [...] /plugin plugin module-idorg.apache.geronimo.configs/ca-helper-tomcat/2.0/car/module-id geronimo-version2.0/geronimo-version source-repositoryhttp://geronimo.apache.org/plugins/geronimo-2.0/source-repository [...] /plugin default-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.1/default-repository default-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.2/default-repository default-repositoryhttp://geronimo.apache.org/plugins/geronimo-2.0/default-repository Plugins are usually not compatible across versions of Geronimo for various reasons, probably the most prominent of which is Geronimo's reliance on serialized java objects in CAR files. Browsing a catalog that contains a plugin element for each version of Geronimo's plugins from the admin console or from the CLI would be confusing because of the many (seemingly redundant) entries. Therefore the collection of Geronimo plugins is distributed across a set of catalogs, one per version of Geronimo, and each version of Geronimo points at a version specific plugin catalog. Modifying the plugin schema so that a plugin element can allow the plugin's module-id and source-repository to depend on the geronimo-version would allow there to be much fewer entries in a consolidated plugin catalog. A plugin catalog that is created using this modified schema might look something like (this is just a sample) : plugin geronimo-version version=1.1 module-idorg.apache.geronimo.configs/ca-helper-tomcat/1.1/car/module-id source-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.1/source-repository /geronimo-version geronimo-version version=1.2 module-idorg.apache.geronimo.configs/ca-helper-tomcat/1.2/car/module-id source-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.2/source-repository /geronimo-version geronimo-version version=2.0 module-idorg.apache.geronimo.configs/ca-helper-tomcat/2.0/car/module-id source-repositoryhttp://geronimo.apache.org/plugins/geronimo-2.0/source-repository /geronimo-version [...] /plugin Also, for this to work a customized list of prerequisite elements would probably have to be supported inside the geronimo-version element as well, since those might also be version specific. Once this improvement is in place it will be easier to maintain Geronimo's plugin collection since each version of Geronimo won't require a separate catalog. Also it will be easier for end users and other external sources to refer to Geronimo's plugin catalog since the repository URL will no longer be version specific. --
[jira] Resolved: (SM-655) org.apache.servicemix.eip.SplitAggregatorTxTest
[ https://issues.apache.org/activemq/browse/SM-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-655. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 org.apache.servicemix.eip.SplitAggregatorTxTest --- Key: SM-655 URL: https://issues.apache.org/activemq/browse/SM-655 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-656) org.apache.servicemix.eip.StaticRecipientListTxTest
[ https://issues.apache.org/activemq/browse/SM-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-656. Resolution: Fixed Cfr. explanation on SM-623 org.apache.servicemix.eip.StaticRecipientListTxTest --- Key: SM-656 URL: https://issues.apache.org/activemq/browse/SM-656 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-657) org.apache.servicemix.eip.MessageFilterTxTest
[ https://issues.apache.org/activemq/browse/SM-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-657. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 org.apache.servicemix.eip.MessageFilterTxTest - Key: SM-657 URL: https://issues.apache.org/activemq/browse/SM-657 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-658) org.apache.servicemix.eip.WireTapTxTest
[ https://issues.apache.org/activemq/browse/SM-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-658. Resolution: Fixed Cfr. explanation on SM-623 org.apache.servicemix.eip.WireTapTxTest --- Key: SM-658 URL: https://issues.apache.org/activemq/browse/SM-658 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-658) org.apache.servicemix.eip.WireTapTxTest
[ https://issues.apache.org/activemq/browse/SM-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-658: --- Fix Version/s: 3.2 org.apache.servicemix.eip.WireTapTxTest --- Key: SM-658 URL: https://issues.apache.org/activemq/browse/SM-658 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-659) org.apache.servicemix.eip.XPathSplitterTxTest
[ https://issues.apache.org/activemq/browse/SM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-659. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 org.apache.servicemix.eip.XPathSplitterTxTest - Key: SM-659 URL: https://issues.apache.org/activemq/browse/SM-659 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-661) org.apache.servicemix.eip.support.NamespaceContextImplTest
[ https://issues.apache.org/activemq/browse/SM-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-661. Resolution: Fixed Fix Version/s: 3.2 org.apache.servicemix.eip.support.NamespaceContextImplTest -- Key: SM-661 URL: https://issues.apache.org/activemq/browse/SM-661 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-660) org.apache.servicemix.eip.DeploymentTest
[ https://issues.apache.org/activemq/browse/SM-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-660. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 org.apache.servicemix.eip.DeploymentTest Key: SM-660 URL: https://issues.apache.org/activemq/browse/SM-660 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-662) org.apache.servicemix.eip.SpringConfigurationTest
[ https://issues.apache.org/activemq/browse/SM-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-662. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 org.apache.servicemix.eip.SpringConfigurationTest - Key: SM-662 URL: https://issues.apache.org/activemq/browse/SM-662 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-663) org.apache.servicemix.eip.ContentBasedRouterTxTest
[ https://issues.apache.org/activemq/browse/SM-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-663. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 org.apache.servicemix.eip.ContentBasedRouterTxTest -- Key: SM-663 URL: https://issues.apache.org/activemq/browse/SM-663 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-653) org.apache.servicemix.eip.WireTapJmsFlowTest
[ https://issues.apache.org/activemq/browse/SM-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-653: --- Fix Version/s: 3.2 org.apache.servicemix.eip.WireTapJmsFlowTest Key: SM-653 URL: https://issues.apache.org/activemq/browse/SM-653 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r555430 - in /geronimo/sandbox/portals/geronimo-console/src/main: java/org/apache/geronimo/console/jsr77/Jsr77Lookup.java webapp/graphs/memoryGraphJS.jsp
That fixed it. Thanks!
On 7/12/07, Paul McMahan [EMAIL PROTECTED] wrote:
needed to merge 554977. should be fixed now.
Best wishes,
Paul
On Jul 12, 2007, at 8:59 AM, Daniel Larsen wrote:
Thanks Paul! I am very interested in getting this to work.
However, I am having a problem building the geronimo-console. I am
getting the following error
Any ideas as to what went wrong. do I need to update anything else?
~Daniel
[INFO] Compiling 97 source files to C:\g\portals\geronimo-console
\target\classes
[INFO]
--
--
[ERROR] BUILD FAILURE
[INFO]
--
--
[INFO] Compilation failure
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo
\console\securitymanager\realm\SecurityRealmPortlet.java:[479,19]
setControlFlag( java.lang.String) in
org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet
.LoginModuleDetails cannot be applied to
(org.apache.geronimo.security.jaas.LoginModuleControlFlag)
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo
\console\securitymanager\realm\SecurityRealmPortlet.java:[483,40]
cannot find symbol
symbol : method isServerSide()
location: interface
org.apache.geronimo.security.jaas.LoginModuleSettings
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo
\console\securitymanager\realm\SecurityRealmPortlet.java:[485,19]
setOptions( java.util.Properties) in
org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet
.LoginModuleDetails cannot be applied to
(java.util.Mapjava.lang.String,java.lang.Object)
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo
\console\securitymanager\realm\SecurityRealmPortlet.java:[540,20]
setControlFlag
( org.apache.geronimo.security.jaas.LoginModuleControlFlag) in
org.apache.geronimo.security.jaas.JaasLoginModuleChain cannot be
applied to (java.lang.String)
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo
\console\securitymanager\realm\SecurityRealmPortlet.java:[542,22]
setOptions( java.util.Mapjava.lang.String,java.lang.Object) in
org.apache.geronimo.security.jaas.LoginModuleSettings cannot be
applied to (java.util.Properties)
C:\g\portals\geronimo-console\src\main\java\org\apache\geronimo
\console\securitymanager\realm\SecurityRealmPortlet.java:[543,22]
cannot find symbol
symbol : method setServerSide(boolean)
location: interface
org.apache.geronimo.security.jaas.LoginModuleSettings
[INFO]
--
--
[INFO] For more information, run Maven with the -e switch
[INFO]
--
--
[INFO] Total time: 1 minute 51 seconds
[INFO] Finished at: Thu Jul 12 08:30:14 EDT 2007
[INFO] Final Memory: 33M/67M
[INFO]
--
--
On 7/11/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: pmcmahan
Date: Wed Jul 11 15:56:27 2007
New Revision: 555430
URL: http://svn.apache.org/viewvc?view=revrev=555430
Log:
fix DWR usage in server info portlet
Modified:
geronimo/sandbox/portals/geronimo-console/src/main/java/org/
apache/geronimo/console/jsr77/Jsr77Lookup.java
geronimo/sandbox/portals/geronimo-console/src/main/webapp/
graphs/memoryGraphJS.jsp
Modified: geronimo/sandbox/portals/geronimo-console/src/main/java/
org/apache/geronimo/console/jsr77/Jsr77Lookup.java
URL: http://svn.apache.org/viewvc/geronimo/sandbox/portals/geronimo-
console/src/main/java/org/apache/geronimo/console/jsr77/
Jsr77Lookup.java?view=diffrev=555430r1=555429r2=555430
==
--- geronimo/sandbox/portals/geronimo-console/src/main/java/org/
apache/geronimo/console/jsr77/Jsr77Lookup.java (original)
+++ geronimo/sandbox/portals/geronimo-console/src/main/java/org/
apache/geronimo/console/jsr77/Jsr77Lookup.java Wed Jul 11 15:56:27
2007
@@ -34,7 +34,7 @@
*/
public class Jsr77Lookup {
public DynamicServerInfo getJavaVMStatistics() {
-HttpSession session = WebContextFactory.get().getSession
(false);
+HttpSession session = WebContextFactory.get().getSession
(true);
ManagementHelper helper =
PortletManager.getManagementHelper(session);
J2EEDomain[] domains = helper.getDomains();
J2EEServer[] servers = domains[0].getServerInstances();
Modified: geronimo/sandbox/portals/geronimo-console/src/main/webapp/
graphs/memoryGraphJS.jsp
URL: http://svn.apache.org/viewvc/geronimo/sandbox/portals/geronimo-
console/src/main/webapp/graphs/memoryGraphJS.jsp?
view=diffrev=555430r1=555429r2=555430
==
--- geronimo/sandbox/portals/geronimo-console/src/main/webapp/
graphs/memoryGraphJS.jsp (original)
[jira] Closed: (GERONIMO-3312) Eliminate obselete org.apache.geronimo.management.geronimo.J2EEServer.getLoginService() method
[ https://issues.apache.org/jira/browse/GERONIMO-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsavardhana Reddy closed GERONIMO-3312. - Resolution: Fixed 1. Removed org.apache.geronimo.management.geronimo.J2EEServer.getLoginService() method 2. Removed org.apache.geronimo.management.geronimo.LoginService interface Completed: At revision: 555665 in trunk. Eliminate obselete org.apache.geronimo.management.geronimo.J2EEServer.getLoginService() method -- Key: GERONIMO-3312 URL: https://issues.apache.org/jira/browse/GERONIMO-3312 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: management Affects Versions: 2.0-M7 Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Priority: Minor Fix For: 2.0-M7 org.apache.geronimo.management.geronimo.J2EEServer.getLoginService() method is made obselete by GERONIMO-3303. A call to this method from SecurityRealmPortlet is resulting in NullPointerException as there is no LoginService defined now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3311) Security Realms portlet is broken. Unable to edit realm.
[ https://issues.apache.org/jira/browse/GERONIMO-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512151 ] Vamsavardhana Reddy commented on GERONIMO-3311: --- Fixed the JSPs in revision 555675 in trunk. geronimo-login-config schema needs to be updated to remove the server-side option. Security Realms portlet is broken. Unable to edit realm. - Key: GERONIMO-3311 URL: https://issues.apache.org/jira/browse/GERONIMO-3311 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 2.0-M7 Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Fix For: 2.0-M7 Security Realms portlet is broken. I guess the problem is introduced by recent changes for GERONIMO-3303 Simplify security authentication framework by removing mixed local/remote logins. When I click on edit link, the following exception is logged. 16:23:37,613 ERROR [edit_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.realmwizard.edit_jsp threw exception javax.el.PropertyNotFoundException: Property 'serverSide' not found on type org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet$LoginModuleDetails at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) at javax.el.BeanELResolver.property(BeanELResolver.java:279) at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at org.apache.el.parser.AstValue.getValue(AstValue.java:97) at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:923) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspx_meth_c_005fif_005f6(edit_jsp.java:850) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspx_meth_c_005fforEach_005f2(edit_jsp.java:586) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspService(edit_jsp.java:146) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.pluto.core.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:65) at org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.renderEdit(SecurityRealmPortlet.java:585) at org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.doView(SecurityRealmPortlet.java:260) 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(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.render(PortletInvokerImpl.java:73) at org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:119) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.renderPortlet(PortletContainerWrapperImpl.java:70) at org.apache.pluto.portalImpl.aggregation.PortletFragment.service(PortletFragment.java:168) at
[jira] Assigned: (GERONIMO-3311) Security Realms portlet is broken. Unable to edit realm.
[ https://issues.apache.org/jira/browse/GERONIMO-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsavardhana Reddy reassigned GERONIMO-3311: - Assignee: David Jencks (was: Vamsavardhana Reddy) Security Realms portlet is broken. Unable to edit realm. - Key: GERONIMO-3311 URL: https://issues.apache.org/jira/browse/GERONIMO-3311 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 2.0-M7 Reporter: Vamsavardhana Reddy Assignee: David Jencks Fix For: 2.0-M7 Security Realms portlet is broken. I guess the problem is introduced by recent changes for GERONIMO-3303 Simplify security authentication framework by removing mixed local/remote logins. When I click on edit link, the following exception is logged. 16:23:37,613 ERROR [edit_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.realmwizard.edit_jsp threw exception javax.el.PropertyNotFoundException: Property 'serverSide' not found on type org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet$LoginModuleDetails at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) at javax.el.BeanELResolver.property(BeanELResolver.java:279) at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at org.apache.el.parser.AstValue.getValue(AstValue.java:97) at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:923) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspx_meth_c_005fif_005f6(edit_jsp.java:850) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspx_meth_c_005fforEach_005f2(edit_jsp.java:586) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspService(edit_jsp.java:146) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.pluto.core.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:65) at org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.renderEdit(SecurityRealmPortlet.java:585) at org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.doView(SecurityRealmPortlet.java:260) 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(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.render(PortletInvokerImpl.java:73) at org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:119) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.renderPortlet(PortletContainerWrapperImpl.java:70) at org.apache.pluto.portalImpl.aggregation.PortletFragment.service(PortletFragment.java:168) at jsp.WEB_002dINF.aggregation.ColumnFragment_jsp._jspService(ColumnFragment_jsp.java:70) at
[jira] Commented: (GERONIMO-2373) build broken with the removal of geronimo-j2ee_1.4_spec from the specs
[ https://issues.apache.org/jira/browse/GERONIMO-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512172 ] Kevin commented on GERONIMO-2373: - How is this patch supposed to be applied? Many of us are just learning J2EE and Websphere, and it's difficult enough to deploy the sample applications. It looks like this patch will fix the daytrader sample app, but I have no idea what to do with this file. How about a README? Please don't assume that those of us trying to use this patch understand as much as those of you who write them. build broken with the removal of geronimo-j2ee_1.4_spec from the specs -- Key: GERONIMO-2373 URL: https://issues.apache.org/jira/browse/GERONIMO-2373 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: buildsystem Affects Versions: 1.2 Reporter: Bill Dudney Assignee: Jason Dillon Fix For: 1.2 Attachments: GERONIMO-2373.bdudney.patch a couple of configs and applications have dependencies that are not correct as a result of the removal of geronimo-j2ee_1.4_spec. The attached patch addes the necessary dependencies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: [jira] Commented: (SM-1000) ServiceMix :: Maven2 JBI Plugin checkstyle issues
Greg,
Thats right... thanks for pointing that out.. I have updated it..Anyway, is
there any specific reason for these checkstyle supressions..WIP???
From: Gert Vanthienen (JIRA) [mailto:[EMAIL PROTECTED]
Sent: Thu 7/12/2007 7:08 PM
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (SM-1000) ServiceMix :: Maven2 JBI Plugin checkstyle
issues
[
https://issues.apache.org/activemq/browse/SM-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39661
]
Gert Vanthienen commented on SM-1000:
-
Rabi,
My checkout has a CheckStyle suppresion for this particular check in the
GraphArtifactCollector class registered in
{{build/src/main/resources/smx-checkstyle-suppressions.xml}}. Can you check if
you have that too? Perhaps your build/ directory needs another update...
Gert
ServiceMix :: Maven2 JBI Plugin checkstyle issues
--
Key: SM-1000
URL: https://issues.apache.org/activemq/browse/SM-1000
Project: ServiceMix
Issue Type: Bug
Components: tooling
Affects Versions: 3.2
Environment: Windows
Reporter: Rabi
[INFO] Building ServiceMix :: Maven2 JBI Plugin
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] Ignoring available plugin update: 2.3 as it requires Maven version
2.0.5
[INFO] [checkstyle:checkstyle {execution: validate}]
[INFO] Starting audit...
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:58:37: More than
7 p
arameters.
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:96:18: More than
7 p
arameters.
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37: method
def
modifier at indentation level 2 not at correct indentation, 4
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37:15: More
th
an 7 parameters.
Audit done.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error has occurred in Checkstyle report generation.
Embedded error: There are 4 checkstyle errors.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 28 seconds
[INFO] Finished at: Wed Jul 11 16:34:15 IST 2007
[INFO] Final Memory: 13M/24M
[INFO]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain proprietary, confidential or privileged information. If you are not the
intended recipient, you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately and destroy all copies of this message and
any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should
check this email and any attachments for the presence of viruses. The company
accepts no liability for any damage caused by any virus transmitted by this
email.
www.wipro.com
[jira] Closed: (SM-1000) ServiceMix :: Maven2 JBI Plugin checkstyle issues
[
https://issues.apache.org/activemq/browse/SM-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rabi closed SM-1000.
Resolution: Won't Fix
checkstyle supressions exist for these classes.. svn update for build resolved
it..
ServiceMix :: Maven2 JBI Plugin checkstyle issues
--
Key: SM-1000
URL: https://issues.apache.org/activemq/browse/SM-1000
Project: ServiceMix
Issue Type: Bug
Components: tooling
Affects Versions: 3.2
Environment: Windows
Reporter: Rabi
[INFO] Building ServiceMix :: Maven2 JBI Plugin
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] Ignoring available plugin update: 2.3 as it requires Maven version
2.0.5
[INFO] [checkstyle:checkstyle {execution: validate}]
[INFO] Starting audit...
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:58:37: More than
7 p
arameters.
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:96:18: More than
7 p
arameters.
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37: method
def
modifier at indentation level 2 not at correct indentation, 4
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37:15: More
th
an 7 parameters.
Audit done.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error has occurred in Checkstyle report generation.
Embedded error: There are 4 checkstyle errors.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 28 seconds
[INFO] Finished at: Wed Jul 11 16:34:15 IST 2007
[INFO] Final Memory: 13M/24M
[INFO]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3314) The Welcome portlet has an error in the way it renders the Common Console Actions table
The Welcome portlet has an error in the way it renders the Common Console Actions table --- Key: GERONIMO-3314 URL: https://issues.apache.org/jira/browse/GERONIMO-3314 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Environment: WindowsXP Reporter: Daniel Larsen Priority: Trivial Attachments: geronimo-3314.patch The Welcome portlet has an error in the way it renders the Common Console Actions table -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3314) The Welcome portlet has an error in the way it renders the Common Console Actions table
[ https://issues.apache.org/jira/browse/GERONIMO-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Larsen updated GERONIMO-3314: Attachment: geronimo-3314.patch There was a missing td tag. Also put the spacing back in. The Welcome portlet has an error in the way it renders the Common Console Actions table --- Key: GERONIMO-3314 URL: https://issues.apache.org/jira/browse/GERONIMO-3314 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Environment: WindowsXP Reporter: Daniel Larsen Priority: Trivial Attachments: geronimo-3314.patch The Welcome portlet has an error in the way it renders the Common Console Actions table -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3314) The Welcome portlet has an error in the way it renders the Common Console Actions table
[ https://issues.apache.org/jira/browse/GERONIMO-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Larsen updated GERONIMO-3314: Attachment: (was: geronimo-3314.patch) The Welcome portlet has an error in the way it renders the Common Console Actions table --- Key: GERONIMO-3314 URL: https://issues.apache.org/jira/browse/GERONIMO-3314 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Environment: WindowsXP Reporter: Daniel Larsen Priority: Trivial The Welcome portlet has an error in the way it renders the Common Console Actions table -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3314) The Welcome portlet has an error in the way it renders the Common Console Actions table
[ https://issues.apache.org/jira/browse/GERONIMO-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Larsen updated GERONIMO-3314: Attachment: geronimo-3314.patch The Welcome portlet has an error in the way it renders the Common Console Actions table --- Key: GERONIMO-3314 URL: https://issues.apache.org/jira/browse/GERONIMO-3314 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Environment: WindowsXP Reporter: Daniel Larsen Priority: Trivial Attachments: geronimo-3314.patch The Welcome portlet has an error in the way it renders the Common Console Actions table -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3314) The Welcome portlet has an error in the way it renders the Common Console Actions table
[ https://issues.apache.org/jira/browse/GERONIMO-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512203 ] Daniel Larsen commented on GERONIMO-3314: - This is a patch for sandbox/portals. (Sorry for the multiple posts, this is my first patch) The Welcome portlet has an error in the way it renders the Common Console Actions table --- Key: GERONIMO-3314 URL: https://issues.apache.org/jira/browse/GERONIMO-3314 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Environment: WindowsXP Reporter: Daniel Larsen Priority: Trivial Attachments: geronimo-3314.patch The Welcome portlet has an error in the way it renders the Common Console Actions table -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2373) build broken with the removal of geronimo-j2ee_1.4_spec from the specs
[ https://issues.apache.org/jira/browse/GERONIMO-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512211 ] Kevan Miller commented on GERONIMO-2373: Patches are applied to source code using the 'patch' command. So, you need to have Geronimo source checked out and be able to build Geronimo. http://cwiki.apache.org/GMOxDEV/committing-patches-to-the-subversion-repository.html has a little information about applying patches... I can't think of a reason why you'd need to apply this particular patch. It's already been applied to Geronimo... build broken with the removal of geronimo-j2ee_1.4_spec from the specs -- Key: GERONIMO-2373 URL: https://issues.apache.org/jira/browse/GERONIMO-2373 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: buildsystem Affects Versions: 1.2 Reporter: Bill Dudney Assignee: Jason Dillon Fix For: 1.2 Attachments: GERONIMO-2373.bdudney.patch a couple of configs and applications have dependencies that are not correct as a result of the removal of geronimo-j2ee_1.4_spec. The attached patch addes the necessary dependencies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
3rd party integration with the Geronimo web admin console
I had a discussion on IRC #geronimo about this, and it was suggested that I post to the G dev list to continue the discussion: The Goal: To put a GUI front end on a downloadable 3rd party Geronimo plugin, preferably in the adminstration console where administrative security is already handled and configuration of components is natural. As far as I can gather, right now I would have to have my plugin modify the portlet configuration files directly and force a console reload on startup for this to happen, but I have also only been looking at the 1.1 code line so far. From the IRC discussion: I chatted briefly with kevan and jgenender about this, and they suggested that instead of using 1.1 I focus on the 2.0 line since there was work being done in the area of the administration console. There seemed to be some minor discord about where exactly this new code lives (sandbox vs. trunk) and when exactly it will be released (2.0 or later). For my part, I'm interested to know what/where this new code is (and when it will be released is always good too), and what I will need to do as the plugin writer to integrate my portlet (or something other than a portlet?) into the new and improved console. Any help or pointers to the code are much appreciated. Thanks, Nat Harward P.S. -- for those interested this is for a plugin for Terracotta clustering for Geronimo.
Re: [VOTE] Release specs for Activation and StAX - rc2
+1 Regards, Alan On Jul 10, 2007, at 6:30 AM, Prasad Kashyap wrote: The activation and stax specs had almost passed the vote the first time around. It got dinged on missing scm section in the poms. I have fixed it now and am resubmitting them for a vote. Please review the specifications located at http://people.apache.org/~prasad/specs_rc2/ Voting concludes on Monday, July 13th at 1000 ET. The other outstanding specs (depending on servlet) that would be released together are servlet_2.5_spec-1.1 jsp_2.1_spec-1.0 jacc_1.1_spec-1.0 Cheers Prasad
[jira] Created: (GERONIMO-3315) Export Plugin functionality broken in sandbox/portals console
Export Plugin functionality broken in sandbox/portals console - Key: GERONIMO-3315 URL: https://issues.apache.org/jira/browse/GERONIMO-3315 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Environment: WindowsXP Reporter: Becky Smith Priority: Minor Export Plugin button on confirmExport.jsp doesn't work - error looking for /console/forwards/car-export -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2757) Enhance plugin schema to allow for multiple versions of a plugin
[ https://issues.apache.org/jira/browse/GERONIMO-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner updated GERONIMO-2757: --- Attachment: Geronimo-2757ExportSimplified.patch I attached another patch that accomplishes the same goal as the previous patch for the export functionality. This time, though, the UI is greatly simplified. This results in more simplified functionality for the geronimo-plugin.xml in that only one version can be specified. Enhance plugin schema to allow for multiple versions of a plugin Key: GERONIMO-2757 URL: https://issues.apache.org/jira/browse/GERONIMO-2757 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.0-M5 Reporter: Paul McMahan Assignee: Jason Warner Fix For: 2.0-M7 Attachments: geronimo-2757.patch, Geronimo-2757.patch, Geronimo-2757.patch, Geronimo-2757Export.patch, Geronimo-2757ExportSimplified.patch, Geronimo-2757Update.patch plugins-1.1.xsd currently allows for a single version of a plugin to be described from within a plugin element. For example, if there were a different version of plugin for each version of geronimo then the plugin catalog would like something like: plugin module-idorg.apache.geronimo.configs/ca-helper-tomcat/1.1/car/module-id geronimo-version1.1/geronimo-version source-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.1/source-repository [...] /plugin plugin module-idorg.apache.geronimo.configs/ca-helper-tomcat/1.2/car/module-id geronimo-version1.2/geronimo-version source-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.2/source-repository [...] /plugin plugin module-idorg.apache.geronimo.configs/ca-helper-tomcat/2.0/car/module-id geronimo-version2.0/geronimo-version source-repositoryhttp://geronimo.apache.org/plugins/geronimo-2.0/source-repository [...] /plugin default-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.1/default-repository default-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.2/default-repository default-repositoryhttp://geronimo.apache.org/plugins/geronimo-2.0/default-repository Plugins are usually not compatible across versions of Geronimo for various reasons, probably the most prominent of which is Geronimo's reliance on serialized java objects in CAR files. Browsing a catalog that contains a plugin element for each version of Geronimo's plugins from the admin console or from the CLI would be confusing because of the many (seemingly redundant) entries. Therefore the collection of Geronimo plugins is distributed across a set of catalogs, one per version of Geronimo, and each version of Geronimo points at a version specific plugin catalog. Modifying the plugin schema so that a plugin element can allow the plugin's module-id and source-repository to depend on the geronimo-version would allow there to be much fewer entries in a consolidated plugin catalog. A plugin catalog that is created using this modified schema might look something like (this is just a sample) : plugin geronimo-version version=1.1 module-idorg.apache.geronimo.configs/ca-helper-tomcat/1.1/car/module-id source-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.1/source-repository /geronimo-version geronimo-version version=1.2 module-idorg.apache.geronimo.configs/ca-helper-tomcat/1.2/car/module-id source-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.2/source-repository /geronimo-version geronimo-version version=2.0 module-idorg.apache.geronimo.configs/ca-helper-tomcat/2.0/car/module-id source-repositoryhttp://geronimo.apache.org/plugins/geronimo-2.0/source-repository /geronimo-version [...] /plugin Also, for this to work a customized list of prerequisite elements would probably have to be supported inside the geronimo-version element as well, since those might also be version specific. Once this improvement is in place it will be easier to maintain Geronimo's plugin collection since each version of Geronimo won't require a separate catalog. Also it will be easier for end users and other external sources to refer to Geronimo's plugin catalog since the repository URL will no longer be version specific. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3306) JMS Objects being bound at an incorrect spot in the JNDI tree.
[
https://issues.apache.org/jira/browse/GERONIMO-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-3306.
--
Resolution: Fixed
Fix Version/s: 2.0-M7
Assignee: David Jencks (was: Tim McConnell)
This seems to be working fine.
JMS Objects being bound at an incorrect spot in the JNDI tree.
--
Key: GERONIMO-3306
URL: https://issues.apache.org/jira/browse/GERONIMO-3306
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0-M7
Environment: All
Reporter: Matt Hogstrom
Assignee: David Jencks
Fix For: 2.0-M7
DayTrader 2.0 uses a Session Bean that acts as a focal point for many
application operations. This bean does a lookup of several resources in the
setSessionContext method. This method looks up the following resources. The
first line is line 1034 from TradeBean.java. Note that the jms/ resource are
successfully looked up but that the items on line 1056 and 1057 needs to have
geronimo inserted into the name in order for the resolution to be successful.
{code}
*1034* public void ejbCreate() throws CreateException {
*1035*try {
*1036*
*1037*if (Log.doTrace())
*1038*Log.trace(TradeBean:ejbCreate -- JNDI
lookups of EJB and JMS resources);
*1039*
*1040*InitialContext ic = new InitialContext();
*1041*quoteHome = (LocalQuoteHome)
ic.lookup(java:comp/env/ejb/Quote);
*1042*accountHome = (LocalAccountHome)
ic.lookup(java:comp/env/ejb/Account);
*1043*profileHome = (LocalAccountProfileHome)
ic.lookup(java:comp/env/ejb/AccountProfile);
*1044*holdingHome = (LocalHoldingHome)
ic.lookup(java:comp/env/ejb/Holding);
*1045*orderHome = (LocalOrderHome)
ic.lookup(java:comp/env/ejb/Order);
*1046*keySequenceHome = (LocalKeySequenceHome)
ic.lookup(java:comp/env/ejb/KeySequence);
*1047*
*1048*orderBySQLSupported = ( (Boolean)
ic.lookup(java:comp/env/orderBySQLSupported) ).booleanValue();
*1049*updateQuotePrices = ( (Boolean)
ic.lookup(java:comp/env/updateQuotePrices) ).booleanValue();
*1050*
TradeConfig.setUpdateQuotePrices(updateQuotePrices);
*1051*
*1052*try
*1053*{
*1054*qConnFactory = (ConnectionFactory)
ic.lookup(java:comp/env/jms/QueueConnectionFactory);
*1055* tConnFactory = (ConnectionFactory)
ic.lookup(java:comp/env/jms/TopicConnectionFactory);
*1056*streamerTopic = (Topic)
ic.lookup(java:comp/geronimo/env/jms/TradeStreamerTopic);
*1057*brokerQueue = (Queue)
ic.lookup(java:comp/geronimo/env/jms/TradeBrokerQueue);
{code}
Now, looking at the streamerTopic and brokerQueue definitions we also have
annotations which have the desired (correct?) names defined. However, when
the bean is initialized we receive the following warnings:
{code}
*46* @Resource(name = jms/TradeBrokerQueue)
*47* private Queue brokerQueue = null;
*48*
*49* private ConnectionFactory tConnFactory = null;
*50*
*51* @Resource(name = jms/TradeStreamerTopic)
*52* private Topic streamerTopic = null;
{code}
12:24:37,117 WARN [OpenEJB] Injection data not found in enc:
jndiName='jms/TradeBrokerQueue', target=class
org.apache.geronimo.samples.daytrader.ejb.TradeBean/brokerQueue
12:24:37,118 WARN [OpenEJB] Injection data not found in enc:
jndiName='jms/TradeStreamerTopic', target=class
org.apache.geronimo.samples.daytrader.ejb.TradeBean/streamerTopic
So, the other resources outlined above (like the ConnectionFactories) seem to
be bound correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3305) Out Of Memory Error when Running DayTrader in WebServices Mode
[
https://issues.apache.org/jira/browse/GERONIMO-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512240
]
David Jencks commented on GERONIMO-3305:
I saw these by just redeploying daytrader a couple times with, IIRC, not doing
any work in daytrader.
Out Of Memory Error when Running DayTrader in WebServices Mode
--
Key: GERONIMO-3305
URL: https://issues.apache.org/jira/browse/GERONIMO-3305
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0-M7
Environment: All
Reporter: Matt Hogstrom
Assignee: Kevan Miller
I deployed DayTrader 2.0 on the latest SVN rev 554753 of trunk.
I deploy daytrader-ear-2.0-SNAPSHOT.ear (using the
daytrader-g-2.0-SNAPSHOT-plan.xml in ${DT}/trunk/plans
Create the tables and populate them in the config section.
Switch to WebServices mode
Log in and do portfolio, quotes, buy and sell a few stocks and then logoff.
Try to log in again and I get:
10:34:34,089 ERROR [Log] Error: JSR 109 lookup failed .. defaulting to JSR 101
javax.naming.NamingException: Could not look up : service/Trade [Root
exception is net.sf.cglib.core.CodeGenerationException:
java.lang.reflect.InvocationTargetException--null]
javax.naming.NamingException: Could not look up : service/Trade [Root
exception is net.sf.cglib.core.CodeGenerationException:
java.lang.reflect.InvocationTargetException--null]
at
org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:65)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:112)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:597)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at
org.apache.geronimo.samples.daytrader.soap.TradeWebSoapProxy.getPortFromFactory(TradeWebSoapProxy.java:67)
at
org.apache.geronimo.samples.daytrader.soap.TradeWebSoapProxy.getTrade(TradeWebSoapProxy.java:47)
at
org.apache.geronimo.samples.daytrader.soap.TradeWebSoapProxy.getAccountData(TradeWebSoapProxy.java:122)
at
org.apache.geronimo.samples.daytrader.web.TradeServletAction.doHome(TradeServletAction.java:277)
at
org.apache.geronimo.samples.daytrader.web.TradeServletAction.doLogin(TradeServletAction.java:372)
at
org.apache.geronimo.samples.daytrader.web.TradeAppServlet.performTask(TradeAppServlet.java:126)
at
org.apache.geronimo.samples.daytrader.web.TradeAppServlet.doPost(TradeAppServlet.java:91)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.geronimo.samples.daytrader.web.OrdersAlertFilter.doFilter(OrdersAlertFilter.java:91)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56)
at
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:351)
at
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
[jira] Created: (GERONIMO-3316) warn but don't prevent deployment if an ear's manifest cps are messed up, and provide more info on where.
warn but don't prevent deployment if an ear's manifest cps are messed up, and provide more info on where. - Key: GERONIMO-3316 URL: https://issues.apache.org/jira/browse/GERONIMO-3316 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: deployment Affects Versions: 2.0-M6 Reporter: David Jencks Assignee: David Jencks Fix For: 2.0-M7 DeploymentContext.getCompleteManifestClassPath figures out the whole set of jars in an ear in a modules classpath. If somethings missing it throws an exception and prevents deployment. We need a switch to be more lenient, and we need to provide more info when there's a problem on which jar has the problem and how we found it. Thanks to David Harbige on the user list for pointing out that this is a big usability problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release specs for Activation and StAX - rc2
+1 Joe Prasad Kashyap wrote: The activation and stax specs had almost passed the vote the first time around. It got dinged on missing scm section in the poms. I have fixed it now and am resubmitting them for a vote. Please review the specifications located at http://people.apache.org/~prasad/specs_rc2/ Voting concludes on Monday, July 13th at 1000 ET. The other outstanding specs (depending on servlet) that would be released together are servlet_2.5_spec-1.1 jsp_2.1_spec-1.0 jacc_1.1_spec-1.0 Cheers Prasad
[jira] Commented: (GERONIMO-3305) Out Of Memory Error when Running DayTrader in WebServices Mode
[
https://issues.apache.org/jira/browse/GERONIMO-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512251
]
Kevan Miller commented on GERONIMO-3305:
I think that will turn out to be a different issue (if it turns out to be a
problem). Matt's scenario is showing a Class memory leak. It looks like we're
attempting to generate an infinite number of Classes.
Deploy/Undeploy memory leak would be a ClassLoader memory leak. Where we aren't
able to GC ClassLoaders. I haven't tested for this, yet, but will...
After a single deploy of Daytrader our permgen utilization is close to 60 megs
(near the default max). So, it wouldn't take much to bump us over the max...
Out Of Memory Error when Running DayTrader in WebServices Mode
--
Key: GERONIMO-3305
URL: https://issues.apache.org/jira/browse/GERONIMO-3305
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0-M7
Environment: All
Reporter: Matt Hogstrom
Assignee: Kevan Miller
I deployed DayTrader 2.0 on the latest SVN rev 554753 of trunk.
I deploy daytrader-ear-2.0-SNAPSHOT.ear (using the
daytrader-g-2.0-SNAPSHOT-plan.xml in ${DT}/trunk/plans
Create the tables and populate them in the config section.
Switch to WebServices mode
Log in and do portfolio, quotes, buy and sell a few stocks and then logoff.
Try to log in again and I get:
10:34:34,089 ERROR [Log] Error: JSR 109 lookup failed .. defaulting to JSR 101
javax.naming.NamingException: Could not look up : service/Trade [Root
exception is net.sf.cglib.core.CodeGenerationException:
java.lang.reflect.InvocationTargetException--null]
javax.naming.NamingException: Could not look up : service/Trade [Root
exception is net.sf.cglib.core.CodeGenerationException:
java.lang.reflect.InvocationTargetException--null]
at
org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:65)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:112)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:597)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at
org.apache.geronimo.samples.daytrader.soap.TradeWebSoapProxy.getPortFromFactory(TradeWebSoapProxy.java:67)
at
org.apache.geronimo.samples.daytrader.soap.TradeWebSoapProxy.getTrade(TradeWebSoapProxy.java:47)
at
org.apache.geronimo.samples.daytrader.soap.TradeWebSoapProxy.getAccountData(TradeWebSoapProxy.java:122)
at
org.apache.geronimo.samples.daytrader.web.TradeServletAction.doHome(TradeServletAction.java:277)
at
org.apache.geronimo.samples.daytrader.web.TradeServletAction.doLogin(TradeServletAction.java:372)
at
org.apache.geronimo.samples.daytrader.web.TradeAppServlet.performTask(TradeAppServlet.java:126)
at
org.apache.geronimo.samples.daytrader.web.TradeAppServlet.doPost(TradeAppServlet.java:91)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.geronimo.samples.daytrader.web.OrdersAlertFilter.doFilter(OrdersAlertFilter.java:91)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56)
at
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:351)
at
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
[jira] Commented: (GERONIMO-2757) Enhance plugin schema to allow for multiple versions of a plugin
[ https://issues.apache.org/jira/browse/GERONIMO-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512258 ] Paul McMahan commented on GERONIMO-2757: Thanks for the patch Jason! committed in rev 555767.I think the last remaining test is to try out the new schema with the geronimo-2.0 plugin catalog. I will try that and post any followup questions here. Enhance plugin schema to allow for multiple versions of a plugin Key: GERONIMO-2757 URL: https://issues.apache.org/jira/browse/GERONIMO-2757 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.0-M5 Reporter: Paul McMahan Assignee: Jason Warner Fix For: 2.0-M7 Attachments: geronimo-2757.patch, Geronimo-2757.patch, Geronimo-2757.patch, Geronimo-2757Export.patch, Geronimo-2757ExportSimplified.patch, Geronimo-2757Update.patch plugins-1.1.xsd currently allows for a single version of a plugin to be described from within a plugin element. For example, if there were a different version of plugin for each version of geronimo then the plugin catalog would like something like: plugin module-idorg.apache.geronimo.configs/ca-helper-tomcat/1.1/car/module-id geronimo-version1.1/geronimo-version source-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.1/source-repository [...] /plugin plugin module-idorg.apache.geronimo.configs/ca-helper-tomcat/1.2/car/module-id geronimo-version1.2/geronimo-version source-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.2/source-repository [...] /plugin plugin module-idorg.apache.geronimo.configs/ca-helper-tomcat/2.0/car/module-id geronimo-version2.0/geronimo-version source-repositoryhttp://geronimo.apache.org/plugins/geronimo-2.0/source-repository [...] /plugin default-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.1/default-repository default-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.2/default-repository default-repositoryhttp://geronimo.apache.org/plugins/geronimo-2.0/default-repository Plugins are usually not compatible across versions of Geronimo for various reasons, probably the most prominent of which is Geronimo's reliance on serialized java objects in CAR files. Browsing a catalog that contains a plugin element for each version of Geronimo's plugins from the admin console or from the CLI would be confusing because of the many (seemingly redundant) entries. Therefore the collection of Geronimo plugins is distributed across a set of catalogs, one per version of Geronimo, and each version of Geronimo points at a version specific plugin catalog. Modifying the plugin schema so that a plugin element can allow the plugin's module-id and source-repository to depend on the geronimo-version would allow there to be much fewer entries in a consolidated plugin catalog. A plugin catalog that is created using this modified schema might look something like (this is just a sample) : plugin geronimo-version version=1.1 module-idorg.apache.geronimo.configs/ca-helper-tomcat/1.1/car/module-id source-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.1/source-repository /geronimo-version geronimo-version version=1.2 module-idorg.apache.geronimo.configs/ca-helper-tomcat/1.2/car/module-id source-repositoryhttp://geronimo.apache.org/plugins/geronimo-1.2/source-repository /geronimo-version geronimo-version version=2.0 module-idorg.apache.geronimo.configs/ca-helper-tomcat/2.0/car/module-id source-repositoryhttp://geronimo.apache.org/plugins/geronimo-2.0/source-repository /geronimo-version [...] /plugin Also, for this to work a customized list of prerequisite elements would probably have to be supported inside the geronimo-version element as well, since those might also be version specific. Once this improvement is in place it will be easier to maintain Geronimo's plugin collection since each version of Geronimo won't require a separate catalog. Also it will be easier for end users and other external sources to refer to Geronimo's plugin catalog since the repository URL will no longer be version specific. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: More problems exporting a plugin and importing into minimal assembly
I just checked in Jason's patch for the plugin export. You should now be able to export activemq-broker from the jee5 assembly as a plugin and import it into the minimal assembly without having to manually edit the exported geronimo-plugin.xml. Best wishes, Paul On Jul 7, 2007, at 10:49 PM, Ajay Panagariya wrote: Hi, I just checked out the current trunk, and deployed the minimal tomcat assembly. I exported it from the regular assembly and tried importing it into the minimal, here's the output of that operation (followed by my geronimo-plugin.xml file). I asked a similar question one or two days ago, and all had gone well, but that was on an older build. This install is using the latest trunk. If posting the output in geonimo.log would help, I will be happy to provide that as well. Thanks ahead of time. $ target/geronimo-tomcat6-minimal-2.0-SNAPSHOT/bin/deploy.bat install-plugin amq.car Using GERONIMO_BASE: C:\g5\target\geronimo-tomcat6-minimal-2.0- SNAPSHOT Using GERONIMO_HOME: C:\g5\target\geronimo- tomcat6-minimal-2.0- SNAPSHOT Using GERONIMO_TMPDIR: var\temp Using JRE_HOME:C:\Program Files\Java\jdk1.5.0_12\jre Checking for status every 1000ms: Searching for org.apache.geronimo.configs/system-database//car at http://geronimo.apache.org/plugins/geronimo-2.0/repository/ Downloading org.apache.geronimo.configs/system-database/2.0- SNAPSHOT/car... (9%) Downloading org.apache.derby/derby/10.2.2.0/jar... Downloading org.apache.derby/derby/10.2.2.0/jar... (4%) Downloading org.apache.derby/derby/10.2.2.0/jar... (11%) Downloading org.apache.derby/derby/10.2.2.0/jar... (19%) Downloading org.apache.derby/derby/10.2.2.0/jar... (26%) Downloading org.apache.derby/derby/10.2.2.0/jar... (34%) Downloading org.apache.derby/derby/10.2.2.0/jar... (42%) Downloading org.apache.derby/derby/10.2.2.0/jar... (48%) Downloading org.apache.derby/derby/10.2.2.0/jar... (56%) Downloading org.apache.derby/derby/10.2.2.0/jar... (64%) Downloading org.apache.derby/derby/10.2.2.0/jar... (69%) Downloading org.apache.derby/derby/10.2.2.0/jar... (75%) Downloading org.apache.derby/derby/10.2.2.0/jar... (83%) Downloading org.apache.derby/derby/10.2.2.0/jar... (90%) Downloading org.apache.derby/derby/10.2.2.0/jar... (93%) Searching for org.apache.geronimo.configs /transaction-jta11//car at http://geronimo.apache.org/plugins/geronimo-2.0/repository/ Searching for org.apache.geronimo.modules/geronimo-transaction- jta11/2.0-SNAPSHOT/jar at http://geronimo.apache.org/plugins/geroni mo-2.0/repository/ Searching for org.apache.geronimo.modules/geronimo-derby/2.0- SNAPSHOT/jar at http://geronimo.apache.org/plugins/geronimo-2.0/repos itory/ Downloading org.apache.geronimo.modules/geronimo-derby/2.0-SNAPSHOT/ jar... Downloading org.apache.derby/derbyclient/10.2.2.0/jar... Downloading org.apache.derby/derbyclient/10.2.2.0/jar... (24%) Downloading org.apache.derby/derbyclient/10.2.2.0/jar... (50%) Downloading org.apache.derby/derbyclient/10.2.2.0/jar... (71%) Searching for org.apache.geronimo.modules /geronimo-timer/2.0- SNAPSHOT/jar at http://geronimo.apache.org/plugins/geronimo-2.0/repos itory/ Downloading org.apache.geronimo.modules/geronimo-timer/2.0-SNAPSHOT/ jar... (26%) Downloading org.apache.derby/derbynet/10.2.2.0/jar... Downloading org.apache.derby/derbynet/10.2.2.0/jar... (17%) Downloading org.apache.derby/derbynet/10.2.2.0/jar... (77%) Searching for org.apache.geronimo.modules /geronimo-activemq/2.0- SNAPSHOT/jar at http://geronimo.apache.org/plugins/geronimo-2.0/re pository/ Downloading org.apache.geronimo.modules/geronimo-activemq/2.0- SNAPSHOT/jar... (25%) Searching for org.apache.geronimo.modules/geronimo-activemq- management/2.0-SNAPSHOT/jar at http://geronimo.apache.org/plugins/gero nimo-2.0/repository/ Downloading org.apache.activemq/activemq-core/4.1.1/jar... Downloading org.apache.activemq/activemq-core/4.1.1/jar... (5%) Downloading org.apache.activemq/activemq-core/4.1.1/jar... (14%) Downloading org.apache.activemq/activemq-core/4.1.1/jar... (25%) Downloading org.apache.activemq/activemq-core/4.1.1/jar... (35%) Downloading org.apache.activemq/activemq-core/4.1.1/jar... (45%) Downloading org.apache.activemq/activemq-core/4.1.1/jar... (55%) Downloading org.apache.activemq /activemq-core/4.1.1/jar... (61%) Downloading org.apache.activemq/activemq-core/4.1.1/jar... (69%) Downloading org.apache.activemq/activemq-core/4.1.1/jar... (77%) Downloading org.apache.activemq/activemq-core/4.1.1/jar... (83%) Downloading org.apache.activemq/activemq-core/4.1.1/jar... (91%) Downloading org.apache.activemq/activeio-core/3.0.0-incubator/jar... Downloading org.apache.activemq/activeio-core/3.0.0-incubator/ jar... (10%) Downloading backport-util-concurrent/backport-util-concurrent/2.2/ jar... Downloading backport-util-concurrent/backport-util-concurrent/2.2/ jar... (20%) Downloading backport-util-concurrent/backport-util-concurrent/2.2/ jar... (61%) Downloading
Re: SNAPSHOT dependencies that need to be released.
Similar to Scout, can Yoko at least release a 1.0-rc1 for us in time ? Cheers Prasad On 7/12/07, Rick McGuire [EMAIL PROTECTED] wrote: I'll raise the issue on the Yoko dev list. Last time, this took a long time to get done because the discussions on how the release should be bundled and whether the tools were ready for release or not. I'm not sure of the status of the tools, as the people who've been working on them have not been very good about doing the work on list. It might be necessary to spin an M3 release of just the run time like the last time Geronimo needed a release. This is further complicated by the project incubating status, since it requires two levels of voting to get released. Rick Prasad Kashyap wrote: The following Geronimo dependencies uses SNAPSHOT versions. Can we please chase these projects and get them to release the artifacts, whatever it takes; contacts, muscles, bribes, favors, etc :-) If enough people on this list volunteer to get some of these released, then I'll create a wiki page where they can sign up. openejbVersion3.0-incubating-SNAPSHOT/openejbVersion groupIdorg.apache.cxf/groupId artifactIdcxf-api/artifactId version2.0-incubator-SNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-java2wsdl/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-kernel/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-adb/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-jaxws-api/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-jaxws/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-metadata/artifactId versionSNAPSHOT/version groupIdorg.apache.axis2/groupId artifactIdaxis2-saaj/artifactId versionSNAPSHOT/version groupIdorg.apache.geronimo.javamail/groupId artifactIdgeronimo-javamail_1.4_mail/artifactId version1.1-SNAPSHOT/version groupIdorg.apache.geronimo.schema/groupId artifactIdgeronimo-schema-jee_5/artifactId version1.1-SNAPSHOT/version groupIdorg.apache.geronimo.schema/groupId artifactIdgeronimo-schema-j2ee_1.4/artifactId version1.1-SNAPSHOT/version groupIdorg.apache.openjpa/groupId artifactIdopenjpa/artifactId version1.0.0-SNAPSHOT/version groupIdorg.apache.xbean/groupId artifactIdxbean-finder/artifactId version3.0-SNAPSHOT/version groupIdorg.apache.xbean/groupId artifactIdxbean-naming/artifactId version3.0-SNAPSHOT/version groupIdorg.apache.xbean/groupId artifactIdxbean-reflect/artifactId version3.1-SNAPSHOT/version groupIdorg.apache.ws.scout/groupId artifactIdscout/artifactId versionSNAPSHOT/version groupIdorg.apache.yoko/groupId artifactIdyoko-core/artifactId version1.0-incubating-SNAPSHOT/version groupIdorg.apache.yoko/groupId artifactIdyoko-spec-corba/artifactId version1.0-incubating-SNAPSHOT/version groupIdorg.apache.yoko/groupId artifactIdyoko-rmi-spec/artifactId version1.0-incubating-SNAPSHOT/version groupIdorg.apache.yoko/groupId artifactIdyoko-rmi-impl/artifactId version1.0-incubating-SNAPSHOT/version groupIdorg.mortbay.jetty/groupId artifactIdjetty/artifactId version6.1-SNAPSHOT/version groupIdorg.mortbay.jetty/groupId artifactIdjetty-ajp/artifactId version6.1-SNAPSHOT/version groupIdorg.mortbay.jetty/groupId artifactIdjetty-sslengine/artifactId version6.1-SNAPSHOT/version groupIdorg.mortbay.jetty/groupId artifactIdjetty-util/artifactId version6.1-SNAPSHOT/version groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-api/artifactId version1.2.0-SNAPSHOT/version groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-impl/artifactId version1.2.0-SNAPSHOT/version Cheers Prasad
[jira] Closed: (GERONIMO-3311) Security Realms portlet is broken. Unable to edit realm.
[ https://issues.apache.org/jira/browse/GERONIMO-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-3311. -- Resolution: Fixed I think it's fixed in rev 555771. I seem to be able to create a new security realm with the console. Security Realms portlet is broken. Unable to edit realm. - Key: GERONIMO-3311 URL: https://issues.apache.org/jira/browse/GERONIMO-3311 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 2.0-M7 Reporter: Vamsavardhana Reddy Assignee: David Jencks Fix For: 2.0-M7 Security Realms portlet is broken. I guess the problem is introduced by recent changes for GERONIMO-3303 Simplify security authentication framework by removing mixed local/remote logins. When I click on edit link, the following exception is logged. 16:23:37,613 ERROR [edit_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.realmwizard.edit_jsp threw exception javax.el.PropertyNotFoundException: Property 'serverSide' not found on type org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet$LoginModuleDetails at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) at javax.el.BeanELResolver.property(BeanELResolver.java:279) at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at org.apache.el.parser.AstValue.getValue(AstValue.java:97) at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:923) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspx_meth_c_005fif_005f6(edit_jsp.java:850) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspx_meth_c_005fforEach_005f2(edit_jsp.java:586) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspService(edit_jsp.java:146) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.pluto.core.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:65) at org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.renderEdit(SecurityRealmPortlet.java:585) at org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.doView(SecurityRealmPortlet.java:260) 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(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.render(PortletInvokerImpl.java:73) at org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:119) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.renderPortlet(PortletContainerWrapperImpl.java:70) at org.apache.pluto.portalImpl.aggregation.PortletFragment.service(PortletFragment.java:168) at jsp.WEB_002dINF.aggregation.ColumnFragment_jsp._jspService(ColumnFragment_jsp.java:70) at
[jira] Commented: (GERONIMO-3314) The Welcome portlet has an error in the way it renders the Common Console Actions table
[ https://issues.apache.org/jira/browse/GERONIMO-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512263 ] Paul McMahan commented on GERONIMO-3314: was this patch intended to fix the links or just move them? clicking them returns a 404 The Welcome portlet has an error in the way it renders the Common Console Actions table --- Key: GERONIMO-3314 URL: https://issues.apache.org/jira/browse/GERONIMO-3314 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Environment: WindowsXP Reporter: Daniel Larsen Priority: Trivial Attachments: geronimo-3314.patch The Welcome portlet has an error in the way it renders the Common Console Actions table -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (GERONIMO-3314) The Welcome portlet has an error in the way it renders the Common Console Actions table
Heh, wow. I was just fixing the way they looked. I didn't even realize that they were broken links! I'll see if I can figure out why. On 7/12/07, Paul McMahan (JIRA) [EMAIL PROTECTED] wrote: [ https://issues.apache.org/jira/browse/GERONIMO-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512263] Paul McMahan commented on GERONIMO-3314: was this patch intended to fix the links or just move them? clicking them returns a 404 The Welcome portlet has an error in the way it renders the Common Console Actions table --- Key: GERONIMO-3314 URL: https://issues.apache.org/jira/browse/GERONIMO-3314 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Environment: WindowsXP Reporter: Daniel Larsen Priority: Trivial Attachments: geronimo-3314.patch The Welcome portlet has an error in the way it renders the Common Console Actions table -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3315) Export Plugin functionality broken in sandbox/portals console
[ https://issues.apache.org/jira/browse/GERONIMO-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan resolved GERONIMO-3315. Resolution: Fixed Assignee: Paul McMahan fixed in rev 555784. thanks for the patch Becky. also merged GERONIMO-2757 from trunk Export Plugin functionality broken in sandbox/portals console - Key: GERONIMO-3315 URL: https://issues.apache.org/jira/browse/GERONIMO-3315 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Environment: WindowsXP Reporter: Becky Smith Assignee: Paul McMahan Priority: Minor Attachments: geronimo-3315.patch Export Plugin button on confirmExport.jsp doesn't work - error looking for /console/forwards/car-export -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3304) ability to update openejb-jar.xml by examining annotations
[ https://issues.apache.org/jira/browse/GERONIMO-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512277 ] Paul McMahan commented on GERONIMO-3304: is your src current? when I try to apply the patch I get: patching file plugins/org.apache.geronimo.j2g.descriptors/src/org/apache/geronimo/j2g/descriptors/ejb/annotation/AnnotationTool.java Hunk #2 FAILED at 39. Hunk #3 succeeded at 63 (offset 1 line). 1 out of 3 hunks FAILED -- saving rejects to file plugins/org.apache.geronimo.j2g.descriptors/src/org/apache/geronimo/j2g/descriptors/ejb/annotation/AnnotationTool.java.rej patching file plugins/org.apache.geronimo.j2g.descriptors/src/org/apache/geronimo/j2g/descriptors/ejb/EJBDescriptorTool.java Hunk #1 succeeded at 82 (offset -9 lines). ability to update openejb-jar.xml by examining annotations -- Key: GERONIMO-3304 URL: https://issues.apache.org/jira/browse/GERONIMO-3304 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: J2G Environment: windows xp, linux Reporter: Viet Hung Nguyen Attachments: geronimo-3304-2.patch, geronimo-3304-3.patch, geronimo-3304.patch As of now, when there is a jboss.xml in a JBoss project, the geronimo equivalent is written to openejb-jar.xml. However, that only covers EJB 2.1's features. We need a way to update the openejb-jar.xml by looking at the annotations because there is still some configuring left to do. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Reminder - Board Report Updates
Please take a few minutes to visit the Wiki and fill in board report which is due next week. I'll take the contents and finalize it on Monday around 1700 ET and send it to the board. Thanks for your help http://cwiki.apache.org/GMOxPMGT/apache-geronimo-board-report-2007-07- july.html
[jira] Closed: (DAYTRADER-46) Add dbscripts and deployment plans for DB2 and Oracle
[ https://issues.apache.org/jira/browse/DAYTRADER-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods closed DAYTRADER-46. - Resolution: Fixed Committed revision 555843, 555844. Also updated README and updated createDerbyDB.bat to handle spaces in the path to Java. Add dbscripts and deployment plans for DB2 and Oracle - Key: DAYTRADER-46 URL: https://issues.apache.org/jira/browse/DAYTRADER-46 Project: DayTrader Issue Type: Improvement Affects Versions: 2.0 Reporter: Donald Woods Assignee: Donald Woods Priority: Minor Fix For: 2.0 Add db scripts and deployment plans for DB2 8.2/9.1 and Oracle 10g. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DAYTRADER-46) Add dbscripts and deployment plans for DB2 and Oracle
Add dbscripts and deployment plans for DB2 and Oracle - Key: DAYTRADER-46 URL: https://issues.apache.org/jira/browse/DAYTRADER-46 Project: DayTrader Issue Type: Improvement Affects Versions: 2.0 Reporter: Donald Woods Assignee: Donald Woods Priority: Minor Fix For: 2.0 Add db scripts and deployment plans for DB2 8.2/9.1 and Oracle 10g. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3311) Security Realms portlet is broken. Unable to edit realm.
[ https://issues.apache.org/jira/browse/GERONIMO-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512361 ] David Jencks commented on GERONIMO-3311: The unit test got left out of the previous commit somehow. It's in rev 555872. Security Realms portlet is broken. Unable to edit realm. - Key: GERONIMO-3311 URL: https://issues.apache.org/jira/browse/GERONIMO-3311 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 2.0-M7 Reporter: Vamsavardhana Reddy Assignee: David Jencks Fix For: 2.0-M7 Security Realms portlet is broken. I guess the problem is introduced by recent changes for GERONIMO-3303 Simplify security authentication framework by removing mixed local/remote logins. When I click on edit link, the following exception is logged. 16:23:37,613 ERROR [edit_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.realmwizard.edit_jsp threw exception javax.el.PropertyNotFoundException: Property 'serverSide' not found on type org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet$LoginModuleDetails at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) at javax.el.BeanELResolver.property(BeanELResolver.java:279) at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at org.apache.el.parser.AstValue.getValue(AstValue.java:97) at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:923) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspx_meth_c_005fif_005f6(edit_jsp.java:850) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspx_meth_c_005fforEach_005f2(edit_jsp.java:586) at jsp.WEB_002dINF.view.realmwizard.edit_jsp._jspService(edit_jsp.java:146) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.pluto.core.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:65) at org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.renderEdit(SecurityRealmPortlet.java:585) at org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.doView(SecurityRealmPortlet.java:260) 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(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.render(PortletInvokerImpl.java:73) at org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:119) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.renderPortlet(PortletContainerWrapperImpl.java:70) at org.apache.pluto.portalImpl.aggregation.PortletFragment.service(PortletFragment.java:168) at jsp.WEB_002dINF.aggregation.ColumnFragment_jsp._jspService(ColumnFragment_jsp.java:70) at
[jira] Closed: (GERONIMO-3307) persistence units in other modules should not be picked up by PersistenceUnitDeployer called from a module
[ https://issues.apache.org/jira/browse/GERONIMO-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-3307. -- Resolution: Fixed Well, when I started writing unit tests I found a lot of problems. I think it all works now. rev 555869 and 555871. persistence units in other modules should not be picked up by PersistenceUnitDeployer called from a module -- Key: GERONIMO-3307 URL: https://issues.apache.org/jira/browse/GERONIMO-3307 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: persistence Affects Versions: 2.0-M6 Reporter: David Jencks Assignee: David Jencks Fix For: 2.0-M7 We have some code that's supposed to prevent the PersistenceUntiBuilder from finding a persistence unit in another module, but it doesn't work if the module calling the persistenceUnitBuilder is a war in an ear. For wars, we have to prepend the path to the persistence unit with ../ since the war is a directory not a jar inside the car, and that no longer matches a module path. We can do two resotutions... one against the module path, once against the ../ and check for another module against the module-path-resolved uri. This could use some unit tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [DISCUSS] Geronimo 2.0 Release Plans - Release around August 3rd - Just a thought
On Jul 12, 2007, at 9:49 AM, Jeff Genender wrote: Matt Hogstrom wrote: Based on previous e-mails I believe we are shipping the following certified releases: Tomcat - Axis 2 - OpenJPA Jetty - CXF - OpenJPA I think if we are going to ship these assemblies, we also should very clearly document how to switch between web service containers (i.e. the switch property) as there is quite a bit of religious war as to which people desire. I think that's a good idea. We could do the same with Web Containers as well, if desired... I'd like to see our release criteria settled before setting a date... --kevan
Re: Offline build failure due to missing geronimo-javamail_1.4_mail-1.2-SNAPSHOT.jar
Deleted the javamail directory from M2REPO and then ran an online build.
This time it downloaded geronimo-javamail_1.4_mail-1.2-SNAPSHOT.jar etc.
Subsequent offline builds are successful.
Vamsi
On 7/12/07, Prasad Kashyap [EMAIL PROTECTED] wrote:
If you are doing an offline build on a clean repo, you will have to
build javamail separately from it's own svn tree. It is not a part of
the Geronimo tree.
Cheers
Prasad
On 7/12/07, Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
When I do an offline build, I am getting the following build error. If
I do
an online build, the build is successful, but,
geronimo-javamail_1.4_mail-1.2-SNAPSHOT.jar is not downloaded to m2repo.
Any ideas how to fix this?
[INFO]
-
---
[INFO] Building Geronimo Configs :: JavaEE Specs
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] [enforcer:enforce {execution: default}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [car:prepare-plan]
[INFO] Generated:
C:\G\trunk\configs\jee-specs\target\plan\plan.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1)
org.apache.geronimo.javamail:geronimo-javamail_1.4_mail:jar:1.2-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.geronimo.javamail
-Dartifact
Id=geronimo-javamail_1.4_mail \
-Dversion=1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1)
org.apache.geronimo.configs:jee-specs:car:2.0-SNAPSHOT
2)
org.apache.geronimo.javamail:geronimo-javamail_1.4_mail:jar:1.2-SNAPS
HOT
--
1 required artifact is missing.
for artifact:
org.apache.geronimo.configs:jee-specs:car:2.0-SNAPSHOT
from the specified remote repositories:
central ( http://repo1.maven.org/maven2),
java.net ( http://download.java.net/maven/1/),
apache.snapshots
(http://people.apache.org/repo/m2-snapshot-repository ),
apache-snapshots
(http://people.apache.org/repo/m2-snapshot-repository ),
codehaus-snapshots (
http://snapshots.repository.codehaus.org),
apache-incubator
(http://people.apache.org/repo/m2-incubating-repository/ ),
tomcat-m2-repo (
http://tomcat.apache.org/dev/dist/m2-repository)
NOTE: Maven is executing in offline mode. Any artifacts not already in
your
loca
l
repository will be inaccessible.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 30 seconds
[INFO] Finished at: Thu Jul 12 15:57:15 IST 2007
[INFO] Final Memory: 38M/68M
[INFO]
[DISCUSS] 2.0 Release Criteria
On Jun 21, 2007, at 12:34 PM, Matt Hogstrom wrote: We've gone through the CTS grind and came out victorious http:// java.sun.com/javaee/overview/compatibility.jsp OpenEJB has moved to TopLevel and CXF has certified and Axis 2 is working that way too. All in all its been an excellent six months. So, what are we going to do for 2.0 and getting it out the door? Here are my thoughts and we can use this thread to gather everyone else's and come to a consensus. 2.0 Ship Criteria Date: mid to end of July (a target only...depends on content) Certified Assemblies Tomcat, Axis 2 and OpenJPA Jetty, CXF and OpenJPA Other assemblies would be the minimal assemblies but cert doesn't apply to them. Work on fit and finish stuff (cleaning up error messages, improving diagnostics, reducing footprint). Personally, I'd like to see the full G have a footprint of about 40MB (that's a little over 5MB larger than 1.1.1) and Minimal be around 20MB. Need to do some research on this (volunteers?) I'm not sure how the WADI clustering presents itself across the two different assemblies (Gianny, comments?) Beneficial, I think, to conclude/summarize this discussion as we move forward to finalizing release plans and dates. Since I'm introducing some potentially new categorizations, I'm not calling this a summary, yet... In release discussions, like this, I'd like to see us be a little clearer with regard to our must-haves and nice-to-haves. In that regard, the following is my evaluation of the criteria that we've been discussing: Must-Haves 1. Certification. For M6 we certified a Tomcat/CXF configuration of Geronimo. We'd like to certify 2.0 using Jetty and Axis2, also. What configuration combinations *must* be certified? Is a single certified configuration sufficient? Or do we want to certify with multiple configurations? In an ideal world, I think we'd certify all 4 combinations of Web Container and Web Services implementations. What's our must have set? From discussions to date, it seems to be Tomcat/Axis2 and Jetty/CXF. However, are we willing to delay a 2.0 release until both configurations are certified? 2. Fit and Finish. The must-have list would include Release Notes, appropriately licensed source files, and up-to-date license and notice files. Other Fit-and-Finish items have been proposed. All are good ideas. However, in my book, they fall into the nice-to- have category and are included below. I'd like to be careful with this category. Otherwise, we end up with an always shifting target 3. Additional Features. With Gianni's latest WADI updates, I believe that people are happy with the current set of functionality. Now would be a really good time to voice any disagreements. ;-) This also implies that we should be careful about starting new function development on trunk. Also begs the question of when we move 2.0 off of trunk and into a branch... I know some people are holding off new function until 2.0 has been branched. 4. Bug Fixes. Recent testing with DayTrader has identified several deployment and memory-related problems which seem to fall into the must-fix category. David J had a problem with manifest classpaths that he was fixing. If we have other must-fix bugs, we should call them out now. Naturally new must-fix problems may be raised prior to release. However, we should avoid last minute surprises. 5. Dependencies. A number of our dependencies are SNAPSHOT dependencies. Many of these projects have or are in the process of being released. Very difficult/impossible to get *all* projects lined up on a release train. Also, likely that we'll have to Geronimo specific builds of some projects (e.g. Tomcat). 6. Little-G. I don't know of much testing that's occurred of our Little-G configurations. We need to perform a basic validation of these assemblies. 7. Eclipse Plugin. This won't release concurrently with 2.0. However, we should insure that it's on target for release shortly after the server release. Nice-to-Haves 1. Fit and Finish. Reducing download and runtime size have been proposed as potential improvements. There was a fair amount of discussion regarding download size. However, I don't see much active work occurring. Improving performance is always nice... ;-) There was also discussion of removing duplicate artifacts from our assemblies (i.e. being smarter about what artifacts are being included by the maven2 war plugin and cleaning up some of our configurations) -- it would be great to see some of these issues fixed. However, IMO, it need not hold up a release. 2. Usability. There are a number of usability improvements (e.g. improved messages and diagnostics) which have been proposed. There has been progress in this area already. My sense is we're ready to go with what we've got. We can make incremental improvements, of course. However, I don't see a complete
