Connector deployer fails for plans with no parent ID
Key: GERONIMO-1359
URL: http://issues.apache.org/jira/browse/GERONIMO-1359
Project: Geronimo
Type: Bug
Components: deployment, connector
Versions: 1.0
[ http://issues.apache.org/jira/browse/GERONIMO-1359?page=all ]
Aaron Mulder resolved GERONIMO-1359:
Resolution: Fixed
Aaron checked in fix on 1.0 branch, David J on trunk
Connector deployer fails for plans with no parent ID
test.
test.
I'd like to know if we have to rename the packages to
org.apache.servicemix.* or if we can keep the current ones
org.servicemix.*.
I think that we also have to modify the headers of all sources to
include apache license, but i want to be sure about that.
Also what copyright should be used, as
This fix seems to have exposed an issue where the connector builder
failed to deploy plans where no parent ID was specified (instead of
using the configured default). David J and I have checked in a fix
for that. I also fixed the problem where the j2ee-installer assembly
failed on missing
Hi there,
correction to my previous mail:
1) The strange split of all files between the two src archives was a
failure on my side. Actually there are exactly the same files in both zip
and tarball.
2) The problem with chopped off last characters in file names to some
extent still exists, but it
I recently experienced trouble deploying an ear file containing a war
module. After a lot of head scratching (and waste of Aaron's time) I
discovered that the source of the error was that the jetty-deployer
wasn't started.
The error returned by the deployer was Module was not a war:
Hi,
the JaxMe project contains a clean room implementation of the JAXB API
1.1. As future versions of J2EE will contain the JAXB API, I propose
that these be moved to the other Geronimo J2EE spec implementations.
Jochen
--
Often it does seem a pity that Noah and his party did not miss the
boat.
Concerning my mails related to strange behaviour of the release tarballs:
There is an incompatibility between gnu tar and other tars as well as
different versions of gnu tar whenever the name of a file (including path)
is exactly 100 chars long. POSIX allows exactly 100 chars without using
Misleading error for missing web deployer
-
Key: GERONIMO-1360
URL: http://issues.apache.org/jira/browse/GERONIMO-1360
Project: Geronimo
Type: Bug
Components: deployment
Versions: 1.0
Reporter: Aaron Mulder
---BeginMessage---
In geronimo-tomcat-j2ee-1.0.zip i tried to deploy an ear application that was
working in M4. with a few changes (new configid format
groupId/artifactId/version/type) it started working.
But i see following two modules throwing error (TradeEJB and
ActiveMQActivationSpec)
CMP having a compound PK with only one fields are not supported
---
Key: GERONIMO-1361
URL: http://issues.apache.org/jira/browse/GERONIMO-1361
Project: Geronimo
Type: Bug
Components: OpenEJB
[ http://issues.apache.org/jira/browse/GERONIMO-1361?page=all ]
Gianny Damour updated GERONIMO-1361:
Summary: CMP having a compound PK with only one field are not supported
(was: CMP having a compound PK with only one fields are not supported)
[ http://issues.apache.org/jira/browse/GERONIMO-1361?page=all ]
Gianny Damour closed GERONIMO-1361:
---
Resolution: Fixed
This was a TranQL issue, which was wrongly trying to identify compound PK based
on the number of primary key fields.
Thanks
Hi Gianny,
Was just seeing the fix you made. 1 question on that.
In CMPContainerBuilder there are 2 methods
private FaultHandler buildFaultHandler(SQLQueryBuilder queryBuilder,
EJB definingEJB, CMRField field, int slot, boolean prefetch) throws
QueryException
and
private LinkedHashMap
I had this figured out several weeks ago, but can't seem to get this
working now. I'm trying to make some changes to the
geronimo-specs-javamail code, but can't seem to get this to build.
What's the procedure for building this code? I'm working with the HEAD
version.
Rick
Hi Aaron,
I'm happy to cut a 1.2.2 TranQL release tomorrow night. However, and as
pointed out by Manu, there was also an OpenEJB impact. So, it seems that
we also need to re-cut an OpenEJB release. So far, I have checked in the
fix to trunk and I will port the fix to the v2_0 branch if we
Author: jstrachan
Date: Wed Dec 14 05:45:12 2005
New Revision: 356776
URL: http://svn.apache.org/viewcvs?rev=356776view=rev
Log:
removed possible threading error
Modified:
incubator/activemq/trunk/activeio/src/java/org/activeio/journal/active/ControlFile.java
Modified:
You are right! And thanks for reviewing my commits :)
Indeed, buildFaultHandler is still creating the wrong type of
IdentityDefiner. I thought that all dependencies on the various
IdentityDefiner implementations were removed from OpenEJB thanks to the
introduction of IdentityDefinerBuilder;
Once the discussion is done can one of you guys put an update on the
list for the less fortunate souls like me who couldn't attend
ApacheCon??
Regards,
Rajith Attapattu.
-Original Message-
From: Jules Gosnell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 13, 2005 8:35 PM
To:
I'll create a JIRA with a patch and instructions on applying the patch.
On Wednesday 14 December 2005 02:24, Aaron Mulder wrote:
That happens on the continuum build machines, but so far not on my
machine. It's kind of not so bad since we aren't distributing the
installer yet. But I'm not
I'm still seeing the failure with the 1.0 branch Rev356751 from this
morning, using Maven 1.1Beta2 and a clean local maven repo and cache...
+
| configurations Server Configuration for the J2EE Server
| Memory: 29M/42M
[
http://issues.apache.org/jira/browse/GERONIMO-1329?page=comments#action_12360434
]
Guillaume Nodet commented on GERONIMO-1329:
---
I'm willingfull to provide a patch for this issue and GERONIMO-1330, using the
way i described in my previous post.
Release notes changes just before 1.0 tag cut caused installer build errors
---
Key: GERONIMO-1362
URL: http://issues.apache.org/jira/browse/GERONIMO-1362
Project: Geronimo
Type: Bug
[ http://issues.apache.org/jira/browse/GERONIMO-1362?page=all ]
erik daughtrey updated GERONIMO-1362:
-
Version: 1.0
(was: 1.0-M5)
Release notes changes just before 1.0 tag cut caused installer build errors
[ http://issues.apache.org/jira/browse/GERONIMO-1362?page=all ]
erik daughtrey updated GERONIMO-1362:
-
Attachment: installer-1.0-build.patch
This patch fixes the 1.0 build problem related to the IzPack based installer.
To apply the patch:
1.
Two other build questions:
1) Should /pom.xml be referencing the old geronimo-spec-* JARs, or is
this file only used by Maven 2?
2) Where are the OpenEJB 2.0 released files, since
etc\project.properties has openejb_version=2.0, but they could not be
found on any of the listed Maven repos? Why
Author: jstrachan
Date: Wed Dec 14 09:34:16 2005
New Revision: 356814
URL: http://svn.apache.org/viewcvs?rev=356814view=rev
Log:
fixed bug that prevented the initialReconnectDelay value from being changed
Modified:
Author: jstrachan
Date: Wed Dec 14 09:35:27 2005
New Revision: 356815
URL: http://svn.apache.org/viewcvs?rev=356815view=rev
Log:
added test case which demonstrates that you can start a JMS connection even
when the broker is not there
Added:
DayTrader still using old geronimo-spec files
-
Key: GERONIMO-1363
URL: http://issues.apache.org/jira/browse/GERONIMO-1363
Project: Geronimo
Type: Bug
Components: sample apps
Versions: 1.0
Environment: 1.0
Below problem has been resolved. I had to delete and checkout the
OpenEJB source again using m:co to resolve the build failure.
We really need the OpenEJB 2.0 files published or JIRA-1317 integrated
into AG 1.0 to keep others from hitting the same problems, given the
default new maven goals
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 assuming the binaries pass the TCK
Geir Magnusson Jr. wrote, On 12/13/2005 9:18 PM:
+1 assuming the binaries pass the TCK
On Dec 13, 2005, at 8:30 PM, Matt Hogstrom wrote:
We are currently going through the final testing phases and have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rick McGuire wrote, On 12/14/2005 5:08 AM:
I had this figured out several weeks ago, but can't seem to get this
working now. I'm trying to make some changes to the
geronimo-specs-javamail code, but can't seem to get this to build.
What's the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jochen Wiedmann wrote, On 12/14/2005 1:46 AM:
Hi,
the JaxMe project contains a clean room implementation of the JAXB API
1.1. As future versions of J2EE will contain the JAXB API, I propose
that these be moved to the other Geronimo J2EE spec
Since JaxMe is at Apache, you can move it over with svn mv.
Has the JaxMe community as a whole voted to do this? I think it makes
sense, it would just be good to ensure everyone agrees. It will also
impact the committer list for Geronimo.
Cheers,
Brett
On 12/14/05, Alan D. Cabrera [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill Stoddard wrote, On 12/13/2005 2:21 PM:
[EMAIL PROTECTED] wrote:
Author: adc
Date: Mon Dec 12 23:39:50 2005
New Revision: 356499
URL: http://svn.apache.org/viewcvs?rev=356499view=rev
Log:
made a copy
Added:
Author: jstrachan
Date: Wed Dec 14 11:00:44 2005
New Revision: 356827
URL: http://svn.apache.org/viewcvs?rev=356827view=rev
Log:
better logging on startup to reveal the journal configuration
Modified:
Author: geirm
Date: Wed Dec 14 11:03:25 2005
New Revision: 356828
URL: http://svn.apache.org/viewcvs?rev=356828view=rev
Log:
added a newline just to test the commit mail stream
Modified:
incubator/servicemix/trunk/maven.xml
Modified: incubator/servicemix/trunk/maven.xml
URL:
Rick,
I've built the specs successfully using maven 2 (maven 2.0.1 doesn't
work). 'mvn install' works fine... Hmmm. Just noticed that the version
of the jars being built is '1.0'. This should be changed to
'1.0-SNAPSHOT' or '1.x-SNAPSHOT'.
BTW, what changes are needed to the javamail spec?
[ http://issues.apache.org/jira/browse/GERONIMO-1362?page=all ]
Aaron Mulder closed GERONIMO-1362:
--
Fix Version: 1.0
Resolution: Invalid
Assign To: Aaron Mulder
This patch is so... yesterday! (which is to say thanks, but we already
Brett Porter wrote:
Since JaxMe is at Apache, you can move it over with svn mv.
Exactly. However, initially, I'd prefer a copy operation. (No idea,
whether that's as easy in SVN.) That would give a smoother step. We
could wait until the generated jar files do meet the Maven repositories
and
Kevan Miller wrote:
Rick,
I've built the specs successfully using maven 2 (maven 2.0.1 doesn't
work). 'mvn install' works fine... Hmmm. Just noticed that the version
of the jars being built is '1.0'. This should be changed to
'1.0-SNAPSHOT' or '1.x-SNAPSHOT'.
Does this require maven 2 to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rick McGuire wrote, On 12/14/2005 11:58 AM:
Kevan Miller wrote:
Rick,
I've built the specs successfully using maven 2 (maven 2.0.1 doesn't
work). 'mvn install' works fine... Hmmm. Just noticed that the version
of the jars being built is '1.0'.
Hi all,
I've been experimenting with creating an rpm with Geronimo, but rpm does
not like spaces in filenames and there are some html documentation that
contain spaces in them. Is there a chance to standardize naming to not
contain spaces to make it more unix/linux friendly?
Under
+1 from me.
On 12/13/05, Matt Hogstrom [EMAIL PROTECTED] wrote:
We are currently going through the final testing phases and have the binary
images available for review. These images represent what we will be making
available to users after we confirm the final set of tests.
Please take some
Alan D. Cabrera wrote:
The stuff in geronimo/specs was always on maven 2.
Whow, I didn't know that. I'm on Maven 1 and can't remember whether or
not I tried to build them at any time, but if I had been asked about
specs and Maven version, I would've answer there was no dependency and
any
I'd like to know if we have to rename the packages to
org.apache.servicemix.* or if we can keep the current ones
org.servicemix.*.
I think that we also have to modify the headers of all sources to
include apache license, but i want to be sure about that.
Also what copyright should be used, as
Jacek Laskowski wrote:
Alan D. Cabrera wrote:
The stuff in geronimo/specs was always on maven 2.
Whow, I didn't know that. I'm on Maven 1 and can't remember whether or
not I tried to build them at any time, but if I had been asked about
specs and Maven version, I would've answer there
update welcome pages to point at HTTP redirects in the geronimo.apache.org site
---
Key: GERONIMO-1364
URL: http://issues.apache.org/jira/browse/GERONIMO-1364
Project: Geronimo
Type:
[ http://issues.apache.org/jira/browse/GERONIMO-1364?page=all ]
Paul McMahan updated GERONIMO-1364:
---
Attachment: GERONIMO-1364.patch
patch contains the updated welcome pages
update welcome pages to point at HTTP redirects in the geronimo.apache.org
[
http://issues.apache.org/jira/browse/GERONIMO-1318?page=comments#action_12360458
]
Paul McMahan commented on GERONIMO-1318:
Alan, there was some confusion about how the welcome pages would be updated.
Please see JIRA 1364.
[ http://issues.apache.org/jira/browse/GERONIMO-1364?page=all ]
Paul McMahan updated GERONIMO-1364:
---
Version: 1.0
update welcome pages to point at HTTP redirects in the geronimo.apache.org
site
Jakob Færch (Trifork) wrote:
I'll just continue working with the jetty-j2ee distribution I managed to
build yesterday.
At last I could build the latest version of Geronimo. It wasn't that
easy as it should be. I remember having to run maven several times
before all jars were in place and
JSR-88 Manfest has incorrect Class-Path entries
---
Key: GERONIMO-1365
URL: http://issues.apache.org/jira/browse/GERONIMO-1365
Project: Geronimo
Type: Bug
Components: deployment
Versions: 1.0
Reporter:
Yanking my +1. The binaries are flawed.
-David
On Dec 13, 2005, at 9:53 PM, David Blevins wrote:
Files uploaded! Here is my +1 baring any tck failures.
-David
On Dec 13, 2005, at 8:30 PM, Matt Hogstrom wrote:
We are currently going through the final testing phases and have
the binary
Maven deployment plugin should use deployer stored username/password
Key: GERONIMO-1366
URL: http://issues.apache.org/jira/browse/GERONIMO-1366
Project: Geronimo
Type: Improvement
Components:
Shutdown JAR should use deployer stored username/password
-
Key: GERONIMO-1367
URL: http://issues.apache.org/jira/browse/GERONIMO-1367
Project: Geronimo
Type: Improvement
Components: startup/shutdown,
Remote deployment probably doesn't handle exploded JARs
---
Key: GERONIMO-1368
URL: http://issues.apache.org/jira/browse/GERONIMO-1368
Project: Geronimo
Type: Bug
Components: deployment
Versions: 1.0
[ http://issues.apache.org/jira/browse/GERONIMO-1363?page=all ]
Matt Hogstrom closed GERONIMO-1363:
---
Resolution: Fixed
Sendingdaytrader/ejb/project.xml
Sendingdaytrader/streamer/project.xml
Sendingdaytrader/web/project.xml
[ http://issues.apache.org/jira/browse/GERONIMO-1363?page=all ]
Matt Hogstrom reopened GERONIMO-1363:
-
Assign To: Matt Hogstrom
Re-opened...I applied this to head. Since we're going to have to re-spin 1.0
I'll apply the fix there after
[ http://issues.apache.org/jira/browse/GERONIMO-1363?page=all ]
Matt Hogstrom updated GERONIMO-1363:
Fix Version: 1.0
1.1
DayTrader still using old geronimo-spec files
-
Key:
Jacek Laskowski wrote:
At last I could build the latest version of Geronimo. It wasn't that
easy as it should be. I remember having to run maven several times
before all jars were in place and the build finished with no errors.
I'm looking into getting AB up and running in it.
My status is
javax.ejb.NoSuchObjectLocalException in the
ServletContextListener.contextInitialized() method
--
Key: GERONIMO-1369
URL: http://issues.apache.org/jira/browse/GERONIMO-1369
Project:
[ http://issues.apache.org/jira/browse/GERONIMO-1369?page=all ]
Alexander Korostov updated GERONIMO-1369:
-
Attachment: test.zip
geronimo.log and test application.
javax.ejb.NoSuchObjectLocalException in the
65 matches
Mail list logo
