purge the dependency of cookie for admin console login
--
Key: GERONIMO-1496
URL: http://issues.apache.org/jira/browse/GERONIMO-1496
Project: Geronimo
Type: Improvement
Components: console
Versions: 1.0
DatabasePoolPortlet Unable to save connection pool
--
Key: GERONIMO-1497
URL: http://issues.apache.org/jira/browse/GERONIMO-1497
Project: Geronimo
Type: Bug
Components: console
Versions: 1.0
Reporter:
Alan D. Cabrera wrote:
Here is the incubation proposal
http://wiki.apache.org/incubator/CorbaProposal
I'm interested in assisting with this. I was wrote the adapter code
that allowed IBM's WAS CE product to work with the IBM JDK ORB. This
required developing a pretty good understanding of
Alan,
I do have a question about the initial committer list. Since I'm relatively new
to Apache my understanding was that commit was based on previous work. Many of
the names on the list are new to me so I have not had an opportunity to work
with them. Are all the suggested names currently
[ http://issues.apache.org/jira/browse/GERONIMO-1498?page=all ]
Kristian Koehler updated GERONIMO-1498:
---
Attachment: DriverDownloader.DriverInfo.patch
the patch
DriverDownloader.DriverInfo causes java.io.NotSerializableException during
server
DriverDownloader.DriverInfo causes java.io.NotSerializableException during
server shutdown
--
Key: GERONIMO-1498
URL: http://issues.apache.org/jira/browse/GERONIMO-1498
Project:
I like the idea of using an env script/bat implementation. It makes lots of
sense in many ways. I don't think one would be allowing users to directly
modify the scripts but we'd ask for their input and validate it before building
the script. So from that perspective the input mechanism is is
Alan D. Cabrera wrote:
Here is the incubation proposal
http://wiki.apache.org/incubator/CorbaProposal
Does anyone have any comments before we vote on it?
There is a half-finished sentence in the document. In the Initial
Source section it says:
As a side benefit the XMLShema API will also
I'd quite like to be involved in this. I wrote the WebLogic ORB.
andy
At 01:31 PM 1/19/2006, Matt Hogstrom wrote:
Alan,
I do have a question about the initial committer list. Since I'm
relatively new to Apache my understanding was that commit was based
on previous work. Many of the names
The multi-server aspect of this potential new feature had crossed my mind. But I didn't have a firm grasp yet on how the console should behave in a clustered environment. For example, if we decide that some particular node in the cluster will be designated as the manager then its console should be
Daytrader: uncomment the drop table statements in daytrader.sql
Key: GERONIMO-1499
URL: http://issues.apache.org/jira/browse/GERONIMO-1499
Project: Geronimo
Type: Bug
Components: sample apps
[ http://issues.apache.org/jira/browse/GERONIMO-1499?page=all ]
Lin Sun updated GERONIMO-1499:
--
Attachment: G1499-daytrader-sql.patch
Daytrader: uncomment the drop table statements in daytrader.sql
Geronimo-Jetty startup fails after adding and removing an HTTPS Connector
-
Key: GERONIMO-1500
URL: http://issues.apache.org/jira/browse/GERONIMO-1500
Project: Geronimo
Type: Bug
Versions:
Daytrader: remove hardcoded dependency versions in project.xml
---
Key: GERONIMO-1501
URL: http://issues.apache.org/jira/browse/GERONIMO-1501
Project: Geronimo
Type: Bug
Components: sample apps
[ http://issues.apache.org/jira/browse/GERONIMO-1501?page=all ]
Lin Sun updated GERONIMO-1501:
--
Attachment: G1501-ejb.patch
G1501-streamer.patch
G1501-web.patch
Daytrader: remove hardcoded dependency versions in
[ http://issues.apache.org/jira/browse/GERONIMO-1501?page=all ]
Lin Sun updated GERONIMO-1501:
--
Attachment: G1501-wsappclient.patch
Daytrader: remove hardcoded dependency versions in project.xml
Hi, I thinkif this new feature will be in a multi-server/cluster topology there should be new java proccess with specific roles (Manager, Node Agent, App.Server) also I think there shouldbe a Sync service for config files, under this topology the Node Agent must have the resposabiliy of luching
Installer does not install docs on 1.0.1
-
Key: GERONIMO-1502
URL: http://issues.apache.org/jira/browse/GERONIMO-1502
Project: Geronimo
Type: Bug
Components: installer
Versions: 1.0
Reporter: erik daughtrey
[ http://issues.apache.org/jira/browse/GERONIMO-1502?page=all ]
erik daughtrey updated GERONIMO-1502:
-
Attachment: installer-1.0.1-docs.patch
This patch just uncomments docs install that was commented out for trunk patch
because trunk docs are
The missing text...
As a side benefit the XMLShema API will also be able to support other
transports and binding through configuration.
Carl.
-Original Message-
From: Anders Hessellund Jensen [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 19, 2006 10:48 AM
To:
Hi,
I am trying to use the KeyStore ssl-keystore-1 created by KeyStore
portlet to add new HTTPS Listener for Jetty. Self signed
certificate generated by the portlet seems to be fine as I am able to
view the certificate. Upon adding a new HTTPS Listener using this
keystore, I am getting the
[ http://issues.apache.org/jira/browse/GERONIMO-1502?page=all ]
David Jencks closed GERONIMO-1502:
--
Fix Version: 1.0.1
Resolution: Fixed
Assign To: David Jencks
Applied
Sendingj2ee-installer/src/izpack/geronimo-izpack.xml
keystore generated by KeyStore portlet could not be used to add either Jetty or
Tomcat HTTPS Listeners
---
Key: GERONIMO-1503
URL:
Guys,
there seems to be some debate about whether the doc should end up in
Confluence or MoinMoin...
please resolve it and I will publish the doc.
Jules
Hernan Cunico wrote:
Jules has the documentation for clustering and I am suggesting him to
get that documentation published in
[ http://issues.apache.org/jira/browse/GERONIMO-1503?page=all ]
Vamsavardhana Reddy updated GERONIMO-1503:
--
Attachment: GERONIMO-1503.patch
Investigating the problem revealed that only keystorePassword is set for the
KeyStoreGBean. An empty
[ http://issues.apache.org/jira/browse/GERONIMO-1503?page=all ]
Vamsavardhana Reddy updated GERONIMO-1503:
--
Geronimo Info: [Patch Available]
Fix Version: 1.0.1
Version: 1.0.1
1.1
keystore generated by
Rajith Attapattu wrote:
Ok, I am not fixed on multiple-active-sessions.
But my concern is high availability with single-active-session model
under high load conditions.
As u pointed out,
In the web world, clients commonly throw multiple concurrent requests at
clusters, however, if we could
Hi All,
With you help I have been developing a small
application. The goal is very simple, we have 3
GBeans: MyGBean, APrinterGBean and BPrinterGBean.
MyGBean invokes a print operation on the two
printers which it references and gets via dependency
injection.
MyGBean prints MyGBean when
Anders Hessellund Jensen wrote, On 1/19/2006 7:48 AM:
Alan D. Cabrera wrote:
Here is the incubation proposal
http://wiki.apache.org/incubator/CorbaProposal
Does anyone have any comments before we vote on it?
There is a half-finished sentence in the document. In the Initial
Source section
Fixed!
Regards,
Alan
Trieloff, Carl wrote, On 1/19/2006 9:13 AM:
The missing text...
As a side benefit the XMLShema API will also be able to support other transports
and binding through configuration.
Carl.
-Original Message-
From: Anders Hessellund Jensen [mailto:[EMAIL
This is a good question. Do we have any Apache sages to provide any
guidance?
IIUC, non-commiters get commit privs but must prove themselves during
incubation, i.e. they could get their commit privs taken away.
Regards,
Alan
Matt Hogstrom wrote, On 1/19/2006 5:31 AM:
Alan,
I do have a
I think you have named your printer gbeans with keys name=gbean1 and
name=gbean2 but the references expect them to be named
name=APrinterGBean and name=BPrinterGBean.
You can look in var/log/geronimo.log for debug messages about why
MyGBean didn't start: it will tell you what it is looking
Before voting on this proposal or sending it to the incubator list, I
want to clarify the first paragraph under Initial Source. Aside
from the Trifork contribution, the rest of the paragraph really
implies three different sources of code: a) reuse of components in the
ObjectWeb Celtix project, b)
On Thu, 19 Jan 2006, Jules Gosnell wrote:
We should avoid making those decesions before hand.
What decisions does the user need to make?
Users need to make a lot of decisions already. Are the decisions you
mention worth the time it will take for users to make them?
as far as clustering
scout.log is created in current directory when running the installer
Key: GERONIMO-1504
URL: http://issues.apache.org/jira/browse/GERONIMO-1504
Project: Geronimo
Type: Bug
Components: installer
I've made some progress on this and it seems to work OK for basic j2ee
deployments, except for the problem below. It's not pretty but it
does what I need for the time being. If anyone else is interested in
this I could clean it up and post it to the list, and if anyone's got
a tip about the
On Jan 18, 2006, at 10:20 PM, lichtner wrote:
This state is transactional, I take it?
Nope. For OpenEJB, only stateful session beans (SFSB) would use this
api, and SFSBs are not transactional although they can receive a
transaction completion notification which can be used to rollback
[ http://issues.apache.org/jira/browse/GERONIMO-1450?page=all ]
Paul McMahan updated GERONIMO-1450:
---
Attachment: GERONIMO-1450.patch
Attaching a patch that fixes the o/a/g/Server parentId attributes in the sample
plans and also changes the suggested
[ http://issues.apache.org/jira/browse/GERONIMO-1450?page=all ]
Paul McMahan updated GERONIMO-1450:
---
Geronimo Info: [Patch Available]
Console usage plans use old namspace parentId
---
Key:
On Thu, 19 Jan 2006, Dain Sundstrom wrote:
On Jan 18, 2006, at 10:20 PM, lichtner wrote:
This state is transactional, I take it?
Nope. For OpenEJB, only stateful session beans (SFSB) would use this api.
I see. I plan to never use them, if I can help it.
EJB Entity beans in OpenEJB or
[ http://issues.apache.org/jira/browse/GERONIMO-1497?page=all ]
Donald Woods updated GERONIMO-1497:
---
Fix Version: 1.1
Assign To: Donald Woods
DatabasePoolPortlet Unable to save connection pool
--
On Jan 19, 2006, at 12:46 PM, toby cabot wrote:
I've made some progress on this and it seems to work OK for basic j2ee
deployments, except for the problem below. It's not pretty but it
does what I need for the time being. If anyone else is interested in
this I could clean it up and post it
Installer should default Tomcat on at runtime if Jetty pack is not selected
---
Key: GERONIMO-1505
URL: http://issues.apache.org/jira/browse/GERONIMO-1505
Project: Geronimo
Type: Bug
DB info portlet should use new GeronimoVersion
--
Key: GERONIMO-1506
URL: http://issues.apache.org/jira/browse/GERONIMO-1506
Project: Geronimo
Type: Bug
Components: console
Versions: 1.0.1
Reporter: Paul
[ http://issues.apache.org/jira/browse/GERONIMO-1506?page=all ]
Paul McMahan updated GERONIMO-1506:
---
Geronimo Info: [Patch Available]
DB info portlet should use new GeronimoVersion
--
Key:
[ http://issues.apache.org/jira/browse/GERONIMO-1506?page=all ]
Paul McMahan updated GERONIMO-1506:
---
Attachment: GERONIMO-1506.patch
patch uses new GeronimoVersion.GERONIMO_VERSION variable
DB info portlet should use new GeronimoVersion
Looks like the Installer has made quite a bit of progress. Thanks Erik!!
I'd like to suggest a few Usabality changes to the current installer..
I'm sure you are already aware of many of these and have plans to update
them. Just wanted to provide some input based on my first impression.
BTW,
[ http://issues.apache.org/jira/browse/GERONIMO-1505?page=all ]
erik daughtrey updated GERONIMO-1505:
-
Attachment: installer-tomcat-only-wc-config-fix.patch
This patch is for both branches/1.0 and trunk.
It's been tested against both.
This fix
prototype offline deploy tool
-
Key: GERONIMO-1507
URL: http://issues.apache.org/jira/browse/GERONIMO-1507
Project: Geronimo
Type: New Feature
Components: deployment
Versions: 1.0.1
Environment: fedora core 2
Java(TM) 2
When projects start in incubator, yes - anyone on the initial committer
list is given committer status on the incubating project. Because
Geronimo may/is sponsor/ing this as a subproject, when the incubator
project graduates, all committers become Geronimo committers.
You can see an example
Good idea, Paul and Joe.
Every solution I have seen on the web so far lays the onus on the
website developer, in other words, on the application, to protect the
site from XSS vulnerability.
Hmm. isn't there a container fix to it ?
[
http://issues.apache.org/jira/browse/GERONIMO-1456?page=comments#action_12363319
]
Paul McMahan commented on GERONIMO-1456:
The binary distributions (both zip and tgz) also contain a META-INF/manifest.mf
file. It's not at the root level of the
All,
I have copied DayTrader from trunk and been restructuring it to stand alone so
it can be versioned independently from Geronimo. This way performance
comparisons can be made. It is currently located at
https://svn.apache.org/repos/asf/geronimo/daytrader.
You'll currently see a trunk
[ http://issues.apache.org/jira/browse/GERONIMO-1495?page=all ]
Kevan Miller closed GERONIMO-1495:
--
Fix Version: 1.0.1
Resolution: Fixed
Assign To: Kevan Miller
Patch applied. Thanks Erik.
trunk:
Sending
[
http://issues.apache.org/jira/browse/GERONIMO-1437?page=comments#action_12363330
]
Kevan Miller commented on GERONIMO-1437:
I also fixed server-log4j.properties in j2ee-installer (required) and
j2ee-jetty-server (perhaps not necessary but keeps
[ http://issues.apache.org/jira/browse/GERONIMO-1438?page=all ]
Kevan Miller closed GERONIMO-1438:
--
Fix Version: 1.1
Resolution: Fixed
Changed server-log4j.properties to Inhibit catalina StandardContext INFO
messages.
1.0:
Sending
It seems like if we move ahead as planned for 1.0.1 and 1.1, we're
going to ship a product with configIds like
geronimo/j2ee-server/1.0.1/car, which means that many deployment plans
written for 1.0 will not be able to be deployed unmodified on 1.0 --
and it will instantly turn a huge number of
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-50?page=comments#action_12363349
]
Sachin Patel commented on GERONIMODEVTOOLS-50:
--
Could you please send me a copy of the war?
resource reference specified in geronimo-web.xml is not
1.0.1 won't accept plans with 1.0 configIds in references, parents, imports,
etc.
-
Key: GERONIMO-1508
URL: http://issues.apache.org/jira/browse/GERONIMO-1508
Project: Geronimo
Type:
[ http://issues.apache.org/jira/browse/GERONIMO-1449?page=all ]
David Blevins closed GERONIMO-1449:
---
Fix Version: (was: 1.0.1)
(was: 1.1)
Resolution: Fixed
Couple things here. The OpenEJB 2.0 jars that are from the
I am getting a build failure because
schemaorg_apache_xmlbeans.system.sDE11075A2786CB38A6E7975788980259.TypeSystemHolder
can not be resolved.
The class that was generated during the build is -
created binary:
[ http://issues.apache.org/jira/browse/GERONIMO-1370?page=all ]
Kevan Miller closed GERONIMO-1370:
--
Fix Version: 1.0.1
Resolution: Fixed
Merged fix from trunk to 1.0
1.0:
Sending
Maven logging output multipled
--
Key: GERONIMO-1509
URL: http://issues.apache.org/jira/browse/GERONIMO-1509
Project: Geronimo
Type: Bug
Components: transaction manager
Versions: 1.0
Reporter: Aaron Mulder
Priority:
[ http://issues.apache.org/jira/browse/GERONIMO-1449?page=all ]
David Blevins reopened GERONIMO-1449:
-
Cannot build from Geronimo 1.0 src zip - issues with missing dependencies
[ http://issues.apache.org/jira/browse/GERONIMO-1449?page=all ]
David Blevins closed GERONIMO-1449:
---
Resolution: Won't Fix
Ok. It's been made clear to me that there is an issue if you are building from
a completely clean repo. Nothing in
NPE in connector DConfigBeans if no config params present on connection
definition instance
---
Key: GERONIMO-1510
URL: http://issues.apache.org/jira/browse/GERONIMO-1510
Project:
[ http://issues.apache.org/jira/browse/GERONIMO-1510?page=all ]
Aaron Mulder updated GERONIMO-1510:
---
Attachment: dconfigbeans.patch
jms.rar
Patch against 1.0 branch attached; fixes this bug and adds test with JMS RAR.
Still doesn't
Rewrite JMS portlet
---
Key: GERONIMO-1511
URL: http://issues.apache.org/jira/browse/GERONIMO-1511
Project: Geronimo
Type: Improvement
Components: ActiveMQ, connector, console
Versions: 1.0
Reporter: Aaron Mulder
Fix For: 1.1
Database driver download portlet should take HTTP proxy
---
Key: GERONIMO-1512
URL: http://issues.apache.org/jira/browse/GERONIMO-1512
Project: Geronimo
Type: Improvement
Components: console
Versions: 1.0
[ http://issues.apache.org/jira/browse/GERONIMO-1513?page=all ]
John Sisson updated GERONIMO-1513:
--
Priority: Minor (was: Major)
The directory geronimo-1.0\lib\extension does not match the
Extension-Dirs: lib/ext value in server.jar's manifest.mf
On Jan 19, 2006, at 7:02 PM, anita kulshreshtha wrote:
I am getting a build failure because
schemaorg_apache_xmlbeans.system.sDE11075A2786CB38A6E7975788980259.Typ
eSystemHolder
can not be resolved.
The class that was generated during the build is -
created binary:
73 matches
Mail list logo
