[jira] Created: (GERONIMO-5271) Classes in the activemq-broker should not be exposed to applications deployed in Geronimo
Classes in the activemq-broker should not be exposed to applications deployed
in Geronimo
--
Key: GERONIMO-5271
URL: https://issues.apache.org/jira/browse/GERONIMO-5271
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: ActiveMQ
Affects Versions: 2.2
Reporter: Bruce Snyder
In the process of deploying a web application in Geronimo that makes use of the
activemq-broker Geronimo plugin, I had to use the {{}} element
in the geronimo-web.xml to prevent the Spring jars in the activemq-broker being
exposed to the web application. This should not be a requirement as the
activemq-broker should not expose any of its dependencies to applications
deployed in Geronimo. Geronimo should just hide all of the activemq-broker
dependencies from leaking into the web app classloader by default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5254) The ActiveMQ XML configuration is incorrect regarding memoryUsage limit
The ActiveMQ XML configuration is incorrect regarding memoryUsage limit Key: GERONIMO-5254 URL: https://issues.apache.org/jira/browse/GERONIMO-5254 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: ActiveMQ Affects Versions: 2.2 Reporter: Bruce Snyder The default ActiveMQ XML configuration in Geronimo 2.2 is incorrect because it limits the amount of memory available to the entire broker to 20mb while both queues and topics are limited to 128mb each. This is obviously a conflict and will cause an issue with ActiveMQ. The solution is to raise the memoryUsage limit to accommodate the limits on the queues and topics. Because queues are limited to 128mb and topics are limited to 128mb (a total of 256mb), and the broker still needs enough memory to do its job, the memoryUsage limit should probably be a mimimum of 384mb or perhaps even 512mb. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-1121) Remove the servicemix-bpe SE from the Apache ServiceMix distribution
[ https://issues.apache.org/activemq/browse/SM-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Snyder updated SM-1121: - Attachment: SM-1121.diff.txt Patch attached > Remove the servicemix-bpe SE from the Apache ServiceMix distribution > > > Key: SM-1121 > URL: https://issues.apache.org/activemq/browse/SM-1121 > Project: ServiceMix > Issue Type: Task > Components: servicemix-bpe >Affects Versions: 3.2 >Reporter: Bruce Snyder > Fix For: 3.2 > > Attachments: SM-1121.diff.txt > > > Since we recommend using the Apache Ode SE directly from the Ode project (see > the [servicemix-bpe > page|http://incubator.apache.org/servicemix/servicemix-bpe.html]), we should > remove the servicemix-bpe from the distribution. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1121) Remove the servicemix-bpe SE from the Apache ServiceMix distribution
Remove the servicemix-bpe SE from the Apache ServiceMix distribution Key: SM-1121 URL: https://issues.apache.org/activemq/browse/SM-1121 Project: ServiceMix Issue Type: Task Components: servicemix-bpe Affects Versions: 3.2 Reporter: Bruce Snyder Fix For: 3.2 Since we recommend using the Apache Ode SE directly from the Ode project (see the [servicemix-bpe page|http://incubator.apache.org/servicemix/servicemix-bpe.html]), we should remove the servicemix-bpe from the distribution. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-1071) Provisioning system
[ https://issues.apache.org/activemq/browse/SM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Snyder reassigned SM-1071: Assignee: Bruce Snyder > Provisioning system > --- > > Key: SM-1071 > URL: https://issues.apache.org/activemq/browse/SM-1071 > Project: ServiceMix > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Bruce Snyder > Fix For: 4.0 > > > Maybe using OBR > (http://felix.apache.org/site/apache-felix-osgi-bundle-repository-obr.html) or > Equinox (http://wiki.eclipse.org/index.php/Equinox_Provisioning). > Basically, i'm thinking about two things: > * leverage OBR to install features easily (activemq, ode, cxf, etc...) > * dynamic / automatic provisioning of applications > For the second one, a service could pull an HTTP url from time to time to > check is a new configuration for itself is available. if yes, download it > and uninstall stop / uninstall unneeded bundes, install new ones, etc... > The configuration would be a simple xml defining which bundles / version > should be started -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-555) Improving reliability of servicemix-jms - servicemix looses messages when crashing
[ https://issues.apache.org/activemq/browse/SM-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Snyder closed SM-555. --- > Improving reliability of servicemix-jms - servicemix looses messages when > crashing > --- > > Key: SM-555 > URL: https://issues.apache.org/activemq/browse/SM-555 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-jms >Affects Versions: 3.0.1 >Reporter: Klaus Alfert >Assignee: Guillaume Nodet >Priority: Critical > Fix For: 3.2 > > > ServiceMix can loose (incoming) messages during a crashing. > The test-setup is simple: one process populates a queue, servicemix reads > this queue and writes each message in a second queue, which is consumed by a > second process. During this test servicemix is killed and restarted. > My test results showed that some times some messages are lost. Looking in the > source code reveals that reading from the queue is done with an > AUTO_ACKNOWLEDGE, which implies that there is no dependency between doing an > (implicit) commit on the queue and successful sending of a message to another > JBI endpoint. Apparently, this can result in lost messages if servicemix > crashes. I could possibly use the JCAProcessor, but then I need an external > transaction manager. > I suggest to extend the servicemix-jms binding component with the > (configurable) ability to make the read of an input queue dependent on the > successful NMR send. This would add more realiability to servicemix, if > needed, payed with a (small) loss of effeciency for wating on receiving a > DONE as MessageExchange status. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-555) Improving reliability of servicemix-jms - servicemix looses messages when crashing
[
https://issues.apache.org/activemq/browse/SM-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Snyder resolved SM-555.
-
Resolution: Fixed
Fix Version/s: 3.2
Assignee: Guillaume Nodet
Fixed in SM-537 via the {{JmsConsumerEndpoint.setSessionAcknowledgeMode()}}
method.
> Improving reliability of servicemix-jms - servicemix looses messages when
> crashing
> ---
>
> Key: SM-555
> URL: https://issues.apache.org/activemq/browse/SM-555
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-jms
>Affects Versions: 3.0.1
>Reporter: Klaus Alfert
>Assignee: Guillaume Nodet
>Priority: Critical
> Fix For: 3.2
>
>
> ServiceMix can loose (incoming) messages during a crashing.
> The test-setup is simple: one process populates a queue, servicemix reads
> this queue and writes each message in a second queue, which is consumed by a
> second process. During this test servicemix is killed and restarted.
> My test results showed that some times some messages are lost. Looking in the
> source code reveals that reading from the queue is done with an
> AUTO_ACKNOWLEDGE, which implies that there is no dependency between doing an
> (implicit) commit on the queue and successful sending of a message to another
> JBI endpoint. Apparently, this can result in lost messages if servicemix
> crashes. I could possibly use the JCAProcessor, but then I need an external
> transaction manager.
> I suggest to extend the servicemix-jms binding component with the
> (configurable) ability to make the read of an input queue dependent on the
> successful NMR send. This would add more realiability to servicemix, if
> needed, payed with a (small) loss of effeciency for wating on receiving a
> DONE as MessageExchange status.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1009) Create a code formatter profile for import into Eclipse
[ https://issues.apache.org/activemq/browse/SM-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Snyder resolved SM-1009. -- Resolution: Fixed Fix Version/s: 3.2 Committed revision [559490|http://svn.apache.org/viewvc?view=rev&revision=559490]. > Create a code formatter profile for import into Eclipse > > > Key: SM-1009 > URL: https://issues.apache.org/activemq/browse/SM-1009 > Project: ServiceMix > Issue Type: Task >Affects Versions: 3.2 >Reporter: Bruce Snyder >Assignee: Bruce Snyder > Fix For: 3.2 > > Attachments: SM-1009.patch.txt > > > The new Checkstyle code convention checking is nice, but it's a major pain > when it keeps causing a build to fail. We should create a code formatter > profile for Eclipse to automatically format code according to the Checkstyle > code conventions we're using. This will prevent a lot of the issues I'm > encountering. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1009) Create a code formatter profile for import into Eclipse
[
https://issues.apache.org/activemq/browse/SM-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Snyder updated SM-1009:
-
Attachment: SM-1009.patch.txt
Attaching the patch to add the {{smx-eclipse-code-conventions.xml}} file to the
repo.
> Create a code formatter profile for import into Eclipse
>
>
> Key: SM-1009
> URL: https://issues.apache.org/activemq/browse/SM-1009
> Project: ServiceMix
> Issue Type: Task
>Affects Versions: 3.2
>Reporter: Bruce Snyder
>Assignee: Bruce Snyder
> Attachments: SM-1009.patch.txt
>
>
> The new Checkstyle code convention checking is nice, but it's a major pain
> when it keeps causing a build to fail. We should create a code formatter
> profile for Eclipse to automatically format code according to the Checkstyle
> code conventions we're using. This will prevent a lot of the issues I'm
> encountering.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-1009) Create a code formatter profile for import into Eclipse
[ https://issues.apache.org/activemq/browse/SM-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Snyder reassigned SM-1009: Assignee: Bruce Snyder > Create a code formatter profile for import into Eclipse > > > Key: SM-1009 > URL: https://issues.apache.org/activemq/browse/SM-1009 > Project: ServiceMix > Issue Type: Task >Affects Versions: 3.2 >Reporter: Bruce Snyder >Assignee: Bruce Snyder > > The new Checkstyle code convention checking is nice, but it's a major pain > when it keeps causing a build to fail. We should create a code formatter > profile for Eclipse to automatically format code according to the Checkstyle > code conventions we're using. This will prevent a lot of the issues I'm > encountering. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1009) Create a code formatter profile for import into Eclipse
Create a code formatter profile for import into Eclipse Key: SM-1009 URL: https://issues.apache.org/activemq/browse/SM-1009 Project: ServiceMix Issue Type: Task Affects Versions: 3.2 Reporter: Bruce Snyder The new Checkstyle code convention checking is nice, but it's a major pain when it keeps causing a build to fail. We should create a code formatter profile for Eclipse to automatically format code according to the Checkstyle code conventions we're using. This will prevent a lot of the issues I'm encountering. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-997) Basic example fails to build: InvalidProjectModelException
[ https://issues.apache.org/activemq/browse/SM-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Snyder updated SM-997: Fix Version/s: (was: 3.2) > Basic example fails to build: InvalidProjectModelException > -- > > Key: SM-997 > URL: https://issues.apache.org/activemq/browse/SM-997 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-assembly >Affects Versions: 3.1.1 > Environment: Servicemix 3.1.1-incubating, Windows XP, Java 1.5.0_12, > Maven 2.0.6 >Reporter: Evan Deaubl >Assignee: Bruce Snyder >Priority: Critical > > When I attempt to run either mvn install, or mvn jbi:embeddedServicemix on > the project in examples/basic, I receive the following error. I have > completely removed my Maven repository and had it redownload everything from > scratch, and still received this error. I manually checked the file it had > downloaded, and the XML file was indeed invalid, and downloading the file > directly from the source > (http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom) > using Firefox yields an XML Parsing Error. > [INFO] Scanning for projects... > Downloading: > http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/samples/3.1.1-incubating/samples-3.1.1-incubating.pom > 2K downloaded > Downloading: > http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom > 69K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '507906935d130cfa9b44696270f62e006367533d'; remote = > 'a79a1012430e34db6e471c444f0dd77c28be9d0e' - RETRYING > Downloading: > http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom > 69K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '507906935d130cfa9b44696270f62e006367533d'; remote = > 'a79a1012430e34db6e471c444f0dd77c28be9d0e' - IGNORING > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] Error building POM (may not be this project's POM). > Project ID: org.apache.servicemix:samples:pom:null > Reason: Cannot find parent: org.apache.servicemix:servicemix for project: > org.apache.servicemix:samples:pom:null > [INFO] > > [INFO] Trace > org.apache.maven.reactor.MavenExecutionException: Cannot find parent: > org.apache.servicemix:servicemix for project: > org.apache.servicemix:samples:pom:null > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find > parent: org.apache.servicemix:servicemix for project: > org.apache.servicemix:samples:pom:null > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1264) > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1281) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:749) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:479) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200) > at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:537) > at > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467) > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364) > ... 11 more > Caused by: org.apache.maven.project.
[jira] Closed: (SM-997) Basic example fails to build: InvalidProjectModelException
[ https://issues.apache.org/activemq/browse/SM-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Snyder closed SM-997. --- > Basic example fails to build: InvalidProjectModelException > -- > > Key: SM-997 > URL: https://issues.apache.org/activemq/browse/SM-997 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-assembly >Affects Versions: 3.1.1 > Environment: Servicemix 3.1.1-incubating, Windows XP, Java 1.5.0_12, > Maven 2.0.6 >Reporter: Evan Deaubl >Assignee: Bruce Snyder >Priority: Critical > > When I attempt to run either mvn install, or mvn jbi:embeddedServicemix on > the project in examples/basic, I receive the following error. I have > completely removed my Maven repository and had it redownload everything from > scratch, and still received this error. I manually checked the file it had > downloaded, and the XML file was indeed invalid, and downloading the file > directly from the source > (http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom) > using Firefox yields an XML Parsing Error. > [INFO] Scanning for projects... > Downloading: > http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/samples/3.1.1-incubating/samples-3.1.1-incubating.pom > 2K downloaded > Downloading: > http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom > 69K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '507906935d130cfa9b44696270f62e006367533d'; remote = > 'a79a1012430e34db6e471c444f0dd77c28be9d0e' - RETRYING > Downloading: > http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom > 69K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '507906935d130cfa9b44696270f62e006367533d'; remote = > 'a79a1012430e34db6e471c444f0dd77c28be9d0e' - IGNORING > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] Error building POM (may not be this project's POM). > Project ID: org.apache.servicemix:samples:pom:null > Reason: Cannot find parent: org.apache.servicemix:servicemix for project: > org.apache.servicemix:samples:pom:null > [INFO] > > [INFO] Trace > org.apache.maven.reactor.MavenExecutionException: Cannot find parent: > org.apache.servicemix:servicemix for project: > org.apache.servicemix:samples:pom:null > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find > parent: org.apache.servicemix:servicemix for project: > org.apache.servicemix:samples:pom:null > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1264) > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1281) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:749) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:479) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200) > at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:537) > at > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467) > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364) > ... 11 more > Caused by: org.apache.maven.project.InvalidProjectModelException: Parse
[jira] Resolved: (SM-997) Basic example fails to build: InvalidProjectModelException
[ https://issues.apache.org/activemq/browse/SM-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Snyder resolved SM-997. - Resolution: Fixed Fix Version/s: 3.2 I copied a valid copy of the pom directly into the repo. > Basic example fails to build: InvalidProjectModelException > -- > > Key: SM-997 > URL: https://issues.apache.org/activemq/browse/SM-997 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-assembly >Affects Versions: 3.1.1 > Environment: Servicemix 3.1.1-incubating, Windows XP, Java 1.5.0_12, > Maven 2.0.6 >Reporter: Evan Deaubl >Assignee: Bruce Snyder >Priority: Critical > Fix For: 3.2 > > > When I attempt to run either mvn install, or mvn jbi:embeddedServicemix on > the project in examples/basic, I receive the following error. I have > completely removed my Maven repository and had it redownload everything from > scratch, and still received this error. I manually checked the file it had > downloaded, and the XML file was indeed invalid, and downloading the file > directly from the source > (http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom) > using Firefox yields an XML Parsing Error. > [INFO] Scanning for projects... > Downloading: > http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/samples/3.1.1-incubating/samples-3.1.1-incubating.pom > 2K downloaded > Downloading: > http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom > 69K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '507906935d130cfa9b44696270f62e006367533d'; remote = > 'a79a1012430e34db6e471c444f0dd77c28be9d0e' - RETRYING > Downloading: > http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom > 69K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '507906935d130cfa9b44696270f62e006367533d'; remote = > 'a79a1012430e34db6e471c444f0dd77c28be9d0e' - IGNORING > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] Error building POM (may not be this project's POM). > Project ID: org.apache.servicemix:samples:pom:null > Reason: Cannot find parent: org.apache.servicemix:servicemix for project: > org.apache.servicemix:samples:pom:null > [INFO] > > [INFO] Trace > org.apache.maven.reactor.MavenExecutionException: Cannot find parent: > org.apache.servicemix:servicemix for project: > org.apache.servicemix:samples:pom:null > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find > parent: org.apache.servicemix:servicemix for project: > org.apache.servicemix:samples:pom:null > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1264) > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1281) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:749) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:479) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200) > at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:537) > at > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467) > at org.apache.maven.Defa
[jira] Commented: (SM-954) Create Binding Component for ODETTE Protocol
[ https://issues.apache.org/activemq/browse/SM-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39133 ] Bruce Snyder commented on SM-954: - If this BC is created, due to it's use of the GPL, it will have to live at the Codehaus. > Create Binding Component for ODETTE Protocol > > > Key: SM-954 > URL: https://issues.apache.org/activemq/browse/SM-954 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-components >Reporter: George Gastaldi >Priority: Minor > > Create A binding component for the OFTP (ODETTE) protocol. > It is a standard used by big automobile companies. > The ODETTEJ (http://odettej.objectweb.org/) might be a great library to > start it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-914) Exception upon generating a dot file from the apache-servicemix-web distribution in Tomcat
[
https://issues.apache.org/activemq/browse/SM-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38956
]
Bruce Snyder commented on SM-914:
-
Oh so the exception _java.io.IOException: dot: not found_ is actually
ServiceMix looking for the GraphViz executable?
> Exception upon generating a dot file from the apache-servicemix-web
> distribution in Tomcat
> ---
>
> Key: SM-914
> URL: https://issues.apache.org/activemq/browse/SM-914
> Project: ServiceMix
> Issue Type: Bug
>Affects Versions: 3.1
> Environment: MacOS X 10.4.8/Tomcat 5.5.20
>Reporter: Bruce Snyder
>
> Upon deploying the {{apache-servicemix-web-3.1-incubating.war}} file in
> Tomcat 5.5.20 and clicking on the 'View' link in the ServiceMix console, the
> following exception is thrown:
> {code}
> WARN - [dispatcher] - Servlet.service() for servlet
> dispatcher threw exception
> java.io.IOException: dot: not found
> at java.lang.UNIXProcess.forkAndExec(Native Method)
> at java.lang.UNIXProcess.(UNIXProcess.java:52)
> at java.lang.ProcessImpl.start(ProcessImpl.java:91)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
> at java.lang.Runtime.exec(Runtime.java:591)
> at java.lang.Runtime.exec(Runtime.java:429)
> at java.lang.Runtime.exec(Runtime.java:326)
> at
> org.apache.servicemix.web.view.DotView.renderMergedOutputModel(DotView.java:71)
> at
> org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:249)
> at
> org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1105)
> at
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:841)
> at
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:755)
> at
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:396)
> at
> org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:350)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at
> org.apache.servicemix.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:81)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at
> com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
> at
> com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
> at
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
> at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
> at java.lang.Thread.run(Thread.java:613)
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-914) Exception upon generating a dot file from the apache-servicemix-web distribution in Tomcat
Exception upon generating a dot file from the apache-servicemix-web
distribution in Tomcat
---
Key: SM-914
URL: https://issues.apache.org/activemq/browse/SM-914
Project: ServiceMix
Issue Type: Bug
Affects Versions: 3.1
Environment: MacOS X 10.4.8/Tomcat 5.5.20
Reporter: Bruce Snyder
Upon deploying the {{apache-servicemix-web-3.1-incubating.war}} file in Tomcat
5.5.20 and clicking on the 'View' link in the ServiceMix console, the following
exception is thrown:
{code}
WARN - [dispatcher] - Servlet.service() for servlet
dispatcher threw exception
java.io.IOException: dot: not found
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:52)
at java.lang.ProcessImpl.start(ProcessImpl.java:91)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:429)
at java.lang.Runtime.exec(Runtime.java:326)
at
org.apache.servicemix.web.view.DotView.renderMergedOutputModel(DotView.java:71)
at
org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:249)
at
org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1105)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:841)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:755)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:396)
at
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:350)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.servicemix.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:81)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
at
com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:613)
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-856) Add a marshaler to the servicemix-http component that handles Java serialization
Add a marshaler to the servicemix-http component that handles Java serialization - Key: SM-856 URL: https://issues.apache.org/activemq/browse/SM-856 Project: ServiceMix Issue Type: New Feature Components: servicemix-http Reporter: Bruce Snyder Fix For: 3.2 This will allow the Spring HTTP remoting to be used as a client to initiate requests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-854) LogService uses hard-coded path to the log4j.xml file
[
https://issues.apache.org/activemq/browse/SM-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Snyder closed SM-854.
---
Resolution: Fixed
Fix Version/s: 3.2
Patch applied:
Sendingsrc/main/java/org/apache/servicemix/jbi/logging/LogService.java
Sendingsrc/main/java/org/apache/servicemix/jbi/logging/LogTask.java
Transmitting file data ..
Committed revision 510267.
> LogService uses hard-coded path to the log4j.xml file
> --
>
> Key: SM-854
> URL: https://issues.apache.org/activemq/browse/SM-854
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
>Affects Versions: 3.1
>Reporter: Bruce Snyder
> Assigned To: Bruce Snyder
> Fix For: 3.2
>
> Attachments: SM-854.patch.txt
>
>
> The path the log4j.xml file is hard-coded to {{conf/log4j.xml}}. If
> ServiceMix is started from inside the {{bin}} directory, ServiceMix won't be
> able to locate this file and logging will not work properly. Below is the
> output from a started in the {{bin}} directory:
> {panel}
> $ ./servicemix
> servicemix: JAVA_HOME not set; results may vary
> java version "1.5.0_07"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
> Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing)
> Starting Apache ServiceMix ESB: 3.1-incubating-SNAPSHOT
> Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
> INFO - ConnectorServerFactoryBean - JMX connector available at:
> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> INFO - JBIContainer - ServiceMix 3.1-incubating-SNAPSHOT
> JBI Container (ServiceMix) is starting
> INFO - JBIContainer - For help or more informations please
> see: http://incubator.apache.org/servicemix/
> INFO - ComponentMBeanImpl - Initializing component:
> #SubscriptionManager#
> INFO - DeploymentService - Restoring service assemblies
> INFO - JBIContainer - ServiceMix JBI Container
> (ServiceMix) started
> INFO - JDBCAdapterFactory - Database driver recognized:
> [apache_derby_embedded_jdbc_driver]
> ERROR - LogTask- java.io.FileNotFoundException:
> conf/log4j.xml (No such file or directory)
> {panel}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-854) LogService uses hard-coded path to the log4j.xml file
[
https://issues.apache.org/activemq/browse/SM-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Snyder updated SM-854:
Attachment: SM-854.patch.txt
Attached a patch.
> LogService uses hard-coded path to the log4j.xml file
> --
>
> Key: SM-854
> URL: https://issues.apache.org/activemq/browse/SM-854
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
>Affects Versions: 3.1
>Reporter: Bruce Snyder
> Assigned To: Bruce Snyder
> Attachments: SM-854.patch.txt
>
>
> The path the log4j.xml file is hard-coded to {{conf/log4j.xml}}. If
> ServiceMix is started from inside the {{bin}} directory, ServiceMix won't be
> able to locate this file and logging will not work properly. Below is the
> output from a started in the {{bin}} directory:
> {panel}
> $ ./servicemix
> servicemix: JAVA_HOME not set; results may vary
> java version "1.5.0_07"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
> Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing)
> Starting Apache ServiceMix ESB: 3.1-incubating-SNAPSHOT
> Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
> INFO - ConnectorServerFactoryBean - JMX connector available at:
> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> INFO - JBIContainer - ServiceMix 3.1-incubating-SNAPSHOT
> JBI Container (ServiceMix) is starting
> INFO - JBIContainer - For help or more informations please
> see: http://incubator.apache.org/servicemix/
> INFO - ComponentMBeanImpl - Initializing component:
> #SubscriptionManager#
> INFO - DeploymentService - Restoring service assemblies
> INFO - JBIContainer - ServiceMix JBI Container
> (ServiceMix) started
> INFO - JDBCAdapterFactory - Database driver recognized:
> [apache_derby_embedded_jdbc_driver]
> ERROR - LogTask- java.io.FileNotFoundException:
> conf/log4j.xml (No such file or directory)
> {panel}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-854) LogService uses hard-coded path to the log4j.xml file
LogService uses hard-coded path to the log4j.xml file
--
Key: SM-854
URL: https://issues.apache.org/activemq/browse/SM-854
Project: ServiceMix
Issue Type: Bug
Components: servicemix-core
Affects Versions: 3.1
Reporter: Bruce Snyder
Assigned To: Bruce Snyder
The path the log4j.xml file is hard-coded to {{conf/log4j.xml}}. If ServiceMix
is started from inside the {{bin}} directory, ServiceMix won't be able to
locate this file and logging will not work properly. Below is the output from a
started in the {{bin}} directory:
{panel}
$ ./servicemix
servicemix: JAVA_HOME not set; results may vary
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing)
Starting Apache ServiceMix ESB: 3.1-incubating-SNAPSHOT
Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
INFO - ConnectorServerFactoryBean - JMX connector available at:
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
INFO - JBIContainer - ServiceMix 3.1-incubating-SNAPSHOT JBI
Container (ServiceMix) is starting
INFO - JBIContainer - For help or more informations please
see: http://incubator.apache.org/servicemix/
INFO - ComponentMBeanImpl - Initializing component:
#SubscriptionManager#
INFO - DeploymentService - Restoring service assemblies
INFO - JBIContainer - ServiceMix JBI Container (ServiceMix)
started
INFO - JDBCAdapterFactory - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
ERROR - LogTask- java.io.FileNotFoundException:
conf/log4j.xml (No such file or directory)
{panel}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQ-1140) Compression not working
[
https://issues.apache.org/activemq/browse/AMQ-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Snyder reassigned AMQ-1140:
-
Assignee: Bruce Snyder
> Compression not working
>
>
> Key: AMQ-1140
> URL: https://issues.apache.org/activemq/browse/AMQ-1140
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 4.1.2
>Reporter: Bruce Snyder
> Assigned To: Bruce Snyder
>
> When setting compression from the message producer side using the
> {{ActiveMQConnectionFactory.setUseCompression(true)}} method, a call to the
> {{ActiveMQConnectionFactory.isUseCompression()}} method then returns true.
> However, when using [Ethereal|http://www.ethereal.com/] to sniff the packets
> between brokers, the message bodies are not compressed - they're just plain
> text. This appears to be a bug.
> I'll try to create a test for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (AMQ-1140) Compression not working
Compression not working
Key: AMQ-1140
URL: https://issues.apache.org/activemq/browse/AMQ-1140
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.1.2
Reporter: Bruce Snyder
When setting compression from the message producer side using the
{{ActiveMQConnectionFactory.setUseCompression(true)}} method, a call to the
{{ActiveMQConnectionFactory.isUseCompression()}} method then returns true.
However, when using [Ethereal|http://www.ethereal.com/] to sniff the packets
between brokers, the message bodies are not compressed - they're just plain
text. This appears to be a bug.
I'll try to create a test for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-621) Issues with ServiceMix startup shell script on Solaris
Issues with ServiceMix startup shell script on Solaris
---
Key: SM-621
URL: https://issues.apache.org/activemq/browse/SM-621
Project: ServiceMix
Issue Type: Bug
Components: servicemix-assembly
Affects Versions: 3.0
Reporter: Bruce Snyder
Attachments: servicemix.diff.txt
1. The following command does not work in Solaris:
{code}
export JAVA_MIN_MEM=64M
{code}
Solution:
{code}
if [ "x$JAVA_MIN_MEM" = "x" ]; then
JAVA_MIN_MEM=64M
export JAVA_MIN_MEM
fi
if [ "x$JAVA_MAX_MEM" = "x" ]; then
JAVA_MAX_MEM=256M
export JAVA_MAX_MEM
fi
{code}
2. Also, in locateHome(), the -e option on test does not work on Solaris.
Instead, the -e should be -d .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SM-621) Issues with ServiceMix startup shell script on Solaris
[ https://issues.apache.org/activemq/browse/SM-621?page=all ]
Bruce Snyder resolved SM-621.
-
Fix Version/s: 3.1
Resolution: Fixed
Assignee: Bruce Snyder
Sendingsrc/main/release/bin/servicemix
Transmitting file data .
Committed revision 452206.
> Issues with ServiceMix startup shell script on Solaris
> --
>
> Key: SM-621
> URL: https://issues.apache.org/activemq/browse/SM-621
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-assembly
>Affects Versions: 3.0
>Reporter: Bruce Snyder
> Assigned To: Bruce Snyder
> Fix For: 3.1
>
> Attachments: servicemix.diff.txt
>
>
> 1. The following command does not work in Solaris:
> {code}
> export JAVA_MIN_MEM=64M
> {code}
> Solution:
> {code}
> if [ "x$JAVA_MIN_MEM" = "x" ]; then
> JAVA_MIN_MEM=64M
> export JAVA_MIN_MEM
> fi
> if [ "x$JAVA_MAX_MEM" = "x" ]; then
> JAVA_MAX_MEM=256M
> export JAVA_MAX_MEM
> fi
> {code}
> 2. Also, in locateHome(), the -e option on test does not work on Solaris.
> Instead, the -e should be -d .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SM-620) Issues with ServiceMix startup shell script on Solaris
Issues with ServiceMix startup shell script on Solaris
---
Key: SM-620
URL: https://issues.apache.org/activemq/browse/SM-620
Project: ServiceMix
Issue Type: Bug
Components: servicemix-assembly
Affects Versions: 3.0
Reporter: Bruce Snyder
Problems with Solaris:
1. The following command does not work in Solaris:
{code}
export JAVA_MIN_MEM=64M
{code}
Solution:
{code}
if [ "x$JAVA_MIN_MEM" = "x" ]; then
JAVA_MIN_MEM=64M
export JAVA_MIN_MEM
fi
if [ "x$JAVA_MAX_MEM" = "x" ]; then
JAVA_MAX_MEM=256M
export JAVA_MAX_MEM
fi
{code}
2. Also, in locateHome()
if [ ! -e ]
does not work for Solaris (not supported option for test). Instead, the -e
should be -d
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-608) The wsdl-first example is broken because it cannot locate the 3.1-incubating-SNAPSHOT version of the jbi-maven-plugin
[ https://issues.apache.org/activemq/browse/SM-608?page=all ]
Bruce Snyder updated SM-608:
Attachment: pom.xml.diff.txt
Attaching a patch to fix the issue.
> The wsdl-first example is broken because it cannot locate the
> 3.1-incubating-SNAPSHOT version of the jbi-maven-plugin
> -
>
> Key: SM-608
> URL: https://issues.apache.org/activemq/browse/SM-608
> Project: ServiceMix
> Issue Type: Bug
>Affects Versions: 3.1
>Reporter: Bruce Snyder
> Fix For: 3.1
>
> Attachments: pom.xml.diff.txt
>
>
> The wsdl-first example has the jbi-maven-plugin specified in the pom.xml
> file, but there is no pluginRepository specified in the pom.xml, so the build
> results in the following failure:
> {panel}
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Plugin could not be found - check that the goal name is correct:
> Unable to download the artifact from any repository
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.servicemix.tooling
> -DartifactId=jbi-maven-plugin \
> -Dversion=3.1-incubating-SNAPSHOT -Dpackaging=maven-plugin
> -Dfile=/path/to/file
>
> org.apache.servicemix.tooling:jbi-maven-plugin:maven-plugin:3.1-incubating-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
>
> org.apache.servicemix.tooling:jbi-maven-plugin:maven-plugin:3.1-incubating-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> {panel}
> I confirmed that this is an issue by moving my local version of the tooling
> directory aside like so:
> {panel}
> mv ~/.m2/repository/org/apache/servicemix/tooling
> ~/.m2/repository/org/apache/servicemix/tooling.old2
> {panel}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SM-608) The wsdl-first example is broken because it cannot locate the 3.1-incubating-SNAPSHOT version of the jbi-maven-plugin
[ https://issues.apache.org/activemq/browse/SM-608?page=all ]
Bruce Snyder closed SM-608.
---
Resolution: Fixed
Assignee: Bruce Snyder
Sendingpom.xml
Transmitting file data .
Committed revision 451073.
> The wsdl-first example is broken because it cannot locate the
> 3.1-incubating-SNAPSHOT version of the jbi-maven-plugin
> -
>
> Key: SM-608
> URL: https://issues.apache.org/activemq/browse/SM-608
> Project: ServiceMix
> Issue Type: Bug
>Affects Versions: 3.1
>Reporter: Bruce Snyder
> Assigned To: Bruce Snyder
> Fix For: 3.1
>
> Attachments: pom.xml.diff.txt
>
>
> The wsdl-first example has the jbi-maven-plugin specified in the pom.xml
> file, but there is no pluginRepository specified in the pom.xml, so the build
> results in the following failure:
> {panel}
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Plugin could not be found - check that the goal name is correct:
> Unable to download the artifact from any repository
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.servicemix.tooling
> -DartifactId=jbi-maven-plugin \
> -Dversion=3.1-incubating-SNAPSHOT -Dpackaging=maven-plugin
> -Dfile=/path/to/file
>
> org.apache.servicemix.tooling:jbi-maven-plugin:maven-plugin:3.1-incubating-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
>
> org.apache.servicemix.tooling:jbi-maven-plugin:maven-plugin:3.1-incubating-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> {panel}
> I confirmed that this is an issue by moving my local version of the tooling
> directory aside like so:
> {panel}
> mv ~/.m2/repository/org/apache/servicemix/tooling
> ~/.m2/repository/org/apache/servicemix/tooling.old2
> {panel}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SM-608) The wsdl-first example is broken because it cannot locate the 3.1-incubating-SNAPSHOT version of the jbi-maven-plugin
The wsdl-first example is broken because it cannot locate the
3.1-incubating-SNAPSHOT version of the jbi-maven-plugin
--
Key: SM-608
URL: https://issues.apache.org/activemq/browse/SM-608
Project: ServiceMix
Issue Type: Bug
Affects Versions: 3.1
Reporter: Bruce Snyder
Fix For: 3.1
The wsdl-first example has the jbi-maven-plugin specified in the pom.xml file,
but there is no pluginRepository specified in the pom.xml, so the build results
in the following failure:
{panel}
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Plugin could not be found - check that the goal name is correct: Unable
to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.servicemix.tooling
-DartifactId=jbi-maven-plugin \
-Dversion=3.1-incubating-SNAPSHOT -Dpackaging=maven-plugin
-Dfile=/path/to/file
org.apache.servicemix.tooling:jbi-maven-plugin:maven-plugin:3.1-incubating-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
org.apache.servicemix.tooling:jbi-maven-plugin:maven-plugin:3.1-incubating-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
{panel}
I confirmed that this is an issue by moving my local version of the tooling
directory aside like so:
{panel}
mv ~/.m2/repository/org/apache/servicemix/tooling
~/.m2/repository/org/apache/servicemix/tooling.old2
{panel}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-892) Allow the JMX RMI server port to be hard set
[ https://issues.apache.org/activemq/browse/AMQ-892?page=comments#action_36831 ] Bruce Snyder commented on AMQ-892: -- The JMX RMI port can be set in ActiveMQ 4.x using the JMX system properties. See the [How can I monitor ActiveMQ? page|http://activemq.org/site/how-can-i-monitor-activemq.html#HowcanImonitorActiveMQ-AdvancedJMXConfiguration] under the Advanced JMX Configuration heading. If the com.sun.management.jmxremote.port system property is set within the SUNJMX environment variable, the ActiveMQ start script will pick it up and pass it to the JVM. > Allow the JMX RMI server port to be hard set > > > Key: AMQ-892 > URL: https://issues.apache.org/activemq/browse/AMQ-892 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Affects Versions: 4.0.2 >Reporter: John Heitmann >Priority: Minor > Attachments: jmxPort.patch > > > When debugging a broker over the firewall with JMX it's often necessary to > use ssh tunneling. JMX uses 2 ports. The RMI registry port is what is > typically configured, but JMX also runs an RMI server on a different port-- > one that's typically chosen randomly. When you're ssh tunneling you need to > know what ports to tunnel to a priori so this is no good. > This patch adds a setting to allow the RMI server port to be set in addition > to the registry port. This is what it looks like in xml: > jmxDomainName="org.apache.activemq"/> > Also I snuck in a one-liner change that will create the connector if the user > configured jmx. This seems like the right thing to do, but my JMX experience > is pretty limited so it could break in something like Tomcat. Please take a > close look at that line before applying. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1786) JMS Listeners for protocols activeio, peer and openwire fail to start
[ http://issues.apache.org/jira/browse/GERONIMO-1786?page=comments#action_12420204 ] Bruce Snyder commented on GERONIMO-1786: This means that the console page for the JMS Server contains links to functionality that cannot be fulfilled in Geronimo 1.1. > JMS Listeners for protocols activeio, peer and openwire fail to start > - > > Key: GERONIMO-1786 > URL: http://issues.apache.org/jira/browse/GERONIMO-1786 > Project: Geronimo > Type: Bug > Security: public(Regular issues) > Components: ActiveMQ, console > Versions: 1.0, 1.2, 1.1 > Environment: Geronimo 1.0.0 > Reporter: Donald Woods > Fix For: 1.2 > > Even though addition of JMS Listeners for activeio, peer and openwire > protocols is successful, the listeners fail to > start with the following exceptions. > activeio --- java.lang.NoSuchMethodError: org.activeio.ChannelFactory: method > bindAsynchChannel(Ljava/net/URI;)Lorg/activeio/AsynchChannelServer; not found > openwire --- javax.jms.JMSException: Could not load protocol: openwire. > Reason: java.lang.ClassNotFoundException: > org.activemq.transport.openwire.OpenWireTransportServerChannelFactory > peer --- javax.jms.JMSException: Could not load protocol: peer. Reason: > java.lang.ClassNotFoundException: > org.activemq.transport.peer.PeerTransportServerChannelFactory > Stack trace of the same. > 192: 14:17:49,499 ERROR [GBeanInstanceState] Error while starting; GBean is > now in the FAILED state: > objectName="geronimo.server:J2EEApplication=null,J2EEModule=geronimo/activemq-broker/1.0/car,J2EEServer=geronimo,br > oker=ActiveMQ,j2eeType=JMSConnector,name=ActiveMQ.activeio.0.0.0.0.12340-aio" > 193: java.lang.NoSuchMethodError: org.activeio.ChannelFactory: method > bindAsynchChannel(Ljava/net/URI;)Lorg/activeio/AsynchChannelServer; not found > 194: at > org.activemq.transport.activeio.ActiveIOTransportServerChannelFactory.createAsynchChannelServer(ActiveIOTranspo > rtServerChannelFactory.java:60) > 195: at > org.activemq.transport.activeio.ActiveIOTransportServerChannelFactory.create(ActiveIOTransportServerChannelFact > ory.java:49) > 196: at > org.activemq.transport.TransportServerChannelProvider.create(TransportServerChannelProvider.java:45) > 197: at > org.activemq.broker.impl.BrokerConnectorImpl.createTransportServerChannel(BrokerConnectorImpl.java:425) > 198: at > org.activemq.broker.impl.BrokerConnectorImpl.(BrokerConnectorImpl.java:69) > 199: at > org.activemq.gbean.ActiveMQConnectorGBean.createBrokerConnector(ActiveMQConnectorGBean.java:161) > 200: at > org.activemq.gbean.ActiveMQConnectorGBean.doStart(ActiveMQConnectorGBean.java:129) > 201: at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java(Compiled > Code)) > 202: at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:325) > 203: at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:110) > 204: at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:132) > 205: at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:537) > 206: at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:208) > 207: at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor$StartRecursiveInvoke.invoke(ProxyMethodInterceptor.java > :365) > 208: at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) > 209: at > org.activemq.gbean.ActiveMQConnector$$EnhancerByCGLIB$$2b4c85ae.startRecursive() > 210: at > org.apache.geronimo.console.jmsmanager.server.JMSConnectorPortlet.processAction(JMSConnectorPortlet.java:79) > 211: at > org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) > 212: at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) > 213: at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) > 214: at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) > 215: at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) > 216: at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > 217: at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > 218: at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) > 219: at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) > 220: at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) > 221: at > org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) > 222: at > org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68) > 223
[jira] Commented: (SM-453) Update the ServiceMix extensions build at the Codehaus to version 3.0-SNAPSHOT and to use the latest ActiveMQ and ServiceMix jars
[ https://issues.apache.org/activemq/browse/SM-453?page=comments#action_36327 ] Bruce Snyder commented on SM-453: - Sendingetc/project.properties Sendingproject.xml Sendingtooling/jboss-deployer/project.xml Sendingtooling/servicemix-web/project.xml Sending tooling/servicemix-web/src/main/java/org/servicemix/web/jmx/ManagementContext.java Transmitting file data . Committed revision 1070. > Update the ServiceMix extensions build at the Codehaus to version > 3.0-SNAPSHOT and to use the latest ActiveMQ and ServiceMix jars > - > > Key: SM-453 > URL: https://issues.apache.org/activemq/browse/SM-453 > Project: ServiceMix > Type: Bug > Components: tooling > Versions: 3.0-M2 > Reporter: Bruce Snyder > Fix For: 3.0-M2 > > > # Update the ServiceMix extensions build version from 2.1-SNAPSHOT to > 3.0-SNAPSHOT > # Update the ServiceMix extensions to make use of the new groupId: > org.apache.servicemix > # Update the ServiceMix extensions to make use of org.apache.activemq.Service > instead of org.apache.activemq.service.Service -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SM-453) Update the ServiceMix extensions build at the Codehaus to version 3.0-SNAPSHOT and to use the latest ActiveMQ and ServiceMix jars
[ https://issues.apache.org/activemq/browse/SM-453?page=all ] Bruce Snyder resolved SM-453: - Resolution: Fixed Assign To: Bruce Snyder > Update the ServiceMix extensions build at the Codehaus to version > 3.0-SNAPSHOT and to use the latest ActiveMQ and ServiceMix jars > - > > Key: SM-453 > URL: https://issues.apache.org/activemq/browse/SM-453 > Project: ServiceMix > Type: Bug > Components: tooling > Versions: 3.0-M2 > Reporter: Bruce Snyder > Assignee: Bruce Snyder > Fix For: 3.0-M2 > > > # Update the ServiceMix extensions build version from 2.1-SNAPSHOT to > 3.0-SNAPSHOT > # Update the ServiceMix extensions to make use of the new groupId: > org.apache.servicemix > # Update the ServiceMix extensions to make use of org.apache.activemq.Service > instead of org.apache.activemq.service.Service -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-453) Update the ServiceMix extensions build at the Codehaus to version 3.0-SNAPSHOT and to use the latest ActiveMQ and ServiceMix jars
[ https://issues.apache.org/activemq/browse/SM-453?page=all ] Bruce Snyder updated SM-453: Summary: Update the ServiceMix extensions build at the Codehaus to version 3.0-SNAPSHOT and to use the latest ActiveMQ and ServiceMix jars (was: Update the ServiceMix extensions build at the Codehaus to version 3.0-SNAPSHOT and to use the latest ServiceMix jars) Description: # Update the ServiceMix extensions build version from 2.1-SNAPSHOT to 3.0-SNAPSHOT # Update the ServiceMix extensions to make use of the new groupId: org.apache.servicemix # Update the ServiceMix extensions to make use of org.apache.activemq.Service instead of org.apache.activemq.service.Service was: # Update the ServiceMix extensions build version from 2.1-SNAPSHOT to 3.0-SNAPSHOT # Update the ServiceMix extensions to make use of the new groupId: org.apache.servicemix # Update the ServiceMix extensions to make use of the new artifactId: incubating-apache-servicemix > Update the ServiceMix extensions build at the Codehaus to version > 3.0-SNAPSHOT and to use the latest ActiveMQ and ServiceMix jars > - > > Key: SM-453 > URL: https://issues.apache.org/activemq/browse/SM-453 > Project: ServiceMix > Type: Bug > Components: tooling > Versions: 3.0-M2 > Reporter: Bruce Snyder > Fix For: 3.0-M2 > > > # Update the ServiceMix extensions build version from 2.1-SNAPSHOT to > 3.0-SNAPSHOT > # Update the ServiceMix extensions to make use of the new groupId: > org.apache.servicemix > # Update the ServiceMix extensions to make use of org.apache.activemq.Service > instead of org.apache.activemq.service.Service -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SM-453) Update the ServiceMix extensions build at the Codehaus to version 3.0-SNAPSHOT and to use the latest ServiceMix jars
Update the ServiceMix extensions build at the Codehaus to version 3.0-SNAPSHOT and to use the latest ServiceMix jars - Key: SM-453 URL: https://issues.apache.org/activemq/browse/SM-453 Project: ServiceMix Type: Bug Components: tooling Versions: 3.0-M2 Reporter: Bruce Snyder Fix For: 3.0-M2 # Update the ServiceMix extensions build version from 2.1-SNAPSHOT to 3.0-SNAPSHOT # Update the ServiceMix extensions to make use of the new groupId: org.apache.servicemix # Update the ServiceMix extensions to make use of the new artifactId: incubating-apache-servicemix -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-450) Extend SM-448 to include a Service Unit to expose the endpoint via HTTP
[ https://issues.apache.org/activemq/browse/SM-450?page=comments#action_36294 ] Bruce Snyder commented on SM-450: - Sendingsamples/pom.xml Sendingsamples/wsdl-first/pom.xml Sendingsamples/wsdl-first/src/main/assembly/sa.xml Sendingsamples/wsdl-first/src/main/sa/META-INF/jbi.xml Adding samples/wsdl-first-http Adding samples/wsdl-first-http/.classpath Adding samples/wsdl-first-http/.project Adding samples/wsdl-first-http/pom.xml Adding samples/wsdl-first-http/src Adding samples/wsdl-first-http/src/main Adding samples/wsdl-first-http/src/main/resources Adding samples/wsdl-first-http/src/main/resources/xbean.xml Transmitting file data Committed revision 413731. > Extend SM-448 to include a Service Unit to expose the endpoint via HTTP > --- > > Key: SM-450 > URL: https://issues.apache.org/activemq/browse/SM-450 > Project: ServiceMix > Type: Improvement > Components: servicemix-jsr181 > Versions: 3.0-M2 > Reporter: Bruce Snyder > Assignee: Bruce Snyder > > > SM-448 created a Service Assembly allowing the JSR181 WSDL creation to be > overridden by providing the WSDL, but the example doesn't include a Service > Unit inside of the Service Assembly to expose the endpoint via the > servicemix-http component. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-450) Extend SM-448 to include a Service Unit to expose the endpoint via HTTP
[ https://issues.apache.org/activemq/browse/SM-450?page=all ] Bruce Snyder updated SM-450: Summary: Extend SM-448 to include a Service Unit to expose the endpoint via HTTP (was: Extend SM-448 to include a Service Unit) Description: SM-448 created a Service Assembly allowing the JSR181 WSDL creation to be overridden by providing the WSDL, but the example doesn't include a Service Unit inside of the Service Assembly to expose the endpoint via the servicemix-http component. (was: SM-448 created a Service Assembly allowing the JSR181 WSDL creation to be overridden by providing the WSDL, but the example doesn't include a Service Unit inside of the Service Assembly. ) > Extend SM-448 to include a Service Unit to expose the endpoint via HTTP > > > Key: SM-450 > URL: https://issues.apache.org/activemq/browse/SM-450 > Project: ServiceMix > Type: Improvement > Components: servicemix-jsr181 > Versions: 3.0-M2 > Reporter: Bruce Snyder > Assignee: Bruce Snyder > > > SM-448 created a Service Assembly allowing the JSR181 WSDL creation to be > overridden by providing the WSDL, but the example doesn't include a Service > Unit inside of the Service Assembly to expose the endpoint via the > servicemix-http component. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SM-450) Extend SM-448 to include a Service Unit
Extend SM-448 to include a Service Unit Key: SM-450 URL: https://issues.apache.org/activemq/browse/SM-450 Project: ServiceMix Type: Improvement Components: servicemix-jsr181 Versions: 3.0-M2 Reporter: Bruce Snyder Assigned to: Bruce Snyder SM-448 created a Service Assembly allowing the JSR181 WSDL creation to be overridden by providing the WSDL, but the example doesn't include a Service Unit inside of the Service Assembly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1760) Several bugs in the javamail spec
[ http://issues.apache.org/jira/browse/GERONIMO-1760?page=all ] Bruce Snyder closed GERONIMO-1760: -- Fix Version: 1.1 Resolution: Fixed Assign To: Bruce Snyder > Several bugs in the javamail spec > - > > Key: GERONIMO-1760 > URL: http://issues.apache.org/jira/browse/GERONIMO-1760 > Project: Geronimo > Type: Bug > Components: specs > Versions: 1.1 > Reporter: Guillaume Nodet > Assignee: Bruce Snyder > Fix For: 1.1 > Attachments: javamail.patch > > * base64 encoder skip the lasts bytes (up to 3, modulo 4) > * base64 decoder stream does not copy data > * reading a multipart message creates an additional empty part -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1760) Several bugs in the javamail spec
[ http://issues.apache.org/jira/browse/GERONIMO-1760?page=comments#action_12371495 ] Bruce Snyder commented on GERONIMO-1760: Committed patch: Sending geronimo-spec-javamail/src/main/java/javax/mail/internet/MimeBodyPart.java Sending geronimo-spec-javamail/src/main/java/javax/mail/internet/MimeMultipart.java Sending geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/Base64DecoderStream.java Sending geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/Base64EncoderStream.java Adding geronimo-spec-javamail/src/test/java/javax/mail/internet/MimeTest.java Transmitting file data . Committed revision 387976. > Several bugs in the javamail spec > - > > Key: GERONIMO-1760 > URL: http://issues.apache.org/jira/browse/GERONIMO-1760 > Project: Geronimo > Type: Bug > Components: specs > Versions: 1.1 > Reporter: Guillaume Nodet > Fix For: 1.1 > Attachments: javamail.patch > > * base64 encoder skip the lasts bytes (up to 3, modulo 4) > * base64 decoder stream does not copy data > * reading a multipart message creates an additional empty part -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1651) Complete implementation of javamail MimeMessage and MimeUtil classes.
[ http://issues.apache.org/jira/browse/GERONIMO-1651?page=all ] Bruce Snyder closed GERONIMO-1651: -- Fix Version: 1.1 Resolution: Fixed > Complete implementation of javamail MimeMessage and MimeUtil classes. > - > > Key: GERONIMO-1651 > URL: http://issues.apache.org/jira/browse/GERONIMO-1651 > Project: Geronimo > Type: Improvement > Components: mail > Versions: 1.x > Reporter: Rick McGuire > Assignee: Bruce Snyder > Fix For: 1.1 > Attachments: GERONIMO-1651.patch, charset.patch > > The javamail code in the geronimo-spec-javamail jar file is an extremely > incomplete implementation, with a lot of methods just throwing unimplemented > exceptions. MimeMessage and MimeUtil were the biggest holes in the support. > This patch provides the following enhancements: > - Completion of the MimeMessage class, including adding support for header > encodings, and message content encodings. > - Completion of the MimeUtility class (which was basically completely empty > implementation methods). > - Fixing HeaderTokenizer to properly implement token scanning rules for > comments and literals and return correct token identifiers for special > characters. > - Fix ContentType type parsing. > - Fix ContentDisposition header parsing. > - Fix multiple bugs in MimeBodyPart (similar problems as MimeMessage). > Also included are enhanced test cases to test these classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-1651) Complete implementation of javamail MimeMessage and MimeUtil classes.
[ http://issues.apache.org/jira/browse/GERONIMO-1651?page=all ] Bruce Snyder reassigned GERONIMO-1651: -- Assign To: Bruce Snyder > Complete implementation of javamail MimeMessage and MimeUtil classes. > - > > Key: GERONIMO-1651 > URL: http://issues.apache.org/jira/browse/GERONIMO-1651 > Project: Geronimo > Type: Improvement > Components: mail > Versions: 1.x > Reporter: Rick McGuire > Assignee: Bruce Snyder > Attachments: GERONIMO-1651.patch, charset.patch > > The javamail code in the geronimo-spec-javamail jar file is an extremely > incomplete implementation, with a lot of methods just throwing unimplemented > exceptions. MimeMessage and MimeUtil were the biggest holes in the support. > This patch provides the following enhancements: > - Completion of the MimeMessage class, including adding support for header > encodings, and message content encodings. > - Completion of the MimeUtility class (which was basically completely empty > implementation methods). > - Fixing HeaderTokenizer to properly implement token scanning rules for > comments and literals and return correct token identifiers for special > characters. > - Fix ContentType type parsing. > - Fix ContentDisposition header parsing. > - Fix multiple bugs in MimeBodyPart (similar problems as MimeMessage). > Also included are enhanced test cases to test these classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1651) Complete implementation of javamail MimeMessage and MimeUtil classes.
[ http://issues.apache.org/jira/browse/GERONIMO-1651?page=comments#action_12367993 ] Bruce Snyder commented on GERONIMO-1651: Patches committed: Sending geronimo-spec-javamail/src/main/java/javax/mail/internet/ContentDisposition.java Sending geronimo-spec-javamail/src/main/java/javax/mail/internet/ContentType.java Sending geronimo-spec-javamail/src/main/java/javax/mail/internet/HeaderTokenizer.java Sending geronimo-spec-javamail/src/main/java/javax/mail/internet/InternetAddress.java Sending geronimo-spec-javamail/src/main/java/javax/mail/internet/InternetHeaders.java Sending geronimo-spec-javamail/src/main/java/javax/mail/internet/MimeBodyPart.java Sending geronimo-spec-javamail/src/main/java/javax/mail/internet/MimeMessage.java Sending geronimo-spec-javamail/src/main/java/javax/mail/internet/MimeUtility.java Sending geronimo-spec-javamail/src/main/java/javax/mail/internet/NewsAddress.java Sending geronimo-spec-javamail/src/main/java/javax/mail/internet/ParameterList.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/ASCIIUtil.java Sending geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/Base64.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/Base64DecoderStream.java Sending geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/Base64Encoder.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/Base64EncoderStream.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/QuotedPrintable.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/QuotedPrintableDecoderStream.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/QuotedPrintableEncoder.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/QuotedPrintableEncoderStream.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/RFC2231Encoder.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/SessionUtil.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/StringBufferOutputStream.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/UUDecoderStream.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/UUEncode.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/UUEncoder.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/UUEncoderStream.java Sending geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/XTextEncoder.java Adding geronimo-spec-javamail/src/main/resources/META-INF/javamail.charset.map Sending geronimo-spec-javamail/src/test/java/javax/mail/internet/ContentDispositionTest.java Sending geronimo-spec-javamail/src/test/java/javax/mail/internet/ContentTypeTest.java Sending geronimo-spec-javamail/src/test/java/javax/mail/internet/HeaderTokenizerTest.java Sending geronimo-spec-javamail/src/test/java/javax/mail/internet/MimeMessageTest.java Sending geronimo-spec-javamail/src/test/java/javax/mail/internet/NewsAddressTest.java Sending geronimo-spec-javamail/src/test/java/javax/mail/internet/ParameterListTest.java Transmitting file data .. Committed revision 381393. > Complete implementation of javamail MimeMessage and MimeUtil classes. > - > > Key: GERONIMO-1651 > URL: http://issues.apache.org/jira/browse/GERONIMO-1651 > Project: Geronimo > Type: Improvement > Components: mail > Versions: 1.x > Reporter: Rick McGuire > Attachments: GERONIMO-1651.patch, charset.patch > > The javamail code in the geronimo-spec-javamail jar file is an extremely > incomplete implementation, with a lot of methods just throwing unimplemented > exceptions. MimeMessage and MimeUtil were the biggest holes in the support. > This patch provides the following enhancements: > - Completion of the MimeMessage class, including adding support for header > encodings, and message content encodings. > - Completion of the MimeUtility class (which was basically completely empty > implementation methods). > - Fixing HeaderTokenizer to properly implement token scanning rules for > comments and literals and return correct token identifiers for special > characters. > - Fix ContentType type parsing. > - Fix ContentDisposition header parsing. > - Fix multiple bugs in MimeBodyPart (similar problems as MimeMessage). > Also included are enhanced test cases to test these classes. -- This message is automatically
[jira] Commented: (GERONIMO-1611) Apache Geronimo Web site update
[ http://issues.apache.org/jira/browse/GERONIMO-1611?page=comments#action_12366237 ] Bruce Snyder commented on GERONIMO-1611: Added the first patch for sites_geronimo.06-02-09.zip: Sendingsite/NOTES.txt Sendingsite/build.xml Sendingsite/docs/contributors.html Sendingsite/docs/dependencies.html Sendingsite/docs/devtools/index.html Sendingsite/docs/documentation.html Sendingsite/docs/downloads.html Sendingsite/docs/faq.html Sendingsite/docs/get-involved.html Sendingsite/docs/guidelines.html Sendingsite/docs/index.html Sendingsite/docs/license.html Sendingsite/docs/mailing.html Adding site/docs/navigation.html Sendingsite/docs/newshistory.html Sendingsite/docs/powered_by.html Sendingsite/docs/roadmap.html Sendingsite/docs/schemas.html Sendingsite/docs/svn.html Sendingsite/xdocs/dependencies.xml Sendingsite/xdocs/documentation.xml Sendingsite/xdocs/downloads.xml Sendingsite/xdocs/index.xml Sendingsite/xdocs/mailing.xml Sendingsite/xdocs/newshistory.xml Sendingsite/xdocs/powered_by.xml Sendingsite/xdocs/stylesheets/project.xml Adding site/xdocs/stylesheets/site.hc.xml Sendingsite/xdocs/stylesheets/site.vsl Sendingsite/xdocs/stylesheets/site.xsl Transmitting file data .. Committed revision 377474. > Apache Geronimo Web site update > --- > > Key: GERONIMO-1611 > URL: http://issues.apache.org/jira/browse/GERONIMO-1611 > Project: Geronimo > Type: Improvement > Components: website > Reporter: Hernan Cunico > Assignee: Bruce Snyder > Attachments: sites_geronimo.06-02-08.zip, sites_geronimo.06-02-09.zip, > sites_geronimo.06-02-10.zip, sites_geronimo.06-02-13.zip > > I have updated the template of the current Apache Geronimo Web site to use > the one proposed from EPIQ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1611) Apache Geronimo Web site update
[ http://issues.apache.org/jira/browse/GERONIMO-1611?page=comments#action_12365693 ] Bruce Snyder commented on GERONIMO-1611: Thank you so much for your work on the site! It's really coming along. I'm getting a bunch of conflicts when doing an svn update on the content in the .zip file. It would be extremely helpful if you could create a diff file against the latest SVN and attach it to this issue as well. The command to produce a diff file is as follows: svn diff > site.diff This command performs a diff and directs the output to a file named site.diff that can be attached to this issue. Please let me know if you have any issues. > Apache Geronimo Web site update > --- > > Key: GERONIMO-1611 > URL: http://issues.apache.org/jira/browse/GERONIMO-1611 > Project: Geronimo > Type: Improvement > Components: website > Reporter: Hernan Cunico > Assignee: Bruce Snyder > Attachments: sites_geronimo.06-02-08.zip > > I have updated the template of the current Apache Geronimo Web site to use > the one proposed from EPIQ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1593) Add SMTP Authentication and STARTTLS support.
[ http://issues.apache.org/jira/browse/GERONIMO-1593?page=comments#action_12365407 ] Bruce Snyder commented on GERONIMO-1593: Had to apply a few fixes to the SMTPTransport class after discovering issues that were confirmed by a user on the dev@ list: Transmitting file data . Committed revision 375548. > Add SMTP Authentication and STARTTLS support. > - > > Key: GERONIMO-1593 > URL: http://issues.apache.org/jira/browse/GERONIMO-1593 > Project: Geronimo > Type: New Feature > Components: mail > Versions: 1.1 > Reporter: Rick McGuire > Assignee: Bruce Snyder > Fix For: 1.1 > Attachments: GERONIMO-1593-geronimo-spec-javamail.patch, > GERONIMO-1593-javamail-transport.patch > > These patches add SMTP PLAIN, LOGIN, CRAM-MD5, and DIGEST_MD5 authentication > to the SMTP driver. Also adds an "smtps" protocl driver and STARTTLS > support. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1593) Add SMTP Authentication and STARTTLS support.
[ http://issues.apache.org/jira/browse/GERONIMO-1593?page=all ] Bruce Snyder closed GERONIMO-1593: -- Fix Version: 1.1 Resolution: Fixed > Add SMTP Authentication and STARTTLS support. > - > > Key: GERONIMO-1593 > URL: http://issues.apache.org/jira/browse/GERONIMO-1593 > Project: Geronimo > Type: New Feature > Components: mail > Versions: 1.1 > Reporter: Rick McGuire > Assignee: Bruce Snyder > Fix For: 1.1 > Attachments: GERONIMO-1593-geronimo-spec-javamail.patch, > GERONIMO-1593-javamail-transport.patch > > These patches add SMTP PLAIN, LOGIN, CRAM-MD5, and DIGEST_MD5 authentication > to the SMTP driver. Also adds an "smtps" protocl driver and STARTTLS > support. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1593) Add SMTP Authentication and STARTTLS support.
[ http://issues.apache.org/jira/browse/GERONIMO-1593?page=comments#action_12365349 ] Bruce Snyder commented on GERONIMO-1593: My apologies for all the fuss. After figuring out that I had to copy the spec jar from my local m2 repo to the my local m1 repo, I've added the second patch: Adding javamail-transport/src/java/org/apache/geronimo/javamail/authentication Adding javamail-transport/src/java/org/apache/geronimo/javamail/authentication/ClientAuthenticator.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/authentication/CramMD5Authenticator.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/authentication/DigestMD5Authenticator.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/authentication/LoginAuthenticator.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/authentication/PlainAuthenticator.java Sending javamail-transport/src/java/org/apache/geronimo/javamail/transport/smtp/MalformedSMTPReplyException.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/transport/smtp/SMTPAddressFailedException.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/transport/smtp/SMTPAddressSucceededException.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/transport/smtp/SMTPMessage.java Sending javamail-transport/src/java/org/apache/geronimo/javamail/transport/smtp/SMTPReply.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/transport/smtp/SMTPSTransport.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/transport/smtp/SMTPSendFailedException.java Sending javamail-transport/src/java/org/apache/geronimo/javamail/transport/smtp/SMTPTransport.java Sending javamail-transport/src/java/org/apache/geronimo/javamail/transport/smtp/SMTPTransportException.java Sending javamail-transport/src/resources/META-INF/javamail.default.providers Transmitting file data ... Committed revision 375375. > Add SMTP Authentication and STARTTLS support. > - > > Key: GERONIMO-1593 > URL: http://issues.apache.org/jira/browse/GERONIMO-1593 > Project: Geronimo > Type: New Feature > Components: mail > Versions: 1.1 > Reporter: Rick McGuire > Assignee: Bruce Snyder > Attachments: GERONIMO-1593-geronimo-spec-javamail.patch, > GERONIMO-1593-javamail-transport.patch > > These patches add SMTP PLAIN, LOGIN, CRAM-MD5, and DIGEST_MD5 authentication > to the SMTP driver. Also adds an "smtps" protocl driver and STARTTLS > support. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1593) Add SMTP Authentication and STARTTLS support.
[ http://issues.apache.org/jira/browse/GERONIMO-1593?page=comments#action_12365344 ] Bruce Snyder commented on GERONIMO-1593: Committed rest of the first patch: Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/Base64.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/Base64Encoder.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/Encoder.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/Hex.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/HexEncoder.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/XText.java Adding geronimo-spec-javamail/src/main/java/org/apache/geronimo/mail/util/XTextEncoder.java Transmitting file data ... Committed revision 375366. > Add SMTP Authentication and STARTTLS support. > - > > Key: GERONIMO-1593 > URL: http://issues.apache.org/jira/browse/GERONIMO-1593 > Project: Geronimo > Type: New Feature > Components: mail > Versions: 1.1 > Reporter: Rick McGuire > Assignee: Bruce Snyder > Attachments: GERONIMO-1593-geronimo-spec-javamail.patch, > GERONIMO-1593-javamail-transport.patch > > These patches add SMTP PLAIN, LOGIN, CRAM-MD5, and DIGEST_MD5 authentication > to the SMTP driver. Also adds an "smtps" protocl driver and STARTTLS > support. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-1593) Add SMTP Authentication and STARTTLS support.
[ http://issues.apache.org/jira/browse/GERONIMO-1593?page=all ] Bruce Snyder reassigned GERONIMO-1593: -- Assign To: Bruce Snyder > Add SMTP Authentication and STARTTLS support. > - > > Key: GERONIMO-1593 > URL: http://issues.apache.org/jira/browse/GERONIMO-1593 > Project: Geronimo > Type: New Feature > Components: mail > Versions: 1.1 > Reporter: Rick McGuire > Assignee: Bruce Snyder > Attachments: GERONIMO-1593-geronimo-spec-javamail.patch, > GERONIMO-1593-javamail-transport.patch > > These patches add SMTP PLAIN, LOGIN, CRAM-MD5, and DIGEST_MD5 authentication > to the SMTP driver. Also adds an "smtps" protocl driver and STARTTLS > support. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1593) Add SMTP Authentication and STARTTLS support.
[ http://issues.apache.org/jira/browse/GERONIMO-1593?page=comments#action_12365340 ] Bruce Snyder commented on GERONIMO-1593: The javamail-transport patch is failing: $ patch -p0 < ./GERONIMO-1593-javamail-transport.patch (Stripping trailing CRs from patch.) patching file src/java/org/apache/geronimo/javamail/authentication/DigestMD5Authenticator.java (Stripping trailing CRs from patch.) patching file src/java/org/apache/geronimo/javamail/authentication/CramMD5Authenticator.java (Stripping trailing CRs from patch.) patching file src/java/org/apache/geronimo/javamail/authentication/LoginAuthenticator.java (Stripping trailing CRs from patch.) patching file src/java/org/apache/geronimo/javamail/authentication/ClientAuthenticator.java (Stripping trailing CRs from patch.) patching file src/java/org/apache/geronimo/javamail/authentication/PlainAuthenticator.java (Stripping trailing CRs from patch.) patching file src/java/org/apache/geronimo/javamail/transport/smtp/SMTPReply.java Hunk #1 succeeded at 23 with fuzz 1. (Stripping trailing CRs from patch.) patching file src/java/org/apache/geronimo/javamail/transport/smtp/SMTPTransportException.java Hunk #1 FAILED at 17. 1 out of 2 hunks FAILED -- saving rejects to file src/java/org/apache/geronimo/javamail/transport/smtp/SMTPTransportException.java.rej (Stripping trailing CRs from patch.) patching file src/java/org/apache/geronimo/javamail/transport/smtp/SMTPTransport.java Hunk #2 succeeded at 74 with fuzz 1. (Stripping trailing CRs from patch.) patching file src/java/org/apache/geronimo/javamail/transport/smtp/SMTPSendFailedException.java (Stripping trailing CRs from patch.) patching file src/java/org/apache/geronimo/javamail/transport/smtp/SMTPSTransport.java (Stripping trailing CRs from patch.) patching file src/java/org/apache/geronimo/javamail/transport/smtp/MalformedSMTPReplyException.java Hunk #1 FAILED at 17. 1 out of 2 hunks FAILED -- saving rejects to file src/java/org/apache/geronimo/javamail/transport/smtp/MalformedSMTPReplyException.java.rej (Stripping trailing CRs from patch.) patching file src/java/org/apache/geronimo/javamail/transport/smtp/SMTPMessage.java (Stripping trailing CRs from patch.) patching file src/java/org/apache/geronimo/javamail/transport/smtp/SMTPAddressFailedException.java (Stripping trailing CRs from patch.) patching file src/java/org/apache/geronimo/javamail/transport/smtp/SMTPAddressSucceededException.java (Stripping trailing CRs from patch.) patching file src/resources/META-INF/javamail.default.providers Hunk #1 succeeded at 7 with fuzz 1. Also, the build after applying this patch fails looking for some classes in the mail module (e.g., org.apache.geronimo.mail.util.Base64, org.apache.geronimo.mail.util.Hex and org.apache.geronimo.mail.util.XText): java:compile: [echo] Compiling to /Users/bsnyder/src/geronimo/trunk/modules/javamail-transport/target/classes [javac] Compiling 31 source files to /Users/bsnyder/src/geronimo/trunk/modules/javamail-transport/target/classes [javac] /Users/bsnyder/src/geronimo/trunk/modules/javamail-transport/src/java/org/apache/geronimo/javamail/authentication/CramMD5Authenticator.java:26: package org.apache.geronimo.mail.util does not exist [javac] import org.apache.geronimo.mail.util.Base64; [javac] ^ [javac] /Users/bsnyder/src/geronimo/trunk/modules/javamail-transport/src/java/org/apache/geronimo/javamail/authentication/CramMD5Authenticator.java:27: package org.apache.geronimo.mail.util does not exist [javac] import org.apache.geronimo.mail.util.Hex; [javac] ^ [javac] /Users/bsnyder/src/geronimo/trunk/modules/javamail-transport/src/java/org/apache/geronimo/javamail/authentication/DigestMD5Authenticator.java:29: package org.apache.geronimo.mail.util does not exist [javac] import org.apache.geronimo.mail.util.Base64; [javac] ^ [javac] /Users/bsnyder/src/geronimo/trunk/modules/javamail-transport/src/java/org/apache/geronimo/javamail/authentication/DigestMD5Authenticator.java:30: package org.apache.geronimo.mail.util does not exist [javac] import org.apache.geronimo.mail.util.Hex; [javac] ^ [javac] /Users/bsnyder/src/geronimo/trunk/modules/javamail-transport/src/java/org/apache/geronimo/javamail/authentication/LoginAuthenticator.java:24: package org.apache.geronimo.mail.util does not exist [javac] import org.apache.geronimo.mail.util.Base64; [javac] ^ [javac] /Users/bsnyder/src/geronimo/trunk/modules/javamail-transport/src/java/org/apache/geronimo/javamail/authentication/PlainAuthenticator.java:24: package org.apache.geronimo.mail.util does not exist [javac] import org.apache.geronimo.mail.util.Base64; [javac] ^ [j
[jira] Commented: (GERONIMO-1593) Add SMTP Authentication and STARTTLS support.
[ http://issues.apache.org/jira/browse/GERONIMO-1593?page=comments#action_12365338 ] Bruce Snyder commented on GERONIMO-1593: Added patch for spec: Sendinggeronimo-spec-javamail/src/main/java/javax/mail/Service.java Transmitting file data . Committed revision 375349. > Add SMTP Authentication and STARTTLS support. > - > > Key: GERONIMO-1593 > URL: http://issues.apache.org/jira/browse/GERONIMO-1593 > Project: Geronimo > Type: New Feature > Components: mail > Versions: 1.1 > Reporter: Rick McGuire > Attachments: GERONIMO-1593-geronimo-spec-javamail.patch, > GERONIMO-1593-javamail-transport.patch > > These patches add SMTP PLAIN, LOGIN, CRAM-MD5, and DIGEST_MD5 authentication > to the SMTP driver. Also adds an "smtps" protocl driver and STARTTLS > support. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1558) InternetHeaders not handling setHeader(String name, Address[] addresses) properly.
[ http://issues.apache.org/jira/browse/GERONIMO-1558?page=all ]
Bruce Snyder closed GERONIMO-1558:
--
Fix Version: 1.1
Resolution: Fixed
> InternetHeaders not handling setHeader(String name, Address[] addresses)
> properly.
> --
>
> Key: GERONIMO-1558
> URL: http://issues.apache.org/jira/browse/GERONIMO-1558
> Project: Geronimo
> Type: Bug
> Components: mail
> Versions: 1.0
> Reporter: Rick McGuire
> Fix For: 1.1
> Attachments: GERONIMO-1558.patch
>
> The method setHeader(String name, Address[] addresses) inserts the new header
> into the header list without lowercasing the name. This results in the added
> header not being retrieveable later. This manifests as a failure in
> MimeMessage.getAllRecipients() if the recipients have been added with
> MimeMessage.setRecipients(). Here's a simple example:
>InternetAddress[] recipients = InternetAddress.parse(to, false);
>System.out.println("Adding " + recipients.length + " recipients to
> message");
>msg.setRecipients(Message.RecipientType.TO, recipients);
>Address[] msgRecipients = msg.getAllRecipients();
>System.out.println("Message reports having " + msgRecipients.length +
> " recipients");
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1558) InternetHeaders not handling setHeader(String name, Address[] addresses) properly.
[
http://issues.apache.org/jira/browse/GERONIMO-1558?page=comments#action_12365336
]
Bruce Snyder commented on GERONIMO-1558:
Added patch:
Sending
geronimo-spec-javamail/src/main/java/javax/mail/internet/InternetHeaders.java
Transmitting file data .
Committed revision 375346.
> InternetHeaders not handling setHeader(String name, Address[] addresses)
> properly.
> --
>
> Key: GERONIMO-1558
> URL: http://issues.apache.org/jira/browse/GERONIMO-1558
> Project: Geronimo
> Type: Bug
> Components: mail
> Versions: 1.0
> Reporter: Rick McGuire
> Fix For: 1.1
> Attachments: GERONIMO-1558.patch
>
> The method setHeader(String name, Address[] addresses) inserts the new header
> into the header list without lowercasing the name. This results in the added
> header not being retrieveable later. This manifests as a failure in
> MimeMessage.getAllRecipients() if the recipients have been added with
> MimeMessage.setRecipients(). Here's a simple example:
>InternetAddress[] recipients = InternetAddress.parse(to, false);
>System.out.println("Adding " + recipients.length + " recipients to
> message");
>msg.setRecipients(Message.RecipientType.TO, recipients);
>Address[] msgRecipients = msg.getAllRecipients();
>System.out.println("Message reports having " + msgRecipients.length +
> " recipients");
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1538) Update the website to use the new look and feel from Epiq
[ http://issues.apache.org/jira/browse/GERONIMO-1538?page=all ] Bruce Snyder updated GERONIMO-1538: --- Description: See the example of the new look and feel for the site here: http://people.apache.org/~bsnyder/geronimo/site/ was: See the example of the new look and feel for the site here: http://people.apache.org/~bsnyder/geronimo/site/ I've emailed Glenn Wheaton from Epiq asking him to attach the new stylesheets and imagery so that he can grant the ASF a license to the content. > Update the website to use the new look and feel from Epiq > - > > Key: GERONIMO-1538 > URL: http://issues.apache.org/jira/browse/GERONIMO-1538 > Project: Geronimo > Type: Improvement > Components: website > Reporter: Bruce Snyder > Assignee: Bruce Snyder > > See the example of the new look and feel for the site here: > http://people.apache.org/~bsnyder/geronimo/site/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1419) javax.mail.internet.InternetHeaders has some non implemented features
[ http://issues.apache.org/jira/browse/GERONIMO-1419?page=all ] Bruce Snyder closed GERONIMO-1419: -- Fix Version: 1.1 Resolution: Fixed > javax.mail.internet.InternetHeaders has some non implemented features > - > > Key: GERONIMO-1419 > URL: http://issues.apache.org/jira/browse/GERONIMO-1419 > Project: Geronimo > Type: Bug > Components: specs > Reporter: Guillaume Nodet > Assignee: Bruce Snyder > Fix For: 1.1 > Attachments: GERONIMO-1419.patch > > Some methods throw a UnsupportedOperationException -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-1419) javax.mail.internet.InternetHeaders has some non implemented features
[ http://issues.apache.org/jira/browse/GERONIMO-1419?page=all ] Bruce Snyder reassigned GERONIMO-1419: -- Assign To: Bruce Snyder > javax.mail.internet.InternetHeaders has some non implemented features > - > > Key: GERONIMO-1419 > URL: http://issues.apache.org/jira/browse/GERONIMO-1419 > Project: Geronimo > Type: Bug > Components: specs > Reporter: Guillaume Nodet > Assignee: Bruce Snyder > Fix For: 1.1 > Attachments: GERONIMO-1419.patch > > Some methods throw a UnsupportedOperationException -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1419) javax.mail.internet.InternetHeaders has some non implemented features
[ http://issues.apache.org/jira/browse/GERONIMO-1419?page=comments#action_12364492 ] Bruce Snyder commented on GERONIMO-1419: Patch added: Sendingsrc/main/java/javax/mail/internet/InternetHeaders.java Transmitting file data . Committed revision 373564. Thanks, Guillaume! > javax.mail.internet.InternetHeaders has some non implemented features > - > > Key: GERONIMO-1419 > URL: http://issues.apache.org/jira/browse/GERONIMO-1419 > Project: Geronimo > Type: Bug > Components: specs > Reporter: Guillaume Nodet > Fix For: 1.1 > Attachments: GERONIMO-1419.patch > > Some methods throw a UnsupportedOperationException -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1527) InternetAddress does not properly implement address parsing.
[ http://issues.apache.org/jira/browse/GERONIMO-1527?page=comments#action_12364490 ] Bruce Snyder commented on GERONIMO-1527: Patches added: Adding geronimo-spec-javamail/src/main/java/javax/mail/internet/AddressParser.java Sending geronimo-spec-javamail/src/main/java/javax/mail/internet/InternetAddress.java Sending geronimo-spec-javamail/src/main/java/javax/mail/internet/InternetHeaders.java Sending geronimo-spec-javamail/src/test/java/javax/mail/internet/InternetAddressTest.java Transmitting file data Committed revision 373554. Thanks, Rick! > InternetAddress does not properly implement address parsing. > > > Key: GERONIMO-1527 > URL: http://issues.apache.org/jira/browse/GERONIMO-1527 > Project: Geronimo > Type: Improvement > Components: mail > Versions: 1.0 > Environment: All. > Reporter: Rick McGuire > Fix For: 1.1 > Attachments: InternetAddress.patch, InternetHeaders.patch > > The InternetAddress class of the javamail spec package does not properly > implement RFC822 address parsing. This is impacting the ability to implement > full SMTP support, as well as adding POP3 and IMAP support. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1527) InternetAddress does not properly implement address parsing.
[ http://issues.apache.org/jira/browse/GERONIMO-1527?page=all ] Bruce Snyder closed GERONIMO-1527: -- Fix Version: 1.1 Resolution: Fixed Assign To: Bruce Snyder > InternetAddress does not properly implement address parsing. > > > Key: GERONIMO-1527 > URL: http://issues.apache.org/jira/browse/GERONIMO-1527 > Project: Geronimo > Type: Improvement > Components: mail > Versions: 1.0 > Environment: All. > Reporter: Rick McGuire > Assignee: Bruce Snyder > Fix For: 1.1 > Attachments: InternetAddress.patch, InternetHeaders.patch > > The InternetAddress class of the javamail spec package does not properly > implement RFC822 address parsing. This is impacting the ability to implement > full SMTP support, as well as adding POP3 and IMAP support. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1528) javax.mail.BodyPart does not implement setParent() method
[ http://issues.apache.org/jira/browse/GERONIMO-1528?page=all ] Bruce Snyder closed GERONIMO-1528: -- Fix Version: 1.1 Resolution: Fixed Assign To: Bruce Snyder > javax.mail.BodyPart does not implement setParent() method > - > > Key: GERONIMO-1528 > URL: http://issues.apache.org/jira/browse/GERONIMO-1528 > Project: Geronimo > Type: Bug > Components: mail > Versions: 1.0 > Reporter: Rick McGuire > Assignee: Bruce Snyder > Priority: Minor > Fix For: 1.1 > Attachments: BodyPart.patch > > The class javax.mail.BodyPart does not implement the setParent() method > (which the Sun version does do). Since this is an abstract class, concrete > implementations are expected to implement this, which creates a difference > between running with the Sun version vs. the Geronimo version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1530) javax.mail.Service does not properly implement the protocol between javamail infrastructure and transport handlers.
[ http://issues.apache.org/jira/browse/GERONIMO-1530?page=all ] Bruce Snyder closed GERONIMO-1530: -- Fix Version: 1.1 Resolution: Fixed Assign To: Bruce Snyder > javax.mail.Service does not properly implement the protocol between javamail > infrastructure and transport handlers. > --- > > Key: GERONIMO-1530 > URL: http://issues.apache.org/jira/browse/GERONIMO-1530 > Project: Geronimo > Type: Bug > Components: mail > Versions: 1.0 > Reporter: Rick McGuire > Assignee: Bruce Snyder > Fix For: 1.1 > Attachments: Service.patch > > The javamail spec defines a Service.connect() method that performs a number > of setup functions (including authentication) before doing a mail transport > operation by calling a transport's protocolConnect() method. . Currently, > the Geronimo javamail implementation has very incomplete implementation of > the connect method, and the SMTP transport implementation directly overrides > connect rather than perform the connection operation in protocolConnect(). > Implementation of SMTP authentication is dependent on a more complete > implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1530) javax.mail.Service does not properly implement the protocol between javamail infrastructure and transport handlers.
[ http://issues.apache.org/jira/browse/GERONIMO-1530?page=comments#action_12364329 ] Bruce Snyder commented on GERONIMO-1530: Patch added: Sendingsrc/java/javax/mail/Service.java Transmitting file data . Committed revision 373194. > javax.mail.Service does not properly implement the protocol between javamail > infrastructure and transport handlers. > --- > > Key: GERONIMO-1530 > URL: http://issues.apache.org/jira/browse/GERONIMO-1530 > Project: Geronimo > Type: Bug > Components: mail > Versions: 1.0 > Reporter: Rick McGuire > Attachments: Service.patch > > The javamail spec defines a Service.connect() method that performs a number > of setup functions (including authentication) before doing a mail transport > operation by calling a transport's protocolConnect() method. . Currently, > the Geronimo javamail implementation has very incomplete implementation of > the connect method, and the SMTP transport implementation directly overrides > connect rather than perform the connection operation in protocolConnect(). > Implementation of SMTP authentication is dependent on a more complete > implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1528) javax.mail.BodyPart does not implement setParent() method
[ http://issues.apache.org/jira/browse/GERONIMO-1528?page=comments#action_12364328 ] Bruce Snyder commented on GERONIMO-1528: Committed: Sendingsrc/java/javax/mail/BodyPart.java Transmitting file data . Committed revision 373193. > javax.mail.BodyPart does not implement setParent() method > - > > Key: GERONIMO-1528 > URL: http://issues.apache.org/jira/browse/GERONIMO-1528 > Project: Geronimo > Type: Bug > Components: mail > Versions: 1.0 > Reporter: Rick McGuire > Priority: Minor > Attachments: BodyPart.patch > > The class javax.mail.BodyPart does not implement the setParent() method > (which the Sun version does do). Since this is an abstract class, concrete > implementations are expected to implement this, which creates a difference > between running with the Sun version vs. the Geronimo version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1527) InternetAddress does not properly implement address parsing.
[ http://issues.apache.org/jira/browse/GERONIMO-1527?page=comments#action_12364327 ] Bruce Snyder commented on GERONIMO-1527: The patch above causes the following compilation problems: [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /Users/bsnyder/src/geronimo/specs/trunk/geronimo-spec-javamail/src/java/javax/mail/internet/InternetHeaders.java:[324,27] parseHeader(java.lang.String,boolean) in javax.mail.internet.InternetAddress cannot be applied to (java.util.List,java.lang.String,boolean,boolean) > InternetAddress does not properly implement address parsing. > > > Key: GERONIMO-1527 > URL: http://issues.apache.org/jira/browse/GERONIMO-1527 > Project: Geronimo > Type: Improvement > Components: mail > Versions: 1.0 > Environment: All. > Reporter: Rick McGuire > Attachments: InternetAddress.patch > > The InternetAddress class of the javamail spec package does not properly > implement RFC822 address parsing. This is impacting the ability to implement > full SMTP support, as well as adding POP3 and IMAP support. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1341) POP3 Implementation
[ http://issues.apache.org/jira/browse/GERONIMO-1341?page=comments#action_12364180 ] Bruce Snyder commented on GERONIMO-1341: The patch has been committed: Adding javamail-transport/src/java/org/apache/geronimo/javamail/store Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3 Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/POP3Command.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/POP3CommandFactory.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/POP3Connection.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/POP3Constants.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/POP3Folder.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/POP3Response.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/POP3ResponseBuilder.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/POP3Store.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/message Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/message/POP3Message.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/message/POP3MessageFactory.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/message/POP3MessageWithContentInfo.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/message/POP3MessageWithEnvelope.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/message/POP3MessageWithFlags.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/response Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/response/DefaultPOP3Response.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/response/POP3ListResponse.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/response/POP3ResponseFactory.java Adding javamail-transport/src/java/org/apache/geronimo/javamail/store/pop3/response/POP3StatusResponse.java Sending javamail-transport/src/resources/META-INF/javamail.default.providers Transmitting file data .. Committed revision 372731. I'm leaving this issue open with the idea that work can continue on this effort from this issue. > POP3 Implementation > --- > > Key: GERONIMO-1341 > URL: http://issues.apache.org/jira/browse/GERONIMO-1341 > Project: Geronimo > Type: New Feature > Components: mail > Versions: 1.0-M5 > Reporter: Rajith Attapattu > Priority: Minor > Fix For: 1.1 > Attachments: javamail.patch > > I have completed the POP3 implementation and the patch is attached. > Comments and code reviews are greatly appreciated. > I have done it in a Geronimo independent way so that the code can be moved > out to a sub project in the future by just changing the package name. > What is done > = > 1. POP3Store, POP3Folder and partial implementation of POP3Message for > JavaMail API > 2. All support classes including factories for POP3Command and POP3Response > and a POP3Connection abstraction. > 3. Can connect, authenticate with user/pass and retrieve mail. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1538) Update the website to use the new look and feel from Epiq
[ http://issues.apache.org/jira/browse/GERONIMO-1538?page=all ] Bruce Snyder updated GERONIMO-1538: --- Summary: Update the website to use the new look and feel from Epiq (was: Update the website to use the new stylesheets and images from Epiq) Description: See the example of the new look and feel for the site here: http://people.apache.org/~bsnyder/geronimo/site/ I've emailed Glenn Wheaton from Epiq asking him to attach the new stylesheets and imagery so that he can grant the ASF a license to the content. was: > Update the website to use the new look and feel from Epiq > - > > Key: GERONIMO-1538 > URL: http://issues.apache.org/jira/browse/GERONIMO-1538 > Project: Geronimo > Type: Improvement > Components: website > Reporter: Bruce Snyder > Assignee: Bruce Snyder > > See the example of the new look and feel for the site here: > http://people.apache.org/~bsnyder/geronimo/site/ > I've emailed Glenn Wheaton from Epiq asking him to attach the new stylesheets > and imagery so that he can grant the ASF a license to the content. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1538) Update the website to use the new stylesheets and images from Epiq
Update the website to use the new stylesheets and images from Epiq -- Key: GERONIMO-1538 URL: http://issues.apache.org/jira/browse/GERONIMO-1538 Project: Geronimo Type: Improvement Components: website Reporter: Bruce Snyder Assigned to: Bruce Snyder -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1439) Precompile JSPs in all apps (e.g., console, daytrader, etc.)
Precompile JSPs in all apps (e.g., console, daytrader, etc.) Key: GERONIMO-1439 URL: http://issues.apache.org/jira/browse/GERONIMO-1439 Project: Geronimo Type: Improvement Components: sample apps Reporter: Bruce Snyder Priority: Minor Add a goal to precompile JSPs throughout the sample apps, console, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1427) Create a stripped down assembly that includes ActiveMQ, Derby, Jetty/Tomcat and transaction
Create a stripped down assembly that includes ActiveMQ, Derby, Jetty/Tomcat and transaction - Key: GERONIMO-1427 URL: http://issues.apache.org/jira/browse/GERONIMO-1427 Project: Geronimo Type: New Feature Components: general Versions: 1.1 Reporter: Bruce Snyder -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1332) Allow deployment and use of exploded modules (e.g., EARs, JARs, WARs, etc.)
[ http://issues.apache.org/jira/browse/GERONIMO-1332?page=all ] Bruce Snyder updated GERONIMO-1332: --- Version: 1.0 > Allow deployment and use of exploded modules (e.g., EARs, JARs, WARs, etc.) > --- > > Key: GERONIMO-1332 > URL: http://issues.apache.org/jira/browse/GERONIMO-1332 > Project: Geronimo > Type: Improvement > Components: deployment > Versions: 1.0 > Reporter: Bruce Snyder > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1332) Allow deployment and use of exploded modules (e.g., EARs, JARs, WARs, etc.)
Allow deployment and use of exploded modules (e.g., EARs, JARs, WARs, etc.) --- Key: GERONIMO-1332 URL: http://issues.apache.org/jira/browse/GERONIMO-1332 Project: Geronimo Type: Improvement Components: deployment Reporter: Bruce Snyder -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=comments#action_12319053 ] Bruce Snyder commented on GERONIMO-851: --- Yes, I'm interested in helping with this effort. I was going to go through a conversion of Castor's Maven build from Maven 1 to Maven 2 before pursuing this effort. Castor's Maven build is very straightforward and far less complex than Geronimo's multiproject Maven build. My assumption is that the conversion of Castor's Maven build will be a good preparation step to the conversion of the Geronimo build. > Move Geronimo Build to M2 (Maven 2) > --- > > Key: GERONIMO-851 > URL: http://issues.apache.org/jira/browse/GERONIMO-851 > Project: Geronimo > Type: Task > Components: buildsystem > Reporter: John Sisson > Assignee: John Sisson > Fix For: 1.0 > > Created this issue to keep track of the status of work to move the Geronimo > build to Maven 2. Does anyone know the status of this effort? I believe some > work was done in OpenEJB? When is the move to M2 planned for? 1.0 or 1.1 > FYI.. In June I attempted to use Maven 1.1 beta 1 to build geronimo and got > some parse exceptions in maven. As a result, some small changes were made to > some project.xml files by David Jencks, which fixed the parse problem, but we > then ran into another problem where we were getting a > java.lang.NoSuchMethodError in maven. This should now be fixed using an > updated artifact plugin, see http://jira.codehaus.org/browse/MAVEN-1625 (but > I have not verified this). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-875) Eclipse Geronimo Server Adapter
[ http://issues.apache.org/jira/browse/GERONIMO-875?page=comments#action_12318930 ] Bruce Snyder commented on GERONIMO-875: --- What's the rationale behind checking this into the sandbox when we are still discussing it as the first potential subproject (see the discussion about this on the dev@ list here: http://tinyurl.com/anujw)? > Eclipse Geronimo Server Adapter > --- > > Key: GERONIMO-875 > URL: http://issues.apache.org/jira/browse/GERONIMO-875 > Project: Geronimo > Type: New Feature > Reporter: Sachin Patel > Assignee: Dain Sundstrom > Fix For: 1.0-M5 > Attachments: geronimo-server-adapter.zip > > Attached is the Geronimo Server Adapter for WTP/Eclipse. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-693) Need startup scripts in bin directory
[ http://issues.apache.org/jira/browse/GERONIMO-693?page=comments#action_12318246 ] Bruce Snyder commented on GERONIMO-693: --- I agree, David. I was already looking at that tool. > Need startup scripts in bin directory > - > > Key: GERONIMO-693 > URL: http://issues.apache.org/jira/browse/GERONIMO-693 > Project: Geronimo > Type: New Feature > Components: usability > Environment: Windows, Linux, Mac OS X > Reporter: Erin Mulder > Assignee: John Sisson > Priority: Minor > > It would be nice to have obvious startup.sh and startup.bat scripts in the > bin directory so that the user doesn't need to look at the README file to > figure out how to start the server. (java -jar bin/server.jar isn't hard -- > it's just not quite as brainless as a script called "startup"). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-693) Need startup scripts in bin directory
[ http://issues.apache.org/jira/browse/GERONIMO-693?page=comments#action_12317031 ] Bruce Snyder commented on GERONIMO-693: --- I just checked in the beginnings of a startup shell script in the scripts directory. I need to figure out how to copy it into the assembly/target/geronimo-1.0-SNAPSHOT/bin/ directory during the build process. > Need startup scripts in bin directory > - > > Key: GERONIMO-693 > URL: http://issues.apache.org/jira/browse/GERONIMO-693 > Project: Geronimo > Type: New Feature > Components: usability > Environment: Windows, Linux, Mac OS X > Reporter: Erin Mulder > Assignee: John Sisson > Priority: Minor > > It would be nice to have obvious startup.sh and startup.bat scripts in the > bin directory so that the user doesn't need to look at the README file to > figure out how to start the server. (java -jar bin/server.jar isn't hard -- > it's just not quite as brainless as a script called "startup"). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-778) Geronimo XDoclet 1.2.2 module contribution
[ http://issues.apache.org/jira/browse/GERONIMO-778?page=comments#action_12316866 ] Bruce Snyder commented on GERONIMO-778: --- Why not just contribute this to the XDoclet project? I hazard a guess the XDoclet team might offer you committer status to keep working on it. Let it be built as part of XDoclet and Geronimo will simply be a consumer of it. There's no need for the G build to grab and build all of XDoclet. > Geronimo XDoclet 1.2.2 module contribution > -- > > Key: GERONIMO-778 > URL: http://issues.apache.org/jira/browse/GERONIMO-778 > Project: Geronimo > Type: New Feature > Reporter: John Sisson > Assignee: John Sisson > Priority: Minor > Attachments: geronimo-xdoclet.zip > > In December 2004 I did done some work on XDoclet 1.2.2 support for Geronimo > but did not get around to contributing it. Currently it supports the > generation of the openejb-jar.xml file for session and message-driven beans. > See the following mail thread for discussion on this contribution. > http://marc.theaimsgroup.com/?t=11200245871&r=1&w=2 > Note that there are a number of issues discussed below that need to be > resolved before this is ready to be included with Geronimo releases. In > other words, it isn't complete :-). > How to build > === > 1. Download the appropriate (zip/tar) xdoclet-src-1.2.2 file from > http://sourceforge.net/project/showfiles.php?group_id=31602: > 2. Extract the xdoclet-src-1.2.2-* file you downloaded > 3. Copy the geronimo directory (in the attached zip file) to the > xdoclet-1.2.2\modules directory > 4. Build the XDoclet code by running ant ( ant 1.5 works, later versions get > an error) in the xdoclet-1.2.2 directory. After the build has completed the > xdoclet-1.2.2\target\lib directory should contain > xdoclet-geronimo-module-1.2.2.jar . > 5. Generate the html documentation (it will be placed in the > xdoclet-1.2.2\target\docs directory) by issuing the command "maven > site:generate" in the xdoclet-1.2.2 directory. After the documentation has > been generated you should be able to see the documentation for the geronimo > XDoclet tags in the file xdoclet-1.2.2/target/docs/tags/geronimo-tags.html . > Note that a link to the geronimo tags is not added to the main XDoclet page ( > xdoclet-1.2.2/target/docs/index.html ) so it seems the link has to be added > manually. > Issues to discuss > == > * how to integrate into Geronimo build. Currently to build the Geronimo > XDoclet module, it requires the XDoclet source code to be available. It may > be possible to write some ant/maven build files that can build the geronimo > XDoclet module without requiring the Xdoclet source code download (although I > haven't seen any other projects build an XDoclet module this way yet). > * create test application utilising the geronimo XDoclet tags > * currently the configId attribute must be specified in the ant file when > invoking the geronimo subtask. The configId value is placed in the generated > plan. The parentId attribute can also be optionally specified. Is this the > best way? See documentation in the file > xdoclet-1.2.2/target/docs/ant/xdoclet/modules/geronimo/ejb/GeronimoSubTask.html > . > * the tag parameter names match the xml element names in the deployment plan, > but for the parameters used to specify portions of jsr-77 object names (e.g. > domain, server, application, module, ..), I have prefixed the parameter with > objname- to make it clearer that they are part of a group. > *Should the parameter names (e.g. the ref-name parameter of the > @geronimo.resource-ref tag) should be more consistent with the parameters of > the @ejb tags (e.g. the res-refname parameter of the @ejb.resource-ref tag). > * Should we be trying to have unique parameter names so that it is easier to > search for the particular parameter. For example, currently the ref-name > parameter is used on the @geronimo.ejb-local-ref , @geronimo.ejb-ref and > @geronimo.resource-ref tags. If we do change the parameter names to be > unique it will mean the parameter names will no longer match the generated > XML element names (this may make troubleshooting generated XML harder). > Further work to be done > > the following contributions/help by others are welcome :-) : > - Improvements to the tag documentation ( > xdoclet-1.2.2/target/docs/tags/geronimo-tags.html ) > - web support > - web services support > - entity beans support > - GBeans support > - Corba support > - Testing with Eclipse WTP and other IDEs -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-512) non-reference gbean dependencies
[ http://issues.apache.org/jira/browse/GERONIMO-512?page=comments#action_62753 ] Bruce Snyder commented on GERONIMO-512: --- It would be really nice if this feature could be expressed dynamically in the respective descriptor. This would allow users to define what *they* want loaded first on a per application basis. > non-reference gbean dependencies > > > Key: GERONIMO-512 > URL: http://issues.apache.org/jira/browse/GERONIMO-512 > Project: Geronimo > Type: New Feature > Components: kernel > Versions: 1.0-M3 > Reporter: David Jencks > Assignee: Dain Sundstrom > > Currently there is no way to make gbeans start in a particular order unless > they have a reference to each other. This is unsatisfactory as for instance > one might open a server socket the other wants to connect to. Also, jndi > refs are not reflected in the gbean dependency graph. > So far the best idea seems to be to add a list of dependencies (object names > or their successors) to GBeanData, and add these to the dependency manager on > startup (and presumably remove them on shutdown). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-546) web service client xsd has been modified... change it back
[ http://issues.apache.org/jira/browse/GERONIMO-546?page=comments#action_58289 ] Bruce Snyder commented on GERONIMO-546: --- Upon further investigation, I figured out that the j2ee_1_4.xsd includes the j2ee_web_services_client_1_1.xsd. Running the j2ee_1_4.xsd through the Castor Source Generator works just fine. > web service client xsd has been modified... change it back > -- > > Key: GERONIMO-546 > URL: http://issues.apache.org/jira/browse/GERONIMO-546 > Project: Apache Geronimo > Type: Bug > Components: deployment > Versions: 1.0-M3 > Reporter: David Jencks > Assignee: David Jencks > > in revision 125988 I commented out a key/uniqueness constraint in > modules/j2ee-schema/src/j2ee_1_4schema/j2ee_web_services_client_1_1.xsd > that xmlbeans 1.0 cannot deal with. After switching to xmlbeans 2 this > change should be reverted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-546) web service client xsd has been modified... change it back
[ http://issues.apache.org/jira/browse/GERONIMO-546?page=comments#action_58165 ] Bruce Snyder commented on GERONIMO-546: --- I tried to run this XSD through the Castor Source Generator and it blew up because it couldn't find the 'j2ee:descriptionGroup' group. It seems that it never imports any schema associated with the 'j2ee' prefix, nor does the schema define locally any group named 'j2ee:descriptionGroup'. Seeing as how this XSD came from Sun, I'm not sure what to think. Am I missing something here? > web service client xsd has been modified... change it back > -- > > Key: GERONIMO-546 > URL: http://issues.apache.org/jira/browse/GERONIMO-546 > Project: Apache Geronimo > Type: Bug > Components: deployment > Versions: 1.0-M3 > Reporter: David Jencks > Assignee: David Jencks > > in revision 125988 I commented out a key/uniqueness constraint in > modules/j2ee-schema/src/j2ee_1_4schema/j2ee_web_services_client_1_1.xsd > that xmlbeans 1.0 cannot deal with. After switching to xmlbeans 2 this > change should be reverted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
