String properties

String cat = name.substring(0, name.lastIndexOf('\\'));
String cat1 = cat.substring(cat.lastIndexOf('\\')+1));
Can anyone explain to be the difference between the 2?
thanks.

either look at this http://java.sun.com/j2se/1.4.2/docs/api/java/lang/String.html
or try it out

Similar Messages

  • Crawled property category option: "Map all string properties in this category to the Content managed property"

    I've been searching online, and haven't been able to find a definitive answer to this. Does anyone know what the following SharePoint 2013 Search Service Application, Crawled property category option does?
    "Map all string properties in this category to the Content managed property"
    It appears when editing a crawled property category.

    Hi Vishal,
    There is no Official documentation explaining the setting "Map all string properties in this category to the Content managed property". In my opinion,  this setting will map all crawled properties which are in current category and 
    whose value is string type   to  the Content managed property.
    Thanks,
    Eric
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • How to use Profiler/XE to capture connection string properties (eg effectiveusername)

    Hi all,
    I'm trying to audit connections to a tabular cube to map usage patterns etc etc
    Problem is, any connections made via sharepoint come in using the sharepoint excel services account. The actual user that is making the connection is passed in via the EffectiveUser property on the connection string. I've not been able to find any info on
    how to add this to an extended event trace. Is it possible?
    Cheers,
    Jakub
    Jakub @ Adelaide, Australia Blog

    Hi jakubk,
    Glad to hear that the issue is resolved. Thanks for your sharing, other community members could benefit from your solution.
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • How to Change String Default Sort Order for Table?

    I have a RichTable with SortableModel, but all string properties sort as follows:
    AAAAAA
    ZZZZZZ
    aaaaaa
    bbbbb
    zzzzzz
    As you can see upper case is before lower case, however I know I'm going to be told that they need to be like this:
    AAAAAA
    aaaaaa
    bbbbb
    ZZZZZZZ
    zzzzz
    Is there a way I can change / override how this sorts?
    Thank you,
    Kris

    So I think you are saying that I need to create my own wrapper class for String. Then override the compare and equal methods and return this class in my getters and setters?
    Or is there a way to tell the String class to use a different method for sort since it would be a global change?
    Thank you,
    Kris

  • XSLT sender plugin fails to set JMS message properties

    When creating a JMS message to be put on a JMS queue, one of the XSLT for the XSLT automation plugin fails to set JMS string properties like: wlsmimehdrContent_Type
    The content on the xslt are listed below.
    The xslt in CPRLookupRequest.xslt sets:
    wlsmimehdrContent_Type
    SERVICE_SUFFIX
    OSM_EVENT_TYPE
    as expected, but the almost similar plugin NABSCreditEvalPluginRequest.xsl fails to set the same string JMS properties.
    I'm looking for a clue, because I'm clueless. I'm an XSLT newbie, so it might be something simple.
    The core part of the problem is put in bold in the listings below
    h2. CPRLookupRequest.xslt:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" xmlns="http://java.sun.com/products/oss/xml/ServiceActivation" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:oms="urn:com:metasolv:oms:xmlapi:1" xmlns:java="http://xml.apache.org/xalan/java" xmlns:xalan="http://xml.apache.org/xalan" xmlns:mslv-sa="http://www.metasolv.com/oss/ServiceActivation/2003" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:co="http://java.sun.com/products/oss/xml/Common" exclude-result-prefixes="oms java xsl xalan">
         <xsl:param name="automator"/>
         <xsl:param name="log"/>
         <xsl:param name="context"/>
         <xsl:param name="outboundMessage"/>
         <xsl:output method="xml" indent="yes" omit-xml-declaration="no" xalan:indent-amount="5"/>
         <xsl:template match="/">
              <xsl:apply-templates select="oms:GetOrder.Response">
                   <xsl:with-param name="SERVICE_SUFFIX" select="'CprDomain/Cpr'"/>
                   <xsl:with-param name="OSM_EVENT_TYPE" select="'CPR_LOOKUP'"/>
              </xsl:apply-templates>
         </xsl:template>
         <xsl:template match="oms:GetOrder.Response">
              <xsl:param name="SERVICE_SUFFIX" />
              <xsl:param name="OSM_EVENT_TYPE" />
    *<xsl:variable name="void2" select="java:setStringProperty($outboundMessage, '_wls_mimehdrContent_Type', 'text/xml; charset=UTF-8')" />*
    *<xsl:variable name="void3" select="java:setStringProperty($outboundMessage, 'SERVICE_SUFFIX', $SERVICE_SUFFIX)" />*
    *<xsl:variable name="void4" select="java:setStringProperty($outboundMessage, 'OSM_EVENT_TYPE', $OSM_EVENT_TYPE)" />*
              <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                   <env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                        <m:getPersonByCPR xmlns:m="/Cpr">
                             <getPersonByCprRequestInfo xmlns:n1="java:dk.tdc.soa.cpr.extern.datatypes" xsi:type="n1:GetPersonByCprRequestInfo">
                                  <applicationId xsi:type="xsd:string"><xsl:text>CPR</xsl:text></applicationId>
                                  <cprNumber xsi:type="xsd:string"><xsl:value-of select="oms:_root/oms:cpr" /></cprNumber>
                             </getPersonByCprRequestInfo>
                        </m:getPersonByCPR>
                   </env:Body>
              </env:Envelope>
         </xsl:template>
    </xsl:stylesheet>
    h2. NABSCreditEvalPluginRequest.xsl
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" exclude-result-prefixes="oms java xsl xalan"
         xmlns="http://java.sun.com/products/oss/xml/ServiceActivation"
         xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
         xmlns:oms="urn:com:metasolv:oms:xmlapi:1"
         xmlns:java="http://xml.apache.org/xalan/java"
         xmlns:xalan="http://xml.apache.org/xalan"
         xmlns:mslv-sa="http://www.metasolv.com/oss/ServiceActivation/2003"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xmlns:co="http://java.sun.com/products/oss/xml/Common">
         <xsl:param name="automator"/>
         <xsl:param name="log"/>
         <xsl:param name="context"/>
         <xsl:param name="outboundMessage"/>
         <xsl:template match="/">
              <xsl:apply-templates select="oms:GetOrder.Response">
                   <xsl:with-param name="SERVICE_SUFFIX" select="'/APILink/CreditServices'"/>
                   <xsl:with-param name="OSM_EVENT_TYPE" select="'NABS_CREDIT_EVAL'"/>
              </xsl:apply-templates>
         </xsl:template>
         <xsl:template match="oms:GetOrder.Response">
              <xsl:param name="SERVICE_SUFFIX"/>
              <xsl:param name="OSM_EVENT_TYPE"/>
    *<xsl:variable name="void2" select="java:setStringProperty($outboundMessage, '_wls_mimehdrContent_Type', 'text/xml; charset=UTF-8')"/>*
    *<xsl:variable name="void3" select="java:setStringProperty($outboundMessage, 'SERVICE_SUFFIX', $SERVICE_SUFFIX)"/>*
    *<xsl:variable name="void4" select="java:setStringProperty($outboundMessage, 'OSM_EVENT_TYPE', $OSM_EVENT_TYPE)"/>*
              <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                   <env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                        <xsl:choose>
                             <xsl:when test="count(oms:_root/oms:cpr) + count(oms:_root/oms:birthDayPart) >0">
                                  <xsl:call-template name="private" />
                             </xsl:when>
                             <xsl:when test="count(oms:_root/oms:cvr) > 0">
                                  <xsl:call-template name="business" />
                             </xsl:when>
                        </xsl:choose>
                   </env:Body>
              </env:Envelope>
         </xsl:template>
         <xsl:template name="private">
              <m:validatePrivateCustomer xmlns:m="java:dk.tdc.apilink.logic.sessions.interfaces">
                   <validateCustomerCreditInput xsi:type="n1:ValidateCustomerCreditInput" xmlns:n1="java:dk.tdc.apilink.logic.datatypes">
                        <accountCategory xsi:type="java1:char" xmlns:java1="java:language_builtins">
                             <xsl:text>I</xsl:text>
                        </accountCategory>
                        <adrLocation xsi:type="xsd:string">
                             <xsl:value-of select="oms:_root/oms:houseNo"/>
                        </adrLocation>
                        <adrStreetName xsi:type="xsd:string">
                             <xsl:value-of select="oms:_root/oms:streetName"/>
                        </adrStreetName>
                        <adrZip xsi:type="xsd:string">
                             <xsl:value-of select="oms:_root/oms:zipCode"/>
                        </adrZip>
                        <xsl:choose>
                             <xsl:when test="count(oms:_root/oms:birthDayPart) > 0">
                                  <birthDate xsi:type="xsd:string">
                                       <xsl:value-of select="substring(oms:_root/oms:birthDayPart,1,4)"/><xsl:text>.</xsl:text>
                                       <xsl:value-of select="substring(oms:_root/oms:birthDayPart,5,2)"/><xsl:text>.</xsl:text>
                                       <xsl:value-of select="substring(oms:_root/oms:birthDayPart,7,2)"/>
                                  </birthDate>
                             </xsl:when>
                             <xsl:otherwise>
                                  <birthDate xsi:type="xsd:string">
                                       <xsl:text>19</xsl:text>
                                       <xsl:value-of select="substring(oms:_root/oms:cpr,5,2)"/><xsl:text>.</xsl:text>
                                       <xsl:value-of select="substring(oms:_root/oms:cpr,3,2)"/><xsl:text>.</xsl:text>
                                       <xsl:value-of select="substring(oms:_root/oms:cpr,1,2)"/>
                                  </birthDate>
                             </xsl:otherwise>
                        </xsl:choose>
                        <firstName xsi:type="xsd:string">
                             <xsl:value-of select="oms:_root/oms:firstName"/>
                        </firstName>
                        <lastBusinessName xsi:type="xsd:string">
                             <xsl:value-of select="oms:_root/oms:lastName"/>
                        </lastBusinessName>
                   </validateCustomerCreditInput>
              </m:validatePrivateCustomer>
         </xsl:template>
         <xsl:template name="business">
              <m:validateCompanyCustomer xmlns:m="java:dk.tdc.apilink.logic.sessions.interfaces">
                   <validateCustomerCreditInput xsi:type="n1:ValidateCustomerCreditInput" xmlns:n1="java:dk.tdc.apilink.logic.datatypes">
                        <accountCategory xsi:type="java1:char" xmlns:java1="java:language_builtins">
                             <xsl:text>B</xsl:text>
                        </accountCategory>
                        <cvrNumber xsi:type="xsd:string">
                             <xsl:value-of select="oms:_root/oms:cvr"/>
                        </cvrNumber>
                   </validateCustomerCreditInput>
              </m:validateCompanyCustomer>
         </xsl:template>
    </xsl:stylesheet>

    I have written an UDF to determine the filename dynamicly:
    //write your code here
    String str = "SAPDATA-" + a + "ES" + ".xml";
    DynamicConfiguration conf = (DynamicConfiguration)
    container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey FileName = DynamicConfigurationKey.create("http:/"+"/sap.com/xi/XI/System/File","FileName");
    conf.put(FileName, str);
    return "";

  • Message properties and performance

              Hi
              Our application uses BytesMessage - but we add some userdefined properties in
              the message header area- all string properties. The number of properties that
              we add is around 5-6 and am trying my best to reduce that somehow. Wondering whether
              the number of proerties would matter or is it like black or white? Also if I end
              up with a screwed up design just to reduce 1 or 2 properties out of 5/6 - id it
              really worth it? Also wondering if there is any way that an MDB instance knows
              which Queue the message came from if the message itself does not contain any user
              defined property like "queuename" put by the producer.
              thanks
              Anamitra
              

    One more thing to consider outside of performance
              - message header and property fields do not get paged out.
              This becomes a factor when there
              are a large number of messages on the server
              and at the same time message properties are
              fairly large in comparison to message header information.
              Tom Barnes wrote:
              > Hi,
              >
              > Anamitra wrote:
              >
              >> Hi
              >> Our application uses BytesMessage - but we add some userdefined
              >> properties in
              >> the message header area- all string properties. The number of
              >> properties that
              >> we add is around 5-6 and am trying my best to reduce that somehow.
              >> Wondering whether
              >> the number of proerties would matter or is it like black or white?
              >> Also if I end
              >> up with a screwed up design just to reduce 1 or 2 properties out of
              >> 5/6 - id it
              >> really worth it?
              >
              >
              > Likely not worth it.
              >
              > Its not the number Strings so much as the size of
              > the Strings that matters.
              >
              > The perf gain is likely not measurable except
              > for high throughput non-persistent messaging (rates
              > of 1000 msgs/sec higher) with "small" (few hundred
              > byte) message bodies and Strings greater than 25
              > characters in length. Of course, these are
              > very rough estimates - say plus/minus 75%, with
              > measured perf gains at 5% or more.
              >
              >> Also wondering if there is any way that an MDB instance knows
              >> which Queue the message came from if the message itself does not
              >> contain any user
              >> defined property like "queuename" put by the producer.
              >
              >
              > javax.jms.Destination dest = ((javax.jms.Message)msg).getJMSDestination();
              >
              > // get JMX mbean name of destination
              > String name =
              > ((javax.jms.Queue)dest_.getName();
              >
              >
              >>
              >> thanks
              >> Anamitra
              >
              >
              

  • Problem trying to use replaceAll with url string

    Can anyone give me some quick advice on how to replace part of a url? I'm trying replaceAll but I'm getting errors. My code is below. Thanks.
    String value = http://localhost:8280/portal/templates/page/library.jsp?foldId=libfold245696
    String hostName = "192.168.0.1";
    value = value.replaceAll("localhost",hostName);I want to replace "localhost" with the ip address.

    Here's the replaceAll version:
    package com.cellexchange.util;
    import java.io.FileInputStream;
    import java.io.FileOutputStream;
    import java.io.IOException;
    import java.io.OutputStream;
    import java.io.PrintWriter;
    import java.util.Enumeration;
    import java.util.Properties;
    * Created on Nov 3, 2005
    public class UpdateExternalLinks {
        private String hostName;
        private String fileName = "/server/fvm/conf/ExternalLinks.properties";
        private static final String pattern = "localhost";
        private Properties properties;
        public UpdateExternalLinks(String hostName,String jBossHome){
            hostName = hostName;
            System.out.println("hostName: " + hostName);
            fileName = jBossHome + fileName;
            readPropertiesFile();
        public static void main(String[] args) {
            if(args.length == 0) {
                System.err.println("Usage: UpdateExternalLinks %HOST_NAME% %JBOSS_HOME%");
                System.exit(1);
            else {
                new UpdateExternalLinks(args[0],args[1]);
        public void readPropertiesFile() {
            try {
                properties = new Properties();
                properties.load(new FileInputStream(fileName));
                Enumeration propertyNames = properties.propertyNames();
                while(propertyNames.hasMoreElements()) {
                    String key = (String)propertyNames.nextElement();
                    String value = (String)properties.getProperty(key);
                    System.out.println("key: " + key);
                    System.out.println("value: " + value);
                    String newValue = value.replaceAll(pattern,hostName);
                    System.out.println("newValue: " + newValue);
                    //properties.setProperty(key,newValue);
               // writePropertiesFile(properties);
            } catch (IOException e) {
                System.err.println("Problem reading properties file");
        public void writePropertiesFile(Properties properties) {
            try {
                properties.store(new FileOutputStream(fileName), null);
            } catch (IOException e) {
                System.err.println("Problem writing properties file");
    }

  • How get event properties value from ocep egine and display in java .

    Hi,
    can please paste a code for that.

    Not quite understand your question. If you want to check the properties in an event type, you can use visualizer to see them easily.
    And if you want to check it in java code, no matter the event is defined with java class or tuple, you can use EventTypeRepository class to get these information.
    import com.bea.wlevs.ede.api.EventTypeRepository;
    import com.bea.wlevs.ede.api.EventType;
    import com.bea.wlevs.util.Service;
    @Service
    public void setEtr(EventTypeRepository etr){};
    public void dumpEvent(String eventType) {
    EventType type = etr.getEventType(eventType);
    String[] properties = type.getPropertyNames();
    }

  • Can I Link BOM Node System Properties to Basic Nodes?

    Configurator Developer R12
    Currently, we utilize basic nodes in the UI that represent the actual BOM nodes which are not displayed in the UI; however, there is a system property, specifically List Price, that is tied to the BOM node that must be visible in the UI next to the appropriate option.
    This is currently being handled as a separate cell element in the UI that is manually tied to a specific option, but this method is very manual as it is outside of a Node List Layout Region.
    I would like to be able to "link" this system property somehow to the basic node so that I can simply point to the property from the basic node rather than create a row for each option that is linked to the BOM node for just this property. Is there a standard way of "linking" these two node types? Anyone have any experience with this type of need?
    Thanks,
    Paul

    Paul --
    Good to know that your desired end state eliminates the dummy Options and uses Properties (whether maintained in Configurator Developer or imported from Inventory Catalog Group Descriptive Elements) to deal with the display captions. This would definitely be the preferred solution, and only if there is a compelling reason why it is not feasible should the scheme I'm about to outline be considered.
    The best way to implement a List Price "linking" mechanism is by leveraging User String Properties. Think of these as dynamic Properties, whose values can be set by a Configurator Extension at runtime. (They're documented in the "User String Properties" section of Chapter 6 of the Oracle Configurator Extensions and Interface Object Developer's Guide.) Your CX would iterate through your Option Class(es), and for each Item it would set a User String Property (UserStr01, for example) on the corresponding Option to the Item's List Price. The UI Content Template used for displaying the Option Feature would then be enhanced to display the UserStr01 value along with the name of each Option.
    To be as reusable and as generic as possible, you want your CX to have as little in the way of hardcoded values as possible. As such, you want to handle the mapping of Items to their corresponding Options via your Model Structure, Properties in particular, and not via hardcoded mappings in your CX code. You'll want to define a Property ("Corresponding Guided-Selling Node", for example) on each Option Class that identifies its corresponding Option Feature, and on each Item that identifies its corresponding Option within the Option Feature. In doing so, you eliminate the need to modify your CX whenever changes are made to your BOM. The CX can operate over all the Option Classes on which it finds the Property defined, so if a new Option Class is added it will automatically get picked up, and a new Item added to an existing Option Class will work as long as the Property is defined on it and a corresponding Option is created for it.
    Hope this helps, let me know if you have any questions or concerns about it.
    Eogan

  • Read out properties generated by XLF files

    Dear community,
    I have a problem reading out property files generated by Web Dynpros XLS (S2X-Editor). What I have to do is generate a printer-friendly version  of my Web Dynpro views to enable users to get a printable report.
    Now my problem is reading out the property-files generated by Web Dynpro with a java utility class.
    I think my attempt fails, because those property files for each view follow a naming convertion, which is like this:
    com.mypackage.mysubpackage.MyViewName.wdview_<Locale>.properties
    so when I try to access those property files with a call like
          Locale sessionLocale = WDResourceHandler.getCurrentSessionLocale();
          ResourceBundle resourceHandler = ResourceBundle.getBundle("com.mypackage.mysubpackage.MyViewName.wdview",sessionLocale);
    I guess the resourceHandler thinks "wdview" is the name of my resource and tries to resolve this name to a propery file such as wdview_de.properties.
    Am I missing something? Did anyone experience a similar behaviour or knows a working work-around?
    My SAP-solution would be to duplicate code (...) which is no fun and a real pain when application texts are changed on later development stages...
    Thanks for your support!
    regards,
    Christian

    Hi,
    found the solution myself, so here is my insight:
    The view-specific property-files generated by the XLF-files can not be accessed by Java as the  ResourceBundle.getBundle(...) method replaces all dots in the name of the Resource file according to this:
    It generates a path name from the candidate bundle name by replacing all "." characters with "/" and appending the string ".properties".
    (see SUN Java API docs [ResourceBundle|http://java.sun.com/j2se/1.4.2/docs/api/java/util/ResourceBundle.html])
    Thing is the generated property-files of the views get merged into property files for the component. So if your component sports 12 views with one xlf-  and property-file each, there is gonna be one big property-file for the whole component, that resides in your wdp folder.
    Accessing this file is pretty straight-forward, the naming is like "Resource" + <Name of Component> +".properties".
    Maybe someone else struggles with WDJ and needs this.
    regards,
    Christian
    Edited by: Christian Henn on Jan 17, 2008 6:01 PM
    Edited by: Christian Henn on Jan 18, 2008 11:06 AM

  • SetProperty with indexed properties

    I think the way I want to automagically set an arbitrary number of properties might be different than the way setProperty is typically used with indexed properties as discussed here:
    http://java.sun.com/products/jsp/tags/syntaxref.fm13.html#17460
    For example, say I have many text inputs in my HTML that are each named something like Description. I want the form POST to auto-set an array of Strings in the bean by letting <jsp:setProperty> call public setDescription(String [ ] s) in the bean. From what I've read at the link above, it almost seems like you can't use this with String properties (that they have to be scalars instead).
    If you can use this with Strings, then how do I name the arbitrary number of Description fields in the HTML form so that <jsp:setProperty> knows how to find them and set them properly? Is there a convention like Description#0, Description#1, etc?
    Thanks...

    make sure your class has a setter that accepts a String[]..
    public void setDescription(String[] values) { this.description = values; }
    public String[] getDescription() { return this.description; }and in your form you name all the fields that correspond to this value the same ie:
    <input type=text name=description>
    <input type=checkbox name=description value=one>
    <input type=checkbox name=description value=two>and then use a
    <jsp:setProperty name="myBean" property="*" />the key is that all your fields are named the same (ie 'description'). I don't believe you have any control over the order of the properties as the protocol allows parameters to be sent in arbitrary order.

  • [C4005]: Get properties from packet failed killing my sessions

    I have a broker in a state where 6 messages are delivered which "kill" the first 6 sessions listening on a particular queue (round-robin delivery sorta situation)
    These exceptions are logged only to stderr and no indication is given to my program about them other than the affected sessions never receive another message again, others do.
    When the broker or consumer service is restarted, it happens again.
    If I start the broker with a -reset messages then the problem goes away. I saved the entire broker var folder to try to find a work around to this.
    This is OpenMQ 4.5B29
    I'll include the stack traces below, anyone seen something like this or have suggestions on how to deal with this without resorting to reset of the broker?
    Could not parse properties java.io.UTFDataFormatException: malformed input around byte 11
    Mar 22, 2011 3:42:55 PM com.sun.messaging.jmq.jmsclient.ExceptionHandler logCaughtException
    WARNING: [I500]: Caught JVM Exception: java.lang.NullPointerException
    java.io.UTFDataFormatException: malformed input around byte 11
         at java.io.DataInputStream.readUTF(Unknown Source)
         at java.io.DataInputStream.readUTF(Unknown Source)
         at com.sun.messaging.jmq.io.PacketProperties.parseProperties(PacketProperties.java:178)
         at com.sun.messaging.jmq.io.PacketPayload.getProperties(PacketPayload.java:155)
         at com.sun.messaging.jmq.io.Packet.getProperties(Packet.java:644)
         at com.sun.messaging.jmq.io.ReadOnlyPacket.getProperties(ReadOnlyPacket.java:348)
         at com.sun.messaging.jmq.jmsclient.MessageImpl.getPropertiesFromPacket(MessageImpl.java:601)
         at com.sun.messaging.jmq.jmsclient.ProtocolHandler.getJMSMessage(ProtocolHandler.java:2061)
         at com.sun.messaging.jmq.jmsclient.SessionReader.getJMSMessage(SessionReader.java:189)
         at com.sun.messaging.jmq.jmsclient.SessionReader.deliver(SessionReader.java:107)
         at com.sun.messaging.jmq.jmsclient.ConsumerReader.run(ConsumerReader.java:192)
         at java.lang.Thread.run(Unknown Source)
    Mar 22, 2011 3:42:55 PM com.sun.messaging.jmq.jmsclient.ConsumerReader run
    WARNING: [C4005]: Get properties from packet failed. - cause: java.lang.NullPointerException
    com.sun.messaging.jms.JMSException: [C4005]: Get properties from packet failed. - cause: java.lang.NullPointerException
         at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSException(ExceptionHandler.java:386)
         at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleException(ExceptionHandler.java:337)
         at com.sun.messaging.jmq.jmsclient.MessageImpl.getPropertiesFromPacket(MessageImpl.java:604)
         at com.sun.messaging.jmq.jmsclient.ProtocolHandler.getJMSMessage(ProtocolHandler.java:2061)
         at com.sun.messaging.jmq.jmsclient.SessionReader.getJMSMessage(SessionReader.java:189)
         at com.sun.messaging.jmq.jmsclient.SessionReader.deliver(SessionReader.java:107)
         at com.sun.messaging.jmq.jmsclient.ConsumerReader.run(ConsumerReader.java:192)
         at java.lang.Thread.run(Unknown Source)
    Caused by: java.lang.NullPointerException
         at java.util.Hashtable.put(Unknown Source)
         at com.sun.messaging.jmq.io.PacketProperties.parseProperties(PacketProperties.java:193)
         at com.sun.messaging.jmq.io.PacketPayload.getProperties(PacketPayload.java:155)
         at com.sun.messaging.jmq.io.Packet.getProperties(Packet.java:644)
         at com.sun.messaging.jmq.io.ReadOnlyPacket.getProperties(ReadOnlyPacket.java:348)
         at com.sun.messaging.jmq.jmsclient.MessageImpl.getPropertiesFromPacket(MessageImpl.java:601)
         ... 5 more
    Mar 22, 2011 3:42:55 PM com.sun.messaging.jmq.jmsclient.ExceptionHandler logCaughtException
    WARNING: [I500]: Caught JVM Exception: java.io.UTFDataFormatException: malformed input around byte 11
    Mar 22, 2011 3:42:55 PM com.sun.messaging.jmq.jmsclient.ConsumerReader run
    WARNING: [C4005]: Get properties from packet failed. - cause: java.io.UTFDataFormatException: malformed input around byte 11
    com.sun.messaging.jms.JMSException: [C4005]: Get properties from packet failed. - cause: java.io.UTFDataFormatException: malformed input around byte 11
         at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSException(ExceptionHandler.java:386)
         at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleException(ExceptionHandler.java:337)
         at com.sun.messaging.jmq.jmsclient.MessageImpl.getPropertiesFromPacket(MessageImpl.java:604)
         at com.sun.messaging.jmq.jmsclient.ProtocolHandler.getJMSMessage(ProtocolHandler.java:2061)
         at com.sun.messaging.jmq.jmsclient.SessionReader.getJMSMessage(SessionReader.java:189)
         at com.sun.messaging.jmq.jmsclient.SessionReader.deliver(SessionReader.java:107)
         at com.sun.messaging.jmq.jmsclient.ConsumerReader.run(ConsumerReader.java:192)
         at java.lang.Thread.run(Unknown Source)
    Caused by: java.io.UTFDataFormatException: malformed input around byte 11
         at java.io.DataInputStream.readUTF(Unknown Source)
         at java.io.DataInputStream.readUTF(Unknown Source)
         at com.sun.messaging.jmq.io.PacketProperties.parseProperties(PacketProperties.java:178)
         at com.sun.messaging.jmq.io.PacketPayload.getProperties(PacketPayload.java:155)
         at com.sun.messaging.jmq.io.Packet.getProperties(Packet.java:644)
         at com.sun.messaging.jmq.io.ReadOnlyPacket.getProperties(ReadOnlyPacket.java:348)
         at com.sun.messaging.jmq.jmsclient.MessageImpl.getPropertiesFromPacket(MessageImpl.java:601)
         ... 5 more
    Mar 22, 2011 3:42:55 PM com.sun.messaging.jmq.jmsclient.ExceptionHandler logCaughtException
    WARNING: [I500]: Caught JVM Exception: java.lang.NullPointerException
    Mar 22, 2011 3:42:55 PM com.sun.messaging.jmq.jmsclient.ExceptionHandler logCaughtException
    WARNING: [I500]: Caught JVM Exception: java.io.StreamCorruptedException: invalid type code: 00
    Mar 22, 2011 3:42:55 PM com.sun.messaging.jmq.jmsclient.ConsumerReader run
    WARNING: [C4005]: Get properties from packet failed. - cause: java.lang.NullPointerException
    com.sun.messaging.jms.JMSException: [C4005]: Get properties from packet failed. - cause: java.lang.NullPointerException
         at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSException(ExceptionHandler.java:386)
         at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleException(ExceptionHandler.java:337)
         at com.sun.messaging.jmq.jmsclient.MessageImpl.getPropertiesFromPacket(MessageImpl.java:604)
         at com.sun.messaging.jmq.jmsclient.ProtocolHandler.getJMSMessage(ProtocolHandler.java:2061)
         at com.sun.messaging.jmq.jmsclient.SessionReader.getJMSMessage(SessionReader.java:189)
         at com.sun.messaging.jmq.jmsclient.SessionReader.deliver(SessionReader.java:107)
         at com.sun.messaging.jmq.jmsclient.ConsumerReader.run(ConsumerReader.java:192)
         at java.lang.Thread.run(Unknown Source)
    Caused by: java.lang.NullPointerException
         at java.util.Hashtable.put(Unknown Source)
         at com.sun.messaging.jmq.io.PacketProperties.parseProperties(PacketProperties.java:193)
         at com.sun.messaging.jmq.io.PacketPayload.getProperties(PacketPayload.java:155)
         at com.sun.messaging.jmq.io.Packet.getProperties(Packet.java:644)
         at com.sun.messaging.jmq.io.ReadOnlyPacket.getProperties(ReadOnlyPacket.java:348)
         at com.sun.messaging.jmq.jmsclient.MessageImpl.getPropertiesFromPacket(MessageImpl.java:601)
         ... 5 more

    From the stack trace, it looks like there is a problem with one of message's string properties. I can't obviously see what, but this might help you track down the cause of the problem.
    When you've found out what it is about your message that's causing this exception, please log this as a bug.
    Nigel

  • Reading properties in kodo.rar

    Hi guys,
    There seems to be a stalemate between Kodo and JBoss on reading properties of type Boolean or
    Integer. I haven't been able to configure Optimistic, RetainValues, etc. using either
    kodo-service.xml or ra.xml. The issue as Marc has explained it to all the world is that JBoss won't
    read properties other than String properties. They should fix this, but they have lot of other
    chickens to fry. In the meantime, wouldn't it be fairly easy for Kodo to provide a workaround?
    Provide overloaded String methods for each of the property methods that take int and boolean? Then
    the property could be set as a string. The JCA rar approach to deploying Kodo in JBoss or any EJB
    container is just too nice to allow it to slip from your grip, in my opinion.
    David Ezzio

    emmm ... however .. it is my bug :) ...
    it does work ... however in another place process of reading proeprty goes through SystemResource...

  • Connect to a cube with Integrated WIndows Sercurity for Windows user with computer outside the domain

    Hello,I am trying to connect to an MSSAS cube with a windows user ( and i need this user to be the end user that connect to the cube) from outside the domain.It will be .Net application.I use msmdpump.dll before but the thing is it impersonate the connection
    so the user that connect to the Cube is not the real client user with is a problem for me because i like to manage the security throw roles.
    SSRS is able to do what i am trying to achieve ( it ask you your domain user and password) then connect to the cube with these credential which is great,but i do that ?
    With ADOMD.Net how do you provide windows user/password in the connection string ?
    I tryed to only active windows security access with IIS and MSSAS but it's not working with a computer outside the domain even if in excel i provide a windows user/password.
    Vincent

    With ADOMD.Net how do you provide windows user/password in the connection string ?
    Hello Vincent,
    See MSDN Connection String Properties (Analysis Services) for all available properties; addtitional: AdomdConnection.ConnectionString
    Property  =>
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • Updating UDFs in the UDF form of a sales order

    I got the UDF form of a corresponding main sales order form.
    I am trying to set a value for one of the UDFs there, but I get a 'General Failure' exception (Simply trying to set the edittext's UDFItem.Value or UDFItem.String properties)
    I know I have the right form and item, since I can change the item's BackColor.
    The DBDataSource.GetValue works, so I can read the existing values.
    The DBDataSource.SetValue doesn't work, but I'm used to it
    Any ideas?

    Avi,
        We cant use Setvalue directly in Predefined for u better to use
    Frm.items.item("").Specific.Value= ""
    Regards,
    Anitha

Maybe you are looking for