You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by harikaried <ed...@gmail.com> on 2008/07/07 21:21:01 UTC
Day Trader deploy Cloudscape issues: "can't resolve admin object
ref"
I'm trying to deploy Day Trader with the embedded Cloudscape db with the
following command:
$GERONIMO_HOME/bin/deploy.sh deploy
modules/ear/target/daytrader-ear-2.0-SNAPSHOT.ear
plans/daytrader-g-2.0-SNAPSHOT-plan.xml
It gives the following error:
Error: Unable to distribute daytrader-ear-2.0-SNAPSHOT.ear: Can not resolve
admin object ref ?j2eeType=JCAAdminObject,name=jms/TradeBrokerQueue# in
configuration
org.apache.geronimo.daytrader/daytrader_web.war/2.0-SNAPSHOT/car
No matches for referencePatterns:
[?j2eeType=JCAAdminObject,name=jms/TradeBrokerQueue#]
The geronimo server is giving some warnings, but they don't seem related:
Retrieving document at 'WEB-INF/wsdl/TradeServices.wsdl'.
WARN [HeavyweightTypeInfoBuilder] No soap array info for schematype:
T=QuoteDataBean@http://daytrader.samples.geronimo.apache.org
Repeated for types HoldingDataBean, OrderDataBean, ArrayOfOrderDataBean,
ArrayOfQuoteDataBean, ArrayOfHoldingDataBean
WARN [EARConfigBuilder] Unable to delete 6 files while recursively deleting
directory
geronimo-tomcat6-javaee5-2.1.1/repository/org/apache/geronimo/daytrader/daytrader/2.0-SNAPSHOT/daytrader-2.0-SNAPSHOT.car
--
View this message in context: http://www.nabble.com/Day-Trader-deploy-Cloudscape-issues%3A-%22can%27t-resolve-admin-object-ref%22-tp18324559s134p18324559.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Day Trader deploy Cloudscape issues: "can't resolve admin
object ref"
Posted by harikaried <ed...@gmail.com>.
Jacek Laskowski wrote:
>
> On Mon, Jul 7, 2008 at 9:21 PM, harikaried <ed...@gmail.com> wrote:
>> $GERONIMO_HOME/bin/deploy.sh deploy
>> modules/ear/target/daytrader-ear-2.0-SNAPSHOT.ear
>> plans/daytrader-g-2.0-SNAPSHOT-plan.xml
> The plan would be of a great help.
http://svn.apache.org/repos/asf/geronimo/daytrader/trunk/plans/daytrader-g-2.0-SNAPSHOT-plan.xml
--
View this message in context: http://www.nabble.com/Day-Trader-deploy-Cloudscape-issues%3A-%22can%27t-resolve-admin-object-ref%22-tp18324559s134p18327325.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Day Trader deploy Cloudscape issues: "can't resolve admin object ref"
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On Mon, Jul 7, 2008 at 9:21 PM, harikaried <ed...@gmail.com> wrote:
>
> I'm trying to deploy Day Trader with the embedded Cloudscape db with the
> following command:
>
> $GERONIMO_HOME/bin/deploy.sh deploy
> modules/ear/target/daytrader-ear-2.0-SNAPSHOT.ear
> plans/daytrader-g-2.0-SNAPSHOT-plan.xml
The plan would be of a great help.
Jacek
--
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
Re: Day Trader deploy Cloudscape issues: "can't resolve admin object ref"
Posted by David Jencks <da...@yahoo.com>.
On Jul 7, 2008, at 3:04 PM, Jacek Laskowski wrote:
> On Mon, Jul 7, 2008 at 11:46 PM, David Jencks
> <da...@yahoo.com> wrote:
>
>> I no longer think its a good idea
>> to include the database and activemq configuration directly in the
>> ear.
>
> Why is so? Could you elaborate? I've been a great fan of using bundled
> plan from the very first day of its inception. Is it because an admin
> may not notice them and his/her server becomes out of his/her control?
What I think is current geronimo best practice for developing a
production ee application would be a development "pipeline" something
like this:
- development stage outputs the application as one or more plugins,
together with supporting db, mq, mail, etc plugins for the other
stages, and assembles these plugins into custom servers
- qa gets a server that has the same application plugins as production
will get, but with modified db/mq/ other "connector" plugins to fit
into the test environment. These are swapped for the production
"connector" plugins using artifact aliases.
- production gets a server that has the same application plugins as qa
got but with connector plugins that attach to the production db, mq
broker, etc etc.
I think this minimizes the chance of unexpected differences between qa
and production environments. If you put the connector configuration
in the main app plan, you either have to modify the plan between qa
and production or be restricted to what you can change using config-
substitutions.propertes.
Also, if you have a "family" of applications, most likely they will be
using the same connections to the environment so it would make sense
to put those connections in separate plugins rather than one
particular application.
If your goal is to provide a sample that has only one artifact, rather
than pointing out (what I think are) best practices, then putting
everything in one plan definitely makes sense. I no longer think that
is very important now that the plugins work fairly well. Or, I'd say
the appropriate artifact now is a custom server with the application
pre-deployed.
thanks
david jencks
>
>
> Jacek
>
> --
> Jacek Laskowski
> Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
Re: Day Trader deploy Cloudscape issues: "can't resolve admin object ref"
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On Mon, Jul 7, 2008 at 11:46 PM, David Jencks <da...@yahoo.com> wrote:
> I no longer think its a good idea
> to include the database and activemq configuration directly in the ear.
Why is so? Could you elaborate? I've been a great fan of using bundled
plan from the very first day of its inception. Is it because an admin
may not notice them and his/her server becomes out of his/her control?
Jacek
--
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
Re: Day Trader deploy Cloudscape issues: "can't resolve admin object ref"
Posted by David Jencks <da...@yahoo.com>.
I had a lot of trouble with the plans in the "plans" directory and
instead came up with the plugins which I think work against geronimo
trunk. After you build the plugins you can fish the plans out of the
target/resources/META-INF directories, modifiy them if you want to run
against e.g. 2.1.1, and deploy with them. I no longer think its a
good idea to include the database and activemq configuration directly
in the ear.
thanks
david jencks
On Jul 7, 2008, at 12:21 PM, harikaried wrote:
>
> I'm trying to deploy Day Trader with the embedded Cloudscape db with
> the
> following command:
>
> $GERONIMO_HOME/bin/deploy.sh deploy
> modules/ear/target/daytrader-ear-2.0-SNAPSHOT.ear
> plans/daytrader-g-2.0-SNAPSHOT-plan.xml
>
> It gives the following error:
>
> Error: Unable to distribute daytrader-ear-2.0-SNAPSHOT.ear: Can not
> resolve
> admin object ref ?j2eeType=JCAAdminObject,name=jms/TradeBrokerQueue#
> in
> configuration
> org.apache.geronimo.daytrader/daytrader_web.war/2.0-SNAPSHOT/car
>
> No matches for referencePatterns:
> [?j2eeType=JCAAdminObject,name=jms/TradeBrokerQueue#]
>
> The geronimo server is giving some warnings, but they don't seem
> related:
>
> Retrieving document at 'WEB-INF/wsdl/TradeServices.wsdl'.
> WARN [HeavyweightTypeInfoBuilder] No soap array info for schematype:
> T=QuoteDataBean@http://daytrader.samples.geronimo.apache.org
> Repeated for types HoldingDataBean, OrderDataBean,
> ArrayOfOrderDataBean,
> ArrayOfQuoteDataBean, ArrayOfHoldingDataBean
>
> WARN [EARConfigBuilder] Unable to delete 6 files while recursively
> deleting
> directory
> geronimo-tomcat6-javaee5-2.1.1/repository/org/apache/geronimo/
> daytrader/daytrader/2.0-SNAPSHOT/daytrader-2.0-SNAPSHOT.car
> --
> View this message in context: http://www.nabble.com/Day-Trader-deploy-Cloudscape-issues%3A-%22can%27t-resolve-admin-object-ref%22-tp18324559s134p18324559.html
> Sent from the Apache Geronimo - Users mailing list archive at
> Nabble.com.
>