JATO 1.2 to 2.0 upgrade
Hello. Our team is currently analyzing the possibility of upgrading from SunOne App. Server 6.5 to 7.0 and from JATO 1.2 to 2.0. We are searching for others who have done the upgrade and conversion. Some of the questions we have follow:
If you have upgraded from 6.5 to 7.0, how did the upgrade go? Were there any problems? Is 7.0 stable?
If you have upgraded from 1.2 to 2.0, how did the conversion go? Were there problems? Was the conversion a major effort? Do the converted pages work in Studio 4.0? Is using Studio a huge benefit?
Do you know if anyone else has done this?
Answers to these question will help us to decide if we have to upgrade or not.
Thank you in advance for any information you can provide to us!
Sincerely,
Jesudas Sundararajan (Das)
Syngenta Seeds, Inc.
7500 Olson Memorial Hwy.
Golden Valley, MN 55427
ph: 800-445-0956 ext. 7167(7am- 4pm cst)
fx: 763-593-7299
[email protected]
(copied from my Yahoo Group response)
The only thing I can give some info on is the JATO 1.2 to 2.0.
First, the JATO runtime has very few changes in it from 1.2 to 2.0. Your app will typically run as is under 2.0. All you really need to do is replace the JATO JAR file. There may be a few minor details, but should not be any show stoppers.
There are some new API's in 2.0, but the old stuff is just deprecated. There are some additionally API's to make JATO toolable, but have no affect on the runtime.
The Studio really reduces the effort it takes to create JATO components. Lots of code gen that is easily manipulated via visual property editor. However, you still have the flexibility to hand code what you want.
The way to bring your 1.2 app into a JATO 2.0 app is as follows:
- use the Studio to create a new application with the same package structure as your current app
- copy your view beans, tiled views, models and custom classes into the new package structure.
Now this allows you to build new objects using 2.0 techniques (visual point/click creation) and the new components will run along side your old components. The old components will not show up in the Studio tool like the new components will. In other words, a newly created view bean is recognized as a "JATO ViewBean" because it has an extra design time meta data file that desribes it. Your older ViewBeans will not have this file and therefore, will only be recognized as a regular Java class.
Creating this meta data file is not really something that can be reasonably done by hand, unfortunately.
If your app will not grow, then go ahead and start using JATO 2.0 runtime, but don't worry about the Studio aspect. But if you plan to expand the app, it would be beneficial to continue with the Studio tools.
Does anyone have some "real" world experience they can lend to the forum.
craig
Similar Messages
-
Namburi,
When you said you used the Reg Exp tool, did you use it only as
preconfigured by the iMT migrate application wizard?
Because the default configuration of the regular expression tool will only
target the files in your ND project directories. If you wish to target
classes outside of the normal directory scope, you have to either modify the
"Source Directory" property OR create another instance of the regular
expression tool. See the "Tool" menu in the iMT to create additional tool
instances which can each be configured to target different sets of files
using different sets of rules.
Usually, I utilize 3 different sets of rules files on a given migration:
spider2jato.xml
these are the generic conversion rules (but includes the optimized rules for
ViewBean and Model based code, i.e. these rules do not utilize the
RequestManager since it is not needed for code running inside the ViewBean
or Model classes)
I run these rules against all files.
See the file download section of this forum for periodic updates to these
rules.
nonProjectFileRules.xml
these include rules that add the necessary
RequestManager.getRequestContext(). etc prefixes to many of the common
calls.
I run these rules against user module and any other classes that do not are
not ModuleServlet, ContainerView, or Model classes.
appXRules.xml
these rules include application specific changes that I discover while
working on the project. A common thing here is changing import statements
(since the migration tool moves ND project code into different jato
packaging structure, you sometime need to adjust imports in non-project
classes that previously imported ND project specific packages)
So you see, you are not limited to one set of rules at all. Just be careful
to keep track of your backups (the regexp tool provides several options in
its Expert Properties related to back up strategies).
----- Original Message -----
From: <vnamboori@y...>
Sent: Wednesday, August 08, 2001 6:08 AM
Subject: [iPlanet-JATO] Re: Use Of models in utility classes - Pease don't
forget about the regular expression potential
Thanks Matt, Mike, Todd
This is a great input for our migration. Though we used the existing
Regular Expression Mapping tool, we did not change this to meet our
own needs as mentioned by Mike.
We would certainly incorporate this to ease our migration.
Namburi
--- In iPlanet-JATO@y..., "Todd Fast" <toddwork@c...> wrote:
All--
Great response. By the way, the Regular Expression Tool uses thePerl5 RE
syntax as implemented by Apache OROMatcher. If you're doing lotsof these
sorts of migration changes manually, you should definitely buy theO'Reilly
book "Mastering Regular Expressions" and generate some rules toautomate the
conversion. Although they are definitely confusing at first,regular
expressions are fairly easy to understand with some documentation,and are
superbly effective at tackling this kind of migration task.
Todd
----- Original Message -----
From: "Mike Frisino" <Michael.Frisino@S...>
Sent: Tuesday, August 07, 2001 5:20 PM
Subject: Re: [iPlanet-JATO] Use Of models in utility classes -Pease don't
forget about the regular expression potential
Also, (and Matt's document may mention this)
Please bear in mind that this statement is not totally correct:
Since the migration tool does not do much of conversion for
these
utilities we have to do manually.Remember, the iMT is a SUITE of tools. There is the extractiontool, and
the translation tool, and the regular expression tool, and severalother
smaller tools (like the jar and compilation tools). It is correctto state
that the extraction and translation tools only significantlyconvert the
primary ND project objects (the pages, the data objects, and theproject
classes). The extraction and translation tools do minimumtranslation of the
User Module objects (i.e. they repackage the user module classes inthe new
jato module packages). It is correct that for all other utilityclasses
which are not formally part of the ND project, the extraction and
translation tools do not perform any migration.
However, the regular expression tool can "migrate" any arbitrary
file
(utility classes etc) to the degree that the regular expressionrules
correlate to the code present in the arbitrary file. So first andforemost,
if you have alot of spider code in your non-project classes youshould
consider using the regular expression tool and if warranted adding
additional rules to reduce the amount of manual adjustments thatneed to be
made. I can stress this enough. We can even help you write theregular
expression rules if you simply identify the code pattern you wish to
convert. Just because there is not already a regular expressionrule to
match your need does not mean it can't be written. We have notnearly
exhausted the possibilities.
For example if you say, we need to convert
CSpider.getDataObject("X");
To
RequestManager.getRequestContext().getModelManager().getModel(XModel.class);
Maybe we or somebody else in the list can help write that regularexpression if it has not already been written. For instance in thelast
updated spider2jato.xml file there is already aCSpider.getCommonPage("X")
rule:
<!--getPage to getViewBean-->
<mapping-rule>
<mapping-rule-primarymatch>
<![CDATA[CSpider[.\s]*getPage[\s]*\(\"([^"]*)\"]]>
</mapping-rule-primarymatch>
<mapping-rule-replacement>
<mapping-rule-match>
<![CDATA[CSpider[.\s]*getPage[\s]*\(\"([^"]*)\"]]>
</mapping-rule-match>
<mapping-rule-substitute>
<![CDATA[getViewBean($1ViewBean.class]]>
</mapping-rule-substitute>
</mapping-rule-replacement>
</mapping-rule>
Following this example a getDataObject to getModel would look
like this:
<mapping-rule>
<mapping-rule-primarymatch>
<![CDATA[CSpider[.\s]*getDataObject[\s]*\(\"([^"]*)\"]]>
</mapping-rule-primarymatch>
<mapping-rule-replacement>
<mapping-rule-match>
<![CDATA[CSpider[.\s]*getDataObject[\s]*\(\"([^"]*)\"]]>
</mapping-rule-match>
<mapping-rule-substitute>
<![CDATA[getModel($1Model.class]]>
</mapping-rule-substitute>
</mapping-rule-replacement>
</mapping-rule>
In fact, one migration developer already wrote that rule andsubmitted it
for inclusion in the basic set. I will post another upgrade to thebasic
regular expression rule set, look for a "file uploaded" posting.Also,
please consider contributing any additional generic rules that youhave
written for inclusion in the basic set.
Please not, that in some cases (Utility classes in particular)
the rule
application may be more effective as TWO sequention rules ratherthan one
monolithic rule. Again using the example above, it will convert
CSpider.getDataObject("Foo");
To
getModel(FooModel.class);
Now that is the most effective conversion for that code if that
code is in
a page or data object class file. But if that code is in a Utilityclass you
really want:
>
RequestManager.getRequestContext().getModelManager().getModel(FooModel.class
So to go from
getModel(FooModel.class);
To
RequestManager.getRequestContext().getModelManager().getModel(FooModel.class
You would apply a second rule AND you would ONLY run this rule
against
your utility classes so that you would not otherwise affect yourViewBean
and Model classes which are completely fine with the simplegetModel call.
<mapping-rule>
<mapping-rule-primarymatch>
<![CDATA[getModel\(]]>
</mapping-rule-primarymatch>
<mapping-rule-replacement>
<mapping-rule-match>
<![CDATA[getModel\(]]>
</mapping-rule-match>
<mapping-rule-substitute>
<![CDATA[RequestManager.getRequestContext().getModelManager().getModel(]]>
</mapping-rule-substitute>
</mapping-rule-replacement>
</mapping-rule>
A similer rule can be applied to getSession and other CSpider APIcalls.
For instance here is the rule for converting getSession calls toleverage
the RequestManager.
<mapping-rule>
<mapping-rule-primarymatch>
<![CDATA[getSession\(\)\.]]>
</mapping-rule-primarymatch>
<mapping-rule-replacement>
<mapping-rule-match>
<![CDATA[getSession\(\)\.]]>
</mapping-rule-match>
<mapping-rule-substitute>
<![CDATA[RequestManager.getSession().]]>
</mapping-rule-substitute>
</mapping-rule-replacement>
</mapping-rule>
----- Original Message -----
From: "Matthew Stevens" <matthew.stevens@e...>
Sent: Tuesday, August 07, 2001 12:56 PM
Subject: RE: [iPlanet-JATO] Use Of models in utility classes
Namburi,
I will post a document to the group site this evening which has
the
details
on various tactics of migrating these type of utilities.
Essentially,
you
either need to convert these utilities to Models themselves or
keep the
utilities as is and simply use the
RequestManager.getRequestContext.getModelManager().getModel()
to statically access Models.
For CSpSelect.executeImmediate() I have an example of customhelper
method
as a replacement whicch uses JDBC results instead of
CSpDBResult.
matt
-----Original Message-----
From: vnamboori@y... [mailto:<a href="/group/SunONE-JATO/post?protectID=081071113213093190112061186248100208071048">vnamboori@y...</a>]
Sent: Tuesday, August 07, 2001 3:24 PM
Subject: [iPlanet-JATO] Use Of models in utility classes
Hi All,
In the present ND project we have lots of utility classes.
These
classes in diffrent directory. Not part of nd pages.
In these classes we access the dataobjects and do themanipulations.
So we access dataobjects directly like
CSpider.getDataObject("do....");
and then execute it.
Since the migration tool does not do much of conversion forthese
utilities we have to do manually.
My question is Can we access the the models in the postmigration
sameway or do we need requestContext?
We have lots of utility classes which are DataObjectintensive. Can
someone suggest a better way to migrate this kind of code.
Thanks
Namburi
[email protected]
[email protected]
[Non-text portions of this message have been removed]
[email protected]
[email protected]Namburi,
When you said you used the Reg Exp tool, did you use it only as
preconfigured by the iMT migrate application wizard?
Because the default configuration of the regular expression tool will only
target the files in your ND project directories. If you wish to target
classes outside of the normal directory scope, you have to either modify the
"Source Directory" property OR create another instance of the regular
expression tool. See the "Tool" menu in the iMT to create additional tool
instances which can each be configured to target different sets of files
using different sets of rules.
Usually, I utilize 3 different sets of rules files on a given migration:
spider2jato.xml
these are the generic conversion rules (but includes the optimized rules for
ViewBean and Model based code, i.e. these rules do not utilize the
RequestManager since it is not needed for code running inside the ViewBean
or Model classes)
I run these rules against all files.
See the file download section of this forum for periodic updates to these
rules.
nonProjectFileRules.xml
these include rules that add the necessary
RequestManager.getRequestContext(). etc prefixes to many of the common
calls.
I run these rules against user module and any other classes that do not are
not ModuleServlet, ContainerView, or Model classes.
appXRules.xml
these rules include application specific changes that I discover while
working on the project. A common thing here is changing import statements
(since the migration tool moves ND project code into different jato
packaging structure, you sometime need to adjust imports in non-project
classes that previously imported ND project specific packages)
So you see, you are not limited to one set of rules at all. Just be careful
to keep track of your backups (the regexp tool provides several options in
its Expert Properties related to back up strategies).
----- Original Message -----
From: <vnamboori@y...>
Sent: Wednesday, August 08, 2001 6:08 AM
Subject: [iPlanet-JATO] Re: Use Of models in utility classes - Pease don't
forget about the regular expression potential
Thanks Matt, Mike, Todd
This is a great input for our migration. Though we used the existing
Regular Expression Mapping tool, we did not change this to meet our
own needs as mentioned by Mike.
We would certainly incorporate this to ease our migration.
Namburi
--- In iPlanet-JATO@y..., "Todd Fast" <toddwork@c...> wrote:
All--
Great response. By the way, the Regular Expression Tool uses thePerl5 RE
syntax as implemented by Apache OROMatcher. If you're doing lotsof these
sorts of migration changes manually, you should definitely buy theO'Reilly
book "Mastering Regular Expressions" and generate some rules toautomate the
conversion. Although they are definitely confusing at first,regular
expressions are fairly easy to understand with some documentation,and are
superbly effective at tackling this kind of migration task.
Todd
----- Original Message -----
From: "Mike Frisino" <Michael.Frisino@S...>
Sent: Tuesday, August 07, 2001 5:20 PM
Subject: Re: [iPlanet-JATO] Use Of models in utility classes -Pease don't
forget about the regular expression potential
Also, (and Matt's document may mention this)
Please bear in mind that this statement is not totally correct:
Since the migration tool does not do much of conversion for
these
utilities we have to do manually.Remember, the iMT is a SUITE of tools. There is the extractiontool, and
the translation tool, and the regular expression tool, and severalother
smaller tools (like the jar and compilation tools). It is correctto state
that the extraction and translation tools only significantlyconvert the
primary ND project objects (the pages, the data objects, and theproject
classes). The extraction and translation tools do minimumtranslation of the
User Module objects (i.e. they repackage the user module classes inthe new
jato module packages). It is correct that for all other utilityclasses
which are not formally part of the ND project, the extraction and
translation tools do not perform any migration.
However, the regular expression tool can "migrate" any arbitrary
file
(utility classes etc) to the degree that the regular expressionrules
correlate to the code present in the arbitrary file. So first andforemost,
if you have alot of spider code in your non-project classes youshould
consider using the regular expression tool and if warranted adding
additional rules to reduce the amount of manual adjustments thatneed to be
made. I can stress this enough. We can even help you write theregular
expression rules if you simply identify the code pattern you wish to
convert. Just because there is not already a regular expressionrule to
match your need does not mean it can't be written. We have notnearly
exhausted the possibilities.
For example if you say, we need to convert
CSpider.getDataObject("X");
To
RequestManager.getRequestContext().getModelManager().getModel(XModel.class);
Maybe we or somebody else in the list can help write that regularexpression if it has not already been written. For instance in thelast
updated spider2jato.xml file there is already aCSpider.getCommonPage("X")
rule:
<!--getPage to getViewBean-->
<mapping-rule>
<mapping-rule-primarymatch>
<![CDATA[CSpider[.\s]*getPage[\s]*\(\"([^"]*)\"]]>
</mapping-rule-primarymatch>
<mapping-rule-replacement>
<mapping-rule-match>
<![CDATA[CSpider[.\s]*getPage[\s]*\(\"([^"]*)\"]]>
</mapping-rule-match>
<mapping-rule-substitute>
<![CDATA[getViewBean($1ViewBean.class]]>
</mapping-rule-substitute>
</mapping-rule-replacement>
</mapping-rule>
Following this example a getDataObject to getModel would look
like this:
<mapping-rule>
<mapping-rule-primarymatch>
<![CDATA[CSpider[.\s]*getDataObject[\s]*\(\"([^"]*)\"]]>
</mapping-rule-primarymatch>
<mapping-rule-replacement>
<mapping-rule-match>
<![CDATA[CSpider[.\s]*getDataObject[\s]*\(\"([^"]*)\"]]>
</mapping-rule-match>
<mapping-rule-substitute>
<![CDATA[getModel($1Model.class]]>
</mapping-rule-substitute>
</mapping-rule-replacement>
</mapping-rule>
In fact, one migration developer already wrote that rule andsubmitted it
for inclusion in the basic set. I will post another upgrade to thebasic
regular expression rule set, look for a "file uploaded" posting.Also,
please consider contributing any additional generic rules that youhave
written for inclusion in the basic set.
Please not, that in some cases (Utility classes in particular)
the rule
application may be more effective as TWO sequention rules ratherthan one
monolithic rule. Again using the example above, it will convert
CSpider.getDataObject("Foo");
To
getModel(FooModel.class);
Now that is the most effective conversion for that code if that
code is in
a page or data object class file. But if that code is in a Utilityclass you
really want:
>
RequestManager.getRequestContext().getModelManager().getModel(FooModel.class
So to go from
getModel(FooModel.class);
To
RequestManager.getRequestContext().getModelManager().getModel(FooModel.class
You would apply a second rule AND you would ONLY run this rule
against
your utility classes so that you would not otherwise affect yourViewBean
and Model classes which are completely fine with the simplegetModel call.
<mapping-rule>
<mapping-rule-primarymatch>
<![CDATA[getModel\(]]>
</mapping-rule-primarymatch>
<mapping-rule-replacement>
<mapping-rule-match>
<![CDATA[getModel\(]]>
</mapping-rule-match>
<mapping-rule-substitute>
<![CDATA[RequestManager.getRequestContext().getModelManager().getModel(]]>
</mapping-rule-substitute>
</mapping-rule-replacement>
</mapping-rule>
A similer rule can be applied to getSession and other CSpider APIcalls.
For instance here is the rule for converting getSession calls toleverage
the RequestManager.
<mapping-rule>
<mapping-rule-primarymatch>
<![CDATA[getSession\(\)\.]]>
</mapping-rule-primarymatch>
<mapping-rule-replacement>
<mapping-rule-match>
<![CDATA[getSession\(\)\.]]>
</mapping-rule-match>
<mapping-rule-substitute>
<![CDATA[RequestManager.getSession().]]>
</mapping-rule-substitute>
</mapping-rule-replacement>
</mapping-rule>
----- Original Message -----
From: "Matthew Stevens" <matthew.stevens@e...>
Sent: Tuesday, August 07, 2001 12:56 PM
Subject: RE: [iPlanet-JATO] Use Of models in utility classes
Namburi,
I will post a document to the group site this evening which has
the
details
on various tactics of migrating these type of utilities.
Essentially,
you
either need to convert these utilities to Models themselves or
keep the
utilities as is and simply use the
RequestManager.getRequestContext.getModelManager().getModel()
to statically access Models.
For CSpSelect.executeImmediate() I have an example of customhelper
method
as a replacement whicch uses JDBC results instead of
CSpDBResult.
matt
-----Original Message-----
From: vnamboori@y... [mailto:<a href="/group/SunONE-JATO/post?protectID=081071113213093190112061186248100208071048">vnamboori@y...</a>]
Sent: Tuesday, August 07, 2001 3:24 PM
Subject: [iPlanet-JATO] Use Of models in utility classes
Hi All,
In the present ND project we have lots of utility classes.
These
classes in diffrent directory. Not part of nd pages.
In these classes we access the dataobjects and do themanipulations.
So we access dataobjects directly like
CSpider.getDataObject("do....");
and then execute it.
Since the migration tool does not do much of conversion forthese
utilities we have to do manually.
My question is Can we access the the models in the postmigration
sameway or do we need requestContext?
We have lots of utility classes which are DataObjectintensive. Can
someone suggest a better way to migrate this kind of code.
Thanks
Namburi
[email protected]
[email protected]
[Non-text portions of this message have been removed]
[email protected]
[email protected] -
Re: [iPlanet-JATO] jato classes serializable
Unless Todd, Mike, or Matt have slick answer to make it work, my only
solution would be to switch from using the objects themselves and
reference by name instead. I don't know exactly what your Utility class
is doing or how the fields use the Utility class, so I can not be
specific in what you should do.
I fear that I may be taking on too much work by asking, but maybe you
could send me the Utility class (send to me directly as Yahoo Groups
doesnot allow attachments: craig.conover@s...).
I'll take a quick glance at it. Maybe I can make some suggestions to
minimize your migration efforts.
craig
Seetharam, Prashanth wrote:
In ND, we had a utility class written whose member variables were visual
objects. This utility object is used to display or not display its elements
depending on user action. The utility object was being put into session.
It could have been implemented in a different way, by storing visual object
names instead of objects themselves. But when we migrated, we tried to keep
re-coding to the minimum and ended up replacing ND visual objects
withcorresponding jato visual objects and ran into this problem.
Since all the jato visual objects extend from DisplayFieldBase which inturn
extends from ViewBase, i started looking at ViewBase and did not understand
why the variable was made transient. Hence the question.
Thanks,
Prashanth Seetharam
-----Original Message-----
From: Craig V. Conover [SMTP:<a href="/group/SunONE-JATO/post?protectID=219212113009229091025149066024064239039098031198039130252055210">craig.conover@s...</a>]
Sent: Tuesday, December 11, 2001 2:43 PM
Subject: Re: [iPlanet-JATO] jato classes serializable
What is your requirement that these be serializable?
The views do not store any values, that is what the model is for, and
they are created lazily as needed.
Is there something you were doing in ND that required it. It is very
likely that you do not need to do it anymore with JATO.
If you are using JATO1.0, you are highly encouraged to start using JATO
1.2. If you are using the iMT, it has an upgrade tool for 1.x to 1.2.
http://developer.iplanet.com/tech/appserver/framework/index.jsp
I'll leave the transient parentViewBean to Todd or Mike to justify. But,
again, what is the need for it to be serialized?
c
Seetharam, Prashanth wrote:
I am using jato1.0 and found that jato classes (especially the visual
objects like StaticTextField) are not serializable.
Is this change made in jato1.1? It will be good to have this feature as
ND
visual objects were serializable.
Also in com.iplanet.jato.view.ViewBase.java, why has this variable been
made
transient?
private transient ViewBean parentViewBean;
Thanks,
Prashanth Seetharam
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jspUnless Todd, Mike, or Matt have slick answer to make it work, my only
solution would be to switch from using the objects themselves and
reference by name instead. I don't know exactly what your Utility class
is doing or how the fields use the Utility class, so I can not be
specific in what you should do.
I fear that I may be taking on too much work by asking, but maybe you
could send me the Utility class (send to me directly as Yahoo Groups
doesnot allow attachments: craig.conover@s...).
I'll take a quick glance at it. Maybe I can make some suggestions to
minimize your migration efforts.
craig
Seetharam, Prashanth wrote:
In ND, we had a utility class written whose member variables were visual
objects. This utility object is used to display or not display its elements
depending on user action. The utility object was being put into session.
It could have been implemented in a different way, by storing visual object
names instead of objects themselves. But when we migrated, we tried to keep
re-coding to the minimum and ended up replacing ND visual objects
withcorresponding jato visual objects and ran into this problem.
Since all the jato visual objects extend from DisplayFieldBase which inturn
extends from ViewBase, i started looking at ViewBase and did not understand
why the variable was made transient. Hence the question.
Thanks,
Prashanth Seetharam
-----Original Message-----
From: Craig V. Conover [SMTP:<a href="/group/SunONE-JATO/post?protectID=219212113009229091025149066024064239039098031198039130252055210">craig.conover@s...</a>]
Sent: Tuesday, December 11, 2001 2:43 PM
Subject: Re: [iPlanet-JATO] jato classes serializable
What is your requirement that these be serializable?
The views do not store any values, that is what the model is for, and
they are created lazily as needed.
Is there something you were doing in ND that required it. It is very
likely that you do not need to do it anymore with JATO.
If you are using JATO1.0, you are highly encouraged to start using JATO
1.2. If you are using the iMT, it has an upgrade tool for 1.x to 1.2.
http://developer.iplanet.com/tech/appserver/framework/index.jsp
I'll leave the transient parentViewBean to Todd or Mike to justify. But,
again, what is the need for it to be serialized?
c
Seetharam, Prashanth wrote:
I am using jato1.0 and found that jato classes (especially the visual
objects like StaticTextField) are not serializable.
Is this change made in jato1.1? It will be good to have this feature as
ND
visual objects were serializable.
Also in com.iplanet.jato.view.ViewBase.java, why has this variable been
made
transient?
private transient ViewBean parentViewBean;
Thanks,
Prashanth Seetharam
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp -
RE: [iPlanet-JATO] Parse error in JSP parser in IAS6
Hi Todd,
removing the defaultValue="" attribute works.
I have not got around to testing the SP3.
BTW. The reason the default value tag was added was to stop Null pointer
exceptions being thrown in the
HrefTag.beginDisplay().
buffer.append("?")
.append(field.getQualifiedName()) // "FooHref"
.append("=")
.append(URLEncoder.encode(value.toString())); // "/foo"
If you don't explicitly add a defaultValue="" to the jsp HREF tag ,
HrefTag.getDefaultValue() returns null.
Our hack was to add the following in HrefTag.java.
if (value==null)
value=getDefaultValue();
//===========================
//IP6 ADDED THE FOLLOWING LINE
value = (value== null? "":value);
//============================
Is that pheasible work-around ? This eliminates the need to add
defaultValue="" to all HREF tags.
Also, I might as well point another behavior that we encountered with HREFS.
In ND, if a HREF's display Field was bound to a column in DataObject and the
particular record had no value, no URL would be rendered on the page.
The HTML would look something like this( from memory ):
<A
HREF="../AppName/PgMsgMain.hrfSubject_onWebEvent(hrfSubject).994226335140? +
ND URL STUFF"></A>
In JATO by default a url get displayed with "null" as the link. ie.
<a href="../AppName/PgMsgMain?PgMsgMain.hrfSubject= + URL STUFF">null</a>
Our hack was modify the HrefTag.doEndTag method to not append "null" to the
buffer.
if (displayed)
buffer.append(getBodyContent().getString().equals("null")? "":
getBodyContent().getString()))
// IP6 HACK buffer.append(getBodyContent().getString())
.append("</a>");
writeOutput(fireEndDisplayEvent(buffer.toString()));
Is there a better way to do this?
thanks
Kostas
-----Original Message-----
From: Todd Fast [mailto:<a href="/group/SunONE-JATO/post?protectID=189233080150012190218067203043176090006144139218183041">toddwork@c...</a>]
Sent: Tuesday, July 03, 2001 12:46 AM
Subject: Re: [iPlanet-JATO] Parse error in JSP parser in IAS6
Hey Kostas--
I personally haven't seen this kind of error. Have you tried simplifying
the expression inside the href tag? For example:
<% Object foo =
viewBean.getRptAssignmentMatch().getvwAssignmentMatchModel().getValue(
vwAssignmentMatchModel.FIELD_ASSIGNMENT_ASSIGNMENT_ID);
%>
<jato:href name="hrefASSIGNMENT_ASSIGNMENT_ID" fireDisplayEvents="true">
<%= foo %>
</jato:href>
Also, is there a different version you could upgrade to? iAS SP3 includes
the Jasper compiler from Tomcat, which should behave quite differently.
Todd
----- Original Message -----
From: "Kostas Morfis" <kmorfis@i...>
Sent: Tuesday, July 03, 2001 12:17 AM
Subject: [iPlanet-JATO] Parse error in JSP parser in IAS6
>
Hi all,
has anyone come across the following error in iPlanet?
[02/Jul/2001 12:21:32:1] error: Exception: SERVLET-compile_failed: Failedin
compiling template: /ras/ras/voyager4/pgAssignmentMatch.jsp, Parse errorin
JSP parser. Missing endtag: /jato:href
Exception Stack Trace:
java.lang.Exception: Parse error in JSP parser. Missing endtag: /jato:href
at com.netscape.jsp.JSP.parseBlock(Unknown Source)
at com.netscape.jsp.JSP.parseUserTag(Unknown Source)
at com.netscape.jsp.JSP.parseTag(Unknown Source)
at com.netscape.jsp.JSP.parseNext(Unknown Source)
etc etc.
We have tested the page in Resin and it works fine.
It seems the JSP parser has a problem with the following type of HREFtags.
>
<jato:href name="hrefASSIGNMENT_ASSIGNMENT_ID" fireDisplayEvents="true"
defaultValue=""><%=
viewBean.getRptAssignmentMatch().getvwAssignmentMatchModel().getValue(com.cb
>
re.ras.voyager4.model.vwAssignmentMatchModel.FIELD_ASSIGNMENT_ASSIGNMENT_ID)
%></jato:href></font></td>
anyone have any suggestions/thoughts/comments ?
Kostas Morfis
Senior Consultant
iRise
www.iRise.com
[Non-text portions of this message have been removed]
[email protected]
[email protected]Hi Todd,
removing the defaultValue="" attribute works.
I have not got around to testing the SP3.
BTW. The reason the default value tag was added was to stop Null pointer
exceptions being thrown in the
HrefTag.beginDisplay().
buffer.append("?")
.append(field.getQualifiedName()) // "FooHref"
.append("=")
.append(URLEncoder.encode(value.toString())); // "/foo"
If you don't explicitly add a defaultValue="" to the jsp HREF tag ,
HrefTag.getDefaultValue() returns null.
Our hack was to add the following in HrefTag.java.
if (value==null)
value=getDefaultValue();
//===========================
//IP6 ADDED THE FOLLOWING LINE
value = (value== null? "":value);
//============================
Is that pheasible work-around ? This eliminates the need to add
defaultValue="" to all HREF tags.
Also, I might as well point another behavior that we encountered with HREFS.
In ND, if a HREF's display Field was bound to a column in DataObject and the
particular record had no value, no URL would be rendered on the page.
The HTML would look something like this( from memory ):
<A
HREF="../AppName/PgMsgMain.hrfSubject_onWebEvent(hrfSubject).994226335140? +
ND URL STUFF"></A>
In JATO by default a url get displayed with "null" as the link. ie.
<a href="../AppName/PgMsgMain?PgMsgMain.hrfSubject= + URL STUFF">null</a>
Our hack was modify the HrefTag.doEndTag method to not append "null" to the
buffer.
if (displayed)
buffer.append(getBodyContent().getString().equals("null")? "":
getBodyContent().getString()))
// IP6 HACK buffer.append(getBodyContent().getString())
.append("</a>");
writeOutput(fireEndDisplayEvent(buffer.toString()));
Is there a better way to do this?
thanks
Kostas
-----Original Message-----
From: Todd Fast [mailto:<a href="/group/SunONE-JATO/post?protectID=189233080150012190218067203043176090006144139218183041">toddwork@c...</a>]
Sent: Tuesday, July 03, 2001 12:46 AM
Subject: Re: [iPlanet-JATO] Parse error in JSP parser in IAS6
Hey Kostas--
I personally haven't seen this kind of error. Have you tried simplifying
the expression inside the href tag? For example:
<% Object foo =
viewBean.getRptAssignmentMatch().getvwAssignmentMatchModel().getValue(
vwAssignmentMatchModel.FIELD_ASSIGNMENT_ASSIGNMENT_ID);
%>
<jato:href name="hrefASSIGNMENT_ASSIGNMENT_ID" fireDisplayEvents="true">
<%= foo %>
</jato:href>
Also, is there a different version you could upgrade to? iAS SP3 includes
the Jasper compiler from Tomcat, which should behave quite differently.
Todd
----- Original Message -----
From: "Kostas Morfis" <kmorfis@i...>
Sent: Tuesday, July 03, 2001 12:17 AM
Subject: [iPlanet-JATO] Parse error in JSP parser in IAS6
>
Hi all,
has anyone come across the following error in iPlanet?
[02/Jul/2001 12:21:32:1] error: Exception: SERVLET-compile_failed: Failedin
compiling template: /ras/ras/voyager4/pgAssignmentMatch.jsp, Parse errorin
JSP parser. Missing endtag: /jato:href
Exception Stack Trace:
java.lang.Exception: Parse error in JSP parser. Missing endtag: /jato:href
at com.netscape.jsp.JSP.parseBlock(Unknown Source)
at com.netscape.jsp.JSP.parseUserTag(Unknown Source)
at com.netscape.jsp.JSP.parseTag(Unknown Source)
at com.netscape.jsp.JSP.parseNext(Unknown Source)
etc etc.
We have tested the page in Resin and it works fine.
It seems the JSP parser has a problem with the following type of HREFtags.
>
<jato:href name="hrefASSIGNMENT_ASSIGNMENT_ID" fireDisplayEvents="true"
defaultValue=""><%=
viewBean.getRptAssignmentMatch().getvwAssignmentMatchModel().getValue(com.cb
>
re.ras.voyager4.model.vwAssignmentMatchModel.FIELD_ASSIGNMENT_ASSIGNMENT_ID)
%></jato:href></font></td>
anyone have any suggestions/thoughts/comments ?
Kostas Morfis
Senior Consultant
iRise
www.iRise.com
[Non-text portions of this message have been removed]
[email protected]
[email protected] -
Conversion of 1.2 JATO project (non-Forte IDE) to S1AF (JATO) 2.0
JATO Team,
First of all, thank you very much for the Studio integration. It
looks very promising in terms of development time consumption,
deployment to S1AS7, etc., etc. It is impossible to observe all
advantages for so short period of time.
The SOAF (JATO) 2.0 is installed on the top of the Sun ONE Studio 4,
update 1 (EE) with JDK 1.4 along with the Sun One Application Server
7 (W2000). Everything looks okay, at least all basic tasks listed in
the "Getting Started" manual (project/view/model creation, basic db
connection, running of a test application with the usage of the
Studio's default Tomcat container, etc.) work proper.
During the installation of S1AF module on the top of the Sun ONE
Studio 4, update 1 (EE) I've got an invitation to convert the
existing project to the new environment. As I realized the only JATO
project integrated/created with Forte IDE is applicable for this auto-
conversion (please correct me, if I am wrong. It could solve a lot of
my problems).
Since we are using JBuilder5 IDE and our JATO 1.2 project is
integrated with this IDE I manually re-created project in the Studio
with its file structure, adjusted the project web.xml file, etc. This
new project looks like a proper one (Studio recognize all methods,
fields, bean patterns, e.g.) except at least one "small" thing. All
java files (project viewBeans, Models, custom viewBeanHelpers a.k.a.
pure java) came up with the same wizard image:java class. Stutio with
the S1AF module reserves the special images (and appropriate studio
properties, of course!) for View and Model. Namely this allows to see
the following structure for a ViewBean, for example, in the Studio:
Modules
ProjectName.ModuleName
FooViewBean
JavaSource
JSPs
Non-Visual Components
View Components
On the other hand, I could add either new View or Model in my
manually converted project and add any View Component or bind the
Model fields, for example. Also, the ProjectModuleServlet has been
converted proper. I tried to convert each View/Model class inside the
Studio to its proper wizard image and failed. Addition of a View
Components (with an appropriate code fragments) via the Studio or
auto-binding of model fields is an essential part of 2.0 and should
drastically speed up the development process as it is designed.
Questions:
1. What I missed in my manual conversion of 1.2 JATO project to the
SOAF (JATO) 2.0 realm? What should I correct in my JATO 1.2
compatible classes (Views and Models) to be recognizable by Studio
wizard (JATO 2.0)?
To be more specific. Some deltas between JATO 1.2 and JATO 2.0 are as
follows (related to a ViewBean):
====++++++++++++++======
JATO 1.2 viewBean extension upon creation:
public class FooViewBeanViewBean extends ViewBeanBase
implements ViewBean
========================
JATO 2.0 (S1AF) version: viewBean extension upon creation:
public class FooViewBean extends BasicBeanBase
====++++++++++++++======
JATO 1.2 viewBean createChild(...) method for one static looks
like:
protected View createChild(String name)
if (name.equals(CHILD_STATICTEXT1))
StaticTextField child = new StaticTextField
(this,
getDefaultModel(),
CHILD_STATICTEXT1,
CHILD_STATICTEXT1,
CHILD_STATICTEXT1_RESET_VALUE,
null);
return child;
========================
JATO 2.0 (S1AF) version: viewBean createChild(...) is renamed (as
a least) to createChildReserved(...):
protected View createChildReserved(String name) {
if (name.equals(CHILD_STATICTEXT1)) {
com.iplanet.jato.view.BasicDisplayField child =
new com.iplanet.jato.view.BasicDisplayField(this,
STATICTEXT1);
return child;
====++++++++++++++======
JATO 1.2 viewBean registerChildren() method for the basic field
types looks like:
private void registerChildren() {
registerChild(CHILD_STATICTEXT1, StaticTextField.class);
registerChild(CHILD_TEXTFIELD1, TextField.class);
registerChild(CHILD_BUTTON1, Button.class);
========================
JATO 2.0 (S1AF) version: viewBean registerChildren() method:
private void registerChildren() {
registerChild(CHILD_STATICTEXT1,
com.iplanet.jato.view.BasicDisplayField.class);
registerChild(CHILD_TEXTFIELD1,
com.iplanet.jato.view.BasicDisplayField.class);
registerChild(CHILD_BUTTON1,
com.iplanet.jato.view.BasicCommandField.class);
Is it correct to say that all existing custom Views/Models
(compatible with JATO 1.2) should be converted to their JATO 2.0
variants to be visible by the Studio?
On the other hand, fast overview of 2.0 API shows that the JATO 1.2
is a sub-set of the 2.0 (BasicViewBean extends ViewBeanBase, for
example). What exactly (only deprecated methods?) should be adjusted
in the project code (1.2), if necessary, to be visible by Studio as a
View or Model component?
2. Where it is possible to find the list of deprecated methods (from
JATO 1.2 to JATO 2.0 versions). It is difficult sometimes to compare
two versions of API docs (1.2 and 2.0) or compare logs between
versions. Also, JATO 2.0 is significantly larger than 1.2 version. If
the later obviously inherits the ND conversion stage (via the
previous versions), the former obviously has additions incoming from
the integration with the Studio (a.k.a. Forte 4.0).
3. What is the current/future Sun/JATO Team policy with regards to
JATO source code access (version 2.0, at least)? The reason of this
question is as follows: in order to display dates formatted on the
screens we adjusted a couple of JATO 1.2 core classes, for example.
The only minimal, absolutely necessary changes in JATO 1.2 was made,
but anyway...
Sorry for so long multiple question. As Todd wrote in his
announcement mail: "We think you will be very pleased with the new
product...". This is exciting moment, I believe, for JATO Team as
well as for any team involved into the conversion of the full size
application/product from ND to J2EE realm with the JATO as
an application framework (1.0, 1.1.x, 1.2.X, and 2.0 finally). The
last step is left in this spiral process to enjoy the ND_Studio
attractive features in the open source environment.
Thank you very much in advance.
Vladimir IvanovI'll get some file templates ASAP and provide them to the group.
As for source code, I'm not sure what the policy is. JATO 1.2 is very
close to what JATO 2.0 is, so that should suffice for now.
The community will be informed when we know more about source availibility.
craig
vivanov4114 wrote:
Craig,
Thank you for the answer. To be honest with you I tried to do exactly
the same: I created the small test project and made an attempt to
adjust the existing *.xml files to the new ones. I got some results,
otherwise I couldn't even see my original 1.2 project in the Studio.
Since I am a newcomer in the Studio, I definitely missed something in
my adjustments. I'll try to observe my changes with the fresh head.
On the other hand, I am afraid that my samples are very pure. If you
could post or send me examples of jatoapp.xml and web.xml files (say
for any of you test project) or excerptions from them with the
appropriate patterns (ViewBean and Model peers, at least), I would be
very appreciated. My mail is: vivanov@b...
In the worst-case scenario I see the workaround: to re-create the
project for one of our releases with the Forte 4.1 IDE and auto-
convert it into the JATO 2.0/Studio world using the Studio
facilities. We must get the current project fully
integrated/converted with/to the Studio (at certain point) because,
first, we expect massive coding with the GUI components involved soon
and, secondly, we have around thousand classes related to JATO only
(and a lot of extras).
Coming back to the question #3 from this post. Now we have full
access to the version 1.2, not only to the JATO 1.2 jar file(I
explained some reasons below). Would we expect the same Sun/JATO Team
policy with JATO 2.0?
Thank you again,
Vlad
--- In SunONE-JATO@y..., "cvconover" <craig.conover@s...> wrote:
It doesn't appear that anyone has responded to this so I am goingto
give you the short answer:
The reason you don't see your ViewBeans and Models showing up with
there "wizard created" icons is because of just that. They weren't
created via the wizards. The wizards create xml formatted filesthat
contain metadata of how/what to generate for the ViewBeans and
Models.
ViewBeans will have a .viewbean fiel, Models will have a .sqlmodel
file (for SQL Models), etc. The content of these files describesthe
code that needs to be generated in the corresponding Java classfile.
So LoginViewBean.java will have a peer LoginViewBean.viewbean file.
The code that is generated is place in protected code blocks thatcan
not be modified in the Studio and should not be modified outsidethe
Studio because the code will likely be regenerated and custom mods
inside the protected blocks will be lost.
Now you can make a JATO 1.2 app appear in the Studio just like aJATO
2.0 app by adding a jatoapp.xml file with the proper content and
adjusting your web.xml properly, but it's much more work to getyour
v1.2 ViewBeans and Models to show up like wizard created versions.
Furthermore, even more work to get the display fields to show up
visually.
The good news is that v1.2 ViewBeans will work with newly wizard
created ViewBeans. And if you do go through the trouble of making
your ViewBeans Studio visible like your wizard created ViewBeans,
adding new display fields visually will work along side yourmanually
created fields.
Try creating a new JATO app using the Studio wizards and then go to
the Filesystems tab and look for the jatoapp.xml file and theweb.xml
file.
I am looking for an email that I have that explains how to do a
partial, manual upgrade.
Also, you will get rid of your JATO 1.2 jar and replace with theJATO
2.0 jar in your lib dir.
Hope this will suffice for now.
craig
--- In SunONE-JATO@y..., "vivanov4114" <vivanov@b...> wrote:
JATO Team,
First of all, thank you very much for the Studio integration. It
looks very promising in terms of development time consumption,
deployment to S1AS7, etc., etc. It is impossible to observe all
advantages for so short period of time.
The SOAF (JATO) 2.0 is installed on the top of the Sun ONE Studio4,
update 1 (EE) with JDK 1.4 along with the Sun One ApplicationServer
7 (W2000). Everything looks okay, at least all basic tasks listedin
the "Getting Started" manual (project/view/model creation, basic
db
connection, running of a test application with the usage of the
Studio's default Tomcat container, etc.) work proper.
During the installation of S1AF module on the top of the Sun ONE
Studio 4, update 1 (EE) I've got an invitation to convert the
existing project to the new environment. As I realized the onlyJATO
project integrated/created with Forte IDE is applicable for thisauto-
conversion (please correct me, if I am wrong. It could solve a
lot
of
my problems).
Since we are using JBuilder5 IDE and our JATO 1.2 project is
integrated with this IDE I manually re-created project in theStudio
with its file structure, adjusted the project web.xml file, etc.This
new project looks like a proper one (Studio recognize all
methods,
fields, bean patterns, e.g.) except at least one "small" thing.All
java files (project viewBeans, Models, custom viewBeanHelpersa.k.a.
pure java) came up with the same wizard image:java class. Stutiowith
the S1AF module reserves the special images (and appropriate
studio
properties, of course!) for View and Model. Namely this allows tosee
the following structure for a ViewBean, for example, in the
Studio:
Modules
ProjectName.ModuleName
FooViewBean
JavaSource
JSPs
Non-Visual Components
View Components
On the other hand, I could add either new View or Model in my
manually converted project and add any View Component or bind the
Model fields, for example. Also, the ProjectModuleServlet hasbeen
converted proper. I tried to convert each View/Model class insidethe
Studio to its proper wizard image and failed. Addition of a View
Components (with an appropriate code fragments) via the Studio or
auto-binding of model fields is an essential part of 2.0 and
should
drastically speed up the development process as it is designed.
Questions:
1. What I missed in my manual conversion of 1.2 JATO project tothe
SOAF (JATO) 2.0 realm? What should I correct in my JATO 1.2
compatible classes (Views and Models) to be recognizable byStudio
wizard (JATO 2.0)?
To be more specific. Some deltas between JATO 1.2 and JATO 2.0are
as
follows (related to a ViewBean):
====++++++++++++++======
JATO 1.2 viewBean extension upon creation:
public class FooViewBeanViewBean extends ViewBeanBase
implements ViewBean
========================
JATO 2.0 (S1AF) version: viewBean extension upon creation:
public class FooViewBean extends BasicBeanBase
====++++++++++++++======
JATO 1.2 viewBean createChild(...) method for one static looks
like:
protected View createChild(String name)
if (name.equals(CHILD_STATICTEXT1))
StaticTextField child = new StaticTextField
(this,
getDefaultModel(),
CHILD_STATICTEXT1,
CHILD_STATICTEXT1,
CHILD_STATICTEXT1_RESET_VALUE,
null);
return child;
========================
JATO 2.0 (S1AF) version: viewBean createChild(...) is renamed(as
a least) to createChildReserved(...):
protected View createChildReserved(String name) {
if (name.equals(CHILD_STATICTEXT1)) {
com.iplanet.jato.view.BasicDisplayField child =
new com.iplanet.jato.view.BasicDisplayField(this,
STATICTEXT1);
return child;
====++++++++++++++======
JATO 1.2 viewBean registerChildren() method for the basic field
types looks like:
private void registerChildren() {
registerChild(CHILD_STATICTEXT1,
StaticTextField.class);
registerChild(CHILD_TEXTFIELD1, TextField.class);
registerChild(CHILD_BUTTON1, Button.class);
========================
JATO 2.0 (S1AF) version: viewBean registerChildren() method:
private void registerChildren() {
registerChild(CHILD_STATICTEXT1,
com.iplanet.jato.view.BasicDisplayField.class);
registerChild(CHILD_TEXTFIELD1,
com.iplanet.jato.view.BasicDisplayField.class);
registerChild(CHILD_BUTTON1,
com.iplanet.jato.view.BasicCommandField.class);
Is it correct to say that all existing custom Views/Models
(compatible with JATO 1.2) should be converted to their JATO 2.0
variants to be visible by the Studio?
On the other hand, fast overview of 2.0 API shows that the JATO1.2
is a sub-set of the 2.0 (BasicViewBean extends ViewBeanBase, for
example). What exactly (only deprecated methods?) should beadjusted
in the project code (1.2), if necessary, to be visible by Studio
as
a
View or Model component?
2. Where it is possible to find the list of deprecated methods(from
JATO 1.2 to JATO 2.0 versions). It is difficult sometimes tocompare
two versions of API docs (1.2 and 2.0) or compare logs between
versions. Also, JATO 2.0 is significantly larger than 1.2
version.
If
the later obviously inherits the ND conversion stage (via the
previous versions), the former obviously has additions incomingfrom
the integration with the Studio (a.k.a. Forte 4.0).
3. What is the current/future Sun/JATO Team policy with regards
to
JATO source code access (version 2.0, at least)? The reason ofthis
question is as follows: in order to display dates formatted onthe
screens we adjusted a couple of JATO 1.2 core classes, forexample.
The only minimal, absolutely necessary changes in JATO 1.2 wasmade,
but anyway...
Sorry for so long multiple question. As Todd wrote in his
announcement mail: "We think you will be very pleased with the
new
product...". This is exciting moment, I believe, for JATO Team as
well as for any team involved into the conversion of the fullsize
application/product from ND to J2EE realm with the JATO as
an application framework (1.0, 1.1.x, 1.2.X, and 2.0 finally).The
last step is left in this spiral process to enjoy the ND_Studio
attractive features in the open source environment.
Thank you very much in advance.
Vladimir IvanovTo download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
[Non-text portions of this message have been removed] -
Upgraded from Tomcat 3.3.1 to Tomcat 4.0.4 receiving Stack
I moved my war file into my new Tomcat 4.0.4 webapps directory since I
need to upgrade in order to use some 'other' tags and I'm receiving
the following stacktrace when I try to hit the first page in my
application....
Any ideas as to why this is occurring?
StackTrace Below:
Application Error
javax.servlet.ServletException: Invalid request - request handler
"VoyagerLogin"
not found
at
com.iplanet.jato.ApplicationServletBase.onRequestHandlerNotFound(Appl
icationServletBase.java:1153)
at
com.iplanet.jato.ApplicationServletBase.fireRequestHandlerNotFoundEve
nt(ApplicationServletBase.java:977)
at
com.iplanet.jato.ApplicationServletBase.getViewBeanInstance(Applicati
onServletBase.java:717)
at
com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationSer
vletBase.java:429)
at
com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase
.java:312)
at
com.iplanet.jato.ApplicationServletBase.doGet(ApplicationServletBase.
java:282)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve
.java:246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:
2347)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche
rValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:
468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcesso
r.java:1027)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.ja
va:1125)
at java.lang.Thread.run(Thread.java:536)There's definitely something wrong with my application directory or
the .war file because I can run the JatoSample and the JatoTutorial
applications fine from within Tomcat-4.0.4.....
--- In SunONE-JATO@y..., "Craig V. Conover" <craig.conover@s...>
wrote:
Send me the war file with source. I'll see if I can run it on mymachine
or figure out what the issue is.
send to: craig.conover@s...
craig
chubbykidd wrote:
Total disaster. My application will not work. I've closed all
instances of Netscape and even logged off the SunRay I'm working on
and I still get the same error. I then took your advice and
downloaded
Resin and installed it. Now when I hit the following URL...
http://localhost:8080/Voyager/voyagermodule/VoyagerLogin I receivean
'Application Error' page which states "Invalid request - request
handler VoyagerLogin not found"
I don't know what to do, I'm running out of possiblities...
Help :-/
--- In SunONE-JATO@y..., "Craig V. Conover" <craig.conover@s...>
wrote:
This will happen if the browser was already running, but you say
you
closed your browsers first. Make sure all instances of the browser
are
closed. For IE, when you launch one IE instance from another
(Ctrl-N),
they share the same process space.
For Netscape, all instances always share the same process space.
This
includes the Mail client, so be sure all of them have been closed.
I might suggest test running in Resin from Caucho (www.caucho.com)
to
make sure it's not a Tomcat bug or setup/install issue. Resin
installs
with just an unzip, and drop the war file in the webapps dir, and
start
the server.
c
chubbykidd wrote:
I deleted my jakarta-tomcat-3.3.1 directory and now I'm getting a
different error when I try to hit the first page in my
application:
>>>>
The URL of my app is:
http://localhost:8080/Voyager/voyagermodule/VoyagerLogin
StackTrace below.... I've restarted tomcat after this stack was
thrown
and I've also closed my browsers and started over and I keep
getting
the same outcome....
javax.servlet.ServletException: This session has timed out
at
com.iplanet.jato.ApplicationServletBase.onSessionTimeout(ApplicationServletBas\
e.java:1075)
>>>
>>>
at
com.iplanet.jato.ApplicationServletBase.fireSessionTimeoutEvent(ApplicationSer\
vletBase.java:941)
>>>
>>>
at
com.iplanet.jato.ApplicationServletBase.fireSessionEvents(ApplicationServletBa\
se.java:649)
>>>
>>>
at
com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.\
java:427)
>>>
>>>
at
com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:312\
>>>
>>>
at
com.iplanet.jato.ApplicationServletBase.doGet(ApplicationServletBase.java:282)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFi\
lterChain.java:247)
>>>
>>>
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChai\
n.java:193)
>>>
>>>
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java\
:243)
>>>
>>>
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566\
>>>
>>>
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java\
:190)
>>>
>>>
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566\
>>>
>>>
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246\
>>>
>>>
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564\
>>>
>>>
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566\
>>>
>>>
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.ja\
va:170)
>>>
>>>
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564\
>>>
>>>
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564\
>>>
>>>
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564\
>>>
>>>
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:1\
74)
>>>
>>>
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566\
>>>
>>>
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:10\
27)
>>>
>>>
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
at java.lang.Thread.run(Thread.java:536)
[85] wb138834@s...:
--- In SunONE-JATO@y..., Todd Fast <Todd.Fast@S...> wrote:
This error means the page/ViewBean you requested was not found.
What is the
URL you are using? Also make sure everything is compiled.
Todd
----- Original Message -----
From: "chubbykidd" <bacon33@o...>
Sent: Thursday, August 29, 2002 11:13 AM
Subject: [SunONE-JATO] Upgraded from Tomcat 3.3.1 to Tomcat
4.0.4
>>>>>
>>>>>
>>>>>
>>>>>
receiving
Stack
I moved my war file into my new Tomcat 4.0.4 webapps directory
since I
need to upgrade in order to use some 'other' tags and I'm
receiving
the following stacktrace when I try to hit the first page in my
application....
Any ideas as to why this is occurring?
StackTrace Below:
Application Error
javax.servlet.ServletException: Invalid request - request
handler
"VoyagerLogin"
not found
at
com.iplanet.jato.ApplicationServletBase.onRequestHandlerNotFound(Appl
icationServletBase.java:1153)
at
com.iplanet.jato.ApplicationServletBase.fireRequestHandlerNotFoundEve
nt(ApplicationServletBase.java:977)
at
com.iplanet.jato.ApplicationServletBase.getViewBeanInstance(Applicati
onServletBase.java:717)
at
com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationSer
vletBase.java:429)
at
com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase
.java:312)
at
com.iplanet.jato.ApplicationServletBase.doGet(ApplicationServletBase.
java:282)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve
.java:246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:
2347)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche
rValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:
468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcesso
r.java:1027)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.ja
va:1125)
at java.lang.Thread.run(Thread.java:536)
To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp -
Re: [SunONE-JATO] Frame Loading
Divakar,
A very challenging scenario for all app servers, especially J2EE web
containers, is concurrent access to session. The HttpSession API does
not provide an interface for either the container vendor or the
developer to manage concurrency issues or events discretely; therefore,
there is little JATO or any framework can do to help you with
concurrency issues AND not add container behavior. The container
vendors have to rely upon implementation details to manage these complex
scenarios. Be that as it may (which is mostly my opinion anyways), the
iAS engineers have worked long and hard the last year from iAS 6.0 sp2
thru 6.5 to deal with issues around session concurrency; the discussion
of which can be fairly verbose. What is important and in some ways
unfortunate, is that the handling on these concurrency scenarios is
different between releases. I believe that there is no blocking/locking
in sp2 and earlier (resembling NetDynamics 3.x behavior). In sp3 (your
case) concurrent access was serialized (resembling in some ways
NetDynamics 4.x and 5.x) In sp4 it was changed again and finally in 6.5
it was improved to ensure data coherency and stability with locking
while eliminating locks within the same JVM. If you would like details
email me offline at [matthew.stevens@s...] and I will see what I can do.
No matter what version of iAS you are using, please ensure that your
application is deployed with Sticky load-balancing such that request
process is handled by the same JVM per session. In this way, you avoid
the 'distributed' computing problem of locking across processes and
machines. In other words, you have far less chance of hung request
threads if you use sticky load-balancing.
You need to establish some debug techniques in your development
environment for J2EE to assess hangs or latencies (there are plenty of
synchronous APIs in any J2EE container so this is not just an iAS thing
or Session concurrency thing). If you are on Solaris you may issue a
kill -3 PID
of the JVM running the web container. Sending this SIGQUIT signal to
the JVM will trap the JVM and result in a full thread dump to the
STDERR. For instance, for iAS you would find the JVM (.kjs) spawned by
the kjs script and send it a SIGQUIT. You should very easily see in the
stack traces of the threads, your own thread which is above the dispatch
to your module servlet [ie. you will see the
<ApplicationServletBase.processRequest()] stack frame in the stack trace.
If you are on Win32 you can run the iAS engines in the foreground by
invoking iAS from the command line [kas -debug] in which case the KJS
will appear in its own console window which you can CTRLBREAK to see the
stack trace.
In this way, you can see what your web container is doing while it is
latent or hung.
In your case, you will probably see your request thread blocked in calls
to PlatformNASSession or PlatformLITESession. These two classes are the
HttpSession implementations for iAS. The 'NAS' session uses the HA
Dsync sub-system for replicated attribute backing store and the 'LITE'
session uses an regular HashTable for the backing store.
Again, concurrency issues are FAR MORE complex with the distributed
implementation. Therefore, as an isolation technique, you may want to
confirm that you are using session-impl=lite in your iAS deployment
descriptor so as to avoid the Dsync implementation. Using Session LITE
should eliminate the hangs during concurrent frame loads.
Is it possible for you to upgrade to iAS 6.5? What about iAS 6.0 sp4?
Please remember to leverage the JATO front controller events, even if it
is for debug. You have the onBeforeRequest event where you could
intercept the front controller before it has bothered with the
HttpSession APIs. For isolation purposes, you could enter a critical
section from your derived onBeforeRequest event to see whether
concurrency is an issue in your case.
I hope this "frames" the problem space for you 8-) Please post any
questions or results from your testing and we can try to help further.
The best information we can use to help you is the stack trace for the
hang condition.
thanks,
matt
padiyar wrote:
I am facing problems with FrameSet loading.
I have a frameset having two frames and src defined
for both. Sometimes one of the frames doesnt get loaded.
I am using iAS 6.0 with SP3 and JATO 1.2
<FRAMESET COLS="200,*" BORDER=0 FRAMEBORDER=no>
<FRAME NAME="Frame1" SRC="../AppName/pgMenu" MARGINHEIGHT=0
MARGINWIDTH=10 SCROLLING=auto NORESIZE >
<FRAME NAME="Frame2" SRC="../AppName/pgDetail" MARGINHEIGHT=6
MARGINWIDTH=12 SCROLLING=auto RESIZE >
</FRAMESET>
From the kjs logs i noticed that onAfterRequest is not getting called
while first frame's viewbean is being executed and kjs just hangs.
If I set the SRC for one of the frames as viewbean and the other one
a blank.html and trigger the loading of second frame using javascript
on load of the first frame it works fine. But i dont
want to go for this approach.
Did anybody faced this problem and know how to fix this without using
javascripts?
Thanks,
Divakar
To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsptest
-
IPod no longer works with car stereo since upgraded MBA & iTunes
My iPod classic has worked just fine connected to my car stereo since i bought it last june. I just bought a new Macbook Air (OS 10.7.3) & installed ITUNES 10.6.1. After I synched my ipod for the first time its recognised by the car but i get a "can't read data" message. I re-formatted my ipod but its exactly the same. Do you think its the upgrade- or the cable? Has anyone else found a bug with this version of Itunes or the OS? I have my doubts a cable would make the difference, and my old ipod nano that i haven't synched for a while works fine.
If standalone works fine, then, most likely the 30 pin connect may have some dirt or lint, prevent data transfer.
You can try to blow it clean, if you have a can of compressed air or gas.
Alternatively you can connect it to the car stereo and do the RESET, while connnected.as follows
Toggle the Hold switch, make sure you dont see the red mark when you do the next step
Reset the iPod -> Press Menu and Center button simultaneously for about 10 secs or till the Apple Logo comes ON
Then release the buttons
Select your preferred language.
Here is the Apple support Article on the 5Rs
http://www.apple.com/support/ipod/five_rs/classic/
The Reset sequence may send a signal to the Car stereo to do the right thing -
Brand new IPOD Touch Apps no longer work after upgrading software
I got a Ipod touch for my wife Today at Wal-Mart. I brought it home, connected to wifi and downloaded some apps and also payed for some. They all worked fine. Then I connected to computer to transfer songs. It told me to upgrade the Ipod software so i Did. After it restarted none of the downloaded apps work anymore. I have read MANY MANY MANY discussions on this and there is no fix. I am not wiping out all the songs and reload everything all over again. It will take forever. My wifes BD is Friday and this is making me so mad after I just dropped $300 on this thing. APPLE!!! Where is the fix? I deleted the apps and reinstalled they still don't work. Anybody got this figured out? I am getting ready to get my money back and tell everyone to avoid buying ipod until they get this upgrade bug fixed.
Message was edited by: 2009 IPOD TOUCHI have the same problem. Brand new two days ago. I synched the touch with Itunes but wasn't hooked up to the internet at the time so didn't do the software upgrade right away. Then I downloaded about a dozen apps (free and paid) with wifi directly to the touch. They all worked fine. Then I plugged it back in to Itunes and had it upgrade it to 3.1.2. It locked up Itunes several times since then and the downloaded apps no longer work (they start to open then disappear).
The problem is, no one is listening to this problem (including Anna above)! Everyone says "just do a hard reboot, or restore to factory settings, reload the apps, etc." I've tried all the standard troubleshooting but none of it fixes this. It sure seems to me this is a problem with 3.1.2 but Apple isn't helping out here. Where are you APPLE? Use some of those outrageous profits you're making to fix the problem you have created. Here's $300 of my hard earned dollars pretty much down the drain.
Message was edited by: IPatronius -
Ipod touch can no longer connect to XP following Apple upgrade, HELP !
This is a nightmare. My son has an ipod touch (8gb)purchased a couple of months, and it's been fine until a couple of days ago. I downloaded some music for him, and just about to synch when Apple informed me on itunes of a software upgrade, so naturally I did this. However, it could not complete it saying there was a problem installing the hardware. The ipod then had a permanent picture of a usb cable pointing towards the itunes logo. Itunes no longer recognises this ipod or my own ipod as a device.
I'm not a techhie expert, but I generally know my way around computers, however I could not resolve this.
I called the Apple technical support desk, where I spent 1 hour 45 minutes with 2 different advisors who could not resolve this. We installed and re-installed various components from drivers to itunes to anti virus software, however nothing could change. There was simply no recognition of the ipod at all when connected.It does give a pop up message to restore the ipod, however you can't actually click on the restore button because to have to get rid of the pop up message first, then the screen with the restore facility disappears.
Windows xp is continually popping up a message saying " FOUND NEW HARDWARE WIZARD There was a problem installing this hardware. Apple Mobile USB driver. An error occured during the installation of the device. The system cannot find the file specified."
You then have to click on finish, however the message keeps coming back. We kept going round and round in circles with the technical support people, where it was left that I should start removing programmes on my computer to see if any of those are causing a problem. I have had the same spyware for the last 12 months now and never had a problem before, nor any other programmes.
I booked a genius appointment at my local Apple store today where the assistant reset the ipod to factory settings so it could at least work. I explained the situation, however 15 minutes was never going to be long enough to look into it, and a restore was all they did. Obviously all of my programmes were lost, however when I got home and plugged it back into the computer again, it could not be recognised by itunes and i got the same pop up message. Luckily we have not spent alot on downloads, however my son has lost his music now and it cannot be connected or upgraded. It's under guarantee however a software upgrade by Apple has totally messed my computer up. I really don't know who to turn to now as both the service support and store has not rectified this, something I feel has been caused by Apple.
Any advice is appreciated. ThanksDoes the iOS device connect to other networks?
Does the iOS device see the network?
Any error messages?
Do other devices now connect?
Did the iOS device connect before?
Try the following to rule out a software problem:
- Reset the iOS device. Nothing will be lost
Reset iOS device: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- Power off and then back on your router
.- Reset network settings: Settings>General>Reset>Reset Network Settings
- iOS: Troubleshooting Wi-Fi networks and connections
- Wi-Fi: Unable to connect to an 802.11n Wi-Fi network
- iOS: Recommended settings for Wi-Fi routers and access points
- Restore from backup. See:
iOS: How to back up
- Restore to factory settings/new iOS device.
If still problem make an appointment at the Genius Bar of an Apple store since it appears you have a hardware problem.
Apple Retail Store - Genius Bar -
Just upgraded HDD, now how do I get my data back??
I just upgraded my stock 60GB HD to a 120GB Seagate Momentus 5400 ($100). This is what I did:
1. Before removing the 60GB HD, i created a read-only disk image of my HD(with Disk Utility on the OSX install CD). I put this disk image on my USB external hard drive.
2. Physically replaced the 60GB with the 120GB.
3. Now, I boot up the computer to the OSX install CD (since it is a blank new HD). I open up Disk Utility on the install CD, and try to restore the image i created (on my external USB HD) to my new 120GB internal drive. I am able to select the image to restore, but cannot select my internal drive as the destination.
I have all sorts of music, movies, applications...etc. on my old HD that I want on my new drive.
I want to have my computer be identical to before I upgraded, just with a larger HD. Is this possible?
I have tons of external USB HD space to use if needed, and I also still have the old HD... if I need to create a different kind of disk image or something.
Please help!
Macbook 2.0GHz (White) Mac OS X (10.4.8)I did this already. I failed to mention it in my first post. I have my HD "111.8 GB Seagate..." and underneath it: "Macintosh HD". Still can't restore an image to the "Macintosh HD" volume.
-
BSI Tax Factory Upgrade 8.0 to 9.0
Hi BSI,
We are upgrading our BSI tax Factory from 8.0 to 9.0. We are running:
Windows 2008 R2
SQL Server version 10.50.1777
I'm able to connect to the database using login TF90 through SQL Server Management Studio, the ODBC Data Source Administrator and the TaxFactory Client is connecting fine too.
But when running report RPUBTCU0 from the SAP system , its caught under ABAP dump-> SYSTEM FAILURE.
Looking at the error.txt.
=Running connect_db_taxfactory
BSI dataset -> 101
ConnectToDataSource... Starting
ConnectToDataSource...Succeeded
Connect to Dataset Error string = 101
ConnectToDataSet... Starting
ConnectToDataSet...failed
Error String -> 4020 - THERE IS NO VALID LICENSE INSTALLED FOR HOST HCA-MSAP68:UNKNOWN.
=RFC error
operation/code connect_db_payroll_tax_calc_us
key RFC_ERROR_SYSTEM_FAILURE
status
message See RFC trace file or SAP system log for more details
internal status .
The machine key is successfully installed.
Please guide what we are missing here.
Please contact me at +60123675076 (malaysia) at anytime.
Thanks.
ThavaWe managed to solve this by changing tf90server.bat file.
from - I:
CD I:\BSI\Server9.0
tf90server.exe %*
To - I:\BSI\Server9.0\tf90server.exe %*
Now we could run report RPUBTCU0 without error.
Thanks.
Thava -
Upgrade to ERp6 phase STARTSAP_NBAS error: DDIC login fails
Hi
During an upgrade from 4.7 to ERP6 I get the following error
message in phase STARTSAP_NBAS:
SYSTEM START failed, code -2
-2: the test rfc did not work.
Try to log on to the system with user DDIC
When I try to log on to the system as user DDIC, I get the following
error message:
DB-Error -0
SAP* can log in .The password I submit is correct. I have not changed this password at
any time.
Any ideas are most welcomeHi,
DB-Error -0 indicate problem with kernel, try to upgrade kernel.
check Note 760175 - 6.20: Logon not possible (after DB export or system copy)
regards,
kaushal -
Lock-ups on MCS-7825 after after OS Upgrade to 2000.4.4aSR6
About 3 weeks ago, I upgraded some MCS-7825 & MCS-7835 servers to 2000.4.4aSR6. Since then, one of the 7825's has been rebooting on its own almost twice a day. The other 7825 and 7835s are operating fine.
Anybody else encountering a problem with this? I see in the release notes, some BIOS and firmware updates are included for the 7825, and am suspecting this is the problem.My problems actually turned out to be hardware, I think. I reviewed the logs and found out it had been happening for several months.
-
I have the Satellite X205-S7483 w/ 2gb ram.
Can I add more memory and can I possibly upgrade the video card? I have a Geoforce 8700m gt 256MB
Thanks!You have a User's Manual right there on your desktop. Go to Start/All Programs/My Toshiba/User's Guide. Or you can click on Download at the top of this page, enter the model info requested and you'll find the User's Guide and lots of other info for your model.
C.B.
Toshiba Sat. C75D-B7260 Win 8.1 64 Bit--Toshiba Sat. L775D-S7132 Win 7 HP SP1 64 Bit and Win 10 PRO Technical Preview--Toshiba Sat. L305-S5921 Win Vista SP2 32 Bit
Maybe you are looking for
-
I may have read it somewhere but forgot... HTML DB reads the session cookie on every single request, correct ? So why is Session ID in URL necessary really ??? since that value is already in the cookie.
-
Hi, How does XSU deal with ID and IDREF in XML document? Are they treated as normal attributes? null
-
Can't install/download Mac OS X Lion. Help please.
My AppStore says I have lion already installed, but it isn't (still have 10.6.8). How can I find it or re-download it?
-
Hi, BEGIN TRANSACTION in Sybase is handled by omwb_emulation package in Oracle. But the associated "RollBack Transaction" in Sybase is replaced to a ROLLBACK WORK in Oracle, which seems to be wrong. I feel that it should be "RollBack to somesavepoint
-
Switching numbers between acounts?
Hey, I have 5 lines on my account and I'm looking to start an additional individual plan. Say I get a new phone during a Black Friday deal. What I want to know is if I will be able to switch one of the phone numbers from the existing lines to the new