Naming AQ objects

Hi there,
I want to name all objects that are automatically created by Oracle 10g when creating a queue.
Those objects are:
SYS_... Index on MSGID column of Queue Table.
SYS_LOB... LOB corresponding to USER_PROP SYSANYDATA column in Queue Table
AQ$_... Indexes, views and queue automatically created with the queue.
Is there a way to use custom names for all these objects at creation, especially for SYS_ index and SYS_LOB?
I tried the storage clause with no luck as it say that "USER_PROP" is an invalid identifier (LOB(USER_PROP) STORE AS XXX)
Thank you very much in advance.

Hi Neerb,
Consider this:
CREATE TABLE "EDC"."RAW_DATA_QUEUETAB"
(     "Q_NAME" VARCHAR2(30 BYTE),
     "MSGID" RAW(16),
     "CORRID" VARCHAR2(128 BYTE),
     "PRIORITY" NUMBER,
     "STATE" NUMBER,
     "DELAY" TIMESTAMP (6),
     "EXPIRATION" NUMBER,
     "TIME_MANAGER_INFO" TIMESTAMP (6),
     "LOCAL_ORDER_NO" NUMBER,
     "CHAIN_NO" NUMBER,
     "CSCN" NUMBER,
     "DSCN" NUMBER,
     "ENQ_TIME" TIMESTAMP (6),
     "ENQ_UID" VARCHAR2(30 BYTE),
     "ENQ_TID" VARCHAR2(30 BYTE),
     "DEQ_TIME" TIMESTAMP (6),
     "DEQ_UID" VARCHAR2(30 BYTE),
     "DEQ_TID" VARCHAR2(30 BYTE),
     "RETRY_COUNT" NUMBER,
     "EXCEPTION_QSCHEMA" VARCHAR2(30 BYTE),
     "EXCEPTION_QUEUE" VARCHAR2(30 BYTE),
     "STEP_NO" NUMBER,
     "RECIPIENT_KEY" NUMBER,
     "DEQUEUE_MSGID" RAW(16),
     "SENDER_NAME" VARCHAR2(30 BYTE),
     "SENDER_ADDRESS" VARCHAR2(1024 BYTE),
     "SENDER_PROTOCOL" NUMBER,
     "USER_DATA" "EDC"."MEASUREMENT_RAW_DATA_TYPE" ,
     "USER_PROP" "SYS"."ANYDATA" ,
     PRIMARY KEY ("MSGID")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "EDC_MAIN" ENABLE
) USAGE QUEUE PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "EDC_MAIN"
LOB ("USER_DATA"."RAW_MESSAGE") STORE AS "RDQT_RAW_MESSAGE_LOBSEG"(
TABLESPACE "EDC_MAIN" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSION 10
NOCACHE LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT))
OPAQUE TYPE "USER_PROP" STORE AS LOB (
ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSION 10
CACHE
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)) ;
Just an idea ...
Perhaps this helps you.
Please post here again, if this works.

Similar Messages

  • RE: Named anchored objects

    Albert,
    In my case I was using a named anchored object to get a handle to an actual
    service object. My named object that I registered in the name service was
    an intermediary to which I did not maintain a connection. So I have not
    explicitly tested what you are asking.
    However, I too was not using a hard coded reference to the SO, and fail over
    and load balancing worked fine. The functions of fail over and load
    balancing are not done by the service object but by the name service, proxy
    and router. Since you are getting a proxy back any time you do a lookup in
    the name service I would think that fail over should work with any anchored
    object that is registered in the name service. When you do a RegisterObject
    call you will notice that one of the arguments is the session duration,
    which implies to me that fail over will be handled the same as for service
    objects.
    Load balancing adds another wrinkle. Load balancing is handled by a router.
    You must get a proxy to the router and not a proxy to an instance of the
    object that the router is doing the load balancing for. In the latter
    scenario you will be bypassing the router. If you are creating, anchoring
    and registering your objects dynamically you will not have a router so you
    will not be able to load balance! This applies even if the objects are
    instantiated within partitions that are load balanced because you will still
    be getting proxies back to a particular instance of the anchored objects.
    There are ways to accomplish load balancing between objects that you
    register yourself. However, the best solution will vary depending on the
    actual problem trying to be solved. If you would like to discuss this
    further, include a little more detail about the scenario you need to
    implement and I will give you what I know.
    BTY what I have outlined above also applies to getting references via a
    system agent.
    Sean
    Cornice Consulting, Inc.
    -----Original Message-----
    From: [email protected]
    [<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of Albert Dijk
    Sent: Friday, July 03, 1998 11:01 AM
    To: [email protected]
    Subject:
    Alex, David, Jez, Sean,...
    My question about both solutions (using Nameservice and agents) is:
    If I reach a remote service object using either a BindObject or an agent, do
    fail-over and load-balancing work the same way as they normally do when
    using a hard coded reference to the SO.
    Albert Dijk
    From: Sean Brown[SMTP:[email protected]]
    Reply To: [email protected]
    Sent: Thursday, June 25, 1998 6:55 AM
    To: Ananiev, Alex; [email protected]
    Subject: RE: multiple named objects with the same name and
    interface
    Alexander,
    I can not comment on the speed difference because I never tested it.
    But, I
    will say that we looked at the agent solution at a client sight
    before. I
    will give the same warning I gave them. If you go the agent direction
    you
    are now using agents for a purpose that they were not intended. Even
    though
    it technically works, as soon as you start using a piece of
    functionality in
    a way the developer did not intend it to be used you run the risk of
    forward
    compatibility problems. By this I mean, since agents were not
    originally
    intended to be used to look up service / anchored object references,
    it may
    not work in the future because it is not likely to be given
    consideration in
    any future design.
    As we all know, programmers are always stretching the bounds of the
    tools
    they use and you may have a good reason (i.e. performance). I just
    wanted to
    let you know the possible risk.
    One final note on a limitation of using system agents to obtain
    references
    to anchored objects. You can not access agents across environments.
    So, if
    you have connected environments and need to get references to services
    in
    another environment for fail-over or whatever, you will not be able to
    do it
    with agents.
    Just some thoughts!
    Sean
    -----Original Message-----
    From: [email protected]
    [<a href="mailto:[email protected]]On">mailto:[email protected]]On</a> Behalf Of Ananiev, Alex
    Sent: Wednesday, June 24, 1998 12:14 PM
    To: '[email protected]'
    Subject: RE: multiple named objects with the same name and interface
    David,
    The problem with dynamic binding is that in this case you have to keep
    the reference to the service object somewhere. You don't want to call
    "bindObject" every time you need to use this service object, "bind" is
    a
    time-consuming operation, even on the same partition. Keeping
    reference
    could be undesirable if your object could be moved across partitions
    (e.g. business object).
    The alternative solution is to use agents. You can create custom
    agent,
    make it a subagent of an active partition agent and use it as a
    placeholder for whatever service you need. "FindSubAgent" works much
    faster than "bindObject", we verified that and agent is "user-visible"
    by its nature.
    Alexander
    From: "Sean Brown" <[email protected]>
    Date: Wed, 24 Jun 1998 09:12:55 -0500
    Subject: RE: multiple named objects with the same name and interface
    David,
    I actually determined it through testing. In my case I did not want
    this to
    happen and was trying to determine why it was happing. It makes sense
    if
    you think about it. Forte is trying to avoid making a remote method
    invocation if it can.
    Now, for anything more complex than looking locally first and if none
    is
    found give me any remote instance you can find, you will need to do
    more
    work. Using a naming scheme like Jez suggests below works well.
    Sean
    - -----Original Message-----
    From: Jez Sygrove [<a href="mailto:[email protected]">mailto:[email protected]</a>]
    Sent: Wednesday, June 24, 1998 4:34 AM
    To: [email protected]; 'David Foote'
    Cc: [email protected]
    Subject: RE: multiple named objects with the same name and interface
    David,
    there's a mechanism used within SCAFFOLDS that allows the
    location of the 'nearest' SO when more than one is available.
    It involves registering each duplicated SO under three dynamically
    built
    names. The names include the partition, the node or the environment
    name.
    When wishing to locate the nearest SO the BO builds a SO name using
    its
    own partition and asks the name service for that.
    If there is an SO registered under that name then it must be in the
    same
    partition and all is well. No cross partition calls.
    If not, then the BO builds the name using its node and asks the name
    service for that.
    This means that if there is an SO outside the BO partition but still
    on
    the same node then this can be used. Again, relatively 'local'.
    If neither of these work then the BO has to resort to an environment
    wide search.
    It may be that this approach could be adapted / adopted; I like it's
    ingenuity.
    Cheers,
    Jez
    From: David Foote[SMTP:[email protected]]
    Reply To: David Foote
    Sent: 24 June 1998 03:17
    To: [email protected]
    Cc: [email protected]
    Subject: RE: multiple named objects with the same name and
    interface
    Sean,
    First, thank you for your response. I have wondered about this fora
    long time.
    I looked at the documentation for ObjectLocationManager and on page
    327
    of the Framework Library and AppletSupport Library Guide indescribing
    the BindObject method Forte says:
    "The name service allows more than one anchored object (from
    different
    partitions) to be registered in the name service under the same
    registration name. When you invoke the BindObject method with a
    request
    for a name that has duplicate registration entries, the BindObject
    method finds an entry corresponding to an active partition, skipping
    any
    entries that do not. If no such active partition is found, or if the
    requested name is not found in the name service registry, a
    RemoteAccessException will be raised when the BindObject method is
    invoked."
    My question is: How did you discover that in the case of duplicate
    registrations the naming service will return the local object if one
    exists? This is not apparent from the documentation I have quoted.
    Is
    it documented elsewhere? Or did you determine it empirically?
    David N. Foote,
    Consultant
    ----Original Message Follows----
    David,
    First I will start by saying that this can be done by using named
    anchored
    objects and registering them yourself in the name service. There is
    documentation on how to do this. And by default you will get mostof
    the
    behavior you desire. When you do a lookup in the name service
    (BindObject
    method) it will first look in the local partition and see if thereis
    a
    local copy and give you that copy. By anchoring the object and
    manually
    registering it in the name service you are programmatically creating
    your
    own SO without defining it as such in the development environment.
    BTW
    in
    response to your item number 1. This should be the case there as
    well.
    If
    your "mobile" object is in the same partition where the serviceobject
    he is
    calling resides, you should get a handle to the local instance ofthe
    service object.
    Here is the catch, if you make a bind object call and there is no
    local
    copy
    you will get a handle to a remote copy but you can not be sure which
    one!
    It end ups as more or less a random selection. Off the top of myhead
    and
    without going to the doc, I am pretty sure that when you register an
    anchored object you can not limit it's visibility to "User".
    Sean
    -----Original Message-----
    From: [email protected]
    [<a href=
    "mailto:[email protected]]On">mailto:[email protected]]On</a> Behalf Of David Foote
    Sent: Monday, June 22, 1998 4:51 PM
    To: [email protected]
    Subject: multiple named objects with the same name and interface
    All,
    More than once, I have wished that Forte allowed you to place named
    objects with the same name in more than one partition. There aretwo
    situations in which this seems desirable:
    1) Objects that are not distributed, but are mobile (passed by value
    to
    remote objects), cannot safely reference a Service Object unless it
    has
    environment visibility, but this forces the overhead of a remote
    method
    call when it might not otherwise be necessary. If it were possibleto
    place a copy of the same Service Object (with user visibility) ineach
    partition, the overhead of a remote method call could be avoided.
    This
    would only be useful for a service object whose state could besafely
    replicated.
    2) My second scenario also involves mobile objects referencing a
    Service
    Object, but this time I would like the behavior of the calledService
    Object to differ with the partition from which it is called.
    This could be accomplished by placing Service Objects with the same
    name
    and the same interface in each partition, but varying the
    implementation
    with the partition.
    Does anyone have any thoughts about why this would be a good thingor
    a
    bad thing?
    David N. Foote
    Consultant
    Alexander Ananiev
    Claremont Technology Group
    916-558-4127
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive
    <URL:<a href="http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
    >
    >
    >
    Alexander Ananiev
    Claremont Technology Group
    916-558-4127
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

    Albert,
    In my case I was using a named anchored object to get a handle to an actual
    service object. My named object that I registered in the name service was
    an intermediary to which I did not maintain a connection. So I have not
    explicitly tested what you are asking.
    However, I too was not using a hard coded reference to the SO, and fail over
    and load balancing worked fine. The functions of fail over and load
    balancing are not done by the service object but by the name service, proxy
    and router. Since you are getting a proxy back any time you do a lookup in
    the name service I would think that fail over should work with any anchored
    object that is registered in the name service. When you do a RegisterObject
    call you will notice that one of the arguments is the session duration,
    which implies to me that fail over will be handled the same as for service
    objects.
    Load balancing adds another wrinkle. Load balancing is handled by a router.
    You must get a proxy to the router and not a proxy to an instance of the
    object that the router is doing the load balancing for. In the latter
    scenario you will be bypassing the router. If you are creating, anchoring
    and registering your objects dynamically you will not have a router so you
    will not be able to load balance! This applies even if the objects are
    instantiated within partitions that are load balanced because you will still
    be getting proxies back to a particular instance of the anchored objects.
    There are ways to accomplish load balancing between objects that you
    register yourself. However, the best solution will vary depending on the
    actual problem trying to be solved. If you would like to discuss this
    further, include a little more detail about the scenario you need to
    implement and I will give you what I know.
    BTY what I have outlined above also applies to getting references via a
    system agent.
    Sean
    Cornice Consulting, Inc.
    -----Original Message-----
    From: [email protected]
    [<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of Albert Dijk
    Sent: Friday, July 03, 1998 11:01 AM
    To: [email protected]
    Subject:
    Alex, David, Jez, Sean,...
    My question about both solutions (using Nameservice and agents) is:
    If I reach a remote service object using either a BindObject or an agent, do
    fail-over and load-balancing work the same way as they normally do when
    using a hard coded reference to the SO.
    Albert Dijk
    From: Sean Brown[SMTP:[email protected]]
    Reply To: [email protected]
    Sent: Thursday, June 25, 1998 6:55 AM
    To: Ananiev, Alex; [email protected]
    Subject: RE: multiple named objects with the same name and
    interface
    Alexander,
    I can not comment on the speed difference because I never tested it.
    But, I
    will say that we looked at the agent solution at a client sight
    before. I
    will give the same warning I gave them. If you go the agent direction
    you
    are now using agents for a purpose that they were not intended. Even
    though
    it technically works, as soon as you start using a piece of
    functionality in
    a way the developer did not intend it to be used you run the risk of
    forward
    compatibility problems. By this I mean, since agents were not
    originally
    intended to be used to look up service / anchored object references,
    it may
    not work in the future because it is not likely to be given
    consideration in
    any future design.
    As we all know, programmers are always stretching the bounds of the
    tools
    they use and you may have a good reason (i.e. performance). I just
    wanted to
    let you know the possible risk.
    One final note on a limitation of using system agents to obtain
    references
    to anchored objects. You can not access agents across environments.
    So, if
    you have connected environments and need to get references to services
    in
    another environment for fail-over or whatever, you will not be able to
    do it
    with agents.
    Just some thoughts!
    Sean
    -----Original Message-----
    From: [email protected]
    [<a href="mailto:[email protected]]On">mailto:[email protected]]On</a> Behalf Of Ananiev, Alex
    Sent: Wednesday, June 24, 1998 12:14 PM
    To: '[email protected]'
    Subject: RE: multiple named objects with the same name and interface
    David,
    The problem with dynamic binding is that in this case you have to keep
    the reference to the service object somewhere. You don't want to call
    "bindObject" every time you need to use this service object, "bind" is
    a
    time-consuming operation, even on the same partition. Keeping
    reference
    could be undesirable if your object could be moved across partitions
    (e.g. business object).
    The alternative solution is to use agents. You can create custom
    agent,
    make it a subagent of an active partition agent and use it as a
    placeholder for whatever service you need. "FindSubAgent" works much
    faster than "bindObject", we verified that and agent is "user-visible"
    by its nature.
    Alexander
    From: "Sean Brown" <[email protected]>
    Date: Wed, 24 Jun 1998 09:12:55 -0500
    Subject: RE: multiple named objects with the same name and interface
    David,
    I actually determined it through testing. In my case I did not want
    this to
    happen and was trying to determine why it was happing. It makes sense
    if
    you think about it. Forte is trying to avoid making a remote method
    invocation if it can.
    Now, for anything more complex than looking locally first and if none
    is
    found give me any remote instance you can find, you will need to do
    more
    work. Using a naming scheme like Jez suggests below works well.
    Sean
    - -----Original Message-----
    From: Jez Sygrove [<a href="mailto:[email protected]">mailto:[email protected]</a>]
    Sent: Wednesday, June 24, 1998 4:34 AM
    To: [email protected]; 'David Foote'
    Cc: [email protected]
    Subject: RE: multiple named objects with the same name and interface
    David,
    there's a mechanism used within SCAFFOLDS that allows the
    location of the 'nearest' SO when more than one is available.
    It involves registering each duplicated SO under three dynamically
    built
    names. The names include the partition, the node or the environment
    name.
    When wishing to locate the nearest SO the BO builds a SO name using
    its
    own partition and asks the name service for that.
    If there is an SO registered under that name then it must be in the
    same
    partition and all is well. No cross partition calls.
    If not, then the BO builds the name using its node and asks the name
    service for that.
    This means that if there is an SO outside the BO partition but still
    on
    the same node then this can be used. Again, relatively 'local'.
    If neither of these work then the BO has to resort to an environment
    wide search.
    It may be that this approach could be adapted / adopted; I like it's
    ingenuity.
    Cheers,
    Jez
    From: David Foote[SMTP:[email protected]]
    Reply To: David Foote
    Sent: 24 June 1998 03:17
    To: [email protected]
    Cc: [email protected]
    Subject: RE: multiple named objects with the same name and
    interface
    Sean,
    First, thank you for your response. I have wondered about this fora
    long time.
    I looked at the documentation for ObjectLocationManager and on page
    327
    of the Framework Library and AppletSupport Library Guide indescribing
    the BindObject method Forte says:
    "The name service allows more than one anchored object (from
    different
    partitions) to be registered in the name service under the same
    registration name. When you invoke the BindObject method with a
    request
    for a name that has duplicate registration entries, the BindObject
    method finds an entry corresponding to an active partition, skipping
    any
    entries that do not. If no such active partition is found, or if the
    requested name is not found in the name service registry, a
    RemoteAccessException will be raised when the BindObject method is
    invoked."
    My question is: How did you discover that in the case of duplicate
    registrations the naming service will return the local object if one
    exists? This is not apparent from the documentation I have quoted.
    Is
    it documented elsewhere? Or did you determine it empirically?
    David N. Foote,
    Consultant
    ----Original Message Follows----
    David,
    First I will start by saying that this can be done by using named
    anchored
    objects and registering them yourself in the name service. There is
    documentation on how to do this. And by default you will get mostof
    the
    behavior you desire. When you do a lookup in the name service
    (BindObject
    method) it will first look in the local partition and see if thereis
    a
    local copy and give you that copy. By anchoring the object and
    manually
    registering it in the name service you are programmatically creating
    your
    own SO without defining it as such in the development environment.
    BTW
    in
    response to your item number 1. This should be the case there as
    well.
    If
    your "mobile" object is in the same partition where the serviceobject
    he is
    calling resides, you should get a handle to the local instance ofthe
    service object.
    Here is the catch, if you make a bind object call and there is no
    local
    copy
    you will get a handle to a remote copy but you can not be sure which
    one!
    It end ups as more or less a random selection. Off the top of myhead
    and
    without going to the doc, I am pretty sure that when you register an
    anchored object you can not limit it's visibility to "User".
    Sean
    -----Original Message-----
    From: [email protected]
    [<a href=
    "mailto:[email protected]]On">mailto:[email protected]]On</a> Behalf Of David Foote
    Sent: Monday, June 22, 1998 4:51 PM
    To: [email protected]
    Subject: multiple named objects with the same name and interface
    All,
    More than once, I have wished that Forte allowed you to place named
    objects with the same name in more than one partition. There aretwo
    situations in which this seems desirable:
    1) Objects that are not distributed, but are mobile (passed by value
    to
    remote objects), cannot safely reference a Service Object unless it
    has
    environment visibility, but this forces the overhead of a remote
    method
    call when it might not otherwise be necessary. If it were possibleto
    place a copy of the same Service Object (with user visibility) ineach
    partition, the overhead of a remote method call could be avoided.
    This
    would only be useful for a service object whose state could besafely
    replicated.
    2) My second scenario also involves mobile objects referencing a
    Service
    Object, but this time I would like the behavior of the calledService
    Object to differ with the partition from which it is called.
    This could be accomplished by placing Service Objects with the same
    name
    and the same interface in each partition, but varying the
    implementation
    with the partition.
    Does anyone have any thoughts about why this would be a good thingor
    a
    bad thing?
    David N. Foote
    Consultant
    Alexander Ananiev
    Claremont Technology Group
    916-558-4127
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive
    <URL:<a href="http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
    >
    >
    >
    Alexander Ananiev
    Claremont Technology Group
    916-558-4127
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

  • Named GOOP Objects

    I've tried to do some GOOP in LV 6.02 and I wanted to use Named objects/instances.
    It is fairly easy to set the name of an object, but then if I want to read the name of the
    object later on, how do I do that?
    The private functions "Get Data" and "Get Data to Modify" only return the Data from the Object repository, not the name.
    Of course I can in addition call the Object repository using the input method "Get Statistics", but is this the only way to get hold of the name?
    I don't want the statistics, I only want the Data and the name in one go.
    And I also don't want to store the name as part of the Data as what could be another solution.
    GOOP 1.0

    Hello,
    This is a very late reply so it is probably not relevant for you but here we go any way.
    The GetObjectStatus returns the object name from an object reference. But the object data has to be read out separately so it does not fulfill your requirement of data and name in one call. To do better you have to make your own version of GetAtributes to make it return the obj name.
    I am a bit curious about how you use the named objects sine you have this need. The way I have used named objects I only use the name to get the ref and after that I don't care about the name any more.
    Jan

  • OOP dynamic naming of objects

    I'm creating an instance in this way:
    var newhouse:House = new House();
    But I need to create fourty of these objects named:
    "newhouse1","newhouse2",...,"newhouse40"
    How can I name the var dynamicly, since the syntax won't
    allow brackets

    Well, at least to me, having all the instances located in an
    array is
    cleaner. I realize it's not _really_ cleaner, I just like
    sticking stuff
    into arrays. <g>
    Dave -
    Head Developer
    http://www.blurredistinction.com
    Adobe Community Expert
    http://www.adobe.com/communities/experts/

  • Dynamicaly naming an object

    Let's say I have a class named MyBox and I want to create a
    certain number of objects from that class in a loop. How do I do it
    for (var i:Number = 1; i < 4; i++){
    var ["b" + i]:MyBox = new MyBox ("box" + i);
    I was hoping that the above code would create 3 objects (b1,
    b2 and b3) of the class MyBox (the first one getting "box1" as a
    parameter, the second one "box2" and the last one "box3").
    Can anyone help me with this code ? It should be quite simple
    but I can't figure it out.
    Thanks

    for (var i = 1; i < 4; i++){ // you don't need to type var
    i as a Number
    this["b" + i] = new MyBox(this["box" + i]);
    trace(b1 instanceof MyBox); // should return true

  • Naming Standard - Object Types

    Is there a way to extend the options under 'Naming Standard:' to include object types? As well as object type attributes, attributes that are created when a REF link is created or when an attribute's datatype is another object type. I would like to change the template format that is used when the default names are used when creating these items.
    Thanks,
    ScottK

    Hi Scott,
    we have such request logged.
    Philip

  • Naming an object with a string.

    Is it possible to make on object that is named with a String?
    so you make a string String a = "Hello";
    and then you make an object that is called Hello.
    Does anyone know?
    thx, SJG

    AFAIK, no. But depending on what you want to do, there are various ways of storing a String on the basis of another string received at runtime.
    A HashMap, for example, could use the String "Hello" as a key to get at another string:
    HashMap map = new HashMap();
    String inputA = "hello";
    String inputB = "to be stored";
    map.put(inputA, inputB);
    System.out.println(map.get(inputA));Perhaps that might be useful to you?

  • Naming an object - Simple?! - Javascript/Windows

    Hey all!
    And again I'm having trouble in a pretty simple thing. I searched for a code that searches the Paragraph Style that i want to, till here no problem. I fount the item, swap to selection tool so that it can change the selection to the text box instead of the text and then I want to name this object. Just that, but I just can't do it! hahahaha
    Take a look:
    // LOCALIZA O PARAGRAPH STYLE DA REFERÊNCIA
    var oDoc = app.activeDocument;
    //First loop through all stories then through all paragraphs in each story
    for(n=0; n< oDoc.stories.length;n++){
        for(i=0;i<oDoc.stories[n].paragraphs.length;i++){
            // If paragraph style is "Silkeborg" then select paragraph and insert "S " before
            if  (oDoc.stories[n].paragraphs[i].appliedParagraphStyle.name == "referencia") {
                oDoc.stories[n].paragraphs[i].select();
    // SELECIONA O BOX
    app.toolBoxTools.currentTool = UITools.SELECTION_TOOL;
    // NOMEIA
    app.activeDocument.selection.name= "Modelo";
    It searches for it, if finds it, change to selection tool but just won't name the object. What am I doing wrong?
    Here's some other script that i found that names the object by the same objects label:
    var myDocItems = app.activeDocument.allPageItems;
    for(var i = 0; i < myDocItems.length; i++)
      if(!myDocItems[i].name)
        myDocItems[i].name = myDocItems[i].label;
    And this one works, but this object that searching at my script doesn't have a label, so I can't use it.
    Any tips?!
    Thanks guys! Cya!

    "Selection" is always an array, so you can't use
    ..selection.name = ..
    you must use
    ..selection[0].name = ...
    Second, "has no label" is not a problem :-) All textframes have a label (and usually it's empty). I don't know whether you should be using "name" or "label" in this case -- I believe the advantage of "name" in CS5.5 is that it will showin the Layers panel.
    Third (!), there is 1. no need to "switch to selection tool" to set a selection, and neither to use app.select.  Javascript allows instant access to everything, so you could simply set the name of any paragraph's outer frame using something like
    oDoc.stories[i].paragraphs[n].parentTextFrames[0].name = ...
    Note that a single paragraph may have more than a single "parent text frame" -- this paragraph maystart in one and end in another.

  • Naming new objects

    I'm a newb to Java (and programming in general) and I was wondering if anyone could help.
    What I need to make is a bank program that can have an unlimited amount of accounts added to it. Each account is supposed to be an object. The problem i'm having is how to do the unlimited part. I'm creating the objects using the following
    BankAccounts account1 = new BankAccount();
    But what I need is too be able to change "account1" to "account2" and so on for each new object created. any help?

    Instead of changing the name of each object you can add a parameter as account name in the class BankAccount() and every time you create a new object set the name attribute different for that object which can be the loop number...
    ArrayList arr = new ArrayList();
    for(int i=0;i<anyNumber;i++){
    BankAccount account = new BankAccount();
    account.name = "account"+i;
    arr.add(account);
    }In this way when later on you fetch out the objects from the list you can differentiate between each account on the basis of the name property..

  • 20011 A default named pool object cannot be created for an existingshared pool

    Further to my above message about "Cannot update eDirectory for this
    pool", i tried under nssmu on OES/Linux instead of iManager and got the
    above message.
    I found this TID which seems to describe the same problem on NetWare:
    http://support.novell.com/cgi-bin/se...i?10094555.htm
    The prescribed steps didn't work to solve the problem on Linux. The
    only objects i could find in NDS relating to the previous pools of the
    same name were in the SLP DA's scope. Deleting them and trying the
    remaining steps in the TID had no effect.
    I'm about to restart the cluster in question and the SLP DA as well, but
    i expect i am going to meet with the same lack of results.
    Any ideas?
    Paul

    Paul,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
    - Check all of the other support tools and options available at
    http://support.novell.com.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://support.novell.com/forums)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://support.novell.com/forums/faq_general.html
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

  • RE: multiple named objects with the same name andinterface

    David,
    First I will start by saying that this can be done by using named anchored
    objects and registering them yourself in the name service. There is
    documentation on how to do this. And by default you will get most of the
    behavior you desire. When you do a lookup in the name service (BindObject
    method) it will first look in the local partition and see if there is a
    local copy and give you that copy. By anchoring the object and manually
    registering it in the name service you are programmatically creating your
    own SO without defining it as such in the development environment. BTW in
    response to your item number 1. This should be the case there as well. If
    your "mobile" object is in the same partition where the service object he is
    calling resides, you should get a handle to the local instance of the
    service object.
    Here is the catch, if you make a bind object call and there is no local copy
    you will get a handle to a remote copy but you can not be sure which one!
    It end ups as more or less a random selection. Off the top of my head and
    without going to the doc, I am pretty sure that when you register an
    anchored object you can not limit it's visibility to "User".
    Sean
    -----Original Message-----
    From: [email protected]
    [<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of David Foote
    Sent: Monday, June 22, 1998 4:51 PM
    To: [email protected]
    Subject: multiple named objects with the same name and interface
    All,
    More than once, I have wished that Forte allowed you to place named
    objects with the same name in more than one partition. There are two
    situations in which this seems desirable:
    1) Objects that are not distributed, but are mobile (passed by value to
    remote objects), cannot safely reference a Service Object unless it has
    environment visibility, but this forces the overhead of a remote method
    call when it might not otherwise be necessary. If it were possible to
    place a copy of the same Service Object (with user visibility) in each
    partition, the overhead of a remote method call could be avoided. This
    would only be useful for a service object whose state could be safely
    replicated.
    2) My second scenario also involves mobile objects referencing a Service
    Object, but this time I would like the behavior of the called Service
    Object to differ with the partition from which it is called.
    This could be accomplished by placing Service Objects with the same name
    and the same interface in each partition, but varying the implementation
    with the partition.
    Does anyone have any thoughts about why this would be a good thing or a
    bad thing?
    David N. Foote
    Consultant
    Get Your Private, Free Email at <a href=
    "http://www.hotmail.com">http://www.hotmail.com</a>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

    David,
    First I will start by saying that this can be done by using named anchored
    objects and registering them yourself in the name service. There is
    documentation on how to do this. And by default you will get most of the
    behavior you desire. When you do a lookup in the name service (BindObject
    method) it will first look in the local partition and see if there is a
    local copy and give you that copy. By anchoring the object and manually
    registering it in the name service you are programmatically creating your
    own SO without defining it as such in the development environment. BTW in
    response to your item number 1. This should be the case there as well. If
    your "mobile" object is in the same partition where the service object he is
    calling resides, you should get a handle to the local instance of the
    service object.
    Here is the catch, if you make a bind object call and there is no local copy
    you will get a handle to a remote copy but you can not be sure which one!
    It end ups as more or less a random selection. Off the top of my head and
    without going to the doc, I am pretty sure that when you register an
    anchored object you can not limit it's visibility to "User".
    Sean
    -----Original Message-----
    From: [email protected]
    [<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of David Foote
    Sent: Monday, June 22, 1998 4:51 PM
    To: [email protected]
    Subject: multiple named objects with the same name and interface
    All,
    More than once, I have wished that Forte allowed you to place named
    objects with the same name in more than one partition. There are two
    situations in which this seems desirable:
    1) Objects that are not distributed, but are mobile (passed by value to
    remote objects), cannot safely reference a Service Object unless it has
    environment visibility, but this forces the overhead of a remote method
    call when it might not otherwise be necessary. If it were possible to
    place a copy of the same Service Object (with user visibility) in each
    partition, the overhead of a remote method call could be avoided. This
    would only be useful for a service object whose state could be safely
    replicated.
    2) My second scenario also involves mobile objects referencing a Service
    Object, but this time I would like the behavior of the called Service
    Object to differ with the partition from which it is called.
    This could be accomplished by placing Service Objects with the same name
    and the same interface in each partition, but varying the implementation
    with the partition.
    Does anyone have any thoughts about why this would be a good thing or a
    bad thing?
    David N. Foote
    Consultant
    Get Your Private, Free Email at <a href=
    "http://www.hotmail.com">http://www.hotmail.com</a>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

  • BO Business Object Naming Convention

    Hi experts,
    we are about to implement SAP Business objects (previously using only using SAP BW). As part of the implementation we are creating a naming convention / standard for Webi and Universe. Is there anything published on SDN or the web regarding naming conventions / standards or is anyone willing to share some tips.
    BR
    Anders

    Hi Anders,
    In regards to naming your universe objects, please take a look at my blog post re Universe Best Practices (Link: [http://geek2live.net/posts/universe-design-best-practices/]).
    I would always recommend naming universe objects (classes, dimensions, measures etc) in business terminology and being explicit in the definition.  For instance, an object called 'Sales' could be interpreted many different ways.  Is it Sales Revenue, Count of Sales Orders, Count of Sales Order Lines, Average Sales Amount, etc etc?
    Your universes should also be named explicitly so users understand exactly what it contains.  Another example - a Finance universe could contain many things - is it General Ledger Actuals, General Ledger Budgets, Fixed Assets, Accounts Payable etc..
    The most important thing imho, is to define a standard that everyone who is designing universes uses, without exception.  Otherwise the standards don't mean anything to the end users.
    Good luck!
    Josh

  • Difference b/w DATA TYPE and DATA OBJECT & differences b/w TYPE and LIKE

    hai
    can any one say the differences between Data type and Data Object.
    And also differences between TYPE and LIKE
    thanks
    Gani

    hi,
    _Data Types and Data Objects_
          Programs work with local program data – that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and – as a further attribute – by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
          In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
    Data Types
       As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
         All programming languages distinguish between various types of data with various uses, such as ….. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
    Data types can be divided into elementary, reference, and complex types.
    a. Elementary Types
    These are data types of fixed or variable length that are not made up of other types.
    The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
    Predefined and User-Defined Elementary Data Types
    You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
    b.  Reference Types
    Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
    c. Complex Data Types
    Complex data types are made up of other data types. A distinction is made here between structured types and table types.
    Data Objects
          Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
           Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
            A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
    Declaring Data Objects
          Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
         The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
    ABAP contains the following kinds of data objects:
    a.  Literals
    Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
    b.  Named Data Objects
    Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
    Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
    Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
    Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
    c.  Anonymous Data  Objects
    Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
    d.  System-Defined Data Objects
    System-defined data objects do not have to be declared explicitly - they are always available at runtime.
    e.  Interface Work Areas
    Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
    What is the difference between Type and Like?
    Answer1:
    TYPE, you assign datatype directly to the data object while declaring.
    LIKE,you assign the datatype of another object to the declaring data object. The datatype is referenced indirectly.
    Answer2:
    Type is a keyword used to refer to a data type whereas Like is a keyword used to copy the existing properties of already existing data object.
    Answer3:
    type refers the existing data type
    like refers the existing data object
    reward if useful
    thanks and regards
    suma sailaja pvn

  • Named Anchored Obj-Environment Failover

    Hi to all,
    We connect from EnvA to EnvB giving the user directory parameter as / and
    set the Environment Search Path
    as EnvA:EnvB. From both environments we start and register
    '/glob/obj1' named anchored objects with the same name.
    From a client we connect to EnvA and bind to'/glob/obj1' when we shutdown EnvA partition it fails-over to
    EnvB. And then we restart EnvA partition. We restart/rebind the client and
    try to use object. We see that it is using the EnvB object.
    Although we started the primary environment object again.
    It is not using the search path. Once we shutdown secondary environment
    it starts using primary environment object.
    When we try to use relative path when we are binding the object
    First parameter ('glob/obj1') No first slash. Trying 3rd parameter
    for bind function or just using environment search path, Is is not able to
    find the object. From nsls command I figured out that
    under the root directory
    /forte/UUID of ENVA/node
    /site
    /UUID of ENVB
    /glob/obj1
    names are available. When we use relative path (without slash)
    is it trying to find /glob/obj1 under the /forte/UUID of ENVA
    but we are registering the name under the root.
    What is the reason of this odd behaviour or is this a bug?
    Any answer will be appreciated,

    Hi Juliesmiley,
    According to your description, I recommend you check the conditions required for an automatic  failover.
      • Primary replica and secondary replica are both configured for syschronous-commit mode and set to AUTOMATIC failover.
      •  All availability databases that are defined in the availability group must be in a SYNCHRONIZED state between the primary replica and the secondary replica.
      • The Windows Server Failover Clustering (WSFC) cluster has quorum.
      • The primary replica has become unavailable.
    For more information, please review the following articles.
    Failover and Failover Modes (AlwaysOn Availability Groups)
    Troubleshooting automatic failover problems in SQL Server 2012 AlwaysOn environments
    Thanks,
    Lydia Zhang

  • RE: (forte-users) Named Anchored Obj-EnvironmentFailover

    I did some playing around with this stuff as well. I can tell you a few
    things.
    1) The search path option of connected environments only works for SO's, not
    for named anchors.
    2) When EnvA creates a directory "/glob", which contains object "obj1", then
    EnvA owns directory "/glob". Even after restarting environments. If EnvB
    tries to add a subdirectory to "/glob" or inserts its own objects into this
    path, then the situation becomes unstable. It doesn't immediately produce an
    error, but things go wrong anyway. Is this a bug or expected behaviour? I
    don't know. I just learned not to do this. Every environment must place it's
    named anchors in it's own tree. Directories can't be shared.
    3) I think the relative name "glob/obj1" should work, but only if you set
    the ObjectLocationMgr to start looking at the root. Default, it will start
    looking in it's own environment basepath. But I don't have any experience
    with this.
    Pascal Rottier
    Atos Origin Nederland (BAS/West End User Computing)
    Tel. +31 (0)10-2661223
    Fax. +31 (0)10-2661199
    E-mail: Pascal.Rottiernl.origin-it.com
    ++++++++++++++++++++++++++++
    Philip Morris (Afd. MIS)
    Tel. +31 (0)164-295149
    Fax. +31 (0)164-294444
    E-mail: Rottier.Pascalpmintl.ch
    -----Original Message-----
    From: Master Programmer [mailto:masterprghotmail.com]
    Sent: Monday, January 08, 2001 11:13 PM
    To: forte-userslists.xpedior.com
    Subject: (forte-users) Named Anchored Obj-Environment Failover
    Hi to all,
    We connect from EnvA to EnvB giving the user directory parameter as / and
    set the Environment Search Path
    as EnvA:EnvB. From both environments we start and register
    '/glob/obj1' named anchored objects with the same name.
    From a client we connect to EnvA and bind to'/glob/obj1' when we shutdown EnvA partition it fails-over to
    EnvB. And then we restart EnvA partition. We restart/rebind the client and
    try to use object. We see that it is using the EnvB object.
    Although we started the primary environment object again.
    It is not using the search path. Once we shutdown secondary environment
    it starts using primary environment object.
    When we try to use relative path when we are binding the object
    First parameter ('glob/obj1') No first slash. Trying 3rd parameter
    for bind function or just using environment search path, Is is not able to
    find the object. From nsls command I figured out that
    under the root directory
    /forte/UUID of ENVA/node
    /site
    /UUID of ENVB
    /glob/obj1
    names are available. When we use relative path (without slash)
    is it trying to find /glob/obj1 under the /forte/UUID of ENVA
    but we are registering the name under the root.
    What is the reason of this odd behaviour or is this a bug?
    Any answer will be appreciated,
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

    I did some playing around with this stuff as well. I can tell you a few
    things.
    1) The search path option of connected environments only works for SO's, not
    for named anchors.
    2) When EnvA creates a directory "/glob", which contains object "obj1", then
    EnvA owns directory "/glob". Even after restarting environments. If EnvB
    tries to add a subdirectory to "/glob" or inserts its own objects into this
    path, then the situation becomes unstable. It doesn't immediately produce an
    error, but things go wrong anyway. Is this a bug or expected behaviour? I
    don't know. I just learned not to do this. Every environment must place it's
    named anchors in it's own tree. Directories can't be shared.
    3) I think the relative name "glob/obj1" should work, but only if you set
    the ObjectLocationMgr to start looking at the root. Default, it will start
    looking in it's own environment basepath. But I don't have any experience
    with this.
    Pascal Rottier
    Atos Origin Nederland (BAS/West End User Computing)
    Tel. +31 (0)10-2661223
    Fax. +31 (0)10-2661199
    E-mail: Pascal.Rottiernl.origin-it.com
    ++++++++++++++++++++++++++++
    Philip Morris (Afd. MIS)
    Tel. +31 (0)164-295149
    Fax. +31 (0)164-294444
    E-mail: Rottier.Pascalpmintl.ch
    -----Original Message-----
    From: Master Programmer [mailto:masterprghotmail.com]
    Sent: Monday, January 08, 2001 11:13 PM
    To: forte-userslists.xpedior.com
    Subject: (forte-users) Named Anchored Obj-Environment Failover
    Hi to all,
    We connect from EnvA to EnvB giving the user directory parameter as / and
    set the Environment Search Path
    as EnvA:EnvB. From both environments we start and register
    '/glob/obj1' named anchored objects with the same name.
    From a client we connect to EnvA and bind to'/glob/obj1' when we shutdown EnvA partition it fails-over to
    EnvB. And then we restart EnvA partition. We restart/rebind the client and
    try to use object. We see that it is using the EnvB object.
    Although we started the primary environment object again.
    It is not using the search path. Once we shutdown secondary environment
    it starts using primary environment object.
    When we try to use relative path when we are binding the object
    First parameter ('glob/obj1') No first slash. Trying 3rd parameter
    for bind function or just using environment search path, Is is not able to
    find the object. From nsls command I figured out that
    under the root directory
    /forte/UUID of ENVA/node
    /site
    /UUID of ENVB
    /glob/obj1
    names are available. When we use relative path (without slash)
    is it trying to find /glob/obj1 under the /forte/UUID of ENVA
    but we are registering the name under the root.
    What is the reason of this odd behaviour or is this a bug?
    Any answer will be appreciated,
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Maybe you are looking for